← Back to Kit Home

Lightweight Test Plan Template

A test plan is a short document that answers: what will we test, how, when, and who?

This is a lightweight version — good for small teams and junior testers. Copy it and fill in your project details.

---

1. Project Info

Field	Value
Project name
Version / Build
Test plan author
Date
Test period	From ... to ...

---

2. Objective

Why are we testing? One or two sentences.

Example: "Verify that the new checkout flow works correctly on web and mobile before the release on October 1st."

---

3. Scope

In scope (we WILL test)

• Feature A
• Feature B
• Regression on login and payments

Out of scope (we will NOT test)

• Admin panel (no changes this release)
• Performance testing (separate team)

---

4. Test Approach

How will we test?

• Manual testing: main flows, exploratory testing of new features
• Automation: existing regression suite runs every night
• Test types: functional, smoke, regression
• Browsers / devices: Chrome, Firefox, Safari; iPhone SE, Samsung Galaxy S23

---

5. Test Environment

Item	Value
Environment URL	e.g. https://staging.example.com
Test data	e.g. test users list, test credit cards
Build to test	e.g. build 2.4.1

---

6. Roles and People

Name	Role	Responsibility
Jane	QA Lead	Plan, review, final report
You	Junior Tester	Test cases, execution, bug reports

---

7. Entry Criteria (when can we START testing?)

• [ ] Build is deployed to the test environment
• [ ] Smoke test passes
• [ ] Test data is ready
• [ ] Requirements/designs are available

8. Exit Criteria (when can we STOP testing?)

• [ ] 100% of planned test cases executed
• [ ] 95%+ pass rate
• [ ] No open Critical or High bugs
• [ ] Test summary report is written

---

9. Risks

Risk	Plan B
Build is delivered late	Test the most critical features first
Only one tester available	Reduce scope — cut low-priority tests
Test environment unstable	Escalate to DevOps, test locally

---

10. Deliverables

What documents/reports will we produce?

• Test cases (in the test management tool)
• Bug reports (in Jira / other tracker)
• Test summary report at the end

---

11. Schedule

Activity	Dates	Owner
Write test cases	Sep 5–7	You
Execute tests	Sep 8–14	You
Regression	Sep 15–16	You + automation suite
Summary report	Sep 17	QA Lead

---

💡 Tip: Keep the test plan short and alive. If things change, update the plan — don't write it once and forget it.