Team Test Plan

Our test plan

Repeat each functional section of the test software in turn, and after several tests, record and summarize the test results.

Do we need to test until our software is perfect?

Our software needs to be tested, but the software is for some people, the software can only do better, but not perfect, so we just have to do good enough.

What is "good enough" for testing?

I think the target user's experience is good enough for testing to represent that the software is good enough.

What is the "standard of exit"?

(1) Integration test Case design has passed the review

(2) All source code and executable code have established a controlled baseline, included in the configuration management controlled library, without approval can not be arbitrarily changed

(3) Complete the integration test of the whole system according to the integrated component plan and incremental integration strategy

(4) Meet the requirements of the test plan for the coverage required for integration testing

(5) Integrated work version to meet the design definition of the functions, performance requirements

(6) The errors found in the integration test have been modified to meet the standard of defect repair rate at all levels

Each project team defines what is your beta version "good enough"? What is your test matrix?

1. The interface is beautiful, and the user is not inconvenient to use, the position of the button is suitable and comfortable;

2. Good software performance, there will be no flash, program crashes and other issues;

3. The software function basically satisfies the user's demand;

4. Login by account number and password, there is a certain confidentiality.

Test matrix:

Software features	Test transactions	Parallel testing	Code inspection Rules
New Notes
Insert Picture
Call camera
Two-dimensional code sharing		X	X

Team Test Plan