Jmteter-based testing method and device, storage medium and electronic device

Abstract

The invention discloses a Jmteter-based testing method and device, and belongs to the technical field of software testing. The method includes the steps: configuring a plurality of main controllers and a plurality of controlled machines and configuring Jmteter for the main controllers and the controlled machines by Agents configured in the main controllers and the controlled machines; receiving scripts to be tested uploaded by a client; uploading the scripts to be tested to the main controllers associated with node identifiers of the controlled machines to be tested and calling the Jmteter totest the scripts to be tested; returning testing results of the scripts to be tested to a file catalog for storing the testing results, storing the testing results according to identifiers of the scripts to be tested, and checking the testing results by the client. The scripts to be tested comprise identifiers of the scripts to be tested, the node identifiers of the controlled machines to be tested and the file catalog for storing the testing results. By the method, testing efficiency can be improved.

Description

technical field [0001] The present disclosure relates to the technical field of software testing, and in particular, relates to a Jmteter-based testing method, a Jmteter-based testing device, a computer-readable storage medium, and electronic equipment. Background technique [0002] Among many types of software testing, software stress testing is also a very important kind of testing. Among them, the stress test may include testing the response speed of the software, especially testing the high concurrency and stress resistance of the software when a large number of concurrent users access within a relatively short period of time. Therefore, software stress testing can be performed on the premise of implementing stress testing when simulating high concurrent requests. [0003] At present, when performing software stress testing, it can be realized by using Jmeter to stress test the interface. Among them, Jmeter supports stress test scripts written in java, and provides a c...

AI Technical Summary

Problems solved by technology

[0004] On the one hand, when the testers use the presses, it is necessary to configure a press for each tester for each tester to use, so when there are many testers, the allocation of the presses will be cumbersome and inconvenient; on the other hand On the one hand, when the interface estimation index is large, scripts need to be transmitted to multiple presses; and each press depends on Jar and data files, and Jmeter needs to be started, stopped, and logs checked during the stress test. The steps are cumbersome and Waste of time; on the other hand, when Jmeter is not installed on multiple machines, it is necessary to manually upload Jmeter for multiple machines and configure Jmeter. Sometimes there will be version conflicts, which will cause problems in the stress test of the script to be tested; further, after Jmeter is used, sometimes the Jmeter service will be forgotten to be closed, so the next tester will need to shut down the Jmeter process again when using it; When there are too many presses, the efficiency is low; finally, when the same data file is transferred to the press, the data files of multiple presses need to be put in the same path; Therefore, it will lead to the situation that the data file cannot be used when executing

Images