Absrtact: Software Testing is a reliable means to ensure the quality of software, and is an essential part in the process of software development. This paper presents a test case design process for reuse, which provides the implementation strategy for software test case reuse. The reuse of software test cases is of great significance to shorten the software development cycle and reduce the cost of software development.
Keywords: Software testing, test cases
1. Introduction
With the development of software engineering, software testing has become an important means to guarantee the quality of software industry. The selection of test cases plays a decisive role in the success or failure of software testing, so how to design the least test cases to achieve the maximum test coverage becomes the main research object in the field of automation testing. A test case is a set of test data and processes that are most likely to find errors and that enable the system to test a function. The design of test cases is closely related to the personal experience of testers, and the differences of personal experience and writing format of different testers lead to the blindness of the test, which leads to higher maintenance costs later. The reuse technology of test cases is to solve the problems caused by the lack of experience of testers, and also avoids the duplication of work in the design test cases, and effectively improves the test efficiency.
2, Software Testing
2.1 Definition of software Testing
Software Testing (Software testing) is a carefully designed batch of test cases (including input data and its expected output) based on the specification and internal structure of the software development stages, using these test cases to run the program to discover the process of the program error.
2.2 Purpose of software testing
Glenford J.myers The following views on the purpose of software testing:
2.2.1 Testing is the process of program execution, which is to detect errors;
2.2.2 A good test case is a use case that discovers errors that have not been discovered so far;
2.2.3 A successful test is a test that reveals errors that have not been discovered so far.
The purpose of the test is to find out the potential errors and defects in the software, to improve the quality of the software by correcting various errors and defects, and to avoid the commercial risks caused by the software potential errors and pitfalls.
3. Reuse of software test cases
3.1 Reuse of software test cases
Software test reuse can be understood as the process of organizing tests over time using the same or similar test resources over two or more different software testing processes. The reuse of software testing includes the reuse of test flow, the reuse of test methods and the reuse of test cases. The reuse of test cases is the key technique in test reuse. A test case reuse is a test case that has been executed by a software to varying degrees of application in the testing of the new phase of the software or in the testing of other software. Reusable test cases are characterized by universality, independence, validity, standardization, and completeness.
3.2 Design of reusable test cases
The successful reuse of test cases depends largely on the independence of test cases, i.e. whether they can be applied independently to different applications and applications. In practical applications, there is a correlation between many test cases. The running environment of some test cases depends on the execution state of the other test case, and the reuse properties of other test cases associated with it may disappear when the environment on which it depends changes or fails. Then how to design a reusable test case that does not depend on the high independence of the software operating environment and is associated with other test cases and has a unified input-output interface is the key to the problem.
Test cases are oriented to different application objects and are highly coupled with the software being tested. In order to achieve successful reuse of the designed test cases, the following steps are taken in the design of test cases.
Common analysis of 3.2.1
First of all, we should analyze the common characteristics of the software being tested, and the software in the same application area should have similar requirements, analyze its features such as workflow or function, and exploit the reusable factors according to their commonness.
3.2.2 Test Case Unified Modeling
According to the reusable factor, design the appropriate test strategy, make the Unified modeling organization for the test case design, design the unified structure and the input and output interface.
3.2.3 Design Reusable Test Cases
In order to reduce the correlation between test case and the side software as far as possible, the test case should be designed as much as possible, while the test case should be kept in a single function. The high coupling of test cases and tested software determines that the reuse of test cases is implemented successfully in the same software regression test or version upgrade test, and it is difficult to use in software testing in different application fields.
......
This article is reproduced from the 51Testing Software test Network, view the full text: http://www.51testing.com/html/12/n-827912.html