Worklenz
Sign in
EN

Software & IT template

QA Testing Template

Plan and run software QA: define scope and approach, write test cases, prepare environments, execute tests, track defects and sign off the release.

  • Free plan available
  • Open source (AGPL-3.0)
  • Cloud or self-hosted
QA engineer testing an application on several devices

What's included in the QA Testing template

phases
5
tasks
15
labels
5
statuses
3
1. Test planning · 3 tasks
  • Define the test scopeList the features, platforms and integrations in scope, and what is out of scope.
  • Choose the test approachDecide the mix of manual, automated, regression, performance and accessibility testing.
  • Set entry and exit criteriaAgree when testing can start and what must be true before release.
2. Test design · 3 tasks
  • Write test casesSteps, test data and expected results for each requirement.
  • Review test casesDevelopers or product owners review cases for gaps.
  • Prepare test dataCreate realistic data for every scenario, without using real personal data.
3. Environment · 2 tasks
  • Set up the test environmentA stable environment that matches production as closely as possible.
  • Prepare devices and browsersThe device and browser list agreed in the test approach.
4. Execution · 4 tasks
  • Run functional testsExecute test cases and record pass or fail with evidence.
  • Run regression testsCheck that existing features still work after changes.
  • Log defectsReport each failure with steps, evidence and severity.
  • Retest fixed defectsConfirm fixes work and close the defects.
5. Sign-off · 3 tasks
  • Write the test summary reportTests run, pass rate, open defects and risks.
  • Hold the release decisionCheck the exit criteria with the product owner and agree go or no-go.
  • Update the regression suiteAdd new test cases for future releases.

Labels

  • Pass
  • Fail
  • Blocked
  • Critical defect
  • Automated

Who this template is for

  • QA teams and testers working with development teams or agencies
  • Software agencies that test releases before client sign-off
  • Product teams preparing a major release

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

  1. 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.
  2. Test design. Write and review test cases and prepare realistic test data.
  3. Environment. Set up a stable test environment and the agreed devices and browsers.
  4. Execution. Run functional and regression tests, log defects with evidence and retest fixes.
  5. Sign-off. Write a summary report, hold the release decision and update the regression suite for next time.

How to use it in Worklenz

  1. Create a project for the release’s testing, or add these phases to the development project.
  2. Create a task per test area and attach test cases, or link to your test management tool.
  3. Log defects as tasks with severity labels and assign them to developers.
  4. Use the kanban board to follow defects from open to fixed to retested.
  5. 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.

Start your qa testing project in Worklenz

Sign up free, then set up the phases and tasks above for your team.

QA Testing template FAQs

What should a QA test plan include?

Scope, test approach, entry and exit criteria, test cases, test data, environments, execution, defect tracking and a sign-off report. This template covers each of them.

What are entry and exit criteria in testing?

Entry criteria say when testing can begin, such as a stable build. Exit criteria say when testing is complete enough to release, such as no open critical defects.

Is this QA testing template free?

Yes. The full template is on this page, and Worklenz's free plan includes task lists, kanban boards and built-in project templates.

Can I track defects in the same project?

Yes. Log each defect as a task with a severity label, or use the separate bug tracking template for ongoing bugs.

Software & IT

Software Development template

Plan and deliver a software project in sprints: requirements, technical design, iterative development, testing, release and early support.

6 phases · 18 tasks. By Worklenz.

Software & IT

Bug Tracking template

A simple bug tracking workflow: capture clear reports, triage and prioritise, fix with review, verify and close, then learn from patterns.

5 phases · 15 tasks. By Worklenz.

Software & IT

E-commerce Development template

Build or rebuild an online store: discovery, platform and design, product catalogue, checkout, payments and shipping, testing and a launch that protects sales.

6 phases · 19 tasks. By Worklenz.

Software & IT

IT Project template

Plan an IT project such as a system rollout, upgrade or migration: assess needs, plan and procure, implement, roll out to users and hand over to support.

6 phases · 18 tasks. By Worklenz.

Software & IT

Data Migration template

Move data between systems safely: assess and map the data, clean it, run test migrations, cut over with a rollback plan and validate the results.

6 phases · 17 tasks. By Worklenz.

Software & IT

Security Assessment template

Run a security assessment from scope to remediation: inventory assets, review risks and controls, test for vulnerabilities, report findings and track fixes to closure.

6 phases · 17 tasks. By Worklenz.

Explore more templates

Run your next project from a template

Worklenz is an open-source platform for agencies and service teams: projects, time tracking and client work in one place.