定义 测试用例（Define test cases）.docVIP

定义 测试用例（Define test cases） 2. to make end-users satisfied with the software, the most powerful move is to articulate the expectations of the end users in order to verify and confirm the validity of these expectations. The test case reflects the requirements to be verified. 3. since it is possible (or not necessary) to verify all requirements, then whether the most appropriate or critical requirements for testing can be determined is related to the success or failure of the project. The selected requirements to be verified will be the result of these three trade-offs in terms of costs, risks, and the need to verify the requirements. 4. a major measure of whether testing is complete is demand based coverage, which is based on the number of test cases that are identified, implemented, and / or executed. As follows: 95% of the key test cases have been implemented and validated, far more than we have completed 95% of the test more meaningful. 5. test cases are usually categorized according to the test type or test requirements of their associated relationships, and will change accordingly with type and requirements. The best solution is to work out at least two test cases for each test requirement: A test case is used to demonstrate that the requirement has been met, often referred to as a positive test case; Another test case that reflects an unacceptable, unusual, or unexpected condition or data that is used to demonstrate that the requirement can only be met on the required conditions. This test case is called a negative test case. 6., we can use the basic methods of software testing, such as equivalence partitioning, boundary value analysis, error guessing, causality diagram and logical covering method, to design test cases. Related problems 1, the review of test cases is the criterion of software testing, but it has not become a criterion once it has been compiled. In the design process, the test cases should be organized to check each other at the same level. After