Mastering Software Testing: A Complete Process Guide from Planning to Acceptance

Overview

The purpose of this document is to improve error detection rates and ensure a structured, manageable testing process by defining standardized testing procedures that serve as a common reference for communication and quality control.

Applicable to project managers, developers, and testers.

Test Process Flow

Planning and Design Phase

Project Initiation Meeting

Analyze project feasibility and appoint a project manager.

Requirement Review

Test team reviews unclear or incomplete requirements and seeks clarification.

Test Kick‑off

Project manager notifies test lead of test schedule and provides relevant documents (requirements, design specs, project plan).

Form test team, assign members, and hold a kickoff meeting to align goals.

Test Design Phase

Test Plan Development

Define test environment, test scope, resources, roles, deliverables, and risk mitigation strategies.

Test Case Design

Design test cases based on equivalence partitioning, boundary value analysis, error guessing, and business knowledge.

Test Case Maintenance

Update test cases when requirements change, defects are found, or cases are inaccurate.

Test Design Review

Review test plan and test cases for correctness, coverage, and feasibility.

Test Execution Phase

Unit Testing

Preconditions: product definition, completed development, ready test environment, approved unit test cases and plan.

Execute tests, record results, and achieve 100% coverage and pass rate.

Integration Testing

Preconditions: completed unit testing, ready environment, approved integration test plan and cases.

Execute integration tests, produce reports covering defects, new findings, and overall quality.

System Testing

Preconditions: completed unit and integration testing, ready environment, approved system test plan and cases.

Execute system tests and generate comprehensive reports.

Regression Testing

Re‑run relevant test cases after each iteration to verify that fixes have not introduced new defects.

Test Reporting

After each test stage, produce a phase report summarizing results, defect analysis, coverage, and recommendations.

Final test summary report includes resource overview, result summary, defect analysis, coverage metrics, quality assessment, and improvement suggestions.

Acceptance Phase

Conduct acceptance testing against final requirements, ensuring 100% test case coverage, 100% pass rate, and no critical defects.

If criteria are not met, perform rollback.

Closure Phase

Archive all test artifacts (test plans, cases, reports, meeting minutes) and close the test team.

Conduct a test work summary meeting to discuss lessons learned and dissolve the test group.

Reference Documents

Software Requirement Specification

Software Design Documents

Test Plans and Cases

Test Reports

User Manuals, Installation Guides