Page 177 - SOFTWARE TESTING & QUALITY ASSURANCE

Software Testing and Quality Assurance

Figure 11.10 shows the dialog box used when a bug is resolved by a
programmer or project manager.

Figure 11.10 A Sample Dialog Box used when a Bug is
Resolved by a Programmer or Project Manager

Source: http://www.bug-track.com/bugs/editBugs.do?action=Edit&key=148950&drill=&drill_key=null&Section=
resolution&user_query_key=main&FromNavURL=&FromNav=&itemsOffSet=&scrollLoc=0#
Several bug reporting and tracking databases track not just comments about the fix, but also details of
what exactly the programmers did to make the fix. Herein, the line number, the module, and even the
type of error can be recorded.
After a bug is resolved, it is given back to the tester for closing. Hence one will have a bug report
containing the entire test history for review.
As the database has tracked every alteration to the bug report since it was opened, it helps to view the
decisions that were made along the way and review what was fixed. It is possible that the bug was not
fixed as expected, possibly a similar bug had been found and added by another tester, or maybe the
programmer made a comment about the fix being risky. All this information will assist when a retest of
the bug is done to make sure it is fixed. If it is found that it is not fixed, the bug is reopened to start the
life cycle all over again.

170 LOVELY PROFESSIONAL UNIVERSITY