Analysis of software test Case Management _ Software Testing

Absrtact: The development and maintenance of test cases is one of the important steps in the software testing process, and it is also the core influencing factor to measure the quality of software testing. This paper analyzes the process of software test case management from the aspects of development, execution and maintenance, and puts forward some relevant principles for the development and maintenance of test cases.

Keywords: Software testing, test cases

1. Test Case Development

1.1 Test Case Preparation basis

In general, test requirements are designed to achieve test objectives and what needs to be tested in the project. All activities in the software testing process can be traced back to the test requirements. For example, when you develop a test plan, the following basic elements need to be clarified: first, you need to clear the test requirements, that is, the target content of the test, then you can decide how to measure, what test method to use, how many test times you need, how many testers you need, what the test schedule is, and what the environment is. In addition, there are other factors, such as the skills and tools required in the test, as well as the corresponding professional background knowledge, the risks that may be encountered in the test, and so on, all of which combine to form the basic elements of the test plan. The important basis for a test plan is testing requirements, and everything in the test plan can be traced back to the test requirements, so testing requirements are the basis and focus of the test plan. Similarly, test scenarios, use cases, and content are based on test requirements.

Test requirements are mapped from software requirements, so the level of detail is closely related to the level of detail of the software requirements. At the time of writing, in order to ensure consistency with the software requirements, and strive to express accurate and detailed, to avoid testing omissions and misunderstandings.

Test cases should be written to cover all test requirements, and test requirements are transformed by software requirements, so the results of all test cases will eventually be traced back to the software requirements, so the test cases are written based primarily on software requirements. In addition, should also comply with the relevant writing rules, norms and so on.

1.2 Test Case Development principles

The design principles for test cases include:

1) According to the principle: the main basis of the test case preparation is the requirement specification and relevant technical specification document provided by the project;

2) The principle of full coverage: the requirements of the specification and related technical specifications required by the main function points for the full coverage of the test, requiring all functions can be normal to achieve;

3) Normative principle: All test cases of the preparation requirements of the specification, for all the function points tested, the application should be in accordance with the requirements of the specification and the relevant technical specifications in the given form, within the specified boundary value of the scope of the use of appropriate tools, resources and data to perform its functions;

4 The overall principle: testing not only for the system functional characteristics of the test, the system's other quality characteristics are also carried out a comprehensive test and evaluation.

The specific quantitative requirements that test case writing should meet include the following:

(1) The user frequently uses, relates the system core function, the high priority level function point, the test case should reach 100% coverage;

(2) For each system End-to-end function and interface with other systems testing should reach 100% coverage;

(3) test cases including normal input and normal business process testing, but also the illegal data input and exception handling testing, and the system is not normal operation of the test cases should account for the total of 20%-30%;

(4) Test cases include Chinese characteristics and system localization test, such as Chinese information display, input, query, print and report display test.

2. Test Case execution

2.1 Test case coverage of test requirements

First look at what is the test requirement overlay. Test requirements come from software requirements, and the relationship to software requirements is one-to-one, or many-to-many. If a software requirement can be converted to one or more test requirements, then the test requirements have covered all the software requirements, which can be said to test requirements of 100% coverage. But this does not indicate that the test requirements have reached 100% coverage. Because the general software requirements only clarify the dominant function and characteristics, and the recessive function and characteristics (not clearly pointed out but should have the functions and characteristics) and not directly reflected in the requirements. This part of the requirements should also be the test requirements, so in the test requirements analysis, to analyze both the explicit and implicit requirements of the software, or according to the defects found in the actual test to supplement or optimize the test requirements, and update the test cases to improve the coverage of the test requirements.

A good set of test cases should cover all test requirements. In the case of system functions, test cases include functional points and business processes. For functional points, the test cases designed need to cover the functional points in all requirements, in addition to the normal test cases, should also design the test cases of abnormal conditions, and the exception test cases accounted for the entire test case set of 20%~30%. Similarly, the test cases for business processes also include normal processes and exception processes.

......

This article is reproduced from the 51Testing Software test Network, view the full text: http://www.51testing.com/html/99/n-823199.html