Communication & Stakeholder Relations Flashcards
7 cards from real Software Testing practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Communication & Stakeholder Relations flashcards as text
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?
Answer: Objective data: test execution rates, open defect counts by severity, and risk coverage metrics
Quality assessments must be grounded in measurable data to be credible and defensible.
Which of the following represents a communication ANTI-PATTERN in software testing?
Answer: Sending raw, unfiltered defect lists directly to executive sponsors
Sending unfiltered defect lists to executives creates confusion and alarm without context or prioritization.
What is the BEST way to communicate a test plan to a new stakeholder who has no testing background?
Answer: Present a one-page executive summary highlighting scope, risks, timeline, and success criteria
A concise executive summary communicates the most critical information in a format accessible to non-technical readers.
During UAT, a business user reports a 'bug' that is actually a user training gap, not a defect. What should the tester communicate?
Answer: Acknowledge the user's concern, explain the intended behavior with reference to documentation, and suggest training as a resolution
Distinguishing training gaps from defects protects the product baseline while addressing the user's underlying need.
What role does a test exit criteria document play in stakeholder communication?
Answer: It defines measurable conditions that both testers and stakeholders agree must be met before release is approved
Exit criteria establish a shared, pre-agreed definition of 'done' that prevents subjective release debates.
A stakeholder from the marketing team requests an unrealistic go-live date that would cut the testing phase in half. What should the QA lead do?
Answer: Present a risk-based analysis showing what testing can be completed in the reduced timeframe and what risks remain untested
A risk-based counteroffer gives stakeholders the information they need to make an informed schedule decision.
When is it appropriate to use informal communication channels (e.g., instant messaging) for bug reporting?
Answer: For quick preliminary flagging of potential issues before logging a formal defect report
Informal channels can serve as a quick heads-up, but formal defect tracking must always follow to ensure traceability.