QA Fundamentals · Senior · Question 8 of 76
How should a team decide what NOT to test?
- 1By explicit risk assessment, documenting accepted risks
- 2By skipping whatever the testers find boring
- 3By testing only what developers ask to be tested
Show the answer
Correct answer: By explicit risk assessment, documenting accepted risks
Explanation
Testing everything is impossible, so leaving areas out is normal. Making it explicit ('admin export: smoke only, low usage') lets stakeholders accept or challenge the risk.