Testers are frequently in disagreements with developers over the validity of a defect. Developers defend their code and understanding of business knowledge. In some organizations, the skill level of developers is measured by the lesser number of defects found in their code.
And this starts the disagreements like the following -
1. This is not a defect. This was not a requirement to begin with.
2. This is not a defect. This is not what the requirement says.
3. This is not a defect. This is a design change. This cannot be accomplished in the given amount of time.
4. Why is the severity of this defect Major? This defect does not stop any processing.
5. This is existing functionality. It has always been like this.
It is quite human that we defend our hard work and what we think is right. And a developer has a technical or a coding angle from which he analyzes the quality of his work. In the real business world, he has a lot of potential to miss a requirement or the accuracy of a requirement. That is why they say - Developers cannot be good testers.
Hence, a lesson is learnt. If there is a disagreement between the tester and the developer, we should have a proper process in place.
- Consult the business analyst and get his opinion.
- If there is still a disagreement, consult business. The word of business should be considered final.
No comments:
Post a Comment