创业管理（雪灵）part 5.pptVIP

Test Case Planning Overview Test Cases IEEE 829 states that the test case specification documents the actual values used for input along with the anticipated outputs. A test case also identifies any constraints on the test procedure resulting from use of that specific test case.“ Test Case Planning Overview The IEEE 829 standard also lists some other important information that should be included: Identifiers. Test item. Input specification. Output specification. Environmental needs. Special procedural requirements. Intercase dependencies. Test Case Planning Overview Test Procedures IEEE 829 states that the test procedure specification identifies all the steps required to operate the system and exercise the specified test cases in order to implement the associated test design. Test Case Planning Overview The test procedure or test script spec defines the step-by-step details of exactly how to perform the test cases. Identifier. Purpose. Special requirements. Procedure steps. Log. Setup. Start. Procedure. Measure. Shut down. Restart. Stop. Wrap up. Contingencies. Detail Versus Reality Test Case Organization and Tracking One consideration that you should take into account when creating the test case documentation is how the information will be organized and tracked. Think about the questions that a tester or the test team should be able to answer: Which test cases do you plan to run? How many test cases do you plan to run? How long will it take to run them? Can you pick and choose test suites (groups of related test cases) to run on particular features or areas of the software? When you run the cases, will you be able to record which ones pass and which ones fail? Of the ones that failed, which ones also failed the last time you ran them? What percentage of the cases passed the last time you ran them? far@ucalgary.ca 4 Part V: Working with Test Documentation Reporting What You Find Contents Getting Your Bugs Fixed Isolating and Reproducing Bugs