On the other hand, test cases that are open to interpretation are not repeatable and can require debugging, consuming time that would be better spent on testing. Detailed test cases are more time-consuming to develop and maintain. This is particularly important if you plan to compare the results of tests over time, such as when you are optimizing configurations.
In addition, detailed test cases are reproducible and are easier to automate than descriptive test cases. Most organizations prefer detailed test cases because determining pass or fail criteria is usually easier with this type of case.
In descriptive test cases, the tester decides at the time of the test how to perform the test and what data to use. In detailed test cases, the steps describe exactly how to perform the test. Organizations take a variety of approaches to documenting test cases these range from developing detailed, recipe-like steps to writing general descriptions. Test cases should be written by a team member who understands the function or technology being tested, and each test case should be submitted for peer review.
Special hardware requirements, such as a modem.Figure 2.10 illustrates the point at which test case design occurs in the lab development and testing process. You need to develop a test case for each test listed in the test plan. Whereas the test plan describes what to test, a test case describes how to perform a particular test. Home » Test Cases » Designing Designing Test CasesĪ test case is a detailed procedure that fully tests a feature or an aspect of a feature. WinRunner LoadRunner Test Director Silk Test Test Partner