4.5The QA Engineer's Role During Incidents

QA engineers bring specific skills to incident response that other roles do not.

During the Incident

Activity	Why QA Is Uniquely Suited
Reproduction	QA knows how to systematically reproduce issues, isolate variables, and document exact steps
Scope assessment	QA can quickly determine which features and user flows are affected by testing adjacent functionality
Fix verification	QA can verify the fix works and does not introduce regressions, in staging and then in production
Evidence collection	QA is trained to capture screenshots, logs, network traces, and other evidence

After the Incident

Activity	Why QA Is Uniquely Suited
Regression testing	Verify that the fix holds and no regressions were introduced
Test gap analysis	Identify what tests should have caught this and add them
Monitoring setup	Define what to monitor to detect similar issues early
RCA contribution	Provide the testing perspective: why did existing tests miss this?
Checklist updates	Update deployment verification checklists based on what was learned

QA's Incident Response Checklist

## QA Incident Response

### Immediate (during incident)
- [ ] Join the war room
- [ ] Reproduce the issue and document exact reproduction steps
- [ ] Assess scope: what features are affected beyond the reported issue?
- [ ] When a fix is ready, verify in staging before production deployment
- [ ] Verify the fix in production after deployment
- [ ] Run smoke tests on adjacent functionality

### Short-term (24-48 hours)
- [ ] Run full regression suite against production
- [ ] Write test cases that would have caught this issue
- [ ] Review and update deployment verification checklist
- [ ] Contribute to the incident report with testing perspective

### Medium-term (1-2 weeks)
- [ ] Automate the new test cases and add to CI
- [ ] Participate in the RCA / post-mortem meeting
- [ ] Update monitoring alerts based on lessons learned
- [ ] Review test strategy: does it need adjustment?