Differences Between Test Specification and Test Plan and When to Write Them

Test specifications and test plans are essential documents for software testing, yet they are often confused. Both are translated as “plan” in English, but they serve different purposes.

What Is a Test Specification?

A test specification describes the features to be tested, the testing methods, the planned environment, tools, test case design approach, and test code design.

What Is a Test Plan?

A test plan outlines the scope, methods, resources, and schedule of testing activities, including test items, features, tasks, responsible personnel, and risk control.

Technical vs. Project Focus

Test Specification – Technical : focuses on how to test (technology, tools, methods).

Test Plan – Project : focuses on what to test (objectives, timeline, personnel, resources).

When to Write Them

Test Specification: drafted during project initiation or requirement analysis, when the test manager decides overall approach, tools, and risk mitigation.

Test Plan: created during project execution, detailing team assignments, timelines, and deliverables for a specific version.

Test Specification Structure (Large and Small Directions)

Large‑direction documents the overall project; small‑direction (or “small scheme”) aligns closely with the test plan and is reviewed with the project manager to confirm scope.

1    Introduction    4
1.1  Purpose          4
1.2  Background       4
1.3  Intended Readers 4
1.4  References       4
2    Terms & Definitions 4
... (remaining outline omitted for brevity)

Test Methods

Integration testing typically uses big‑bang and bottom‑up approaches.

1. Functional testing: verify features, protocols, drivers.
2. Performance testing: assess behavior under load.
3. Stability testing: run monkey tests.
4. Fatigue testing: continuous operation on devices.
5. Stress testing: simulate high‑traffic scenarios.
6. Exception testing: handle abnormal conditions.
7. Memory testing: monitor memory usage.
8. Concurrency testing: multiple apps/services simultaneously.

Test Report Formats

Report Name

Content

Author

Recipient

Daily Test Report

Daily test status, impact, risk, lessons learned

Tester

Project manager, development manager, department head, etc.

Weekly Test Report

Weekly progress, issues, lessons learned

Tester, development manager

Department head, development manager, tester, project staff

Monthly Test Report

Monthly status, defect tracking, lessons learned

Tester, development manager

Department head, development manager, tester, project staff

Phase Test Report

Milestone summary, problems, solutions, risks

Development manager, tester

Department head, tester, project staff

Test Summary Report

Overall summary, defect statistics, analysis, recommendations

Tester

Project manager, development manager, department head, tester, project staff

Test Plan (5W+1H)

Follow the 5W+1H principle:

1. What : testing objectives and scope.

2. When : schedule.

3. Where : environment.

4. Who : personnel.

5. Why : purpose.

6. How : methods and tools.

In practice, the plan details the version’s testing goals, coverage, resources, environment, tools, and schedule, making the testing process transparent to stakeholders.

Test Report

The test report is presented to leadership, summarizing test case count, personnel, defects, and resolutions, preferably with quantitative charts. The report should clearly state whether the version passed based on predefined criteria.

FunTester – Tencent Cloud annual author, Boss Direct hiring author, GDevOps official media partner (non‑famous test developer). Links to related articles and resources are provided.