Analysis of individual test runs comprises output examination and software bug detection as a part of the test implementation activities.
As soon as defects are detected, extra analyses are typically conducted by software developers to diagnose the trouble and locate the faults that caused the failures for defect elimination.
This activity consists of such stages:
- Comprehension of the defect with the help of studying the implementation record
- The possibility to refresh the equal trouble scenario and monitor the equal trouble. It is significant to confirm the defect and rule out possibilities of transient troubles due to environmental disturbances or user errors. It also provides input to diagnose the reasons of the defects.
- Defect diagnosis to check what type of defect it is, and its possible reasons. This can involve analyzing the records and using some diagnostic tools or extra test runs to zoom in on possible reasons or to remove other possibilities.
- Fault locating, to detect the precise location of fault based on data from the previous steps and information about the software product.
- Software bug correcting, to correct the located fault by adding, eliminating or fixing some parts of the code. It happens so that design and requirement modifications could also be triggered or propagated from the modifications due to logical linkage among the various software elements.
As soon as an integrated fix is available, the failed test cases were re-run to verify the fix. If it is successful, the normal test implementation continues; if not – another round of software bug correcting is beginning anew.
- No Related Posts