Page 169 - SOFTWARE TESTING & QUALITY ASSURANCE

Software Testing and Quality Assurance

13. Wrap Up: Tells how to restore the environment to its pre-test condition.
14. Contingencies: Tells what to do if things do not go as planned.
It is not enough for a test procedure to direct a tester to try all the test cases and get back with the
observations. The test procedure should instruct a new tester on the way to perform the testing. A
detailed procedure helps a tester know what exactly needs to be tested and how.

Figure 11.3 shows an excerpt from a fictional example of a test procedure for
Windows Calculator.
Figure 11.3 Sample Test Procedure

Source: Ron Patton, Software Testing, Second Edition, Sams Publishing
11.1.5 Test Organization and Tracking
An important consideration that needs to be taken into account when creating the test case
documentation is the organization and tracking of information. Some questions that a tester or the test
team should be able to answer may include:
1. Which are the test cases you plan to run?
2. What is the number of test cases you plan to run? What will be the time taken to run them?

3. Can you decide on choosing the test suites (groups of related test cases) to run particular features
of the software?
4. When the test cases are run, will you be able to record pass and fail result of each test case?
5. Of the cases that failed, which ones failed the last time too?
6. What is the percentage of the test cases that passed?

162 LOVELY PROFESSIONAL UNIVERSITY