Software Testing Communication & Stakeholder Relations 4

Question 1

A senior stakeholder asks for a 'quick gut check' on whether the system is ready to ship. What should the QA lead base their answer on?

Accepted Answer

Objective data: test execution rates, open defect counts by severity, and risk coverage metrics

Answer

Quality assessments must be grounded in measurable data to be credible and defensible.

Question 2

Which of the following represents a communication ANTI-PATTERN in software testing?

Accepted Answer

Sending raw, unfiltered defect lists directly to executive sponsors

Answer

Sending unfiltered defect lists to executives creates confusion and alarm without context or prioritization.

Question 3

What is the BEST way to communicate a test plan to a new stakeholder who has no testing background?

Accepted Answer

Present a one-page executive summary highlighting scope, risks, timeline, and success criteria

Answer

A concise executive summary communicates the most critical information in a format accessible to non-technical readers.

Question 4

During UAT, a business user reports a 'bug' that is actually a user training gap, not a defect. What should the tester communicate?

Accepted Answer

Acknowledge the user's concern, explain the intended behavior with reference to documentation, and suggest training as a resolution

Answer

Distinguishing training gaps from defects protects the product baseline while addressing the user's underlying need.

Question 5

What role does a test exit criteria document play in stakeholder communication?

Accepted Answer

It defines measurable conditions that both testers and stakeholders agree must be met before release is approved

Answer

Exit criteria establish a shared, pre-agreed definition of 'done' that prevents subjective release debates.

Software Testing Practice Test