CN117520139A - Interface testing method, system, electronic equipment and storage medium - Google Patents

Interface testing method, system, electronic equipment and storage medium Download PDF

Info

Publication number
CN117520139A
CN117520139A CN202210910717.4A CN202210910717A CN117520139A CN 117520139 A CN117520139 A CN 117520139A CN 202210910717 A CN202210910717 A CN 202210910717A CN 117520139 A CN117520139 A CN 117520139A
Authority
CN
China
Prior art keywords
file
interface
test
template
database
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
Application number
CN202210910717.4A
Other languages
Chinese (zh)
Inventor
王娟
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Gridsum Technology Co Ltd
Original Assignee
Beijing Gridsum Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Beijing Gridsum Technology Co Ltd filed Critical Beijing Gridsum Technology Co Ltd
Priority to CN202210910717.4A priority Critical patent/CN117520139A/en
Publication of CN117520139A publication Critical patent/CN117520139A/en
Pending legal-status Critical Current

Links

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
    • G06F11/3688—Test management for test execution, e.g. scheduling of test suites
    • 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/3696—Methods or tools to render software testable

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The invention provides an interface testing method, an interface testing system, electronic equipment and a storage medium, and belongs to the technical field of computers. The method comprises the following steps: generating a test case based on the configured template file, wherein the test case refers to a structured storage file obtained by analyzing an interface file; updating the key value of the program execution environment in the structured storage file to the template value appointed in the template file; importing test data into a database of the program execution environment, and exporting a configuration file of the program execution environment from the database, wherein the configuration file comprises an address of the database and an identifier of the test data; the test case is executed based on the updated structured store file, wherein the template value is replaced with the identifier. The invention is used for automatic interface test.

Description

Interface testing method, system, electronic equipment and storage medium
Technical Field
The present invention relates to the field of computer technology, and in particular, to an interface testing method, an interface testing system, an electronic device, and a machine-readable storage medium.
Background
In a software/code testing process, it is often necessary to test software/code in an environment of multiple executable programs in order to expose specific defects of the tested software/code in different environments so that development and modification can be performed in a targeted manner. However, at present, an automation test script needs to depend on environments, and each environment needs to develop a special automation test script in a targeted manner, so that the software/code test is long in time consumption, the test development cost is high, and the delivery time of a software product is long.
Disclosure of Invention
The invention aims to provide an interface testing method, an interface testing system, electronic equipment and a storage medium, which avoid the need of redevelopment of scripts caused by mismatching of an automatic testing script and an environment, further realize the execution and the environment of the divided scripts and improve the testing development time, the cost and the product delivery time.
In order to achieve the above object, an embodiment of the present invention provides an interface testing method, including:
generating a test case based on the configured template file, wherein the test case refers to a structured storage file obtained by analyzing an interface file;
updating the key value of the program execution environment in the structured storage file to the template value appointed in the template file;
importing test data into a database of the program execution environment, and exporting a configuration file of the program execution environment from the database, wherein the configuration file comprises an address of the database and an identifier of the test data;
the test case is executed based on the updated structured store file, wherein the template value is replaced with the identifier.
Specifically, the interface testing method further comprises the following steps:
analyzing the interface file, and writing the interface request information obtained by analysis and the expected return result information corresponding to the interface request information into the structured storage file with the specified name.
Specifically, the configuration-based template file generates test cases, wherein,
the template files are named and classified to be stored according to the combination of the interface address and the request mode in the interface request information.
Specifically, among others,
the specified name of the structured store file is written as a parameter to the template file.
Specifically, the interface testing method further comprises the following steps:
and executing parameterized test in a specified scene based on the structured storage file.
Specifically, the template value in the interface test method comprises a designated character string;
the test case is configured to invoke a method of matching the string for replacing the template value with the identifier.
Specifically, the interface testing method further comprises at least one of the following steps:
generating a visual report through a tool according to the execution result of the test case;
submitting code holes or defects corresponding to the interface files to a code library;
recording code branches corresponding to the interface files by adopting a code library or merging the code branches;
executing control of a code version corresponding to the interface file;
and matching the corresponding configuration files through the test cases based on the names of the redeployed program execution environments.
The embodiment of the invention provides an interface test system, which comprises:
the system comprises a case generation module, a configuration module and a configuration module, wherein the case generation module is used for generating a test case based on a configured template file, and the test case refers to a structured storage file obtained by interface file analysis;
the file updating module is used for updating the key value of the program execution environment in the structured storage file into the template value appointed in the template file;
a file acquisition module, configured to import test data into a database of the program execution environment, and export a configuration file of the program execution environment from the database, where the configuration file includes an address of the database and an identifier of the test data;
and the use case execution module is used for executing the test use case based on the updated structured storage file, wherein the template value is replaced by the identifier.
In still another aspect, an embodiment of the present invention provides an electronic device, including:
at least one processor;
a memory coupled to the at least one processor;
wherein the memory stores instructions executable by the at least one processor, the at least one processor implementing the aforementioned methods by executing the memory-stored instructions.
In yet another aspect, embodiments of the present invention provide a machine-readable storage medium storing machine instructions that, when executed on a machine, cause the machine to perform the foregoing method.
According to the invention, interface information is obtained through the interface file of the tested software/code, the structured storage file and the environment of the associated interface are separated, and identifiers of test data required by the test case are provided through the configuration file in a method calling mode, so that the functions of dividing the test case execution environment and the program execution environment are achieved, and the problem that the special automatic test case needs to be developed in different environments caused by the fact that the test case needs to depend on the environment is avoided. The invention can automatically generate a plurality of configuration files for different environments, only the configuration file of the corresponding environment is needed to be selected when the test is operated, and the invention is applicable to the deployment of new environments, and is applicable to the version verification test (Build Verification Test, BVT), delivery test, smoking test and the like, and an operator does not need to pay attention to the code, and only one set of used test data (prepared and ready-made data) is needed to be imported to generate the corresponding configuration file.
Additional features and advantages of embodiments of the invention will be set forth in the detailed description which follows.
Drawings
The accompanying drawings are included to provide a further understanding of embodiments of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain, without limitation, the embodiments of the invention. In the drawings:
FIG. 1 is a schematic diagram of the steps of the main method according to the embodiment of the present invention;
FIG. 2 is a schematic diagram of an exemplary test flow according to an embodiment of the present invention;
fig. 3 is a schematic diagram of an apparatus architecture according to an embodiment of the present invention.
Detailed Description
The following describes the detailed implementation of the embodiments of the present invention with reference to the drawings. It should be understood that the detailed description and specific examples, while indicating and illustrating the invention, are not intended to limit the invention.
Example 1
The embodiment of the invention provides an interface testing method which is applied to software/code interface testing and can be executed by a machine, wherein the machine can be a computer or equipment with instruction processing and computing capabilities. The machine is installed with a program for supporting execution of the interface test method. The machine may be connected to a display, which may be used to display the machine-generated visual content, and may also be connected to a human-machine interaction device (touch screen and/or keyboard, mouse). As shown in fig. 1, the interface test method may include:
s1) generating a test case based on a configured template file, wherein the test case refers to a structured storage file obtained by interface file analysis;
s2) updating the key value of the program execution environment in the structured storage file into a template value appointed in the template file;
s3) importing test data into a database of the program execution environment, and exporting a configuration file of the program execution environment from the database, wherein the configuration file comprises an address of the database and an identifier of the test data;
s4) executing the test case based on the updated structured storage file, wherein the template value is replaced with the identifier.
In the embodiment of the invention, the interface file corresponding to the current version can be obtained from a developer of the service program to be tested (software/code for providing an interface). Based on the framework adopted by the service program to be tested, the type of the interface file can be selected, for example, a Spring boot framework is adopted, a developer can automatically generate the swagger interface file by using the swagger dependency library, and the interface file can accord with the specification of the OpenAPI. Before step S1) starts, in the interface testing method, the performing an parsing step may include:
analyzing the interface file, and writing the interface request information obtained by analysis and the expected return result information corresponding to the interface request information into the structured storage file with the specified name.
Through the written analysis script, a dump (dump) of a swagger interface file can be written into a JSON file describing an interface, the JSON file is a key-value structured storage file, information in the JSON file comprises interface request information (request type information, request address and request parameter) of a service program interface to be tested, expected return result (expected return code and expected result) information and the like, the JSON file can be placed in a specified swagger folder, and visual viewing and path searching can be facilitated.
In step S1), template files are named and classified according to the combination of the interface address and the request mode in the interface request information, and in some advantageous implementations, the template files may be YAML files, which are also structured storage files with a key value, may directly use JSON objects in the JSON files, and the content of the YAML files may include a test case name, a request header structure, parameters associated with the interface request information of the service program interface to be tested, expected return codes, expected results, and the like. The YAML file can be used as a basic test case, can be named according to the combination of the address and the request mode (such as POST or GET) of each interface, and can be classified and stored according to the appointed label, so that the YAML file is convenient to test and use.
In the basic test case, a part of JSON objects may be extracted based on the parsed JSON file, and a structured storage file (which may also be a JSON file) with a specified name may be written, where the structured storage file has a specific key structure and key values (such as a file mapping relation map, keys and values of a source object identifier sourceID and a target object identifier targetID) of parameters required by a request mode of a service program interface to be tested, and the specified name (file name) of the JSON file is used as a key value, and the key value corresponding to the specified key in the basic test case is referred to, where the specified key is a parameter (parameter) associated with interface request information of the service program interface to be tested. Thus, the YAML file can be converted from a basic test case to an available test case, a structured storage file with a designated name can be placed in a resource folder, and the designated name can be associated with the YAML file, for example, the test case name or the test case name and the extension name in the YAML file, for example, a 'test case name_request mode_parameter. Json', so that the association test and the use are facilitated.
In some advantageous test applications of embodiments of the present invention, step S1) may further comprise:
and executing parameterized test in a specified scene based on the structured storage file.
Based on the structured storage file with the specified name, a pytest tool can be adopted, different request parameters and expected results can be defined in different test scenes, mark labels are used for marking different scene modes, parameterization execution is carried out by combining @ pytest.mark.parameter when the test cases are operated, one interface corresponds to one basic case, one basic case corresponds to the test cases of a plurality of scenes, and therefore comprehensive test is covered. In the same Mark, the request parameters are in one-to-one correspondence with the expected results, different verification can be carried out according to use cases of different scenes, an optimal verification mode is designed according to different situations, the scenes can be the scenes of successful verification and failure verification, and the parameterized execution can use test data.
The program execution environment may include a test environment, a pre-production environment, a client environment, and the like, and test data needed in each environment has a form of environment individualization format, path, and the like, which results in that key values of parameters needed by a request mode in the structured storage file (JSON file) with the specified name need to have a corresponding form of environment individualization. In the embodiment of the invention, the test data is not written into the structured storage file with the specified name, and the configured template value is written into the structured storage file with the specified name.
In some applications of the embodiment of the invention, different identifiers ID, data and the like can be written into the configuration files, and each set of environment (env, which can be bound with a network address) has a set of independent configuration files, so that the environment can be switched at any time to perform test work. The test data identifier may be a variable name, and a variable having the variable name may be assigned specific data (e.g., a specified character string). After the configuration file is ready, the key value in the JSON file with the designated name is updated into a Template value $ { Template } (the Template is only an example, the actual naming is not limited to the unique mode), when the program runs, the Template value is encountered, the Template method is used for identification, the data corresponding to the identifier is confirmed in the configuration file for replacement, so that one test case is complete and correct, the key value in the JSON file with the designated name is replaced by the data with the characteristic of environment individuation through the calling method, and the test case and the parameters adopted by the test case are separated from the environment, and the code change and development of the test case are not needed to be carried out again in different environments. In some advantageous scenarios, the corresponding configuration files may be matched by the test case based on the name of the redeployed program execution environment, for example, the configuration files are placed under a config folder, and at the same time, a written script is configured in the folder, which may be used to detect the deployed environment, and the detected name of the environment is used to match the name of the configuration file (preconfigured as the name of the associated environment), so that when the test case is executed, the test of the interfaces in multiple environments may be fully automated.
In the foregoing interface test method, the interface test method may further include: and generating a visual report according to a pytest+alure tool, wherein the test address, the test parameters, the test verification content and the test verification result are clearly displayed in the test report, and the test problem and analysis can be quickly checked. The integrated CI/CD can be further included, code holes or defects corresponding to the interface files are submitted to the code library, code branches corresponding to the interface files are recorded by the code library, or the code branches are combined, so that the automatic test efficiency is effectively improved, the test assembly line can be automatically triggered after the operation, maintenance and development and deployment environments are completed, and the test results are fed back to related personnel. When the related personnel deploy the environment, the name of the environment is given, the test code can be matched with the configuration file corresponding to the environment, and when the test code operates, the data in the configuration file can be replaced, so that effective automatic test is performed.
In an exemplary embodiment of the disclosure, as shown in fig. 2, a python script is used to parse a swagger interface file of a service program to be tested (or a data packet obtained by capturing the service program to be tested through a Charles tool, and an interface file derived after capturing the data packet is scanned), so that the foregoing interface request information and return result information can be obtained, and a YAML file is formed as a basic test case, parameters related to a request manner are referred to in the basic test case by a specified name of the JSON file, and meanwhile, a key value in the JSON file is modified to be a template value ($ { id } is specified as id at this time, and is used as a specific form of the foregoing template), a usable test case (file) can be formed after the target value is modified, the test case is executed, and when the template value is encountered, a replacement method is called, the specified variable can be assigned first, and then a new variable is assigned, and can be assigned to be provided as replacement data in the configuration file, and then the JSON file can be deployed, and the test case has the test environment. When the data corresponding to the identifier is accessed through the configuration file, login information can be filled first, and then the database is accessed, so that the data in the database can be safely acquired, and the function can be realized by defining a method in the configuration file. And finally, after the test case is executed in different environments, generating a test report of the service program to be tested.
The embodiment of the invention can rapidly develop test work, does not need to write codes, only focuses on related data configuration files, and can realize multi-environment switching operation, concurrent operation and the like at any time at zero cost. Different profiles are used to maintain different environments for different environments of the same suite of items. The embodiment of the invention can analyze and scan the API interface file or the package capture file, automatically generate the test basic use case, and the tester only needs to fill the data in the request parameters, and the language scripts such as python, go and the like realize one set of codes aiming at different environments of the same project, use different configuration files to maintain different environments, and one set of test use case is cut and operated in a plurality of different environments and is operated simultaneously.
Example 2
The embodiment of the present invention belongs to the same inventive concept as embodiment 1, and provides an interface test system, which may include:
the system comprises a case generation module, a configuration module and a configuration module, wherein the case generation module is used for generating a test case based on a configured template file, and the test case refers to a structured storage file obtained by interface file analysis;
the file updating module is used for updating the key value of the program execution environment in the structured storage file into the template value appointed in the template file;
a file acquisition module, configured to import test data into a database of the program execution environment, and export a configuration file of the program execution environment from the database, where the configuration file includes an address of the database and an identifier of the test data;
and the use case execution module is used for executing the test use case based on the updated structured storage file, wherein the template value is replaced by the identifier.
The interface test method further comprises the following steps:
analyzing the interface file, and writing the interface request information obtained by analysis and the expected return result information corresponding to the interface request information into the structured storage file with the specified name.
Specifically, a test case is generated based on the configured template file, wherein,
the template files are named and classified to be stored according to the combination of the interface address and the request mode in the interface request information.
Specifically, among others,
the specified name of the structured store file is written as a parameter to the template file.
Specifically, the interface test system further includes:
and the parameterized execution module is used for executing parameterized test in a specified scene based on the structured storage file.
Specifically, the template value in the interface test system comprises a designated character string;
the test case is configured to invoke a method of matching the string for replacing the template value with the identifier.
Specifically, the interface test system further comprises at least one of the following:
the visualization module is used for generating a visual report from the execution result of the test case through a tool;
the CI/CD module is used for submitting code holes or defects corresponding to the interface files to a code library;
the CI/CD module is used for recording code branches corresponding to the interface files by adopting a code base or merging the code branches;
the CI/CD module is used for executing control of a code version corresponding to the interface file;
and the configuration file matching module is used for matching the corresponding configuration file through the test case based on the name of the redeployed program execution environment.
In an advantageous embodiment of the invention, the system may be implemented on the basis of a processor and a memory, the above-mentioned modules may each be stored as program modules in the memory, which are executed by the processor to implement the corresponding functions.
Example 3
Embodiments of the present invention belong to the same inventive concept as embodiments 1 and 2, and embodiments of the present invention provide an electronic device, as shown in fig. 3, the electronic device A0 may include: at least one processor a01; a memory a02 connected to the at least one processor a01, e.g. the memory a02 may be communicatively connected to the at least one processor a01 via a bus a 03; wherein the memory a02 stores instructions executable by the at least one processor a01, the at least one processor a01 implementing the method of embodiment 1 by executing the instructions stored by the memory a 02.
Embodiments of the present invention also provide a machine-readable storage medium storing machine instructions that, when executed on a machine, cause the machine to perform the method of embodiment 1.
The present invention also provides a computer program product adapted to perform a program initialized with the method steps of embodiment 1 when executed on a data processing device.
The foregoing details of the optional implementation of the embodiment of the present invention have been described in detail with reference to the accompanying drawings, but the embodiment of the present invention is not limited to the specific details of the foregoing implementation, and various simple modifications may be made to the technical solution of the embodiment of the present invention within the scope of the technical concept of the embodiment of the present invention, and these simple modifications all fall within the protection scope of the embodiment of the present invention.
In addition, the specific features described in the above embodiments may be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, various possible combinations of embodiments of the present invention are not described in detail.
Those skilled in the art will appreciate that all or part of the steps in implementing the methods of the embodiments described above may be implemented by a program stored in a storage medium, including instructions for causing a single-chip microcomputer, chip or processor (processor) to perform all or part of the steps of the methods described in the embodiments of the present application. Whereas the foregoing storage medium readable medium includes both permanent and non-permanent, removable and non-removable media, information storage may be implemented by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), flash memory (Flash), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Disks (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium which can be used to store information that can be accessed by the computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
In addition, any combination of various embodiments of the present invention may be performed, so long as the concept of the embodiments of the present invention is not violated, and the disclosure of the embodiments of the present invention should also be considered.

Claims (10)

1. An interface testing method, characterized in that the interface testing method comprises:
generating a test case based on the configured template file, wherein the test case refers to a structured storage file obtained by analyzing an interface file;
updating the key value of the program execution environment in the structured storage file to the template value appointed in the template file;
importing test data into a database of the program execution environment, and exporting a configuration file of the program execution environment from the database, wherein the configuration file comprises an address of the database and an identifier of the test data;
the test case is executed based on the updated structured store file, wherein the template value is replaced with the identifier.
2. The interface testing method of claim 1, further comprising:
analyzing the interface file, and writing the interface request information obtained by analysis and the expected return result information corresponding to the interface request information into the structured storage file with the specified name.
3. The interface testing method of claim 2, wherein the configuration-based template file generates test cases, wherein,
the template files are named and classified to be stored according to the combination of the interface address and the request mode in the interface request information.
4. The method for testing an interface according to claim 3, wherein,
the specified name of the structured store file is written as a parameter to the template file.
5. The interface testing method according to claim 3, further comprising:
and executing parameterized test in a specified scene based on the structured storage file.
6. The interface test method according to claim 1, wherein the template value in the interface test method includes a specified character string;
the test case is configured to invoke a method of matching the string for replacing the template value with the identifier.
7. The interface testing method of claim 1, further comprising at least one of:
generating a visual report through a tool according to the execution result of the test case;
submitting code holes or defects corresponding to the interface files to a code library;
recording code branches corresponding to the interface files by adopting a code library or merging the code branches;
executing control of a code version corresponding to the interface file;
and matching the corresponding configuration files through the test cases based on the names of the redeployed program execution environments.
8. An interface test system, comprising:
the system comprises a case generation module, a configuration module and a configuration module, wherein the case generation module is used for generating a test case based on a configured template file, and the test case refers to a structured storage file obtained by interface file analysis;
the file updating module is used for updating the key value of the program execution environment in the structured storage file into the template value appointed in the template file;
a file acquisition module, configured to import test data into a database of the program execution environment, and export a configuration file of the program execution environment from the database, where the configuration file includes an address of the database and an identifier of the test data;
and the use case execution module is used for executing the test use case based on the updated structured storage file, wherein the template value is replaced by the identifier.
9. An electronic device, comprising:
at least one processor;
a memory coupled to the at least one processor;
wherein the memory stores instructions executable by the at least one processor, the at least one processor implementing the method of any one of claims 1 to 7 by executing the instructions stored by the memory.
10. A machine readable storage medium storing machine instructions which, when run on a machine, cause the machine to perform the method of any one of claims 1 to 7.
CN202210910717.4A 2022-07-29 2022-07-29 Interface testing method, system, electronic equipment and storage medium Pending CN117520139A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210910717.4A CN117520139A (en) 2022-07-29 2022-07-29 Interface testing method, system, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210910717.4A CN117520139A (en) 2022-07-29 2022-07-29 Interface testing method, system, electronic equipment and storage medium

Publications (1)

Publication Number Publication Date
CN117520139A true CN117520139A (en) 2024-02-06

Family

ID=89753764

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210910717.4A Pending CN117520139A (en) 2022-07-29 2022-07-29 Interface testing method, system, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN117520139A (en)

Similar Documents

Publication Publication Date Title
CN107908541B (en) Interface testing method and device, computer equipment and storage medium
US10872034B2 (en) Method, device and computer program product for executing test cases
US10372597B2 (en) Software testing and verification
US7673292B2 (en) Auto conversion of tests between different functional testing tools
CN107665171B (en) Automatic regression testing method and device
US8839107B2 (en) Context based script generation
US8301720B1 (en) Method and system to collect and communicate problem context in XML-based distributed applications
US20170286264A1 (en) System and method for data element tracing
CN113568839A (en) Method, device, equipment and medium for software testing and statistical test coverage rate
CN112241360A (en) Test case generation method, device, equipment and storage medium
CN111367803A (en) Method and system for improving testing efficiency of client software
CN114398293A (en) Interface test case generation method, electronic device and storage medium
CN115658496A (en) Extensible Web automatic test method, system, equipment and storage medium
US11422917B2 (en) Deriving software application dependency trees for white-box testing
CN110147313B (en) Log output method and device
CN113742215A (en) Method and system for automatically configuring and calling test tool to perform test analysis
CN112765032A (en) Program debugging method, device, equipment and storage medium
CN117370203A (en) Automatic test method, system, electronic equipment and storage medium
CN115470152B (en) Test code generation method, test code generation device, and storage medium
CN110888641A (en) Automatic script generation method and device, server and storage medium
CN115987821A (en) Gateway routing test method and device
CN117520139A (en) Interface testing method, system, electronic equipment and storage medium
CN114115982A (en) Code issuing method, device, equipment and storage medium
US20140006865A1 (en) System and method for capturing and using web page views in a test environment
CN113626307A (en) Data verification method and device based on K8S container platform

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