Templates Library
The artefacts professionals actually use
Seven copy-paste-ready templates covering the full QA lifecycle — from a single test case to a programme-level test strategy. Each template is opinionated enough to be useful on day one and structured enough to satisfy NZ government and enterprise stakeholders.
Pick a template
Test Case
Structure any test case for manual or automated execution — preconditions, steps, expected results, and traceability to requirements.
Open template →Bug Report
Write defects that developers actually act on — clear reproduction steps, environment detail, severity and priority, and evidence attachments.
Open template →Test Plan
Lightweight plan for feature or sprint scope — scope, approach, entry and exit criteria, schedule, and a short risk section.
Open template →Test Strategy
Programme-level document for NZ government and enterprise — objectives, test levels, techniques, environments, tools, and governance sign-off.
Open template →Risk Register
Test risk register aligned to NZ government procurement — risk ID, description, likelihood, impact, exposure score, mitigation, and owner.
Open template →Playwright Boilerplate
Production-ready TypeScript Playwright project structure — config, page objects, fixtures, CI workflow, and reporting out of the box.
Open template →Test Report
End-of-sprint or release test summary — coverage achieved, defects found and closed, outstanding risks, and a go/no-go recommendation.
Open template →Why templates matter
Most testers spend time re-inventing artefacts from scratch. A blank Confluence page becomes a half-finished test plan. A bug reported in a Slack message gets ignored. A test strategy written from memory omits the sections a procurement panel needs to sign off.
These templates solve that problem. They encode the professional standard for each document so you can focus on the content — the feature under test, the risk, the environment — not the structure.
NZ-context aware
The test strategy and risk register templates include sections required for NZ government ICT procurement, the Government Assurance Programme (GAP), and the Privacy Act 2020. They are immediately usable on NZGP and public sector contracts.
ISTQB-aligned
Each template maps to the relevant ISTQB process area: test case and test plan align to CTFL Chapter 5, test strategy to CTAL-TM Chapter 2, and risk register to the risk-based testing process in CTAL-TM Chapter 2.5. Field labels follow the ISTQB glossary.
Annotated, not just blank
Every field has guidance text in italics and a filled NZ example alongside the blank version. You can delete the guidance when you hand the document over. New team members can read it to understand why each field exists.
Consistent across the team
Adopt these as your team baseline and every bug report, test case, and sign-off document follows the same structure. Developers stop ignoring bug reports that are missing information. Stakeholders get reports they can actually read.