To avoid such a cumbersome activity spreadsheets and databases can be used to

To avoid such a cumbersome activity spreadsheets and

This preview shows page 173 - 178 out of 216 pages.

To avoid such a cumbersome activity, spreadsheets and databases can be used to record the status of bugs.
Image of page 173
Software Testing and Quality Assurance LOVELY PROFESSIONAL UNIVERSITY 168 Automated Bug Reporting and Tracking The IEEE 829 standard can serve as a guideline while using automated systems for bug reporting and tracking. As seen in figure 11.9, the information related to bug tracking is filled in the form which is primarily text and numbers. This information can easily be recorded on a database. The main window of a typical bug-reporting database shows what an automated system can provide. Figure 11.8 an automated bug reporting and tracking system. Figure 11.8 A Sample Bug Reporting Database Source: Figure 11.8 illustrates a bug reporting and tracking database. A glance at the screen is enough to know the status of bugs. The bug’s description includes its type, component, priority, environment, target version, fix version, and so on.
Image of page 174
Unit 11: Test Case Planning LOVELY PROFESSIONAL UNIVERSITY 169 Figure 11.9 shows the New Bug Dialog Box, in which information is entered to record a new bug into the system. Figure 11.9 A Sample New Bug Dialog Box Source: This dialog box is typically used by the programmer to record information concerning the bug fix. A drop-down list supplies different types of bug and their status. The bug is then given back to the tester for closing.
Image of page 175
Software Testing and Quality Assurance LOVELY PROFESSIONAL UNIVERSITY 170 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: 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.
Image of page 176
Unit 11: Test Case Planning LOVELY PROFESSIONAL UNIVERSITY 171 Figure 11.11 shows the bug closing dialog box.
Image of page 177
Image of page 178

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture