The Art of Software Testing Relies On…
Several critical truths. One of these is, “A bug not reported will never get fixed.”
The corollary of this according to Schroedinger-Murphy is, “This bug will return to bite you in the * at the worst possible time.”
Never Has There Been A Tale Of More Woe…
(Poetic license and changes of name and gender have been used to protect the innocent in this story)
Once upon a time, Bob the tester was working on a testing project with a new feature. Bob was testing this feature which relied on a 3rd party backend service and another 3rd party client plugin.
Bob had tested a prior version and declared the feature as working but in the latest version he found bugs with UI and function.
His manager, Jim got involved after he heard Bob explain to the Developer the problems and the Dev and their manager said, “This is an issue with the 3rd party integrations. We can’t do anything.”
Jim asked Bob one question, “Are the issues documented in our Bug Tracking?”
Bob shook his head and could see Jim was not pleased.
Image screen captured from Youtube clip from Star Trek 3: The Wrath of Khan
“Bob. I must have said this a hundred times. Dev doesn’t decide if a bug gets reported, bug reporting means all bugs with the appropriate severity, Bob.”
Bob went back to his computer and was about to document the bugs when he said, “Hey Jim should these bugs all be reported as one bug?”
Jim came over and sat down with Bob, drained his coffee and said, “If they are all facets or symptoms of the same bug then maybe but ask yourself this Bob. If a Developer marks the bug fixed and you have multiple issues in there, how do you know which are fixed? More to the point, if some of these issues aren’t fixed what status does the bug acquire?”
Bob thought about it for a few seconds, grinned and told Jim he was going to open a bug for each. Jim slapped him on the back and went back to his desk.
The Warptest POV
Software Testing and Bug Reporting is somewhere between an art and a science. It is rule based and if you don’t want to cock-up, these fundamental rules need following.
What happens after you document bugs you discover and allocate the right priority is the next step in delivering a robust, sellable product that makes happy customers.
So as you sit down with your coffee to test the latest deliverable, make sure you are sharing information with good bug reporting.