[Current Status of Software Testing Industry] Do you still dare to learn software testing in 2023? The future has been sent... Where should the testers go? [Automated testing, test development, performance testing]
A defect report is a collection of descriptions of software defect phenomena and steps to reproduce them. Software Bug Report (SBR) or Software Problem Report (SPR)
Function: Defect reports are one of the work results of software testers. They reflect the value of software testing. Defect reports can accurately describe the defects in the software. When testers find a defect, they need to fill in a "defect report" to record this. Defects, and inform developers of the problems that occurred through this defect report – Defect reports are an important tool for communication between testers and developers. It is convenient for developers to correct the defect report, which can reflect the current quality status of the project product and facilitate the overall progress and quality control of the project. Software testing defect report is one of the output results of software testing and can measure the work ability of testers.
1. Key points of defect report
1) Title
2) Description: concise, accurate, complete, reflecting the essence of the defect
3) Steps to reproduce
4) Severity
5) Priority
6) Screenshot
7) Number
8) Designee
2. “5C” Principle
Correct: The description of each component is accurate and will not cause misunderstanding.
Concise steps: only include essential information and do not include any superfluous content
Clear content (Clear): The description of each component is clear and easy to understand
Complete: Contains complete steps to reproduce the defect and other essential information
Consistent style: Write all defect reports in a consistent format
3. The
review and testing of the 28/20 theorem in the analysis, design, and implementation stages can discover and avoid 80% of defects, while system testing can find 80% of the remaining defects. The last 4% of defects may only be found by users. It will be exposed after extensive and long-term use.
4. Composition of defect report
1. Defect ID: the order in which defects are submitted
2. Title of the defect (summary): describe the defect concisely and concisely
3. Defective By: Tester
4. The date the defect was discovered (date): usually the same day
5. The module to which the defect belongs (subject): the bug discovered when testing that functional module
6. Defective version (Defected in release): the version of the software developed
7. Assigned to: The tester is assigned to the development manager. The development manager needs to assign specific developers again based on the module where the defect is located.
8. Defect status: the processing stage or processing situation of the defect at this time
(1) The tester discovers a defect, submits a defect report, and sets the defect status to new (new)
(2) The development manager verifies the submitted bug. If it is a bug, change the status to open (an open bug, a bug recognized by the development team) and assign it to a specific developer to solve; if it is not a bug, change the status to rejected (rejected) bug)
(3) When developers see the bugs assigned to them, they fix the defects. After the modifications are completed, the defect status is fixed (bugs that have been fixed and bugs that can be returned to testing)
(4) The tester performs back-testing on the fixed bug. If the back-testing is successful, the status is changed to closed (closed defect, archived bug); if the back-testing is unsuccessful, the status is changed to reopen (reopened bug).
5. In-depth understanding of defect reports
1. Are the severity and priority of defects directly proportional to each other?
The severity of interface problems is generally low, and the priority may be high - fix it immediately
Some major functional problems may not be solved temporarily, but they will not affect the use of other functions. In this case, the priority may be defined as relatively low - fix them before release.
2. After the severity and priority of the defect are determined, can it still be modified?
The severity is not allowed to be changed, but the priority may be fixed.
The tester determines that a defect is "fixed immediately", but the development team believes that the defect is difficult to solve, and the defect does not affect other functions. In this case, it may be required to be "modified in the next version" or "modified before release."
3. Will all defects discovered be fixed?
The cost of fixing some defects is too high or may not be fixed before release due to schedule pressure. Such defects must be discussed by the project team, cost and risk must be weighed, and it must be ensured that there will be no major impact on users or legal disputes. . Later, defects or vulnerabilities will be fixed by upgrading software or applying patches.
6. The role of defect reports
1. Record bugs
2. Classify bugs (module, bug status, severity, version)
3. Track bugs
4. Analyze and count bugs
The interface testing tool can use the domestic interface testing and interface document generation tool: apipost
The following are supporting learning materials. For those who are doing [software testing], it should be the most comprehensive and complete preparation warehouse. This warehouse has also accompanied me through the most difficult journey. I hope it can also help you!
Software testing interview applet
A software test question bank that has been used by millions of people! ! ! Who is who knows! ! ! The most comprehensive interview test mini program on the Internet, you can use your mobile phone to answer questions, take the subway, bus, and roll it up!
Covers the following interview question sections:
1. Basic theory of software testing, 2. web, app, interface function testing, 3. network, 4. database, 5. linux
6. Web, app, interface automation, 7. Performance testing, 8. Programming basics, 9. HR interview questions, 10. Open test questions, 11. Security testing, 12. Computer basics
How to obtain documents:
This document should be the most comprehensive and complete preparation warehouse for friends who want to engage in [software testing]. This warehouse has also accompanied me through the most difficult journey. I hope it can also help you!
