How should you approach incident response during testing?

• A. Detect, document, escalate, coordinate with teams, and implement mitigations or workarounds.
• B. Ignore incidents during testing.
• C. Only log incidents after release.
• D. Blame developers.

Answer: (D)

Incident response during testing should be proactive and structured: detect issues early, document what happened, escalate to the right people, coordinate with relevant teams, and implement mitigations or workarounds to keep testing moving while those risks are addressed. This approach ensures that problems are understood and contained rather than ignored, so tests can proceed without exposing the system to unnecessary danger. Documenting incidents creates a clear record for later root-cause analysis and improvement, while escalation brings in the right expertise from security, operations, development, and QA to respond quickly. Coordinating with these teams prevents duplicate efforts and confusion, and applying mitigations or workarounds reduces risk to the environment and maintains the integrity of the testing process. Approaches that ignore incidents, delay logging until after release, or assign blame erode safety, transparency, and collaboration, making it harder to learn from issues and improve the system.