1. Introduction
Defect is also known as bug, bug is an English word, the original meaning is bed bug, small bug, eavesdropping, damage and so on. Now people refer to all kinds of problems in software as bugs
Any problem or defect in the computer system or program that destroys the normal operation ability can be called "
Bug"; sometimes it is also generally referred to as the deviation of the final running time of the software product from the expected properties caused by the internal defects of the software product.
The type of defect
1. Mistake: The behavior of the person that causes the software to contain a fault;
2. Defect: abnormal condition of the software;
3. Fault: An unexpected situation that causes a functional component to fail to perform the required function;
4. Failure: The inability of a functional component to perform its specified function
3. Bug report
A defect report is also called a defect report or a defect tracking sheet. In the process of test execution, after software problems are found, the written report is provided to developers or other relevant personnel as a basis for locating defects, and also as a data basis for future defect measurement.
Fourth, the main content of the defect report:
1. Title: Do xx operation in xx place and find xx problem
2. Steps
3. Expected results
4. Actual Results
5. Project
6. Numbering
7. Test environment
a. The operating system, browser, etc. used
b. Tested software or system environment, version, etc.
8. Severity
a, fatal problem. The software does not work at all or causes system problems.
b. Serious problems. Seriously affect the use of users.
c. General questions. affect user usage.
d. Indicative questions. Non-interface string errors.
9. Frequency of appearance
a. Must present:
b. Occasional:
Occurs at a fixed frequency
Does not appear at a fixed frequency
only appears once
10. Preliminary positioning
11. Find people
12. Others, such as problem location analysis, etc.
5. Defect management tools
1. Bugzilla
2. Bugfree
BugFree is a bug management system independently written using PHP+MySQL for reference to Microsoft's R&D process and bug management concept. Simple and practical, free and open source (under GNU GPL)
3. TestDirector （Quality Center）
Provides a web-based system to automate software quality testing and management in a wide range of application environments. Dashboard technology allows you to understand validation capabilities and automate business processes, and identify bottlenecks in production that are hindering business outcomes. HP Quality Center enables IT teams to participate in application testing before the development process is complete. This will shorten the release schedule while ensuring the highest level of quality
4. ClearQuest
5. JIRA
The default issue types created by JIRA include New Feature, Bug, Task and Improvement, which can also be defined by themselves, so it is also a process management system.
6. Mantis
Mantis is a lightweight defect tracking system based on PHP technology. Its function is similar to the JIRA system mentioned above, and it provides project management and defect tracking services in the form of Web operations. It may not be as professional as JIRA in function, and the interface is not as beautiful as JIRA, but it is practical enough to meet the management and tracking of small and medium-sized projects
7. Bugzero
It is a multifunctional, web-based bug management and tracking system that runs under the browser (browser). and defects in the hardware system. BUGZERO is also a complete service management software, including integrated Help Desk process management (Help Desk), which can be used to record various daily affairs, change requests, and problem reports, and track and process various customer inquiries, feedback, and comments.
8. BugTracker
9. UR Tracker
10.KisTracker
11.TestLink
12 、 JTrac
13 、 BugNet
14、BugOnline
15、eTraxis
6. Test Cases vs Defect Reports
1. The effect is different. Test cases are used to guide testing and defect reports are mainly used to locate problems.
2. Test cases are written by testers to testers, while defect reports are written by testers to developers.
3. The content of test cases and defect reports are different.
Seven, the purpose of defect management
1. Ensure the consistency of information
2. Ensure that defects are effectively tracked, shorten communication time and improve resolution efficiency.
3. It is beneficial to defect analysis, product quality measurement, and to strengthen the visualization of the project.
8. Defect status
New-------Initial state of the defect
Open------- developers start to modify
Fixed------ the developer has modified it
Reopen-----regression test failed
Closed-----regression test passed
postpone------ postponed revision
rejected------ The developer thinks it is not a problem and refuses to modify it.
duplicate-----repeated with a bug that has already been submitted
abandon-------rejected or duplicated by development and confirmed by testers that it is not a problem
9. Evaluation Criteria for Defects
1. The software does not implement the functions required by the requirements specification ( SRS)
2. The software does not achieve the goals that the requirements specification ( SRS) does not explicitly mention but should achieve
3. The software has errors that the requirements specification ( SRS) indicates should not occur
4. The software implements functions not mentioned in the requirements specification ( SRS)
5. The software is hard to understand, hard to use, slow, or from a test engineer's point of view - which end users would consider bad
10. Question list process
The picture comes from Baidu
