What should the software test report include? Interview must ask

Catalog

One 、 What is a test report ？

Two 、 Criteria for test execution and completion

3、 ... and 、 Test report objectives and concerns

Four 、 Test report components

5、 ... and 、 Test report template

6、 ... and 、 System test coverage

7、 ... and 、 Test report highlights

---

One 、 What is a test report ？

A test report is to document the process and results of a test , Analyze the problems and defects found , Provide the basis for correcting the quality problems of software , At the same time, lay the foundation for software acceptance and delivery .

Two 、 Criteria for test execution and completion

1. End reason of test execution

1） After the test has achieved its intended purpose , Finish as planned

2） Subject to time schedule 、 Resource constraints , The test was forced to end

1. Test execution completion criteria

1） Specify the conditions for the end of the test in the test plan

2）Good-Enough principle

3) The determination of the end condition is a compromise between quality and cost

4) No new defects are found within the specified time period

5) Based on cost considerations （ Not applicable to weapons 、 Medical equipment ）

3. Test execution end condition

1） It meets the requirements of coverage

2） unit testing ： Statement override 、...

3） Integration testing ：API、 Parameter combination ...

4） The system test ： function 、 Use cases 、 Use case scenarios ...

（ for example ：100% Statement override 90% Use case scenarios cover ）

5） The project team agreed

6） Due to the time schedule 、 Resource constraints must end

7） According to the experience, when the proportion of defects found and solved in the total defects reaches 85% when , The test can be terminated .

                 

 

3、 ... and 、 Test report objectives and concerns

1. The goal is

1） Show the actual situation of the current project

2） Define what the test does , What is not done .

3） Give the evaluation of the operating performance of the system

4） Specify when the system can be commercialized

1. concerns

2. Test reports are only useful when they are really needed , Need to cooperate with the market and management

3. The information tested is insufficient （ For evaluating a project ）

4. The test situation does not really reflect the personal situation

Four 、 Test report components

1） The overall strategy of this test

2） Preparation and design of this test （ decompose ）

3） The specific content and implementation of the test

4） Coverage analysis

5） Statistics and analysis of defects

6） Test conclusion and suggestion

7） Support material

5、 ... and 、 Test report template

Test summary report ：

1） summary （ Such as what was tested 、 What is the conclusion ）

2） test plan 、 Changes in test cases ;

3） Comprehensive evaluation of version information ;

4） Summary of results （ Measure 、 Count ）;

5） The test item passed / Fail to pass the evaluation of the code ;

6） Summary of activities （ Use of resources 、 Efficiency etc. ）;

7) The examination and approval

2. Report current software status

1) function / Test matrix

2) Status report of functional test , Focus on analysis

3) About the working timeline of the function

4) Expect to find VS The ratio of defects actually found

5) The gap between undetected defects and corrected defects

6) By type , Average value of uncorrected defects

7) Defect classification report

8) Test activity report

3. Test data collection

1） Accumulated data on test results

2） Test task , Description of test sets and test events

3) Defect analysis

4) Due to planning problems , Data leading to undetected defects

5) Serious defects

6) Type of defect

7) Why are defects not found

8) effect

                     

 

6、 ... and 、 System test coverage

1. Test coverage is a measure of test completeness . Test coverage is represented by the coverage of test requirements and test cases or the coverage of executed code .

Coverage is equal to coverage area / Total area

2. The estimation of software requirements is divided into two parts ：

2.1 Requirement based test coverage estimation

Requirements based test coverage is evaluated many times in the test life cycle , And provide the identification of test coverage at the milestone of test life cycle （ As planned 、 Implemented 、 Executed and successful test coverage ）. During the execution of test activities , Use two test coverage profiles , A determination of the test coverage obtained by executing the test , Another test coverage that determines success （ That is, there are no failed tests during execution , Such as tests without defects or unexpected results ）.

2.2 Code based test coverage estimation

Code - based testing coverage measures how much code has been executed during testing , The opposite is how much code remains to be executed . Code coverage can be built on the control flow （ sentence 、 Branch or path ） Or data flow .

7、 ... and 、 Test report highlights

So what is the most important thing in the test summary ？

The most important thing is the test results and defect analysis . This part is mainly shown by charts , Like all bug State diagram of 、bug Severity status of . Here are some terms to explain to you .

1） Name of test project

2） Comparison between measured results and expected results

3） Problems found

4） Defect detection rate = Total number of defects / Number of test cases executed

5） Use case density = Total number of defects / Total number of test cases x100%

6） Defect density = Total number of defects / Total number of function points

7） The effect of the test