Test file generation method and system, server and storage medium

Abstract

The invention discloses a test file generation method that comprises the steps of reading interface information from a database; generating a first template based on the csv parameter; generating a second template based on the interface dependence identifier; generating a third template based on the assertion verification; and splicing the first template, the second template and / or the third template to generate a test script file. According to the method and the system of the invention, the template is set, and the locust file execution script is automatically generated according to the interface information and the template, so that the interface information, the interface parameters, the performance weight and the interface test task can be conveniently multiplexed, the locust script file is automatically generated, and a performance scene test in a certain range is carried out. The working efficiency of interface data testing, performance scene designing and script editing is effectively improved, and the effects of reducing development cost and saving script maintenance time are achieved.

Description

technical field [0001] The embodiment of the present invention relates to the field of computer technology, in particular to a method, system, server and storage medium for generating a test file. Background technique [0002] Usually, when people use the Locust open source performance testing tool for related performance testing, it is necessary for the tester to manually write the locust script file according to the test scenario, related interfaces, and parameterization. Since manually written scripts cannot form a certain test case reuse. [0003] When performing performance testing by manually writing scripts, a new locust file needs to be rewritten every time based on relevant data such as interface information, interface parameters, and performance request proportions, which cannot better meet the needs of the testing team for agile performance testing, but The following problems will appear during the testing process. For example, the number of interfaces is huge, a...

AI Technical Summary

Problems solved by technology

Since manually written scripts cannot form a certain test case reuse

[0003] When performing performance testing by manually writing scripts, it is necessary to rewrite new locust files based on relevant data such as interface information, interface parameters, and performance request ratios each time, which cannot better meet the needs of the testing team for agile performance testing, but The following problems will appear during the testing process. For example, the number of interfaces is huge, and writing automated test cases for interfaces will consume a lot of human resources, and the writing of similar interface use cases is basically copy-pasted and then adaptively modified. The work is relatively boring. In addition, when the interface When the document writing is relatively simple and the code logic description is incomplete, the manual communication cost of writing automated test cases will be very high. Finally, due to the deviation of the script style and test focus written by different testers, it will cause difficulty in use case maintenance and incomplete test functions. At the same time, it takes a lot of time to manually generate the corresponding locust executable file because of the complexity and diversity of performance test scenarios, the construction of test parameters, and the reading structure.

Images