Automatic generation method for software test case

Abstract

An automatic generation method for a software test case comprises the following steps: establishing multiple predetermined case generation specification modules and combinational algorithms; inputting at least one test parameter value according to test demands to create an extensible markup language (XML) file; reading in the XML file and selecting test parameters and corresponding combinational algorithms; establishing multiple valid parameter test cases and multiple invalid parameter test cases with the multiple predetermined case generation specification modules according to the test parameters which are read in; synthesizing the multiple parameter test cases into at least one actual test case according to the selected combinational algorithms; and outputting the actual test case as a receipt file. Therefore, testing personnel can finish output of a test case receipt automatically after creating the XML file according to the demands, workloads of the testing personnel are greatly reduced, and the universality of a test platform and the reliability of test results are improved.

Description

technical field [0001] The invention relates to computer software testing technology, in particular to a method for automatically generating software test cases. Background technique [0002] Software testing is a very important link in software engineering, especially in the testing of software interfaces, in order to ensure the stability of interfaces and the stability of the entire software program. The traditional test case writing process is mostly done manually. Due to the complexity of writing use case files and test codes, coupled with the large number of use cases and poor scalability, and the final use cases contain a lot of repeated data and are not easy to modify, the test process is time consuming. Time-consuming and labor-intensive, it may not necessarily achieve good results. [0003] For example, take the character test of the Chinese Character Internal Code Extension Specification (GBK) of the software text interface as an example. All GBK characters are ab...

AI Technical Summary

Problems solved by technology

The traditional test case writing process is mostly done manually. Due to the complexity of writing use case files and test codes, coupled with the large number of use cases and poor scalability, and the final use cases contain a lot of repeated data and are not easy to modify, the test process is time consuming. Time-consuming and labor-intensive, it may not necessarily achieve good results

[0003] For example, take the character test of the Chinese Character Internal Code Extension Specification (GBK) of the software text interface as an example. All GBK characters are about 20,000. If there are four fields in the test that require relevant test cases, according to the previous practice, It is undoubtedly a monotonous and tiring job for testers to write tens of thousands of documents manually before they can test all GBK characters

Images