CN114443466A - Method for converting executable script by using case file, terminal equipment and storage medium - Google Patents
Method for converting executable script by using case file, terminal equipment and storage medium Download PDFInfo
- Publication number
- CN114443466A CN114443466A CN202111541220.1A CN202111541220A CN114443466A CN 114443466 A CN114443466 A CN 114443466A CN 202111541220 A CN202111541220 A CN 202111541220A CN 114443466 A CN114443466 A CN 114443466A
- Authority
- CN
- China
- Prior art keywords
- module
- type
- converting
- use case
- executable script
- 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
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
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- 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
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/258—Data format conversion from or to a database
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Data Mining & Analysis (AREA)
- Stored Programmes (AREA)
Abstract
The invention relates to a method for converting an executable script by using a case file, a terminal device and a storage medium, wherein the method comprises the following steps: s1: reading a configuration file corresponding to the use case file to acquire the type, the module name and the use case grade of the conversion use case; s2: reading use case data in the use case file, and filtering out the use cases corresponding to the module names and the use case grades acquired in the step S1; s3: integrating information of each use case into a dictionary object according to the filtered use case data, classifying the dictionary objects corresponding to the use cases according to module names, and storing the dictionary objects in a module list; s4: according to the type of the conversion use case acquired in step S1, the use case file is converted into an executable script file of a corresponding type based on the contents in the module list. The invention can be applied to the automatic interface verification work of a plurality of big data platforms, supports the mainstream automatic interface testing tool in the market, and greatly saves the human resource cost.
Description
Technical Field
The present invention relates to the field of software testing, and in particular, to a method for converting an executable script using a case file, a terminal device, and a storage medium.
Background
In recent years, with the continuous increase of the complexity of a service system, the traditional test method has the limitations of low test efficiency, incapability of running in parallel and the like, so that the product release period is prolonged, the test coverage rate is seriously low, and the product quality is sharply reduced. Therefore, the interface-oriented testing technology is imperative.
The interface test inherently brings high-efficiency defect detection and quality supervision capability for a high-complexity platform, and the interface test is implemented under the framework of multiple systems and multiple platforms and has extremely high cost-benefit ratio. The more complex the platform, the larger the system, and the more obvious the effect of the interface test. Although the interface automation test tools on the market are various, the interface automation test tools all need to be manually debugged for each case. Because the number of the cases of various combination scenes is very large, each interface is debugged manually, and a large amount of human resources are consumed. Therefore, how to convert the interface use case into the executable script and then realize the one-click conversion becomes a problem to be solved.
Disclosure of Invention
In order to solve the above problem, the present invention provides a method, a terminal device and a storage medium for converting an executable script with a case file.
The specific scheme is as follows:
a method for converting an executable script with a file comprises the following steps:
s1: reading a configuration file corresponding to the use case file to acquire the type, the module name and the use case grade of the conversion use case;
s2: reading use case data in the use case file, and filtering out the use cases corresponding to the module names and the use case grades acquired in the step S1;
s3: integrating information of each use case into a dictionary object according to the filtered use case data, classifying the dictionary objects corresponding to the use cases according to module names, and storing the dictionary objects in a module list;
s4: according to the type of the conversion use case acquired in step S1, the use case file is converted into an executable script file of a corresponding type based on the contents in the module list.
Further, before integrating the information of the use cases into a dictionary object in step S3, the method further includes cleaning the use case data and removing the use cases that do not meet the requirements of the data format.
Further, in step S4, when the type of the conversion use case is jmx type, the specific conversion process includes the following steps:
s411: reading the parameter file in an xml writing mode to generate a test plan;
s412: traversing each module in the module list, and generating a thread group aiming at each module in the module list in a way of writing in xml;
s413: generating a basic configuration element corresponding to each thread group in an xml writing mode;
s414: traversing each module in the module list, and generating a corresponding HTTP request according to the request type corresponding to each module;
s415: adding an assertion element for each HTTP request;
s416: jmx type files are generated and format conversion is performed.
Further, in step S412, the thread group corresponding to each module is named by the module name.
Further, the basic configuration elements in step S413 include: HTTP request header, HTTP request information, view result tree, debug sampler and aggregate report.
Further, the HTTP request information includes a transport protocol, IP, port information, path, and request parameters.
Further, in step S414, when the request type is the POST type, the dictionary format data in the dictionary object corresponding to the module is converted into data in the format required by the meter, and the unescape method is used to prohibit the data from being transferred after being written, and finally, the HTTP request of the thread group corresponding to the module is generated according to the converted data.
Further, in step S414, when the request type is a GET type, a pair of parameters is generated from the dictionary format data in the dictionary object corresponding to the module in a key-value pair manner, and finally, an HTTP request of the thread group corresponding to the module is generated according to the generated parameters.
Further, the addition manner of the assertion element in step S415 is as follows: analyzing the content of an assertion value field in a dictionary object corresponding to the HTTP request, judging whether a character | | or & &existsin the dictionary object, if the character | | or & &exists, judging that multiple assertions exist, and adding a mark bit according to the type of the character; after the content of the assertion value field is divided by a split method, judging whether the multiple assertions are in a mode or an OR mode according to the mark bits, and further generating an assertion element corresponding to the mode or an assertion element corresponding to the mode; if the characters | | and & & &donot exist, single assertion is judged, and an assertion element is directly generated according to the content of the assertion value field.
Further, the format converted in step S416 is Utf-8.
Further, in step S4, when the type of the conversion use case is a json type, the specific conversion process includes the following steps:
s421: reading the parameter file in a json writing mode to generate a test plan;
s422: traversing each module in the module list, and generating a thread group aiming at each module in the module list in a json writing mode;
s423: generating a basic configuration element corresponding to each thread group and conforming to a postman format in a json writing mode;
s424: traversing each module in the module list, and generating a corresponding HTTP request according to the request type corresponding to each module;
s425: adding an assertion element for each HTTP request;
s426: generating a json type file.
Further, the basic configuration element in step S423 includes an HTTP request header and HTTP request information.
Further, in step S424, when the request type is a POST type, the dictionary format data in the dictionary object corresponding to the module is converted into data in a format required by postman, and the data is prohibited from being escape after being written by using an unescape method, and finally, an HTTP request of the thread group corresponding to the module is generated according to the converted data in the item list.
Further, in step S424, when the request type is the GET type, generating a pair of parameters from the dictionary format data in the dictionary object corresponding to the module in a key-value pair manner, and finally generating an HTTP request of the thread group corresponding to the module according to the generated parameters in the item list.
Further, the addition manner of the assertion element in step S425 is as follows: and extracting the content of the assertion value field in the dictionary object corresponding to the HTTP request as an assertion value, and adding the assertion value field in a mode of writing the assertion grammar corresponding to postman.
A terminal device for converting an executable script with a file includes a processor, a memory, and a computer program stored in the memory and executable on the processor, where the processor implements the steps of the method described above in the embodiments of the present invention when executing the computer program.
A computer-readable storage medium, in which a computer program is stored, which, when being executed by a processor, carries out the steps of the method as described above for an embodiment of the invention.
The technical scheme adopted by the invention can be applied to the automatic interface calibration work of a plurality of big data platforms, supports the mainstream automatic interface testing tool in the market, greatly saves the human resource cost and ensures the quality of the project.
Drawings
Fig. 1 is a flowchart of a first embodiment of the invention.
Detailed Description
To further illustrate the various embodiments, the invention provides the accompanying drawings. The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate embodiments of the invention and, together with the description, serve to explain the principles of the embodiments. Those skilled in the art will appreciate still other possible embodiments and advantages of the present invention with reference to these figures.
The invention will now be further described with reference to the drawings and the detailed description.
The first embodiment is as follows:
the embodiment of the invention provides a method for converting an executable script by using a case file, which is used for converting a text type interface case (such as excel types and yaml types) into the executable script (such as jmx types and json types) by one key, and the executable script is operated by main flow tools such as a jmeter and postman, so that the automatic checking work of an interface can be completed. As shown in fig. 1, the method comprises the steps of:
s1: and reading a configuration file corresponding to the use case file to acquire the type, the module name and the use case grade of the conversion use case.
The type of configuration file in this embodiment is yml type. It should be noted that, when the type of the use case file is an excel type, the corresponding excel password also needs to be acquired from the configuration file, and then the use case data in the use case file is read in subsequent steps.
S2: and reading the use case data in the use case file, and filtering out the use cases corresponding to the module names and the use case grades acquired in the step S1.
S3: and integrating the information of each use case into a dictionary object according to the filtered use case data, classifying the dictionary objects corresponding to the use cases according to the module names, and storing the dictionary objects in a module list.
Before integrating the information of the use cases into a dictionary object, the method also comprises the steps of cleaning the use case data, eliminating the use cases which do not meet the requirements of the data format in the use case data and generating a corresponding log for recording the position of the cleaning data.
S4: according to the type of the conversion use case acquired in step S1, the use case file is converted into an executable script file of a corresponding type based on the contents in the module list.
(1) When the type of the conversion use case is jmx type, the specific conversion process comprises the following steps:
s411: and reading the parameter file in an xml writing mode to generate a test plan.
S412: traversing each module in the module list, and generating a thread group aiming at each module in the module list in a way of writing xml.
In this embodiment, the thread group corresponding to each module is named by the module name.
S413: and generating a basic configuration element corresponding to each thread group by writing xml.
The basic configuration elements in this embodiment include: HTTP request headers, HTTP request information including transport protocol, IP, port information, path and request parameters, view results, debug samplers, aggregate reports, etc.
S414: and traversing each module in the module list, and generating a corresponding HTTP request according to the request type corresponding to each module.
And when the request type is a POST type, converting dictionary format data in the dictionary object corresponding to the module into data in a format required by a Jmeter, using a unescape method to prohibit the data from being transferred after being written, and finally generating an HTTP request of a thread group corresponding to the module according to the converted data.
And when the request type is a GET type, generating a pair of parameters by the dictionary format data in the dictionary object corresponding to the module in a key-value pair mode, and finally generating the HTTP request of the thread group corresponding to the module according to the generated parameters.
S415: an assertion (assert) element is added for each HTTP request.
The addition mode of the assertion element in this embodiment is as follows: analyzing the content of an assertion value field in a dictionary object corresponding to the HTTP request, judging whether a character | | or & &existsin the dictionary object, if the character | | or & &exists, judging that multiple assertions exist, and adding a mark bit according to the type of the character; after the content of the assertion value field is divided by a split method, judging whether the multiple assertions are in a mode or an OR mode according to the mark bits, and further generating an assertion element corresponding to the mode or an assertion element corresponding to the mode; if the characters | | and & & &donot exist, single assertion is judged, and an assertion element is directly generated according to the content of the assertion value field.
S416: jmx type files are generated and format conversion is performed.
The converted format is set to Utf-8 in this embodiment.
(2) When the type of the conversion use case is a json type, the specific conversion process comprises the following steps:
s421: reading the parameter file by writing in json to generate a test plan.
S422: traversing each module in the module list, and generating a thread group (collection) for each module in the module list in a json writing mode.
S423: and generating a basic configuration element corresponding to each thread group and conforming to a postman format by writing json.
The basic configuration elements in this embodiment include an HTTP request header and HTTP request information.
S424: and traversing each module in the module list, and generating a corresponding HTTP request according to the request type corresponding to each module.
And when the request type is a POST type, converting dictionary format data in the dictionary object corresponding to the module into data in a format required by postman, using a unescape method to prohibit the data from being read in, and then escaping, and finally generating an HTTP request of a thread group corresponding to the module according to the converted data in the item list.
And when the request type is the GET type, generating a pair of parameters of the dictionary format data in the dictionary object corresponding to the module in a key-value pair mode, and finally generating an HTTP request of the thread group corresponding to the module according to the generated parameters in the item list.
S425: an assertion element is added for each HTTP request.
The addition mode of the assertion element in the embodiment is as follows: and extracting the content of the assertion value field in the dictionary object corresponding to the HTTP request as an assertion value, and adding the assertion value field in a mode of writing the assertion grammar corresponding to postman.
S426: generating a json type file.
The embodiment of the invention can quickly and automatically convert the interface test case of the text type into the executable interface test script, has wider application prospect and can be applied to the following scenes:
the development and testing personnel of the large-scale information system are used for unit and function testing;
secondly, front line technical support personnel are used for quickly verifying the accuracy of the operating environment in the actual combat supporting process;
and (III) the project sets with complex service, high repeatability and the same interface attribute are used for the verification work of installation, upgrading and operation and maintenance links.
And (IV) the method is used for service scenes which have more internal and external interfaces, more docking items and data deficiency verification.
And (V) the method is used for a service scene requiring a large-batch interface to quickly construct a large amount of data.
The second embodiment:
the invention also provides a terminal device for converting an executable script with a file, which comprises a memory, a processor and a computer program stored in the memory and capable of running on the processor, wherein the processor executes the computer program to realize the steps of the method embodiment of the first embodiment of the invention.
Further, as an executable scheme, the terminal device for converting the executable script by the use-case file may be a computing device such as a desktop computer, a notebook, a palmtop computer, and a cloud server. The terminal device for converting the executable script with the use case file can include, but is not limited to, a processor and a memory. It will be understood by those skilled in the art that the above-mentioned structure of the terminal device for converting an executable script with a case file is merely an example of the terminal device for converting an executable script with a case file, and does not constitute a limitation of the terminal device for converting an executable script with a case file, and may include more or less components than the above-mentioned one, or combine some components, or different components, for example, the terminal device for converting an executable script with a case file may further include an input/output device, a network access device, a bus, etc., which is not limited in this embodiment of the present invention.
Further, as an executable solution, the Processor may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, a discrete hardware component, and the like. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, and the processor is a control center of the terminal device for converting the executable script using the use case file, and various interfaces and lines are used to connect various parts of the terminal device for converting the executable script using the use case file.
The memory may be configured to store the computer program and/or the module, and the processor may implement various functions of the terminal device that converts the executable script using the case file by running or executing the computer program and/or the module stored in the memory and calling data stored in the memory. The memory can mainly comprise a program storage area and a data storage area, wherein the program storage area can store an operating system and an application program required by at least one function; the storage data area may store data created according to the use of the mobile phone, and the like. In addition, the memory may include high speed random access memory, and may also include non-volatile memory, such as a hard disk, a memory, a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), at least one magnetic disk storage device, a Flash memory device, or other volatile solid state storage device.
The invention also provides a computer-readable storage medium, in which a computer program is stored, which, when being executed by a processor, carries out the steps of the above-mentioned method of an embodiment of the invention.
The module/unit integrated with the terminal device for converting the executable script with the use case file may be stored in a computer-readable storage medium if it is implemented in the form of a software functional unit and sold or used as an independent product. Based on such understanding, all or part of the flow of the method according to the embodiments of the present invention may also be implemented by a computer program, which may be stored in a computer-readable storage medium, and when the computer program is executed by a processor, the steps of the method embodiments may be implemented. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), software distribution medium, and the like.
While the invention has been particularly shown and described with reference to a preferred embodiment, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.
Claims (17)
1. A method for converting an executable script by using a case file is characterized by comprising the following steps:
s1: reading a configuration file corresponding to the use case file to acquire the type, the module name and the use case grade of the conversion use case;
s2: reading use case data in the use case file, and filtering out the use cases corresponding to the module names and the use case grades acquired in the step S1;
s3: integrating information of each use case into a dictionary object according to the filtered use case data, classifying the dictionary objects corresponding to the use cases according to module names, and storing the dictionary objects in a module list;
s4: according to the type of the conversion use case acquired in step S1, the use case file is converted into an executable script file of a corresponding type based on the contents in the module list.
2. The method for converting an executable script using a case file according to claim 1, wherein: before integrating the information of the use cases into a dictionary object in the step S3, the method further includes cleaning the use case data, and removing the use cases which do not meet the requirements of the data format.
3. The method for converting an executable script using a case file according to claim 1, wherein: in step S4, when the type of the conversion use case is jmx type, the specific conversion process includes the following steps:
s411: reading the parameter file in an xml writing mode to generate a test plan;
s412: traversing each module in the module list, and generating a thread group aiming at each module in the module list in a way of writing in xml;
s413: generating a basic configuration element corresponding to each thread group in an xml writing mode;
s414: traversing each module in the module list, and generating a corresponding HTTP request according to the request type corresponding to each module;
s415: adding an assertion element for each HTTP request;
s416: jmx type files are generated and format conversion is performed.
4. The method for converting an executable script using a case file according to claim 3, wherein: in step S412, the thread group corresponding to each module is named by the module name.
5. The method of converting an executable script with a case file according to claim 3, wherein: the basic configuration elements in step S413 include: HTTP request header, HTTP request information, view results tree, debug sampler and aggregate report.
6. The method for converting an executable script using a case file according to claim 4, wherein: the HTTP request information includes a transport protocol, IP, port information, path, and request parameters.
7. The method for converting an executable script using a case file according to claim 3, wherein: in step S414, when the request type is a POST type, converting the dictionary format data in the dictionary object corresponding to the module into data in a format required by a meter, and using an unescape method to prohibit data from being written and then being escaped, and finally generating an HTTP request of the thread group corresponding to the module according to the converted data.
8. The method for converting an executable script using a case file according to claim 3, wherein: in step S414, when the request type is the GET type, generating a pair of parameters from the dictionary format data in the dictionary object corresponding to the module in a key-value pair manner, and finally generating an HTTP request of the thread group corresponding to the module according to the generated parameters.
9. The method for converting an executable script using a case file according to claim 3, wherein: the addition manner of the assertion element in step S415 is: analyzing the content of an assertion value field in a dictionary object corresponding to the HTTP request, judging whether a character | | or & &existsin the dictionary object, if the character | | or & &exists, judging that multiple assertions exist, and adding a mark bit according to the type of the character; after the content of the assertion value field is divided by a split method, judging whether the multiple assertions are in a mode or an OR mode according to the mark bits, and further generating an assertion element corresponding to the mode or an assertion element corresponding to the mode; if the characters | | and & & &donot exist, single assertion is judged, and an assertion element is directly generated according to the content of the assertion value field.
10. The method for converting an executable script using a case file according to claim 3, wherein: the format after the format conversion in step S416 is Utf-8.
11. The method for converting an executable script using a case file according to claim 1, wherein: in step S4, when the type of the conversion use case is json type, the specific conversion process includes the following steps:
s421: reading the parameter file in a json writing mode to generate a test plan;
s422: traversing each module in the module list, and generating a thread group aiming at each module in the module list in a json writing mode;
s423: generating a basic configuration element corresponding to each thread group and conforming to a postman format in a json writing mode;
s424: traversing each module in the module list, and generating a corresponding HTTP request according to the request type corresponding to each module;
s425: adding an assertion element for each HTTP request;
s426: generating a json type file.
12. The method for converting an executable script using a case file according to claim 11, wherein: the basic configuration element in step S423 includes an HTTP request header and HTTP request information.
13. The method for converting an executable script using a case file according to claim 11, wherein: in step S424, when the request type is a POST type, converting the dictionary format data in the dictionary object corresponding to the module into data in a format required by postman, and using a unescape method to prohibit data from being written, and then performing escape, and finally generating an HTTP request of the thread group corresponding to the module according to the converted data in the item list.
14. The method for converting an executable script using a case file according to claim 11, wherein: in step S424, when the request type is a GET type, generating a pair of parameters from the dictionary format data in the dictionary object corresponding to the module in a key-value pair manner, and finally generating an HTTP request of the thread group corresponding to the module according to the generated parameters in the item list.
15. The method for converting an executable script using a case file as claimed in claim 11, wherein: the addition manner of the assertion element in step S425 is: and extracting the content of the assertion value field in the dictionary object corresponding to the HTTP request as an assertion value, and adding the assertion value field in a mode of writing the assertion grammar corresponding to postman.
16. A terminal device for converting an executable script with a file is characterized in that: comprising a processor, a memory and a computer program stored in the memory and running on the processor, the processor implementing the steps of the method according to any one of claims 1 to 15 when executing the computer program.
17. A computer-readable storage medium storing a computer program, characterized in that: the computer program when executed by a processor implementing the steps of the method as claimed in any one of claims 1 to 15.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111541220.1A CN114443466A (en) | 2021-12-16 | 2021-12-16 | Method for converting executable script by using case file, terminal equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111541220.1A CN114443466A (en) | 2021-12-16 | 2021-12-16 | Method for converting executable script by using case file, terminal equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114443466A true CN114443466A (en) | 2022-05-06 |
Family
ID=81364534
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111541220.1A Pending CN114443466A (en) | 2021-12-16 | 2021-12-16 | Method for converting executable script by using case file, terminal equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114443466A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115048922A (en) * | 2022-06-20 | 2022-09-13 | 上海联影医疗科技股份有限公司 | Data analysis method and device |
| CN115348169A (en) * | 2022-08-24 | 2022-11-15 | 大陆汽车研发（重庆）有限公司 | Route configuration method, device, equipment and storage medium for vehicle-mounted gateway |
-
2021
- 2021-12-16 CN CN202111541220.1A patent/CN114443466A/en active Pending
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115048922A (en) * | 2022-06-20 | 2022-09-13 | 上海联影医疗科技股份有限公司 | Data analysis method and device |
| CN115348169A (en) * | 2022-08-24 | 2022-11-15 | 大陆汽车研发（重庆）有限公司 | Route configuration method, device, equipment and storage medium for vehicle-mounted gateway |
| CN115348169B (en) * | 2022-08-24 | 2023-09-22 | 大陆汽车研发（重庆）有限公司 | Route configuration method, device, equipment and storage medium for vehicle-mounted gateway |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109800258B (en) | Data file deployment method, device, computer equipment and storage medium | |
| CN114443466A (en) | Method for converting executable script by using case file, terminal equipment and storage medium | |
| CN111324526B (en) | Interface test system, method and server | |
| CN110287696B (en) | Detection method, device and equipment for rebound shell process | |
| CN110262979B (en) | Simulated third-party data source testing method based on MOCK platform | |
| CN109446042B (en) | Log management method and system for intelligent electric equipment | |
| CN110716866A (en) | Code quality scanning method and device, computer equipment and storage medium | |
| CN113190220A (en) | JSON file differentiation comparison method and device | |
| CN112241362A (en) | Test method, test device, server and storage medium | |
| CN113050987B (en) | Method and device for generating interface document, storage medium and electronic equipment | |
| CN112650673A (en) | Method and device for creating test case in transaction tracking system and electronic equipment | |
| CN115022201B (en) | Data processing function test method, device, equipment and storage medium | |
| CN111046393A (en) | Vulnerability information uploading method and device, terminal equipment and storage medium | |
| CN115757174A (en) | Database difference detection method and device | |
| CN115543832A (en) | Software code standard detection method, system, equipment and storage medium | |
| CN114157439B (en) | Vulnerability scanning method, computing device and recording medium | |
| WO2021129849A1 (en) | Log processing method, apparatus and device, and storage medium | |
| CN114979100A (en) | Cloud resource checking method and related device | |
| CN114997815A (en) | Processing method of laboratory information management system | |
| CN114281761A (en) | Data file loading method and device, computer equipment and storage medium | |
| CN113238940A (en) | Interface test result comparison method, device, equipment and storage medium | |
| CN109062797B (en) | Method and device for generating information | |
| CN111026654A (en) | Automatic testing method based on interface | |
| CN117076546B (en) | Data processing method, terminal device and computer readable storage medium | |
| CN116166462A (en) | Program exception collection management method, device, terminal equipment and medium |
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 |