Table of contents
2. Guidelines for Test Execution and Ending
3. Test Report Goals and Concerns
7. Key points of the test report
8. Problem severity description and response time specification
9. Main roles and responsibilities of testing
1. What is a test report?
The test report refers to writing the process and results of the test into documents, analyzing the problems and defects found, providing a basis for correcting the quality problems of the software, and laying the foundation for software acceptance and delivery.
2. Guidelines for Test Execution and Ending
1. The reason for the end of the test execution
1) After the test achieves the expected purpose, it ends as planned
2) Limited by time schedule and resources, the exam was forced to end
2. After the test is executed
1) In the test plan, clearly state the conditions for the end of the test
2) Good-Enough principle
3) The determination of the end condition is a compromise between quality and cost
4) No new defects were found within the specified time period
5) Cost-based considerations (weapons, medical equipment not applicable)
3. After the test is executed
1) Meet the coverage requirements
2) Unit testing: statement coverage, ...
3) Integration testing: API, parameter combination...
4) System testing: functions, use cases, use case scenarios...
(For example: 100% statement coverage and 90% use case scenario coverage)
5) The project team reached a consensus
6) Due to time schedule and resource constraints, it must be completed
7) According to experience, when the proportion of defects found and resolved reaches 85% of the total defects, the test can be terminated.
3. Test Report Goals and Concerns
Target
1) Indicate the actual status of the current project
2) Be clear about what the tests do and what they don't.
3) Give an evaluation of the system's operational performance
4) Clarify when the system can be used for production work
focus point
The test report is only useful when it is really needed, and it needs to cooperate with the market and management
Insufficient information for the test (to evaluate a project)
Test conditions do not truly reflect individual conditions
4. Elements of test report
1) Overall strategy for this test
2) Preparation and design of this test (decomposition)
3) The specific content and execution of the test
4) Coverage Analysis
5) Defect statistics and analysis
6) Test conclusions and suggestions
7) Support material
5. Test report template
1. Test summary report:
1) Summary (such as what was tested, what is the conclusion, etc.)
2) Changes in test plans and test cases;
3) Comprehensively evaluate the version information;
4) Summary of results (measures, counts);
5) Evaluation of test item fail/fail criteria;
6) summary of activities (use of resources, efficiency, etc.);
7) Approval
2. Report the current software status
1) Function/test matrix
2) Status report of functional testing, focus analysis
3) About the working timeline of the function
4) Expected to find VS actual found defect ratio
5) The gap between the defects not found and the defects corrected
6) Average value of uncorrected defects by type
7) Defect classification report
8) Test Activity Report
3. Test data collection
-
Cumulative data on test results
-
Description of test tasks, test collections and test events
-
defect analysis
-
Due to planning problems, the data that did not find the defect
-
serious flaw
-
defect type
-
Why the defect was not found
-
Effect
6. System test coverage
1. Test coverage is the evaluation of the completeness of the test. Test coverage is represented by coverage of test requirements and test cases or coverage of executed code.
Coverage is equal to area covered/total area
2. The estimation of software requirements is divided into two parts:
2.1 Requirements-Based Test Coverage Estimation
Requirements-based test coverage is evaluated multiple times in the test life cycle and provides identification of test coverage (such as planned, implemented, executed, and successful test coverage) at milestones in the test life cycle. In the Execution Test activity, two test coverage measures are used, one to determine the test coverage obtained by executing the tests and the other to determine the successful test coverage (that is, the tests that were executed without failures, such as tests that did not exhibit defects or unexpected results) .
2.2 Code-Based Test Coverage Estimation
Code-based test coverage measures how much code has been executed during testing, as opposed to how much code remains to be executed. Code coverage can be based on control flow (statement, branch, or path) or data flow.
7. Key points of the test report
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 displayed with diagrams, such as the status diagram of all bugs and the severity status of bugs. There are mainly some terms here to explain to you.
1) Test project name
2) Comparison of measured results with expected results
3) Problems found
4) Defect discovery rate = total number of defects / number of executed test cases
5) Use case density = total number of defects / total number of test cases x 100%
6) Defect density = total number of defects / total number of function points
7) The effect achieved by the test
the case
I. Introduction
1. Purpose of writing
This document covers test scope, test requirements, test strategies, test methods, test tools, test resources, test delivery documents, risk analysis, etc., and provides a clear process for subsequent test work to ensure that test work is carried out effectively.
2. Project background
With the improvement of people's living standards, cars have become one of the indispensable means of transportation for the public. The number of newly purchased cars that need to be registered every day has exceeded 1 million. As a result, the vehicle registration outlets of various vehicle management offices cannot satisfy people's easy registration. Hunan traffic police commissioned our company to customize and develop this software, aiming to allow people to easily choose their favorite license plate number at home. And complete transactions, transfers, gifts and other matters related to the license plate number.
3. Scope of application
4. Terminology
2. Test task
1. Test scope
This plan document covers the function test, stress test, load test, compatibility test, acceptance test, etc. of "Hunan Traffic Police All-in-One Netcom".
2. Test target
Test whether the functions and performance required by the "Hunan Traffic Police One Netcom" system and requirements specifications are fully realized, whether the explicit and implicit needs of users are met, whether there are risks in system release, etc.
3. Reference documents
4. Submit documents (deliverables)
3. Test progress
4. Test resources
1. Human resources
2. Environmental resources
hardware environment
Software Environment
3 test tools
5. Testing strategy
1. Functional test
2. Stress test
3. Load test
4. Compatibility testing
6. Test Completion Criteria
1. Test Sufficiency
a. The use cases have fully covered the requirements: the test case coverage is required to reach 100%.
b. In principle, all use cases are required to be executed 100%, that is, use cases with high, medium and low priority must be executed 100%.
c. Sufficiency of work investment: The project testing work should be fully invested to ensure the rationality of the test investment.
2 Test validity
a. The resolution rate of defects above the severity level must reach 100%.
b. Defect density reaches a certain standard, and the number of bugs is normally distributed.
c. Relevant responsible departments approve the test results, including customer trial and acceptance tests, etc.
7. Risks and constraints
1. Process constraints
(1) Development process: omitted
(2) Test process: omitted
(3) Defect process: slightly
2. Risk analysis
8. Problem severity description and response time specification
9. Main roles and responsibilities of testing
Testing is not the work of a single team in the testing group. It requires the participation of all colleagues in the entire project. The main roles and responsibilities involved in the testing work are roughly as follows:
This post ends here, and finally, I hope that friends who read this post can gain something.
I have prepared all the test reports in the article, please reply to [Test Report] to get it for free if you need it.
If you think the article is not bad, please like, share, and leave a message, because this will be the strongest motivation for me to continue to output more high-quality articles!