Test script processing device, system and method

Abstract

The invention discloses a test script processing device, system and method. The test script processing device comprises a data structure acquisition device, a script generation device and a script editing device, wherein the data structure acquisition device is used for acquiring interface information and a data structure of a script from an external server, the script generation device is used for generating a script file frame and padding data according to the interface information and the data structure, and the script editing device is used for editing the script file frame padded with the data to a test script file. Or, the test script processing device comprises a script conversion device, a source code compiling and loading device and a parsing and invoking device, the script conversion device is used for receiving the test script file and converting the test script file into program source codes of the test script file, the source code compiling and loading device is used for performing compiling processing on the program source codes of the test script file, and the parsing and invoking device is used for parsing and invoking the program source codes subjected to compiling processing, and interacts with a to-be-tested system to acquire an execution result of the test script file. By the device, system and method, compilation test efficiency of the test script can be improved, and value of script reutilization can be increased.

Description

technical field [0001] The invention relates to the technical field of software testing, in particular to a test script processing device, system and method. Background technique [0002] Software testing can be carried out in interface-driven or program-driven mode. Unit test and integration test need to simulate the calling process of the program to implement the test, which needs to be driven by program-driven mode. With the expansion of the software system, the size of the development team becomes larger, and the system becomes more and more complex. The unit test and integration test of the interface are more important and account for a larger proportion of the work. The test work also tends to become independent and become a separate work. People with a business background but not a technical background are involved. [0003] Common recording and playback methods to record scripts can usually only record interactive actions or interactive data generated by the interfa...

AI Technical Summary

Problems solved by technology

With the expansion of the software system, the size of the development team becomes larger, and the system becomes more and more complex. The unit test and integration test of the interface are more important and account for a larger proportion of the work. The test work also tends to become independent and become a separate work. Participation of people with business background but not technical background

[0003] Common recording and playback methods to record scripts can usually only record interactive actions generated by the interface, or interactive data, which cannot meet the testing needs of systems that do not support recorded data

If you use the common method of manually writing program scripts or source codes in the industry, the work will be difficult, the work efficiency will be low, the style will be difficult to maintain consistency, and the maintainability will be reduced.

According to the characteristics of the test implementation process, the test of a program component can essentially be considered as multiple sets of "key-value" as parameter input and information return, requiring users to be familiar with programming, and manual work is required for the message structure or data structure of the interface The work of compilation, the code compiled by hand is not conducive to the use of computer programs to achieve synchronous changes in data structures

If the message structure or data structure is relatively large and complex, the compilation work will be labor-intensive, time-consuming, error-prone, and occupy a high proportion of the test workload.

Therefore, the original method of manually weaving test scripts has high development costs and low reuse value, and it is difficult to meet the needs of a large number of interfaces, frequent changes, and rapid testing.

Images