Software Testing Communication & Stakeholder Relations 3

Question 1

A stakeholder pressures the QA team to sign off on a release despite 3 open critical defects. What is the tester's BEST course of action?

Accepted Answer

Document the open defects, communicate the associated risks clearly, and let stakeholders make an informed decision

Answer

Testers provide risk information; the release decision ultimately belongs to business stakeholders who must understand the consequences.

Question 2

What does 'managing stakeholder expectations' primarily mean in a testing context?

Accepted Answer

Communicating realistic timelines, coverage limitations, and quality risks proactively and consistently

Answer

Proactive and honest communication prevents misunderstandings about what testing can and cannot guarantee.

Question 3

When should a tester escalate a defect directly to the project manager rather than the development lead?

Accepted Answer

When a critical defect has been ignored or deprioritized by the developer for an unacceptable period of time

Answer

Escalation is appropriate when normal resolution channels have failed and business impact is at risk.

Question 4

A tester notices that two stakeholders have contradictory requirements for the same feature. What is the CORRECT action?

Accepted Answer

Raise the conflict as a formal ambiguity and request clarification before writing test cases

Answer

Unresolved requirement conflicts lead to wasted test effort and potential defect disputes; formal clarification is essential.

Question 5

Which of the following BEST describes active listening during a requirements walkthrough?

Accepted Answer

Paraphrasing stakeholder statements, asking clarifying questions, and taking structured notes

Answer

Active listening involves engagement through paraphrasing and questioning to ensure accurate understanding.

Software Testing Practice Test