As a newcomer who used to be a tester, when I received a task for the first time, I always had a complex emotion of anxiety, excitement, nervousness and expectation~~ I was anxious and nervous because I was afraid that I would not do well and would not be appreciated by the leader; excitement and expectation were Wow, I have a task, I finally have a place for me~~~ Just like today's topic, if after a project is completed, the leader asks you to organize the test report independently, what will you do? Are you confident? Still shivering?
I hope that everyone who reads today's article can become an excellent newcomer who is confident and appreciated by the leaders!
The provincial version is at the end of the article
Closer to home, straight to the point. The specific content of the test report includes the following (the templates provided by different companies may be different, but they are generally the same):
Part 1: The introduction consists of two parts 1.1 Project Background and 1.2 References
1.1 Project background
The specific writing purpose of this test report indicates the intended readership. (3-4 sentences)
This test report is the (system name) system test report; the purpose of this report is to summarize the tests performed during the test phase
And test results analysis, describe whether the system meets the requirements.
The expected reference personnel of this report include testers, test department managers, project managers, SQA personnel and other quality control personnel.
1.2 References
This mainly includes "requirements specification", test plan, test case, defect record
Part 2: Basic test information mainly includes test scope, test plan design ideas
2.1 Test scope
2.2 Test case design ideas
Design the test cases according to the test points of the above test scope. Mainly adopt black box use case design method equivalence class division method, boundary value analysis method, error guessing method, scene method.
l Functional test: to ensure that the function of the test object is normal, including business process, data processing, boundary value and other functions.
l User interface (UI) testing: verify the interaction between the user and the software, ensure that the user interface will provide the user with corresponding access or browsing functions through the function of the test object, ensure that the objects in the UI operate as expected, and ensure that each The window style (including color, font, prompt message, icon, etc.) is consistent with the requirements, or meets the acceptable standard, which can ensure the friendliness and ease of operation of the user interface, and conform to the user's operating habits
l Process testing: verify the complete and correct implementation of the actual business process in the system. It should ensure the correctness of the internal data flow of each business process and the interface data between processes, and the correctness of the restrictions on the operation of the process by role permissions
l Security testing: ensure the security of user and administrator password management security, application level and system level security
l Compatibility testing: to ensure that the system can normally realize its functions under various browsers of different versions and types
Part 3: Test results and defect analysis mainly includes test execution and records, defect statistics and analysis
3.1 Test Execution and Records
3.1.1 Test organization
3.1.2 Test time
3.1.3 Smoke situation
3.1.4 Test case statistics
3.2 Defect statistics and analysis
Defect summary:
Total Defects: 59, Resolved: 1, Active: 58
Defect analysis:
Statistics by defect type:
From the above data, it can be concluded that a large number of bug types are code problems, and only one is a performance problem
Statistics by severity:
Statistics by function module:
Statistics by testing stage:
(The statistics and analysis of the above three kinds of Laixing are organized by referring to the statistics and analysis of defect types)
Residual defects and open issues:
(The above section sorts out all the remaining unresolved problems by list)
Part 4: Test conclusions and recommendations including risk analysis and recommendations, test conclusions
4.1 Risk Analysis and Recommendations
(List the problems in the test execution process, such as incomplete test coverage due to insufficient resources, such as the compatibility test in the app test process, due to the lack of test machines in the company, there are incomplete tests) 4.2 Test conclusions
According to business needs and feedback from developers, this project covers all test requirements and cases, and has been tested in the ST environment. There are a total of xx effective cases, execution rate xx%, success rate xx%, and defect closure rate xx%, the current defects have been fixed and returned to close;
To sum up, the xx project has reached the ST project test export standard, and the ST test (pass/fail) of this project can be accepted for acceptance testing/release
Part 5: Delivery Documents Deliver all the documents included in the testing process, mainly including test plans, test cases/cases, defect records, test reports
The above is all the content contained in the test report. If your company does not have a template, just write according to this, so easy~
