Page 178 - SOFTWARE TESTING & QUALITY ASSURANCE

Unit 11: Test Case Planning

Figure 11.11 shows the bug closing dialog box.

Figure 11.11 A sample Bug Report, Ready for closing

Source: Mantis Bug Database Images Courtesy of Dave Ball and HBS International, Inc.
A bug-tracking database helps to organize the entire project team. By using a bug-tracking database,
testers can communicate the status of the project, know who is assigned what task, and most
importantly, assure that no bug slips occur.

Microsoft Access and Bugzilla are very popular bug tracker databases. FogBugz
is another example.

11.3 Summary

• Test planning is the basic test documentation that contains the record of the testing effort.
• The goal of a test plan is to facilitate communication between the tester and programmer. Both
cannot work in isolation.

• The IEEE Standard 829 for Software Test Documentation states that the purpose of a software test
plan is to prescribe the scope, approach, resources, and schedule of the testing activities.
• To plan the test stages, the test team analyzes the selected development model and decides
whether certain stages of testing should be performed during the course of the project.
• The testing schedule outlines the duration of each test that will be performed on the module.
• The four features that make it necessary to plan the test cases are its organization, repeatability,
tracking, and proof of testing.

• Test design specifications are used to organize and describe the testing that needs to be performed
on a specific module.
• The main aim of a bug report is to let the programmer know that some part of the software is not
giving the expected result.

• Bug tracking and reporting can be carried out manually or by using automated tools.

LOVELY PROFESSIONAL UNIVERSITY 171