CN116185826A - Test method, device, equipment and storage medium - Google Patents

Abstract

The application provides a testing method, device, equipment and storage medium, which can easily, conveniently and visually arrange interfaces to obtain test cases, lower the threshold of software testing, and improve the efficiency of software testing. The method includes: according to the information of multiple interfaces, generating a plurality of interface call tags corresponding to a plurality of interfaces, receiving a user's drag-and-drop connection operation on the plurality of interface call tags in the canvas, and obtaining a first functional test case corresponding to a business execution logic relationship of a plurality of interfaces, According to the first functional test case, generate json data, execute the json data, and test the first functional test case.

Description

A test method, device, equipment and storage medium

technical field

The present application relates to the field of automated testing, in particular to a testing method, device, equipment and storage medium.

Background technique

As the fields of software applications become more and more extensive, more and more companies are faced with the need for automated testing of software. At present, test engineers can write test cases (that is, functions assembled from one or more interfaces of the software) with the help of different automated test frameworks or tools, and complete the automated testing of the software by simulating and running the test cases.

However, existing automated testing frameworks or tools require test engineers to learn the language under the corresponding automated testing framework, so as to use the corresponding language under different automated testing frameworks to complete the writing of test cases. Therefore, test engineers are required to have a certain code foundation, and the threshold for software testing is high, and software test cases need to be written by test engineers in the form of code. There are problems of low writing efficiency and difficulty in error correction and modification, which will also affect testing efficiency.

Contents of the invention

The present application provides a test method, device, equipment and storage medium, which can easily, conveniently and visually arrange interfaces to obtain test cases, lower the threshold of software test, and improve the efficiency of software test.

In a first aspect, the application provides a test method, the method comprising:

generating a plurality of interface call labels corresponding to the plurality of interfaces according to the information of the plurality of interfaces;

receiving the user's drag-and-drop connection operation on the plurality of interface calling labels in the canvas, and obtaining a first functional test case corresponding to the business execution logic relationship of the plurality of interfaces;

Generate json data according to the first functional test case;

Execute the json data to test the first functional test case.

Further, receiving a user's drag-and-drop connection operation on the plurality of interface call tags in the canvas to obtain a first functional test case corresponding to the business execution logic relationship of the plurality of interfaces, further comprising:

receiving a user's drag-and-drop connection operation on the plurality of interface call tags and the controller call tag corresponding to at least one controller in the canvas, and obtaining a service execution corresponding to the plurality of interfaces and the at least one controller The first functional test case of the logical relationship;

Wherein, the controller includes a loop controller, a condition controller, a delay controller, and a parameter extractor.

Further, the method also includes:

Receive the user's drag-and-drop connection operation on the functional test case labels corresponding to the multiple functional test cases in the canvas, and obtain a scenario test case corresponding to the business execution logic relationship of the multiple functional test cases, wherein the multiple functional test cases The test case includes the first functional test case;

Generate json data according to the scenario test case;

Execute the json data to test the scenario test case.

Further, the interface information includes one or more of the following:

Interface name, request path, request parameters, request header.

Further, after the testing of the first functional test case, it also includes:

If an error occurs after the first functional test case is tested, an error is reported to the error interface in the first functional test case.

In a second aspect, the application provides a use case testing device, the device comprising:

A processing module, configured to generate a plurality of interface call labels corresponding to the plurality of interfaces according to the information of the plurality of interfaces;

An acquisition module, configured to receive a user's drag-and-drop connection operation on the plurality of interface call tags in the canvas, and obtain a first functional test case corresponding to the business execution logic relationship of the plurality of interfaces;

The processing module is further configured to generate json data according to the first functional test case; execute the json data to test the first functional test case.

Further, when the acquisition module receives the user's drag-and-drop connection operation on the plurality of interface call tags in the canvas, and obtains a first functional test case corresponding to the business execution logic relationship of the plurality of interfaces, the specific use At:

receiving a user's drag-and-drop connection operation on the plurality of interface call tags and the controller call tag corresponding to at least one controller in the canvas, and obtaining a service execution corresponding to the plurality of interfaces and the at least one controller A first functional test case of a logical relationship; wherein, the controller includes a loop controller, a condition controller, a delay controller, and a parameter extractor.

Further, the processing module is also used for:

Receive the user's drag-and-drop connection operation on the functional test case labels corresponding to the multiple functional test cases in the canvas, and obtain a scenario test case corresponding to the business execution logic relationship of the multiple functional test cases, wherein the multiple functional test cases The test case includes the first functional test case;

Generate json data according to the scenario test case;

Execute the json data to test the scenario test case.

Further, the interface information includes one or more of the following:

Interface name, request path, request parameters, request header.

Further, after the processing module tests the first functional test case, it is also used to:

If an error occurs after the first functional test case is tested, an error is reported to the error interface in the first functional test case.

In a third aspect, the present application provides an electronic device, the electronic device includes at least a processor and a memory, and when the processor executes a computer program or an instruction stored in the memory, the method of the first aspect above is realized.

In a fourth aspect, the present application provides a computer-readable storage medium, which stores computer programs or instructions, and when the computer programs or instructions are executed by a processor, the method in the above-mentioned first aspect is realized.

In this application, multiple interface call labels corresponding to multiple interfaces are generated according to the information of multiple interfaces, and a user's drag-and-drop connection operation on the multiple interface call labels in the canvas is received to obtain one corresponding to multiple interfaces. For the first functional test case of the business execution logic relationship, generate corresponding json data according to the node relationship of each interface in the first functional test case, execute the json data, and test the first functional test case, which can be simple, convenient and visualized The test case can be obtained by arranging the interface in a timely manner, lowering the threshold of software testing and improving the efficiency of software testing.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings that need to be used in the description of the embodiments. Obviously, the drawings in the following description are only some embodiments of the present application. For Those of ordinary skill in the art can also obtain other drawings based on these drawings without making creative efforts.

Fig. 1 is a flow chart of a testing method provided in this application.

FIG. 2 is a schematic diagram of a visual drag-and-drop functional test case provided in this application.

FIG. 3 is an architecture diagram of a test case visualization construction system provided in this application.

FIG. 4 is a flowchart of a test case visualization construction method provided in this application.

Fig. 5 is a schematic structural diagram of a test device provided in this application.

FIG. 6 is a schematic structural diagram of an electronic device provided in this application.

Detailed ways

In order to make the purpose and implementation of the application clearer, the following will clearly and completely describe the exemplary implementation of the application in conjunction with the accompanying drawings in the exemplary embodiment of the application. Obviously, the described exemplary embodiment is only the present application. Claim some of the examples, not all of them.

It should be noted that the brief description of the terms in this application is only for the convenience of understanding the implementations described below, and is not intended to limit the implementations of this application. These terms are to be understood according to their ordinary and usual meaning unless otherwise stated.

The terms "first", "second", and "third" in the description and claims of this application and the above drawings are used to distinguish similar or similar objects or textual entities, and do not necessarily mean limiting specific sequence or sequence, unless otherwise noted. It is to be understood that the terms so used are interchangeable under appropriate circumstances.

The terms "comprising" and "having", as well as any variations thereof, are intended to be inclusive but not exclusive, for example, a product or device comprising a series of components is not necessarily limited to all components expressly listed, but may include not expressly listed other components listed or inherent to these products or equipment.

The term "module" refers to any known or later developed hardware, software, firmware, artificial intelligence, fuzzy logic, or combination of hardware or/and software code capable of performing the function associated with that element.

As the fields of software applications become more and more extensive, more and more companies are faced with the need for automated testing of software. At present, test engineers can use different automated testing frameworks or tools to realize automated testing of software.

Table 1

As shown in Table 1, Table 1 is the framework and implementation techniques commonly used in writing test cases for automated testing. At present, the mainstream automated testing frameworks include Robot Framework (Robot Framework, RF), functional testing tools (Quick Test Professional, QTP), Jmeter, and Cucumber. For each automated testing framework, test engineers need to learn the language under the automated testing framework to complete the writing of test cases. In addition, test engineers can also use common languages Python, shell, and java tools to directly write test cases for testing software. In short, writing test cases requires test engineers to have a certain code foundation, and obtain test cases by writing code, which may lead to repeated coding processes for the same type of test cases. When a large number of test cases need to be written or in a test case When the number of interfaces included is large, the coding process is time-consuming and laborious, and since the test cases are all coded and presented to the test engineer, when an error occurs, the test engineer needs to check the code one by one, and the error correction efficiency is low.

Based on this, the application provides a testing method, device, equipment and storage medium, in order to simply, conveniently and visually arrange interfaces to obtain test cases, lower the threshold of software testing, and improve the efficiency of software testing.

Fig. 1 is the flow chart of a kind of test method that the embodiment of the present application provides, and this method can be applied to electronic equipment, and this method comprises:

S101: Generate multiple interface call labels corresponding to the multiple interfaces according to the information of the multiple interfaces.

In the process of testing the software, the user can input the information of multiple interfaces of the software to be tested into the electronic device. After receiving the information of the multiple interfaces input by the user, the electronic device can , generating multiple interface call labels corresponding to multiple interfaces. As an example, the user can input interface information (such as interface name, request path, request parameters, request header, interface functions, etc.) into the electronic device, and the electronic device can Generate the interface call label of this interface on the canvas. For example, if the function of the interface is "login", the electronic device can generate an interface call label named "login" in the canvas, and the interface call label and the information of the interface (such as interface name, request path, request parameters, request header, Information such as the function of the interface), the electronic device can realize the call or simulate call of the interface through the interface information associated with the interface call label.

S102: Receive a user's drag-and-drop connection operation on the plurality of interface call tags in the canvas, and obtain a first functional test case corresponding to the business execution logic relationship of the plurality of interfaces.

The electronic device receives the user's drag-and-drop connection operation on multiple interface call labels in the canvas displayed on the front end, and then obtains a first functional test case, which corresponds to the business logic relationship that implements the function. multiple interfaces.

FIG. 2 is a schematic diagram of a visual drag-and-drop function test case provided by the embodiment of the present application. As shown in Figure 2, the left side is the function directory for building use cases. The function directory includes: starting point, interface, interface pool, loop controller, parameter extraction, assertion, script file, end and other options. The user can click the interface option to enter the information of the interface to be tested, and the electronic device can generate corresponding interface call labels in the canvas on the right according to the interface information entered by the user (such as the information of the public login interface entered by the user, the loading event type For the interface information of hierarchical search, the electronic device will generate the corresponding interface call label for public login and the interface call label for loading event type hierarchical search) in the canvas on the right. You can also click the start point, end and other options, and the corresponding Logical node labels such as start point and end point. In the canvas, the user can visually drag and drop one or more interface call labels and one or more logical node labels, arrange one or more interface call labels and one or more logical node labels, and obtain a functional test Example. Figure 2 shows a functional test case for testing login and extracting parameters. The functional test case is composed of the user visually dragging and dropping the corresponding interface call label and logical node label in the canvas. The business logic relationship of the functional test case Displayed in sequence in the canvas are: "Start" logical node label (used to start the use case), "public login" interface call label (used to test the public login interface for login operation), "load event type hierarchical search" interface call label ( It is used to test the loading event type hierarchical search interface load and search data operation), "parameter extraction" logical node label (used to extract the data searched by the previous interface), "assertion" logical node label (used to judge the last searched Whether the data is consistent with the expected data, where the expected data can be pre-configured in the test parameters of the assertion), the "end" logical node label (used to end the use case).

S103: Generate json data according to the first functional test case.

The electronic device generates json data according to the node relationship of the functional test case generated by dragging and dropping by the user in the canvas. Among them, the json data of the functional test case contains at least node relationship and node information. In the node relationship, for each node, there can be three types of data source node (source), target node (target), type (type), source data The identity document (id) of the source node is recorded in the target data, the id of the target node is recorded in the target data, and the connection relationship type between the source node and the target node is recorded in the type data, where the connection relationship type can include a one-way connection , two-way connection, etc., for example, when the type is hvh, it means that the connection relationship type between the source node and the target node is a one-way connection.

In the node information, the node id, node label (label) and node information of each node in the functional test case are recorded, wherein the node label includes one of the interface call label and logical node label, etc., if the node Corresponding to the interface call label, the node information includes the interface name, request path, request parameters, request header, interface function and other information; if the node corresponds to the logical node label, the node information includes the relevant preset parameters of the logical node.

Taking the node relationship between the starting point and the public login node in the functional test case shown in Figure 2 as an example, the node relationship of the json data records source: "start1", target: "loadcase1655978104633" and type: "hvh", and In the node information of the json data, it is recorded that the label corresponding to the node with the id "start1" is "starting point", and the label corresponding to the node with the id "loadcase1655978104633" is "public-login", and the node relationship and node information in the integrated json data Recorded data can be obtained from "origin" one-way connection "public-login". Similarly, the electronic device can read the connection relationship between each node and the information of each node from the json data, and complete the first functional test according to the connection relationship between each node and the information of each node Use case testing. Wherein, the id of the node may be assigned by the electronic device to the node or a label corresponding to the node.

S104: Execute the json data to test the first functional test case.

After the electronic device obtains the json data, it can sequentially execute operations corresponding to each node (such as sequentially calling interfaces corresponding to each node, etc.) according to the node relationship recorded in the json data and the information of multiple nodes, so as to implement the first functional test case. Test, and can generate a test report after the test.

In a possible implementation, the electronic device executes the json data to test the first functional test case, including:

Using the RF conversion engine to convert the json data into an execution script, and using the RF execution engine to execute the execution script to test the first functional test case. Among them, the RF conversion engine is used to obtain the node relationship and node information of each node in the json data, and input the node relationship and node information of each node into the pre-compiled robot file template to obtain the RF automated test framework. An identifiable robot file (that is, an execution script), and the RF execution engine is used to run the robot file to complete the test of the first functional test case.

In a possible implementation manner, through the above method, the json data can be converted into execution scripts under the QTP, Jmeter and Cucumber automated test frameworks to complete the test of the first functional test case.

In this application, multiple interface call labels corresponding to multiple interfaces are generated according to the information of multiple interfaces, and a user's drag-and-drop connection operation on the multiple interface call labels in the canvas is received to obtain one corresponding to multiple interfaces. For the first functional test case of the business execution logic relationship, generate corresponding json data according to the node relationship of each interface in the first functional test case, execute the json data, and test the first functional test case, which can be simple, convenient and visualized The test case can be obtained by arranging the interface in a timely manner, lowering the threshold of software testing and improving the efficiency of software testing.

Further, receiving the user's drag-and-drop connection operation on the plurality of interface call tags in the canvas, and obtaining a first functional test case corresponding to the business execution logic relationship of the plurality of interfaces, including:

receiving a user's drag-and-drop connection operation on the plurality of interface call tags and the controller call tag corresponding to at least one controller in the canvas, and obtaining a service execution corresponding to the plurality of interfaces and the at least one controller The first functional test case of the logical relationship;

Wherein, the controller includes a loop controller, a condition controller, a delay controller, a parameter extractor and the like.

In order to better realize the diversification and feasibility of functional test cases, in addition to the interface call label generated by clicking the interface option to enter the information of the interface and logical node labels such as "start point" and "end point", there are also a variety of controller call labels that can be used. As a new node, it is added to the functional test case to achieve the user's expected test effect. Among them, various controller call tags can include loop controller call tags, conditional controller call tags, delay controller call tags, parameters One or more of the extractor call tags, etc., are consistent with the implementation principle of the interface call tags. Users only need to click the corresponding controller option to use any of the various controller call tags, and set The basic parameters of the controller, and the controller calling label of the corresponding function is generated in the canvas.

On the basis of the foregoing embodiments, in the embodiment of the present application, the method further includes:

Receive the user's drag-and-drop connection operation on the functional test case labels corresponding to the multiple functional test cases in the canvas, and obtain a scenario test case corresponding to the business execution logic relationship of the multiple functional test cases, wherein the multiple functional test cases The test case includes the first functional test case;

Generate json data according to the scenario test case;

Execute the json data to test the scenario test case.

In order to meet more complex and diverse business requirements, when implementing a complex scenario business, multiple functional test cases may be required to jointly complete the scenario business. The user can use the functional test case label of the saved functional test case or the functional test case label of the first functional test case to be tested to drag and drop a connection to obtain a scenario test case composed of multiple functional test cases. Receive the business logic relationship of the scenario test case in the canvas, generate json data, generate the corresponding execution script file according to the business logic relationship recorded in the json data, and test the scenario test case by running the execution script file.

Optionally, after receiving the information of a single interface entered by the user, the electronic device may generate a corresponding interface use case according to the test item selected by the user, for testing whether the interface can realize the test item selected by the user.

On the basis of each of the above embodiments, in order to facilitate the user to quickly find the error location, after the test of the first functional test case, it also includes:

If an error occurs after the first functional test case is tested, an error is reported to the error interface in the first functional test case.

After running the execution script file for the first functional test case, a corresponding log file will be generated. If an error occurs, the location of the error can be displayed on the interface call label in the corresponding canvas.

FIG. 3 is an architecture diagram of a test case visualization construction system provided by an embodiment of the present application. As shown in Figure 3, the system includes a presentation layer, a business interface layer, a business logic layer, database access, database storage, and a server. The presentation layer is mainly composed of the Angular framework (the Angular framework includes html, css, ts (TypeScript) A framework for building client applications) and G6 canvas. The display layer is used to provide a visual interface for customers to display the platform interface and perform interactive operations such as dragging and entering information. The business interface layer is mainly composed of Django (Django is an open source Code Web application framework) frame and py (python) function; business logic layer consists of use case management, use case orchestration, execution engine, task processing (this module is implemented by Celery, Celery is a simple, flexible and reliable distributed system) , task queue (this module is implemented by Redis, Redis is completely open source, complies with the BSD protocol, and is a high-performance key-value database), report templates, business interface layer and business logic layer are mainly responsible for receiving users collected by the presentation layer Enter the information of the interface, and perform operations such as use case arrangement and test case, and complete the construction and testing of functional test cases and scenario test cases; the interface used for database access is psycopg2 (psycopg2 is a PostgreSQL database interface in Python language), and the database storage Part of the system uses postgresql (postgresql is a free software object-relational database management system with complete features). The database is mainly used to store and test some interface information, interface use cases, scenario test cases and test function test cases or The report log after the scenario test case; the server includes uwsgi server and nginx server, and the server is mainly used to request corresponding data information from the database according to the needs of the business layer.

FIG. 4 is a flow chart of a test case visualization construction method provided by an embodiment of the present application. As shown in Figure 4, test case layout and execution mainly includes three parts, which are composed of three parts: layout interface, functional test case and scenario test case. In the layout interface part, users can input one or more interfaces. Information, and input the interface information of one or more interfaces into the execution script template to generate the corresponding execution script, or receive the execution script containing one or more interfaces input by the user, and run the above execution script through the interface execution engine, Simulate the calling process of one or more interfaces included in the execution script, obtain the call test result of one or more interfaces included in the execution script, and complete the debugging of the interface according to the call test result. After obtaining multiple debugged interfaces, generate an interface call label corresponding to each interface, and receive the user's drag-and-drop connection operation on multiple interface call labels in the canvas displayed on the front end (optionally, this solution uses jsplumb technology Realize multiple interface call labels (visual drag-and-drop editing process), get a functional test case, and generate the json data of the functional test case, call the RF conversion engine to convert it into an execution script (ie robot file), and use the RF execution engine to run the execution script , to complete the test of the functional test case. Further, the electronic device can receive the user's drag-and-drop connection operation on the functional test case tags corresponding to multiple functional test cases in the canvas, obtain a scenario test case, call the Robot_Runner engine, and run multiple scenarios contained in the scenario test cases in batches. The execution script of the functional test case completes the test of a complex business.

Based on the above test method, the present application provides a test device, and Fig. 5 is a schematic structural diagram of a test device provided in an embodiment of the present application, the device comprising:

A processing module 501, configured to generate a plurality of interface call labels corresponding to the plurality of interfaces according to the information of the plurality of interfaces;

The acquisition module 502 is configured to receive a user's drag-and-drop connection operation on the plurality of interface call tags in the canvas, and obtain a first functional test case corresponding to the business execution logic relationship of the plurality of interfaces;

The processing module 501 is further configured to generate json data according to the first functional test case; execute the json data to test the first functional test case.

Further, when the processing module 501 executes the json data, when testing the first functional test case, it is specifically used for:

Convert the json data into an execution script;

Running the execution script to test the first functional test case.

Further, when the acquisition module 502 receives the user's drag-and-drop connection operation on the plurality of interface call tags in the canvas, and obtains a first functional test case corresponding to the business execution logic relationship of the plurality of interfaces, it also Used for:

receiving a user's drag-and-drop connection operation on the plurality of interface call tags and the controller call tag corresponding to at least one controller in the canvas, and obtaining a service execution corresponding to the plurality of interfaces and the at least one controller A first functional test case of a logical relationship; wherein, the controller includes a loop controller, a condition controller, a delay controller, and a parameter extractor.

Further, the processing module 501 is also used for:

Receive the user's drag-and-drop connection operation on the functional test case labels corresponding to the multiple functional test cases in the canvas, and obtain a scenario test case corresponding to the business execution logic relationship of the multiple functional test cases, wherein the multiple functional test cases The test case includes the first functional test case;

Generate json data according to the scenario test case;

Execute the json data to test the scenario test case.

Further, the interface information includes one or more of the following:

Interface name, request path, request parameters, request header.

Further, after the processing module 501 tests the first functional test case, it is also used to:

If an error occurs after the first functional test case is tested, an error is reported to the error interface in the first functional test case.

Fig. 6 is a schematic structural diagram of an electronic device. As shown in FIG. 6 , the electronic device includes: a processor 601 , a communication interface 602 , a memory 603 and a communication bus 604 , wherein the processor 601 , the communication interface 602 and the memory 603 communicate with each other through the communication bus 604 .

A computer program is stored in the memory 603, and when the program is executed by the processor 601, the processor 601 is made to implement the steps of any one of the above-mentioned testing methods.

The communication bus mentioned in the above electronic device may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus or the like. The communication bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.

The communication interface 602 is used for communication between the electronic device and other devices.

The memory may include a random access memory (Random Access Memory, RAM), and may also include a non-volatile memory (Non-Volatile Memory, NVM), such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.

Above-mentioned processor can be general-purpose processor, comprises central processing unit, network processor (NetworkProcessor, NP) etc.; Programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

On the basis of the above-mentioned embodiments, the embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium stores a computer program executable by the electronic device, when the program is stored in the electronic When running on the device, the electronic device is executed to realize the steps of any one of the above-mentioned testing methods.

The above-mentioned computer-readable storage medium may be any available medium or data storage device that can be accessed by a processor in an electronic device, including but not limited to magnetic storage such as floppy disk, hard disk, magnetic tape, magneto-optical disk (MO), etc., optical storage such as CD, etc. , DVD, BD, HVD, etc., and semiconductor memory such as ROM, EPROM, EEPROM, non-volatile memory (NANDFLASH), solid-state hard disk (SSD), etc.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and are not intended to limit it; although the application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: It is still possible to modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements for some or all of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the technical solutions of the various embodiments of the application. scope.

For convenience of explanation, the above description has been made in conjunction with specific implementation manners. However, the above exemplary discussion is not intended to be exhaustive or to limit the implementations to the precise forms disclosed above. Many modifications and variations are possible in light of the above teachings. The selection and description of the above embodiments are to better explain the principles and practical applications, so that those skilled in the art can better use the embodiments and various modified embodiments suitable for specific use considerations.

Those skilled in the art should understand that the embodiments of the present application may be provided as methods, systems, or computer program products. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

Those skilled in the art should understand that the embodiments of the present application may be provided as methods, systems, or computer program products. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to the present application. It should be understood that each procedure and/or block in the flowchart and/or block diagram, and a combination of procedures and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions may be provided to a general purpose computer, special purpose computer, embedded processor, or processor of other programmable data processing equipment to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing equipment produce a An apparatus for realizing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the instructions The device realizes the function specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby The instructions provide steps for implementing the functions specified in the flow chart or blocks of the flowchart and/or the block or blocks of the block diagrams.

Obviously, those skilled in the art can make various changes and modifications to the application without departing from the spirit and scope of the application. In this way, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalent technologies, the present application is also intended to include these modifications and variations.

Claims (10)

1. A test method, characterized in that the method comprises: generating a plurality of interface call labels corresponding to the plurality of interfaces according to the information of the plurality of interfaces; receiving the user's drag-and-drop connection operation on the plurality of interface calling labels in the canvas, and obtaining a first functional test case corresponding to the business execution logic relationship of the plurality of interfaces; Generate json data according to the first functional test case; Execute the json data to test the first functional test case. 2. The method according to claim 1, characterized in that, receiving the user's drag-and-drop connection operation on the plurality of interface calling labels in the canvas, and obtaining a first logical relationship corresponding to the business execution of the plurality of interfaces A functional test case includes: receiving a user's drag-and-drop connection operation on the plurality of interface call tags and the controller call tag corresponding to at least one controller in the canvas, and obtaining a service execution corresponding to the plurality of interfaces and the at least one controller The first functional test case of the logical relationship; Wherein, the controller includes a loop controller, a condition controller, a delay controller, and a parameter extractor. 3. The method according to claim 1 or 2, characterized in that the method further comprises: Receive the user's drag-and-drop connection operation on the functional test case labels corresponding to the multiple functional test cases in the canvas, and obtain a scenario test case corresponding to the business execution logic relationship of the multiple functional test cases, wherein the multiple functional test cases The test case includes the first functional test case; Generate json data according to the scenario test case; Execute the json data to test the scenario test case. 4. The method according to claim 1, wherein the interface information includes one or more of the following: Interface name, request path, request parameters, request header. 5. The method according to claim 1, characterized in that, after the first functional test case is tested, further comprising: If an error occurs after the first functional test case is tested, an error is reported to the error interface in the first functional test case. 6. A testing device, characterized in that the device comprises: A processing module, configured to generate a plurality of interface call labels corresponding to the plurality of interfaces according to the information of the plurality of interfaces; An acquisition module, configured to receive a user's drag-and-drop connection operation on the plurality of interface call tags in the canvas, and obtain a first functional test case corresponding to the business execution logic relationship of the plurality of interfaces; The processing module is further configured to generate json data according to the first functional test case; execute the json data to test the first functional test case. 7. The device according to claim 6, wherein the obtaining module receives a user's drag-and-drop connection operation on the multiple interface calling labels in the canvas, and obtains a service execution corresponding to the multiple interfaces When the first functional test case of the logical relationship is used, it is specifically used for: receiving a user's drag-and-drop connection operation on the plurality of interface call tags and the controller call tag corresponding to at least one controller in the canvas, and obtaining a service execution corresponding to the plurality of interfaces and the at least one controller A first functional test case of a logical relationship; wherein, the controller includes a loop controller, a condition controller, a delay controller, and a parameter extractor. 8. The device according to claim 6, wherein the processing module is further used for: Receive the user's drag-and-drop connection operation on the functional test case labels corresponding to the multiple functional test cases in the canvas, and obtain a scenario test case corresponding to the business execution logic relationship of the multiple functional test cases, wherein the multiple functional test cases The test case includes the first functional test case; Generate json data according to the scenario test case; Execute the json data to test the scenario test case. 9. An electronic device, characterized in that the electronic device includes at least a processor and a memory, and when the processor executes the computer program or instructions stored in the memory, it can realize the process described in any one of claims 1-5. described method. 10. A computer-readable storage medium, characterized in that it stores computer programs or instructions, and when the computer programs or instructions are executed by a processor, the method according to any one of claims 1-5 is implemented.

Images