The main purpose of the software test is to discover the error (bug) of software, and will directly affect the effect of the test for the errors discovered in the test. Only correct, quickly, accurately handle these errors, can eliminate software errors to ensure that the software to be published meets the needs of demand design. During the actual software test, it is an important part of software testing for each bug, and the management process of testing, confirming, repairing, verifying, etc. Error Tracking Management System In order to properly track the process of processing each software error, each error discovered by the software test is usually found as an error tracking management system that is entered into the input. As a defect tracking management system, you need to correctly design all the contents of each error containing field content and processing information of the record error. Field content may include test software name, test version number, tester name, test event, test software, and hardware configuration environment, discover software errors, errors, detailed steps, necessary drawings, test comments. Processing information includes the current state of the handler name, processing time, processing step, error record. The correct database rights management is an important consideration of an error tracking management system, which is generally guaranteed to be deleted from the database for the added error. Software error status new information (New): Software defects in the test; Open: Open: Confirmation and assignment to related developers; fix, developers have completed corrections, waiting for testers to verify; refuse (DECLINED): Refused to modify the defect; deferred: not in the current version of the error, the next version of the repair is closed: Error has been fixed; BUG management general process tester submits a new BUG storage, error status For new. Advanced testers verify errors, if confirmed is an error, assigned to the corresponding developer, set the status as Open. If it is not an error, the rejection is set to the Declined state. The developer query status is Open's bug, if it is not an error, then the status is decloyd; if it is bug, the parallel status is fixed. The bug that cannot be resolved is to leave a text description and keep bugs for Open state. For bugs that cannot be resolved and extended, they cannot be decided by developers, usually through some conference (review will) can be recognized. The tester queries the status of Fixed, and then verifies whether the bug has been resolved, such as solving the status of the bug is Closed, if there is no resolution status as Reopen. Software Error Process Management Points In order to ensure the correctness of the error, you need to have a rich test personnel to verify that the error discovered is a true error, whether the test steps of writing are accurate and can be repeated. Each time the error is handled, processing information, including processing name, time, processing method, handling opinion, BUG status. Refused or extension errors cannot be decided by the programmer, and should be determined by the project manager, the test manager and the design manager. After the error is fixed, you must verify the testor of the report error, confirm that the error has been fixed to turn off the error. Strengthen the testers and programmers, for some unusable errors, you can provide testers to supplement the detailed test steps and methods, as well as the necessary test cases.
