Integration test process

　　Purpose:

● Defined by ProjectTestTest the process. A test plan and test cases are developed by a test group independent of software developers and a test report is submitted.

Roles and responsibilities:

● Project software Manager (Development Manager): Reviews test cases, and integrates the content to be tested into the test environment.

● Testers: responsible for completing test case design,Integration TestBuild Environment, perform integration testing, verify problems, and write test reports.

● Developers: they are responsible for timely fixing test problems.

　　Entry criteria:

● The project has been started.

● The requirement document has been reviewed

　　Input:

● Requirement document

Termination principle:

● Pass the integration test.

　　Output:

● Code and software that have passed the integration test

● Test Cases

● Problem records

● Test report

　　Main activities:

1. The tester prepares the test plan after the project starts, which can include the integration test plan, which can be refined or changed during the integration test. The test plan should be conducted by relevant persons

Personnel (Project Manager, SQA, and requirement personnel) for review. Integration testing is divided into two phases: Unit (assembly) Integration Testing and system integration testing.

2-unit (assembly) Integration Testing (synchronized with development, refers to the testing of integrating a program unit to the system ):

● The tester designs the test according to the test plan and prepares the test cases and test scripts (optional ). The test design results should be reviewed.

● The tester builds an independent test environment with the assistance of the Development Director (this environment can run code programs ).

● The development owner will have passedUnit TestThe Program unit is submitted and integrated into the test environment.

● The tester executes the unit integration test and registers the test problems to the project bug library. For details, see "Development Project defect library usage instructions".

● Developers can promptly fix program problems based on the registration in the project bug library. No more than 5 survival cycles for each non-final state problemWork.

● The tester verifies the problem.

● The tester issues the weekly test report in stages according to the project test plan.

● Repeat steps 1-7 above until all Subsystem module units pass the unit integration test passed standards defined in the test plan.

　　Unit (assembly) integration test pass criteria:

◇ Related test cases are completed.

◇ 90% of serious problems (level 1 and level 2) found in unit (assembly) integration testing were correctly modified; 70% of general problems (level 3) were modified.

3. System Integration Testing (testing compiled build ):

● The tester designs the test according to the test plan and prepares the test cases and test scripts (optional ). The test design results should be reviewed.

● The tester builds an independent test environment with the assistance of the developer.

● The Development Director submits the build that has been compiled and built into the test environment according to the plan.

● The tester executes the system integration test and registers the problems found in the test to the project bug library. For details, see the "Development Project defect library usage instructions".

● Developers can promptly fix program problems based on the registration in the project bug library. For non-final state problems, the life cycle of each State cannot exceed 5 working days.

● The tester verifies the problem.

● The tester issues the Build Test Report in stages according to the project test plan.

● Repeat steps 1-7 above until all Subsystem module units pass the system integration test passed standards defined in the test plan.

　　System integration test pass criteria:

◇ All test cases have been executed.

◇ 90% of serious problems (level 1 and level 2) found in system integration testing were correctly modified; 70% of general problems (level 3) were modified.

◇ All the questions in the question bank are in the final state (except for the last build problem ).

4. The tester analyzes and summarizes the integration test activities and prepares the integration test report.

5. The tester fills in the requirement coverage table in the requirement list for tracking and verification. Process cropping description:

◆ Projects with full-time testers must be executed in this process.

◆ Project integration tests not established in the company can be carried out with reference to this process

　　Related documents:

◆ Integration test plan template

◆ Test Weekly Report Template

◆ Build Test Report Template

◆ Integration Test Report Template

◆ Use of the development project defect Library

◆ Classification criteria of defect severity

◆ Requirement coverage table
From: http://www.51testing.com/html/93/n-126193.html