A method and device for generating integrated test cases

Abstract

The invention discloses a method and device for generating an integrated test case. The method includes: standardizing the output data of the pre-unit test case, converting the output data into a preset format, and obtaining the standardized output data ; Extract useful data from the standardized output data, generate standardized input data for post-unit test cases according to the useful data, and perform corresponding data filling; wherein, the format of the standardized input data is the same as that of the standardized output data The format is the same; the standardized input data is converted into a form acceptable to the post-unit test case and input into the post-unit test case. The invention can simplify the generation process of the integration test case, improve the generation efficiency of the integration test case, and reduce the maintenance cost of the test case.

Description

technical field [0001] The invention relates to the field of software testing, in particular to a method and device for generating integrated test cases. Background technique [0002] Integration testing, also called assembly testing or joint testing, refers to assembling some or all modules into subsystems or systems based on unit testing according to design requirements (such as according to structural diagrams) for testing. A certain function of the system is usually implemented by multiple modules working together. In order to verify a certain function during integration testing, these modules need to be tested together to ensure that the modules can work together according to the established intention and do not occur. conflict. [0003] Integration testing is a logical extension of unit testing. Before integration testing, unit testing needs to be completed first. In the process of testing modules such as smoke testing and unit testing, a lot of unit testing cases are...

AI Technical Summary

Problems solved by technology

However, because the input and output data of different unit test cases implement different logic standards, each unit test case has different requirements for input data, and the format and form of output data are also different. Testers need to spend a lot of time writing intermediate scripts to achieve The connection and data exchange between unit test cases, the writing of scripts is more complicated, and it is more difficult to integrate the existing unit test cases, and these intermediate scripts are composed of a large number of simple judgments. It will become more and more bloated, and the maintenance cost of the script will become higher and higher

In practice, testers often prefer to rewrite the integration test cases directly, but the rewriting of the integration test cases does not reuse the existing unit test cases, obviously the cost of writing is high and the efficiency is low; at the same time, the rewritten test cases The coverage of use cases is often not high, and its reliability is difficult to be recognized by the team

Images