Mastering Software Acceptance Testing: A Complete Process Guide

1 Introduction

The purpose of this document is to make the acceptance testing process transparent, public, and actionable. It is intended for product development, testing, and operations teams.

2 Test Process Overview

A flowchart (see image) illustrates the overall acceptance testing workflow.

2.2 Startup Phase

2.2.1 Write Requirement Specification

Input: Product definition

Work: Analyze product definition, write requirement spec, mind map, architecture diagram

Exit: Requirement spec completed and approved by product department

Participants: Product manager (owner and responsible)

2.2.2 Project Initiation

Input: Initiation meeting

Work: Feasibility analysis, approval, produce requirement spec

Exit: Project initiation approved

Owner: PMO

2.2.3 Develop Acceptance Test Plan

Input: Completed product definition, requirement spec, project initiation, development plan

Work: Draft test plan covering environment, scope, resources, strategy, deliverables, risk management; review by all roles

Exit: Test plan reviewed and approved

Owner: Test project manager

2.3 Acceptance Test Design Phase

2.3.1 Test Design

Based on requirement and design documents, create a test plan that includes functional coverage, non‑functional tests, test techniques, test cases, etc.

Exit: Test plan drafted and internally reviewed

Owner: Test engineer

2.3.2 Test Case Maintenance

Update test cases when designs are incomplete, bugs are uncovered, new features appear, or cases are inaccurate.

Ensure coverage of all test requirements and regular review

2.3.3 Test Design Review

Review test plan and cases with product, development, and testing teams, focusing on resources, scope, priorities, strategy, risk, and case quality.

Exit: Test plan and cases approved

Owner: Test engineer

2.4 Functional Verification Phase

2.4.1 Version Release for Testing

Version must pass smoke test before formal testing

Testing must be performed in a stable, isolated environment

2.4.2 Functional Verification Testing

Execute test cases against the baseline version, ensure environment stability, run acceptance tests, and produce a detailed test report.

Exit: Test cases reviewed, 100% coverage, 100% pass rate, system meets specifications, bugs closed, bug metrics within limits

Owner: Test project manager, test engineer

2.5 Production Line Acceptance

Conduct comprehensive functional, performance, security, and reliability testing on the release candidate, evaluate results, and decide on acceptance or rollback.

Exit: Acceptance criteria met (100% coverage, 100% pass, no critical bugs, trial operation passed)

Owner: Test project manager, test engineer

2.6 Test Archiving

After successful acceptance, archive all related documents (test plan, cases, reports, meeting minutes) and seal the version.

Exit: All documents archived, version sealed

Owner: Test project manager, test engineer

2.7 Test Work Summary

Hold a summary meeting to review overall testing activities, issues, lessons learned, and suggestions.

Exit: Issues resolved with satisfactory solutions

Participants: Test engineers, test project manager

3 Appendix

3.1 Acceptance Criteria Reference

Defines bug severity thresholds, functional completeness, and test pass rates required for acceptance.

3.2 Defect Severity Levels