四川大学软件工程课件 Unit09_2.pptVIP

*/41 OOT—Test Case Design (I) Berard [BER93] proposes the following approach: Each test case should be uniquely identified and should be explicitly associated with the class to be tested, 2. The purpose of the test should be stated, */41 OOT—Test Case Design (II) A list of testing steps should contain: a. a list of specified states for the object that is to be tested b. a list of messages and operations that will be exercised as a consequence of the test c. a list of exceptions that may occur as the object is tested d. a list of external conditions (changes in the environment external to the software) e. supplementary information that will aid in understanding or implementing the test */41 Testing Methods (I) Fault-based testing The tester looks for plausible faults (i.e., aspects of the implementation of the system that may result in defects). To determine whether these faults exist, test cases are designed to exercise the design or code. Class Testing and the Class Hierarchy Inheritance does not obviate the need for thorough testing of all derived classes. In fact, it can actually complicate the testing process. */41 Testing Methods (II) Scenario-Based Test Design Scenario-based testing concentrates on what the user does, not what the product does. This means capturing the tasks (via use-cases) that the user has to perform, then applying them and their variants as tests. */41 OOT Methods: Random Testing identify operations applicable to a class define constraints on their use identify a minimum test sequence an operation sequence that defines the minimum life history of the class (object) generate a variety of random (but valid) test sequences exercise other (more complex) class instance life histories */41 OOT Methods: Partition Testing reduces the number of test cases required to test a class in much the same way as equivalence partitioning for conventional software state-based partitioning categorize and test operations based on their ability to chang