Resources
Put the advice to work.
Practical worksheets for the next release, investigation or review. Read the example, download the editable file and adapt it to your product. No account or email required.
What needs attention before your next release?
Answer eight questions about evidence, access, automation and recovery. The readiness check turns missing or uncertain controls into a short action list, with a worksheet for each area. Your answers stay in your browser unless you choose to share the result link or send an enquiry.
The working library
20 matching items
Automation effort and cost calculator
Compare manual execution with automation setup, review, maintenance and tool costs. Edit every assumption and export a planning worksheet.
Find a Starting Scope for Your Software Problem
Match a release, website, automation, security or AI problem to a small first engagement, its deliverables and the information needed to start.
Exploratory testing charter
Give an exploratory session a mission, a time box and a reviewable record. Includes an example for an invitation workflow.
Flaky-test investigation flowchart and log
Follow a repeatable investigation from a failing run to a supported cause. Preserve evidence before rerunning and track quarantine decisions explicitly.
Security questionnaire evidence library
Map a buyer’s question to an owned control, dated evidence and an honest limitation. Includes a sample finding, retest record and engagement boundaries.
Manual or automated? Decision worksheet
Decide whether a repeated check earns its setup and maintenance cost. Pair the decision record with the interactive automation cost calculator.
Software handover and preview checklist
Give the receiving team a usable preview, clear ownership and enough context to operate and change the product without guessing.
Project discovery brief
Turn a vague request into a focused first engagement: problem, constraints, evidence, exclusions and decisions needed.
Industry test scenario matrices
Worked planning prompts for SaaS, healthcare, finance, e-commerce, logistics, manufacturing and startup releases, with boundaries and first-engagement suggestions.
Dependency verification and triage register
Verify package identity and record vulnerable-version exposure, reachability, upgrade decisions and retest evidence. Includes an SBOM inventory structure.
Performance budget and accessibility remediation record
Record comparable performance observations and practical keyboard/accessibility checks without mistaking an automated score for user experience.
Playwright, Postman and CI starter kit
A versioned, executable local shop example with isolated sessions, browser/API checks, repeat-request and refused-access scenarios, a CI gate and Allure results.
Audit API collection and recurring comparison kit
A Postman collection and opt-in weekly CI example for creating audits, respecting polling limits and comparing like-for-like results without extending report retention.
Release evidence checklist
A compact record of the build, critical journeys, unresolved defects, operational checks and release owner. Make unknowns visible before deciding to ship.
Bug report template and filled example
Capture a defect another person can reproduce. Includes a fictional report showing build details, precise steps, expected behaviour and safe evidence handling.
Focused test plan
Define the risks, scope, test data, ownership and completion criteria for a change before the first test run. Includes a small planning example.
Test summary and handover
Turn test runs into a decision record. Separate executed checks, blocked coverage, unresolved findings and the person accepting the remaining risk.
Role and object access matrix
Plan positive and negative permission checks across roles, accounts and objects. Include cross-organisation access rather than testing only valid requests.
AI-assisted change review checklist
Review generated code and AI workflow changes using independent expectations, explicit permissions, failure handling and a named human decision owner.
Sample site audit report
A permanent, fictional excerpt showing how an automated finding becomes a fix and a verification step. Available even when temporary live reports expire.
Use these in a real decision
A template is a starting structure, not evidence that a product works. Assign a person to each open action, record the build and environment, and link the underlying test run or investigation. Replace placeholders with observations before the document becomes part of a release decision.
Start with the smallest document that helps the team agree. A reproducible defect needs steps and expected behaviour; a release needs a clear scope, known limitations and an owner. More fields do not improve a weak observation. Delete sections that do not fit, and explain why a risk is outside the agreed scope.
The downloads use Markdown so they can live beside code, in a ticket or in a shared document without a special tool. Each page includes the same text as its download, along with instructions and related reading. Keep sensitive evidence in an access-controlled location rather than attaching production data to a public issue.
Examples in this library are explicitly fictional. They demonstrate the form of a useful handover and the limits of a conclusion; they are not client records, benchmarks or a claim that a particular system passed testing. For project work, agree the evidence and acceptance criteria before testing begins.