Multiple choice technology testing

If you think a piece of code should work one way, and the developer says it should work another way, what would you do to resolve the conflict?

  1. If there is a discrepancy in code then the best approach is to check the use case documents for functionality. If the functionality is misunderstood by the tester then he will not raise a bug and to make things clear he can involve the project manager.

  2. If there is a discrepancy in code then the best approach is to check the use case documents for bugs. If the functionality is misunderstood by the tester then he will not raise a bug and to make things clear he can involve the project manager.

  3. If there is a discrepancy in code then the best approach is to check the requirement documents for functionality. If the functionality is misunderstood by the tester then he will not raise a bug and to make things clear he can involve the business analyst

  4. If there is a discrepancy in code then the best approach is to check the requirement documents for functionality. If the functionality is misunderstood by the tester then he will not raise a bug and to make things clear he can involve the QA lead.
Reveal answer Fill a bubble to check yourself
C Correct answer
Explanation

When there's a disagreement about expected functionality, the requirements documents are the authoritative source. If uncertainty remains after checking requirements, the business analyst is the right person to consult as they own the requirement definition. Options A and B incorrectly mention use case documents instead of requirements, and option D involves the QA lead who doesn't own requirements.

Keep practicing — related questions