Part 7 "Test Process & Incident Management" As a technical test analyst, you have found out during test case design that the design document is incomplete. Which is an example of a good way to…

Question

Options

• AE-mail: "Until I have received an updated version of the design document, I will not do any work
• BE-mail: "When will it be possible to receive the missing information? Test design is impeded by a
• CE-mail: "Here we go again. The developer gave us incomplete and ambiguous design
• DDo not communicate the problem, just log the delaying effect of the information problem and be

• A
  5% (1)
• B
  90% (18)
• C
  5% (1)

Explanation

Option B is correct because it communicates the problem professionally and constructively - it identifies the impact ("test design is impeded"), asks a specific actionable question about timing, and maintains a collaborative tone without assigning blame or making threats.

• A is wrong because issuing an ultimatum ("I will not do any work") is unprofessional, obstructive, and damages team relationships - it's a threat, not a problem report.
• C is wrong because "Here we go again" is emotionally charged and accusatory; blaming the developer in writing is unprofessional and escalates conflict unnecessarily.
• D is wrong because not communicating a blocking issue violates the core principle that defects and impediments must be reported - silently logging the delay hides a problem that stakeholders need to act on.

Memory tip: Think "B = Business-like." Good incident communication in testing follows the pattern: state the impact + ask for resolution + stay neutral. If the email sounds like something from a complaint letter or a passive-aggressive note, it's wrong.

No community discussion yet for this question.