CN111427793A - Automatic Jmeter script generation method - Google Patents
Automatic Jmeter script generation method Download PDFInfo
- Publication number
- CN111427793A CN111427793A CN202010248488.5A CN202010248488A CN111427793A CN 111427793 A CN111427793 A CN 111427793A CN 202010248488 A CN202010248488 A CN 202010248488A CN 111427793 A CN111427793 A CN 111427793A
- Authority
- CN
- China
- Prior art keywords
- keywords
- jmeter
- keyword
- parameter
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000013515 script Methods 0.000 title claims abstract description 72
- 238000000034 method Methods 0.000 title claims abstract description 25
- 238000012360 testing method Methods 0.000 claims abstract description 33
- 238000012795 verification Methods 0.000 claims abstract description 23
- 238000004806 packaging method and process Methods 0.000 claims abstract description 10
- 238000011056 performance test Methods 0.000 claims description 23
- 230000005540 biological transmission Effects 0.000 claims description 10
- 238000012546 transfer Methods 0.000 claims description 4
- 230000000007 visual effect Effects 0.000 claims description 2
- 235000014510 cooky Nutrition 0.000 claims 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/31—Programming languages or programming paradigms
- G06F8/315—Object-oriented languages
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Stored Programmes (AREA)
Abstract
The invention relates to the technical field of software performance testing, in particular to a method for automatically generating a Jmeter script, which comprises the following steps: s1: packaging a Jmeter script keyword; s2: setting a test strategy; s3: selecting keywords and configuring parameters; s4: checking the keywords and the parameters thereof; s5: checking context association; s6: data compliance verification; s7: a Jmeter script is generated. The method described by the invention can quickly and accurately automatically generate the Jmeter script and improve the readability and comprehensibility of the script configuration.
Description
Technical Field
The invention relates to the technical field of software performance testing, in particular to a method for automatically generating a Jmeter script.
Background
As a popular performance testing tool, the meter tool is increasingly applied to performance testing of various servers, software systems, software interfaces, and the like. The test script is the basis of performance test, and the complete Jmeter script at least comprises test plan, thread group, external parameterized file, HTTP request, request response reading, result report and the like. Meanwhile, due to the diversity and variability of the test requirements, the test script is changed accordingly. Generally, the performance test scripts are manually compiled by performance testers, and because the experience and the technical capability of the performance testers are greatly different and a large number of professional terms and skills which are difficult to master exist in a Jmeter tool and the scripts, the manually compiled Jmeter scripts often have a lot of errors when the performance test is actually executed, so that the efficiency is low and even the expected performance test cannot be completed.
In order to solve the above problems, some methods or auxiliary tools for semi-automatically generating a Jmeter test script exist in the prior art, which can improve the writing rate of the Jmeter script to some extent, but cannot automatically generate a complete Jmeter test script, and still need to be developed and adjusted secondarily in a Jmeter GUI tool. In addition, because a large number of error reports may exist in the Jmeter script generated by semi-automation or the Jmeter tool is incompatible, the efficiency of compiling and generating the Jmeter script is not high, the automatic test script with accuracy, completeness and high flexibility cannot be generated, and the difficulty of compiling the Jmeter script is not reduced.
Disclosure of Invention
In order to overcome the problems in the prior art, the invention aims to provide an automatic Jmeter script generation method, which solves the problems in the prior art.
The technical scheme adopted by the invention is as follows: a method for automatically generating a Jmeter script comprises the following steps:
s1: packaging a Jmeter script keyword;
s2: setting a test strategy;
s3: selecting keywords and configuring parameters;
s4: checking the keywords and the parameters thereof;
s5: checking context association;
s6: data compliance verification;
s7: a Jmeter script is generated.
Further, the Jmeter script keywords encapsulated in step S1 include a test plan, an execution plan, an http ookie manager, an http request default, an http request, a transaction (scene) controller, a simple controller, a conditional branch controller, a cycle controller, a regular expression, a csv file generation, a csv file uploading, and a back-end listener;
further, in step S2, the test policy is set as: defining a performance test scene, and determining a performance test range and a test strategy according to requirements, wherein the test strategy comprises the number of concurrent users, execution time (times), set time, a concurrent user growth mode and the like;
further, step S3 is to combine the performance test scenario defined in step S2, select the Jmeter keyword packaged in step S1, and perform parameter configuration on the selected keyword according to the requirement in step S2;
step S4 further includes verifying keywords and their parameters including keyword validity, mandatory keyword parameter verification, content validity, and checking whether the selected keyword is necessary for the whole Jmeter script, and giving clear and definite prompts and suggested values for items that fail to be verified;
further, the context association check of step S5 is a performance test scenario context association check, which includes checking the front-back order of http requests and the validity of parameter transmission when parameter data transmission between multiple http requests exists;
step S6 is further described as a performance test scenario data compliance check, which includes performing a validity check on a data source corresponding to a field that needs parameterization in the http request, and simultaneously performing a check on the validity of uploaded or generated csv file data and whether the data is introduced by the http request;
further, step S7 is to generate a Jmeter script according to the keywords selected in step S3 and the configured parameters, after the verification in steps S4 to S6, generate a Jmeter script for the keywords passing the verification according to the Jmeter script specification, where the generated script file is jmx file, and if step S3 selects uploading csv and generates csv file, and after the verification in step S6, the generated file also includes csv file.
In step S1, during the process of packaging the keyword, the user-defined keyword name corresponds to the operation of the meter, and meanwhile, the parameter of the meter is extracted and the parameter value is preset as the parameter and the parameter data of the packaged keyword.
In step S2, after the test policy is set, a growth trend graph of the number of concurrent users is automatically generated as a visual reference.
After selecting the keywords and configuring the parameter values of the keywords in step S3, step S4 is automatically performed, and the verification result is fed back to the current configuration page, and step S3 can be repeatedly performed to select a plurality of keywords.
Further, the keywords in step S3 support parent-child relationship keywords, that is, one keyword may include multiple child keywords as a group of keywords, and the http request keyword in step S3 is batch imported through formatted files such as external excel files, csv files, json files, and the like, and the imported http request keyword includes parameters and parameter data in the http request keyword.
Further, the validity of the keywords in step S4 includes whether the selected keywords correspond to the keywords packaged in step S1, whether the parameters of the keywords and the requirements of the parameters correspond to the parameters of the keywords packaged in step S1, whether the keyword parameters are required to be verified as the keywords that have been configured with data satisfy the minimum parameter set of the keywords preset in step S1, whether the content validity is verified as the data form that the configured keyword parameter data satisfy the requirements of the Jmeter, and meanwhile, the security, validity, and compliance of the data are verified, whether the keywords necessary for the Jmeter script are selected as the minimum set of the keywords necessary for performing a complete and successful performance test using the Jmeter, and meanwhile, the necessary keywords are set according to the actual requirements.
The context correlation check in step S5 is performed after the execution of steps S3 and S4 is completed, and the parameter transfer between http requests includes the transfer of parameter data by two or more interfaces.
Further, in step S6, the checking the validity of the data source corresponding to the field that needs parameterization in the http request includes checking whether the parameterized parameter data source is set for the http request, and checking the validity, consistency, and compliance of the parameterized parameter data source, and at the same time, checking whether the uploaded or generated data field of the csv file corresponds to the parameterized parameter of the http request, and at the same time, checking the validity and compliance of the csv file data.
Further, if the file generated in step S7 is a single jmx file, it is directly saved in the folder designated by the host in the form of jmx file, and if the file includes jmx file and csv file in step S7, it is saved in the folder designated by the host in the form of compressed package.
The invention has the beneficial effects that: by the automatic generation method of the Jmeter script, firstly, a Jmeter tool and a necessary environment thereof do not need to be installed when script contents are configured, and the dependency of writing the Jmeter script on the tool and the environment is eliminated; secondly, the configuration of script key parameters and data is realized through simplified user-defined key words, and meanwhile, the configuration of related data can be quickly completed due to the fact that partial data values are preset in the key words; moreover, the parameter data values of all the keywords are subjected to conformance verification, so that script errors caused by data and parameter configuration errors are avoided; meanwhile, the context association and the parameterized data source of the script are verified while the script is generated, so that execution failure and error report caused by data missing during script execution are avoided.
The method described by the invention can quickly and accurately automatically generate the Jmeter script and improve the readability and comprehensibility of the script configuration.
Drawings
FIG. 1 is a flow chart of the method steps of the present invention.
Detailed Description
The invention is described in detail below with reference to the following figures and detailed description:
a method for automatically generating a Jmeter script comprises the following steps:
s1: packaging a Jmeter script keyword;
s2: setting a test strategy;
s3: selecting keywords and configuring parameters;
s4: checking the keywords and the parameters thereof;
s5: checking context association;
s6: data compliance verification;
s7: a Jmeter script is generated.
Further, the Jmeter script keywords encapsulated in step S1 include a test plan, an execution plan, an http ookie manager, an http request default, an http request, a transaction (scene) controller, a simple controller, a conditional branch controller, a cycle controller, a regular expression, a csv file generation, a csv file uploading, and a back-end listener; packaging Jmeter keywords by using languages such as Java, Python and the like, and setting keyword names and parameter names for the packaged keywords; setting key word attributes such as key word grouping marks, whether key words are necessary or not and the like according to actual requirements; multiple operations in the meter can be packaged as the same key or group of keys if desired.
Further, in step S2, the test policy is set as: defining a performance test scene, and determining a performance test range and a test strategy according to requirements, wherein the test strategy comprises the number of concurrent users, execution time (times), set time, a concurrent user growth mode and the like;
further, step S3 is to combine the performance test scenario defined in step S2, select the Jmeter keyword packaged in step S1, and perform parameter configuration on the selected keyword according to the requirement in step S2;
step S4 further includes verifying keywords and their parameters including keyword validity, mandatory keyword parameter verification, content validity, and checking whether the selected keyword is necessary for the whole Jmeter script, and giving clear and definite prompts and suggested values for items that fail to be verified;
further, the context association check of step S5 is a performance test scenario context association check, which includes checking the front-back order of http requests and the validity of parameter transmission when parameter data transmission between multiple http requests exists;
step S6 is further described as a performance test scenario data compliance check, which includes performing a validity check on a data source corresponding to a field that needs parameterization in the http request, and simultaneously performing a check on the validity of uploaded or generated csv file data and whether the data is introduced by the http request;
further, step S7 is to generate a Jmeter script according to the keywords selected in step S3 and the configured parameters, after the verification in steps S4 to S6, generate a Jmeter script for the keywords passing the verification according to the Jmeter script specification, where the generated script file is jmx file, and if step S3 selects uploading csv and generates csv file, and after the verification in step S6, the generated file also includes csv file.
Preferably, the keywords packaged in step 1 are the minimum set meeting performance tests, and other keywords can be packaged and expanded according to actual requirements; the keyword name is a suggested name, and can be freely appointed according to actual requirements; the keyword parameter is a minimum set required in the meter or an optimized set meeting the minimum set, and can be expanded according to actual requirements; the preset value of the keyword parameter is a suggested value, and other values or no preset value can be specified according to actual requirements; packaging Jmeter keywords by using languages such as Java, Python and the like, and setting keyword names and parameter names for the packaged keywords; setting key word attributes such as key word grouping marks, whether key words are necessary or not and the like according to actual requirements; multiple operations in the meter can be packaged as the same key or group of keys if desired.
Preferably, in step 2, after the test strategy is set, a growth trend graph of the number of concurrent users is automatically generated as an intuitive reference.
Preferably, the keywords in step 3 support parent-child relationship keywords, that is, one keyword may include a plurality of child keywords as a group of keywords; the http request keyword in the step 3 may be imported in batch through formatted files such as external excel files, CSV files, json files, and the like, and the imported http request keyword includes parameters and parameter data in the http request keyword.
Preferably, after selecting the keywords and configuring the parameter values of the keywords in the step 3, automatically performing the actions listed in the step 4, and feeding back the verification result to the current configuration page; and step 3 can be repeatedly executed to select a plurality of keywords.
Preferably, the validity of the keyword in step 4 includes, but is not limited to, whether the selected keyword corresponds to the keyword packaged in step 1, and whether the parameter of the keyword and the requirement of the parameter correspond to the parameter of the keyword packaged in step 1; the mandatory check of the keyword parameters is whether the keyword parameters of the configured data meet the keyword minimum parameter set preset in the step 1; the content validity check is to check whether the configured keyword parameter data meets the data form required by the Jmeter, and meanwhile, the safety, the validity and the compliance of the data are checked; the check whether the necessary key for the Jmeter script is selected is the minimum set of keys necessary to perform a complete and successful performance test using Jmeter, and the necessary key can be set according to actual requirements.
Preferably, the context correlation check in step 5 is a check performed after the execution of step 3 and step 4 is finished; the parameter transmission among the plurality of http requests comprises the transmission of parameter data by two or more interfaces; parameters that are simultaneously transferred include, but are not limited to, incoming parameters for interface a as incoming parameters for interface B, outgoing parameters for interface a as incoming parameters for interface B, incoming parameters or a combination of outgoing parameters for interface a, interface B as incoming parameters or outgoing parameters for interface C, and so forth.
Preferably, the legality check of the data source corresponding to the field needing parameterization in the http request in step 6 includes checking the presence, legality, consistency and compliance of the parameterized parameter data source set in the http request; simultaneously, whether the data field of the uploaded or generated csv file corresponds to the parameterized parameter of the http request or not is verified; and meanwhile, the legality and the compliance of the csv file data are verified.
Preferably, if the file generated in step 7 is a single jmx file, the file is directly saved to a folder designated by the host in the form of jmx files; if jmx files and CSV files are included in step 7, all relevant files are saved in the form of compressed packages to the folder specified by the host.
The embodiment of the invention as shown in fig. 1 is as follows:
packaging Jmeter keywords by using languages such as Java, Python and the like, and setting keyword names and parameter names for the packaged keywords; setting key word attributes such as key word grouping marks, whether key words are necessary or not and the like according to actual requirements; multiple operations in the meter can be packaged as the same key or group of keys if desired.
Setting a test strategy, which comprises the number of concurrent users, the execution time (times), the set time of the number of concurrent users and the design of a test scene; selecting and combining required keywords according to the keywords packaged in the S1 and the test scene designed in the S2, wherein the keywords can be selected repeatedly, and the keywords can also be combined in a parent-child relationship mode; the parameters of the keywords selected in S3 are assigned, and corresponding parameter values are assigned for different keywords.
Verifying the keywords and the parameters thereof according to the packaging rule in S1, and simultaneously, verifying the security and the validity of the parameter values of the keywords; performing S5 if the check passes, and continuing to perform S4 if the check does not pass until S4 passes the rear executable S5;
verifying the parameter transmission among all keywords, wherein the main content of the verification is whether the parameter transmission among the http request keywords meets the preset rule in S1, and meanwhile, verifying the security and the legality of the transmitted parameter values; performing S6 if the check passes, performing S3 if the check does not pass, until S5 passes the rear executable S6;
verifying data sources corresponding to fields needing parameterization of the keywords in the S3, including verifying whether the parameterized parameter data sources of the keywords in the S3 are available, legality, consistency and compliance; performing S7 if the check passes, performing S3 if the check does not pass, until S6 passes the rear executable S7;
generating a Jmeter file, if no external data exists in S6, generating a Jmeter script into a folder designated by a host in the form of a jmx file; if S6 has external data, the Jmeter script generated in jmx file form and the data file imported or generated in CSV file form in S3 are merged and generated in compressed package form to the folder designated by the host.
Claims (10)
1. A method for automatically generating a Jmeter script is characterized by comprising the following steps:
s1: packaging a Jmeter script keyword;
s2: setting a test strategy;
s3: selecting keywords and configuring parameters;
s4: checking the keywords and the parameters thereof;
s5: checking context association;
s6: data compliance verification;
s7: a Jmeter script is generated.
2. The method of claim 1, wherein the method comprises the steps of: the Jmeter script keywords packaged in the step S1 include a test plan, an execution plan, an http Cookie manager, an http request default value, an http request, a transaction (scene) controller, a simple controller, a conditional branch controller, a cycle controller, a regular expression, a csv file generation, a csv file uploading and a rear-end listener;
the step S2 sets the test policy as: defining a performance test scene, and determining a performance test range and a test strategy according to requirements, wherein the test strategy comprises the number of concurrent users, execution time (times), set time, a concurrent user growth mode and the like;
the step S3 is to combine the performance test scenario defined in the step S2, select the Jmeter keyword packaged in the step S1, and perform parameter configuration on the selected keyword according to the requirement in the step S2;
the verification of the keywords and the parameters thereof in the step S4 comprises keyword validity verification, mandatory verification of keyword parameters and content validity verification, meanwhile, whether the keywords required by the whole Jmeter script are selected or not is verified, and clear and definite prompts and suggested values are provided for items which fail to be verified;
the context correlation check of the step S5 is a performance test scenario context correlation check, which includes checking the front-back sequence of http requests and the validity of parameter transmission when parameter data transmission between multiple http requests exists;
the step S6 is a step of verifying the data compliance of the performance test scene, which comprises verifying the legality of the data source corresponding to the field needing parameterization in the http request, and simultaneously verifying the legality of the uploaded or generated csv file data and whether the data is introduced by the http request;
the step S7 generates a Jmeter script according to the keywords selected in the step S3 and the configured parameters, after the verification in the steps S4 to S6, the Jmeter script is generated according to the Jmeter script specification for the keywords passing the verification, the generated script file is jmx file, and if the uploading csv is selected in the step S3, the csv file is generated, and after the verification in the step S6, the generated file also includes the csv file.
3. The method of automatically generating a Jmeter script according to claim 2, wherein: in the step S1, in the process of packaging the keyword, the customized keyword name corresponds to the operation of the meter, and meanwhile, the parameter of the meter is extracted and the parameter value is preset as the parameter and the parameter data of the packaged keyword.
4. The method of automatically generating a Jmeter script according to claim 2, wherein: in the step S2, after the test policy is set, a growth trend graph of the number of concurrent users is automatically generated as a visual reference.
5. The method of automatically generating a Jmeter script according to claim 2, wherein: after the keywords are selected and the keyword parameter values are configured in the step S3, the step S4 is automatically performed, the check result is fed back to the current configuration page, and the step S3 can be repeatedly performed to select a plurality of keywords.
6. The automatic generation method of a Jmeter script according to claim 5, wherein: the keywords in step S3 support parent-child relationship keywords, that is, one keyword may include multiple child keywords as a group of keywords, and the http request keywords in step S3 are batch imported through formatted files such as external excel files, csv files, json files, and the like, and the imported http request keywords include parameters and parameter data in the http request keywords.
7. The method of automatically generating a Jmeter script according to claim 2, wherein: the validity of the keywords in step S4 includes whether the selected keywords correspond to the keywords packaged in step S1, whether the parameters and the requirements of the keywords correspond to the parameters and the requirements of the keywords packaged in step S1, whether the keyword parameters of the keywords are required to be verified as the keywords with configured data satisfy the minimum parameter set of the keywords preset in step S1, whether the content validity is verified as the data form of the configured keyword parameter data satisfying the requirements of the Jmeter, and meanwhile, the security, validity and compliance of the data are verified, whether the keywords necessary for the Jmeter script are selected as the minimum set of the keywords necessary for performing a complete and successful performance test by using the Jmeter, and meanwhile, the necessary keywords are set according to the actual requirements.
8. The method of automatically generating a Jmeter script according to claim 2, wherein: the context correlation check in step S5 is performed after the execution of steps S3 and S4 is completed, and the parameter transfer between http requests includes the transfer of parameter data by two or more interfaces.
9. The method of automatically generating a Jmeter script according to claim 2, wherein: the step S6 of checking the validity of the data source corresponding to the field that needs parameterization in the http request includes checking whether the parameterized parameter data source is set for the http request, checking the validity, consistency, and compliance of the parameterized parameter data source, checking whether the uploaded or generated data field of the csv file corresponds to the parameterized parameter of the http request, and checking the validity and compliance of the csv file data.
10. The method of automatically generating a Jmeter script according to claim 2, wherein: if the file generated in step S7 is a single jmx file, it is directly saved in the folder designated by the host in the form of jmx file, and if the file includes jmx file and csv file in step S7, it is saved in the folder designated by the host in the form of compressed package.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010248488.5A CN111427793A (en) | 2020-04-01 | 2020-04-01 | Automatic Jmeter script generation method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010248488.5A CN111427793A (en) | 2020-04-01 | 2020-04-01 | Automatic Jmeter script generation method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111427793A true CN111427793A (en) | 2020-07-17 |
Family
ID=71557353
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010248488.5A Pending CN111427793A (en) | 2020-04-01 | 2020-04-01 | Automatic Jmeter script generation method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111427793A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112948480A (en) * | 2021-04-21 | 2021-06-11 | 平安好医投资管理有限公司 | Data extraction method and device, electronic equipment and storage medium |
| CN114253814A (en) * | 2020-09-22 | 2022-03-29 | Igg新加坡有限私人贸易公司 | Game server pressure testing method and device |
| CN114285616A (en) * | 2021-12-16 | 2022-04-05 | 上海商汤科技开发有限公司 | Data transmission method and device, electronic equipment and storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130055028A1 (en) * | 2011-08-31 | 2013-02-28 | Ebay Inc. | Methods and systems for creating software tests as executable resources |
| CN108572916A (en) * | 2018-03-22 | 2018-09-25 | 平安科技（深圳）有限公司 | Method for testing pressure, device, equipment based on Jmeter and storage medium |
-
2020
- 2020-04-01 CN CN202010248488.5A patent/CN111427793A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130055028A1 (en) * | 2011-08-31 | 2013-02-28 | Ebay Inc. | Methods and systems for creating software tests as executable resources |
| CN108572916A (en) * | 2018-03-22 | 2018-09-25 | 平安科技（深圳）有限公司 | Method for testing pressure, device, equipment based on Jmeter and storage medium |
Non-Patent Citations (2)
| Title |
|---|
| 豆姐姐: "Jmeter 之测试片段、Include Controller、模块控制器应用[6]", 《HTTPS://WWW.CNBLOGS.COM/TUDOU-22/P/11452192.HTML》 * |
| 黑马程序员: "五步教你如何去做jmeter接口java二次开发", 《HTTPS://ZHUANLAN.ZHIHU.COM/P/85985170》 * |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114253814A (en) * | 2020-09-22 | 2022-03-29 | Igg新加坡有限私人贸易公司 | Game server pressure testing method and device |
| CN112948480A (en) * | 2021-04-21 | 2021-06-11 | 平安好医投资管理有限公司 | Data extraction method and device, electronic equipment and storage medium |
| CN112948480B (en) * | 2021-04-21 | 2023-11-14 | 平安好医投资管理有限公司 | Data extraction method, device, electronic equipment and storage medium |
| CN114285616A (en) * | 2021-12-16 | 2022-04-05 | 上海商汤科技开发有限公司 | Data transmission method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110297774B (en) | Automatic interface testing method based on python | |
| CN111427793A (en) | Automatic Jmeter script generation method | |
| US20060265475A9 (en) | Testing web services as components | |
| US7054881B2 (en) | Method and system for reporting standardized and verified data | |
| US20120089868A1 (en) | Fuzz testing of asynchronous program code | |
| CN108920139B (en) | Program generation method, device and system, electronic equipment and storage medium | |
| CN110362490B (en) | Automatic testing method and system for integrating iOS and Android mobile applications | |
| CN111459821A (en) | Software automation unit testing method based on TestNG | |
| US10452522B1 (en) | Synthetic data generation from a service description language model | |
| CN109977012B (en) | Joint debugging test method, device, equipment and computer readable storage medium of system | |
| CN106612204B (en) | Service checking method and device | |
| CN102866944A (en) | Pressure testing system and method | |
| CN111737152B (en) | Method and device for realizing WEB automatic test by inputting data through webpage | |
| CN111679979A (en) | Destructive testing method and device | |
| JP2013524312A (en) | Method, computer program, and apparatus for verifying task execution in an adaptive computer system | |
| CN111459809A (en) | Software testing method based on rapid demand version iteration | |
| CN117370217B (en) | Automatic interface test result generation method based on python | |
| Belli et al. | Test generation and minimization with" Basic" statecharts | |
| Nursimulu et al. | Cause-effect graphing analysis and validation of requirements | |
| CN111078527B (en) | Auxiliary system and method for pressure testing of server | |
| CN117389880A (en) | Automatic testing method and device for web interface and storage medium | |
| CN117194259A (en) | Interface testing method, system, electronic equipment and storage medium | |
| CN109947645A (en) | Automatic configuration tool method and system | |
| CN114661592A (en) | Software testing method based on version iteration adaptive to rapid demand | |
| CN107423210A (en) | Software performance testing method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200717 |