1.1 What is the test case
1.1.1 Test Case
1) software testing software quality management is the most practical action, but also the most time-consuming one. One based on consideration of the time factor, the software must be able to conduct testing be quantified in order to further allow management to grasp the testing process required, and the test case is to test the behavior of specific quantitative methods
2) Simply put, is to design a test case, the software program in this case, must be able to function properly and achieve the expected results of the program designed, if the program does not run correctly in this case, and this problem recurring, it means the software programs have already detected the software is defective, this time it must be marked this issue, and to inform software developers. Upon notification of software developers, this issue will modify completed within the next test version
3) After the software test engineer I made a new test version, you must use the same use cases to test this issue, make sure that the problem has modifications are complete. This process is called "back test or retest"
4) sentence memory: a test case for a particular target and prepared a set of test inputs, execution conditions and expected results, in order to test a program path or to verify whether to meet the needs of a particular
1.2 Test Case Features
1.2.1 The benefits of using test cases are now mainly the following aspects
- Before starting the test design a good test case, avoid blind test and improve test efficiency
- Software testing test cases to make use of the implementation of focused, purposeful
- Just a small part of the amendment after the test version of the software update can expand testing, reduce the work intensity, shorten the project cycle
- Universal function modules and reuse of the software easy to develop, but generic test case and reuse of software will make the test easy to carry, and with the continuous refinement of its efficiency test cases rising
- Test case design forms the basis for the development and testing process. Number of "depth" and the test is proportional to the test. Since each test case reflects the different scenarios, conditions or events via the product stream, therefore, with the increase in the number of test cases, confidence in the product quality and testing process also will enhance
- The number of test cases and test workload is proportional. According to a comprehensive and refined test cases can be estimated more accurately each successive phase of the test cycle schedule
- The type of test design and development and the resources needed are mainly controlled by the test case
- Test commonly classified according to the type of test or a test requirement which they are affiliated, and will accordingly vary with the type and requirements. The best solution is prepared for each test needs at least two test cases: - kind of test case for proving that the requirements have been met, called positive test; another kind of test cases reflect an unacceptable, abnormal or accident conditions or data for demonstration only needs to meet the conditions required in this test called a reverse test ,,
1.3 The purpose of the test case
1.3.1 The purpose of the test case design
1) Effectiveness: test cases are important reference testers during the test. Different testers should be consistent based on the output of the same test cases obtained, for accurate test case planning, execution and tracking is a testament to the effectiveness of the test
2) reusability: good test reuse has a function such that the test process more effective ,, Therefore, a good design will greatly reduce test time and improve the test efficiency
3) Easy organization: Even small projects, there may be thousands or even more test cases, test cases may be created and used in the testing process for months or even years, the correct test plan will be these good people to organize test cases and made available to testers or other items of reference and effective use
4) can be evaluated: the project management from the perspective of the test, the test is to ensure that the pass rate test code quality. Often said code quality is not high or very good quality of the code, quantitative criteria should be the test case pass rate and the number of software errors
5) Manageability: test test test can also be used as staff progress, workload and efficiency of tracking / management testers of factors, in particular, it is more suited to testing of new testers, which is more reasonable and make arrangements for testing plan
1.4 Description of test cases
1.4.1 A standard test case should contain the following
- Identifier: illustrated by the test design process description and test procedures referenced unique identifier
- Test Item: characteristics are described in detail in the test code module should test characteristics than the description set forth in more specific. If the test design specification refers to "adding function calculator program," then the test case will be explained accordingly referred to "the upper limit of the addition operation overflow handling." It is also noted that other designs referenced product specification or test cases are based file
- Input Description: The description of all the input content or conditions include test case execution. If the test calculator program, enter a description may be as simple as "1 + 1." If the test cellular telephone exchange software, enter a description may be hundreds of input conditions. If the test file-based product, enter a description may be described in the file name and content
- Output Description: test described for the expected results. For example, 1 + 1 equals 2 it? Cellular software in thousands of output variable settings correct? As expected the entire contents of the file to read it
- Environmental requirements: refers to the implementation of test cases necessary hardware, software, test tools, and other personnel
- Special requirements: describe the implementation of the special requirements of test required. WordPad test procedures may not need any special conditions, but some special test software (such as nuclear power plant software) have special requirements
- Dependencies between use cases: if a test case depends on other use cases, affected or other use cases, it should be noted here
1.5 Test Case Notes
1) Do not design "exhaustive test case"
2) to find a balance in the detailed test cases and test effective time
3) a good test case should be more concerned about "reverse test question"
4) test case library should be constantly updated and maintained
5) test cases can be reused, but pay attention to the validity of the data and Environmental Change
6) test is designed, not to write out
7) more to learn and experienced test engineers, test cases are designed
8) for different types of requirements and test objects, flexible design approach using different test cases