An important part of software testing: Bug Management Process

The main purpose of software testing is to discover software errors (bugs,

Will directly affect the test results. Software errors can be eliminated only when errors are handled correctly, quickly, and accurately.

The software to be released meets the design objectives. In the actual software testing process, every bug must be tested and confirmed.

Management processes such as identification, repair, and verification are an important part of software testing.

Error Tracking Management System

To correctly track the handling process of each software error, each error found in the software test is usually recorded

Enter the specified Error Tracking Management System.

Currently, the existing defect tracking management software includes compuware's trackrecord software (commercial software ),

Mozilla's buzilla software (Free Software), as well as domestic BMS software for micro-invasive companies.

And can be selected based on the actual situation. Of course, you can also develop defect tracking software by yourself, such

Or clearquese development defect tracking management software.

As a defect tracking management system, you need to correctly design the field content containing information for each error and record the error

Process all information. The field content may include the test software name, test version number, tester name, and test case.

Module, test software and hardware configuration environment, identify software error types, error severity levels, detailed steps, necessary attached

Figure, test annotation. The processing information includes the handler name, processing time, processing steps, and the current status of the error record.

Correct database permission management is an important consideration for the Error Tracking Management System. It is generally necessary to ensure that errors are added.

Cannot be deleted from the database.

Software Error status

New information (new): Software defects newly reported in the test;

Open: confirmed and assigned to relevant developers for handling;

Fixed: The developer has completed the fix and is waiting for verification by the tester;

Declined: reject the defect modification;

Deferred: an error that is not fixed in the current version. It is fixed in the next version.

Close: the error has been fixed;

General Bug Management Process

The tester submits a new bug to the database and the error status is new.

The advanced tester verifies the error. If it is confirmed that it is an error, assign it to the corresponding developer and set the status to open. For example

If it is not an error, it is rejected and set to declined.

A bug whose query status is open. If it is not an error, the status is declined. If it is a bug, the bug is fixed.

The union status is fixed. For bugs that cannot be solved, leave a text description and keep the bug open.

For bugs that cannot be solved or solved by extension, developers cannot decide by themselves. Generally, they must pass a certain meeting (Review

Yes.

The tester queries the bug whose status is fixed and then verifies whether the bug has been resolved. For example, if the bug status is fixed

Closed. If it is not resolved, set the status to reopen.

Key Points of software error process management

To ensure the correctness of errors, testers with extensive testing experience are required to verify whether the error is true.

The test steps are accurate and can be repeated.

The processing information should be retained for each error handling, including the processing NAME, time, processing method, processing opinion, and bug.

Status.

A denial or extension error cannot be determined by the programmer. It should be jointly determined by the Project Manager, test Manager, and design manager.

Yes.

After the error is fixed, it must be verified by the tester who reported the error and confirmed that the error has been fixed before the error can be disabled.

Enhance the communication between testers and programmers. For some errors that cannot be repeated, ask the testers to add detailed tests.

Test steps and methods, as well as necessary test cases.