| 1: | What are the four reasons for test case planning? |
| A1: | Organization, repeatability, tracking, and proof of testing. |
| 2: | What is ad hoc testing? |
| A2: | Ad hoc testing is testing without a plan. It's easy and fun but it's not organized, it's not repeatable, it can't be tracked, and when it's over, there's no proof that it was ever done. |
| 3: | What's the purpose of a test design specification? |
| A3: | The purpose of the test design spec is to organize and describe the testing that needs to be performed on a specific feature. It outlines the features to be tested and the approach to be used. It identifies the test cases, but doesn't specify them, and what the pass/fail criteria is. |
| 4: | What is a test case specification? |
| A4: | This document defines the actual input values used for testing and the expected outputs. It also lists any special environmental needs or procedure requirements and any inter-dependencies among test cases. |
| 5: | Other than a traditional document, what means can you use to present your test cases? |
| A5: | Tables, matrices, lists, graphical diagramswhatever means most efficiently presents the test cases to you, other testers, and other members of your product team. |
| 6: | What's the purpose of a test procedure specification? |
| A6: | The purpose of the test procedure spec is to identify all the steps required to perform the test cases, including how to set up, start, run, and shut down the test. It also explains what to do in case the test doesn't go as planned. |
| 7: | At what level of detail should test procedures be written? |
| A7: | That's a question without a specific answer. It greatly depends on who will be using the procedures. Too little detail makes the test procedures ambiguous and variable. Too much detail can bog down the test process. The level of detail should be set by the industry, the company, the project, and the test team. |
