You are here

Partner track: Why It Is Important to Fix Non-Specification Bugs?

Most of the time we spend on testing is making sure that the software product is working as specified in the requirement documentation. The tester bases his testing using the documentation and together with experience and common sense. Sometimes we can log bugs which are conflicting with our common-sense interpretation of how things should work. This type of issues leads to skewed or outright wrong first impressions. How important is your first impression really?

This speech can accent on what problems manual tester face during their work (those testers who do not see the code itself).  How do we react, if we see something that is not normal based on our understanding or point of view.

If we will think that human being has the code inside (written by mother nature). Code that explains how should the heart beat or how blood is cycling through your body. Tester does not see this code, he sees only the result of code execution.  And the result  is your appearance and your fully working body. Here we come to the place, where tester sees how do you look like, your outfit, your hair condition, your face etc.

Let’s take an example. Your hair shampoo has in the instructions,  that you need to wash your hair every two days. And you do it. The “loop condition” cycle as described in the manual, but your hair looks slightly dirty every day. Tester will see this and judge your hair condition. Tester will think, that you can wash your head more often just because you have a different type of hair. Should we blame the tester for that judgement that it was based on his common sense, but not the manual itself, or should we ensure that non-specification issues should be logged and treated the same way as issues logged based on technical documentation?