Shulou(Shulou.com)06/03 Report--

What does a software defect (or Bug) record contain? In a traditional BugZilla, the BUG description should include the following information:

The module and BUG generate the priority of the BUG developed by the software version, the severity of the BUG may belong to the module, if not confirmed, you can use the developer to judge the BUG title, need a clear description of the phenomenon BUG description, need to give the steps of re-Bug as far as possible, the BUG attachment can give the relevant logs and screenshots.

The tracking process of the BUG management tool and the status of the bug: during the period between the discovery of a bug and the shutdown of the bug, bug may have the following states: new, open Postpone,Pending Retest,Retest,Pending Reject,Reject,Deferred,closed.

New (new)-assign-R & D revision-Test confirmation-close.

New: (new)

When a "bug" is found (for the first time), the tester needs to communicate with the project leader to confirm that it is indeed a bug, if it is identified as a bug, record it, and set the status of the bug to New.

Assigned (assigned)

When a bug is referred to as a New, it will be given to the developer, and the developer will confirm whether it is a bug. If so, the head of the development team assigns the bug to a developer and sets the status of the bug to "Assigned"

Open (open)

Once the developer starts working on the bug, he or she sets the status of the bug to "Open", which means that the developer is working on the "bug"

Fixed (fixed)

After the developer has processed it (and thinks it has been resolved), he or she can set the status of the bug to "Fixed" and submit it to the head of the development team, who then returns the bug to the test team.

Pending Reset (to be tested)

When bug is returned to the test group, we set the status of bug to "Pending Reset"

Reset (retest)

The leader of the test group assigned bug to a tester for retesting, and set the status of bug to "Reset"

Closed (closed)

If the tester confirms that the bug has been resolved after testing again, set the status of the bug to "Closed"

Reopen (opened again)

If, after a second test, it is found that the bug (which refers to the bug itself rather than the new bug caused by the fix) still exists, the tester passes the bug to the development team again and sets the status of the bug to "Reopen"

Pending Reject (rejecting)

If the bug passed by the tester to the development team is considered normal behavior by the developer rather than bug, the developer can reject it and set the status of the bug to "Pending Reject"

Rejected (rejected)

When the leader of the test team receives the above bug, if he or she finds that this is the normal behavior defined in the product specification or after discussion with the developer that it does not count as bug, the leader of the development team sets the status of the bug to "Rejected".

Postponed (deferral)

Sometimes, the testing of some special bug needs to be shelved for a period of time, in fact, there are many reasons that may lead to this situation, such as invalid test data, some special invalid functions and so on. In this case, the state of bug is set to "Postponed".

Deferred (deferred)

In some cases, some special bug is not so important and can be eliminated. At this time, we can set the status of bug to "Deferred".

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.