When to use a QA testing template
Testing is often squeezed into whatever time is left before a release. Without a plan, testers test what they remember, regression testing is skipped and the release decision is made on a feeling. A QA template makes testing visible and planned, with clear criteria for when a release is ready.
Use it for a major release, a new product, a client project before handover or any release where quality risk is high. It suits dedicated QA teams, agencies testing client work and product teams without full-time testers.
How the template is structured
- Test planning. Define scope, choose the approach and set entry and exit criteria. Exit criteria turn the release decision into a check instead of a debate.
- Test design. Write and review test cases and prepare realistic test data.
- Environment. Set up a stable test environment and the agreed devices and browsers.
- Execution. Run functional and regression tests, log defects with evidence and retest fixes.
- Sign-off. Write a summary report, hold the release decision and update the regression suite for next time.
How to use it in Worklenz
- Create a project for the release’s testing, or add these phases to the development project.
- Create a task per test area and attach test cases, or link to your test management tool.
- Log defects as tasks with severity labels and assign them to developers.
- Use the kanban board to follow defects from open to fixed to retested.
- Track testing time on the Pro plan and above to plan future QA effort.
Making QA work visible and billable
Agencies often underestimate testing in proposals because they do not know how long it takes. Time tracking shows the real effort by release, so the next estimate includes enough QA. On the Business plan, project finance compares the budget with the cost of logged time.
Example: testing a mobile app release
A small QA team is testing a mobile app release with a new payments screen. The plan sets the scope, lists four devices and sets exit criteria: no open critical or high defects, and all payment tests passing. Test cases are reviewed by a developer, who spots a missing refund scenario.
Execution finds 14 defects, including one critical defect in the payment confirmation. Developers fix it, QA retests it, and the summary report shows two low-severity defects remaining. The product owner agrees to release, and the new payment tests are added to the regression suite.
Choosing what to automate
Not every test is worth automating. Good candidates are tests you run on every release, tests of stable features and tests that check many combinations of data, such as pricing rules or form validation. Poor candidates are features that change every sprint, one-off checks and tests that depend on human judgement, such as whether a layout looks right. Start by automating the regression tests for your most important user journeys, like sign-up and checkout, and grow from there. Mark automated test areas with the Automated label so the team can see what is covered and what still needs manual testing each release.
Who should be involved
A QA lead owns the plan, criteria and sign-off report. Testers write and run tests. Developers review test cases and fix defects. A product owner or client agrees the exit criteria and makes the release decision.
Common QA mistakes
The first mistake is starting tests without agreed exit criteria, which makes the release decision subjective. The second is skipping regression testing because new features take all the time. The third is unclear defect reports that send developers back to ask questions. This template plans for each of these.
Tips for effective QA
- Agree exit criteria early. They make the release decision simple.
- Protect regression time. Breaking existing features costs more than late new ones.
- Attach evidence to defects. Screenshots and steps save hours.
- Grow the regression suite every release. Each new test protects future releases.
- Test with realistic data. Edge cases such as long names, special characters and empty fields find bugs that tidy sample data never does.
Related: the bug tracking template and the software development template.





