//Templates

Steps to reproduce, expected vs actual behaviour, environment details, and severity. For Jira, Linear, GitHub Issues.

End-of-cycle test results report. Coverage, pass/fail counts, defects found, and risk assessment.

Sign-off report when testing completes. Final results, lessons learned, and recommendations.

Triage meeting agenda, defect prioritisation grid, and decisions log. For weekly QA syncs.

Requirements-to-tests mapping with coverage gaps highlighted. Markdown table format.

Scope, approach, schedule, risks, entry/exit criteria. IEEE 829-style structure.

High-level testing approach for an entire product or release programme. Org-level document.

Product/release risk register with likelihood, impact, and mitigation per risk.

Preconditions, steps, expected results, postconditions. Manual or automated, supports Gherkin.

Mission, time-box, areas to explore, oracles, notes. Session-based testing (SBTM).

Pre-release sign-off checklist covering testing, monitoring, rollback, and comms.

What went well, what didn't, action items. QA-flavoured retro template for sprint reviews.

Load, stress, spike, and soak test planning. NFRs, environment, tools, scenarios, acceptance criteria.

Results vs SLOs, bottlenecks observed, recommendations, regressions vs baseline.

On-call playbook: severity ladder, triage flow, comms templates, escalation paths.

5 Whys, fishbone, timeline of events, contributing factors, action items.

Context for the next on-call rotation: open incidents, hot systems, deferred work, watch-outs.

Report a security issue clearly and safely: impact, evidence, scope and escalation notes — with sensitive values masked.