Question 1

Which QA templates does a modern team actually need?

Accepted Answer

At minimum: a Test Plan per release, a Test Strategy (organisation-wide), a Bug Report template, a Test Case template, a Test Status Report (sprint), and a Test Completion Report (release). Modern teams also need a Release Readiness Checklist, a Blameless Postmortem template, a Definition of Done, and Quality Goals / SLOs documented. Teams shipping AI features need an AI Feature Test Plan and an LLM Prompt Test Case template.

Question 2

What is the difference between a Test Plan and a Test Strategy?

Accepted Answer

Test Strategy is stable, organisation-wide, and answers HOW you test: pyramid, automation framework, shift-left/right, quality gates, SLO targets. Test Plan is per-release, project-specific, and answers WHAT, WHEN, WHO: scope, schedule, resources for a given release. Strategy is rewritten once or twice a year; plan is rewritten per release.

Question 3

When should I run a release readiness review vs a postmortem?

Accepted Answer

Release readiness is proactive — run it 24 hours before deploy to verify code quality, testing, observability, rollback, and communication. Postmortem is reactive — run it within 7 days of any SEV-0/SEV-1 incident to understand root cause and capture action items. They are complementary: better release readiness reduces postmortems; better postmortems improve release readiness.

Question 4

Do I need a separate test plan for AI / LLM features?

Accepted Answer

Yes. AI features are probabilistic, not deterministic. Traditional pass/fail tests miss what matters: hallucination rate, prompt-injection resistance, cost stability, latency drift, graceful degradation. The AI Feature Test Plan template addresses these explicitly with a golden evaluation set, hallucination budget, red-team scenarios, monitoring, and rollout plan.

Question 5

Can I paste these templates into Notion, Confluence, Linear, Jira, or GitHub?

Accepted Answer

Yes. Every template exports as Markdown, which pastes cleanly into Linear, GitHub Issues, GitLab, Slack, Discord, Notion, Confluence, and Obsidian. For Jira, paste into the description field; the new editor renders Markdown. DOC export is available for Word-compatible systems; CSV for spreadsheet-based trackers.

Question 6

Are these templates free? Do I need to sign up?

Accepted Answer

All 14 templates are free with no signup. Forms run entirely in your browser. Your data auto-saves to localStorage (your device only) so you can refresh without losing work. Nothing is uploaded anywhere — no analytics on the form content.

Question 7

What's a blameless postmortem and why is it called blameless?

Accepted Answer

A blameless postmortem assumes everyone acted with the best information they had at the time. The goal is to find latent system properties that allowed the incident, not to assign fault. Pioneered at Google, Etsy, and Netflix, blameless culture is now standard at high-functioning engineering organisations because it produces better learning and higher long-term reliability than blame-based reviews.

Templates

Planning

Test Plan

Test Strategy

Definition of Done

Quality Goals & SLOs

QA RFC / ADR

Execution

Test Case

Bug Report

Bug Bash Plan

LLM Prompt Test Case

Reporting

Test Status Report

Test Completion Report

Operations

Release Readiness Checklist

Incident Postmortem

AI-Era

AI Feature Test Plan

LLM Prompt Test Case