Software Testing Communication & Stakeholder Relations 2

Question 1

A product owner keeps changing requirements mid-sprint. What is the BEST approach for the QA lead to handle this?

Accepted Answer

Document all changes and assess their impact on existing test cases before proceeding

Answer

Documenting changes and assessing impact ensures informed decision-making before modifying test artifacts.

Question 2

Which communication style is MOST effective when delivering a defect report to a non-technical business stakeholder?

Accepted Answer

Focus on business impact, risk, and user experience rather than technical details

Answer

Non-technical stakeholders respond best to information framed in terms of business risk and user impact.

Question 3

A developer disputes a bug report, claiming the behavior is 'by design.' What should the tester do FIRST?

Accepted Answer

Re-check the requirement specification and provide evidence linking the defect to documented expectations

Answer

Referencing the specification provides objective evidence to resolve the dispute professionally.

Question 4

What is the PRIMARY purpose of a test summary report shared with stakeholders at project end?

Accepted Answer

To provide an objective overview of testing activities, coverage, results, and outstanding risks

Answer

The test summary report gives stakeholders a transparent view of quality status and remaining risks.

Question 5

During a sprint review, a stakeholder says 'I thought this feature was already tested.' How should the QA engineer respond?

Accepted Answer

Explain what was tested, what was not, and why, referencing the agreed test scope

Answer

Transparent communication about scope boundaries helps stakeholders understand what testing was actually contracted.

Software Testing Practice Test