CN114936152A

CN114936152A - Application testing method and device

Info

Publication number: CN114936152A
Application number: CN202210494675.0A
Authority: CN
Inventors: 宋佳明
Original assignee: Alibaba China Co Ltd
Current assignee: Alibaba China Co Ltd
Priority date: 2022-05-07
Filing date: 2022-05-07
Publication date: 2022-08-23

Abstract

The embodiment of the application provides an application testing method and application testing equipment. The method comprises the following steps: according to the flow chart drawing operation of a user on the flow configuration interface, displaying a test flow chart drawn by the user on the flow configuration interface; the test flow chart comprises a plurality of task nodes; according to task binding operation of a user aiming at each task node in a plurality of task nodes on a process configuration interface, establishing a binding relationship between each task node and a corresponding test task; generating test flow data according to the test flow chart and the binding relationship; sending the test flow data to a test management platform; and the test management platform tests the application to be tested according to the test flow data. By adopting the test scheme provided by the embodiment of the application, the user-defined arrangement of the test flows of a plurality of test tasks can be completed based on simple interface operation, and the test method not only has the advantage of high test flexibility, but also has the advantage of low test cost.

Description

Application testing method and device

Technical Field

The present application relates to the field of communications technologies, and in particular, to an application test method and device.

Background

In recent years, the biggest challenge facing industry organizations has been the changing customer needs and finding ways to quickly address these issues without impacting service operations. Agile software development methodologies followed by most organizations play a crucial role in dealing with this competitive situation. Agile approaches require integration of product components, such as: an API (Application Programming Interface) deploys products (i.e., applications) in a pre-production environment and tests them often.

At present, the problem of high test cost exists in a test scheme aiming at an application API interface.

Disclosure of Invention

In view of the above, the present application is proposed to provide an application testing method and apparatus that solves the above problems, or at least partially solves the above problems.

Accordingly, in an embodiment of the present application, an application testing method is provided, which is applied to a test terminal, and includes:

according to the flow chart drawing operation of a user on a flow configuration interface, displaying a test flow chart drawn by the user on the flow configuration interface; the test flow chart comprises a plurality of task nodes;

according to the task binding operation of the user on the flow configuration interface aiming at each task node in the plurality of task nodes, establishing the binding relationship between each task node and the corresponding test task;

generating test flow data according to the test flow chart and the binding relationship;

sending the test flow data to a test management platform;

and the test management platform tests the application to be tested according to the test flow data.

In another embodiment of the present application, an application testing method is provided, which is applied to a test management platform, and includes:

acquiring test flow data; the test flow data are generated by the test terminal according to the binding relationship between each task node in the test flow chart and the corresponding test task; the test flow chart comprises a plurality of task nodes; the test flow chart is generated by the test terminal according to the flow chart drawing operation of the user on the flow configuration interface; the binding relationship is established by the test terminal according to the task binding operation of the user on the flow configuration interface aiming at each task node;

and testing the application to be tested according to the test flow data.

In another embodiment of the present application, there is provided an application testing system, including: the system comprises a test terminal and a test management platform;

the test terminal is used for: according to the flow chart drawing operation of a user on a flow configuration interface, displaying a test flow chart drawn by the user on the flow configuration interface; the test flow chart comprises a plurality of task nodes; according to the task binding operation of the user on the process configuration interface aiming at each task node in the plurality of task nodes, establishing a binding relation between each task node and a corresponding test task; generating test flow data according to the test flow chart and the binding relationship; sending the test flow data to the test management platform;

the test management platform is used for: and testing the application to be tested according to the test flow data.

In yet another embodiment of the present application, a memory and a processor are provided, wherein,

the memory is used for storing programs;

the processor is coupled with the memory and is configured to execute the program stored in the memory to implement any one of the application testing methods described above.

In yet another embodiment of the present application, there is provided a computer-readable storage medium storing a computer program, which when executed by a computer, is capable of implementing any one of the above-described application testing methods.

According to the technical scheme, a user can perform custom arrangement on test logics among a plurality of test tasks through flow chart drawing operation and task binding operation on a flow configuration interface, and then execute the plurality of test tasks according to the test logics arranged by the user so as to test the application to be tested. Therefore, the test scheme provided by the embodiment of the application realizes that the user-defined arrangement of the test flows of a plurality of test tasks can be completed based on simple interface operation, and has the advantages of high test flexibility and low test cost.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative efforts.

Fig. 1 is a schematic structural diagram of an application test system according to an embodiment of the present application;

fig. 2 is a schematic flowchart of an application testing method according to an embodiment of the present application;

FIG. 3 is a first example of a test flow chart provided by an embodiment of the present application;

FIG. 4 is an exemplary second flowchart of a test provided in an embodiment of the present application;

FIG. 5 is a schematic flow chart illustrating an application testing method according to another embodiment of the present application;

FIG. 6 is a schematic structural diagram of a task definition and management apparatus according to an embodiment of the present application;

FIG. 7 is a schematic structural diagram of a visualization task orchestration device according to an embodiment of the present application;

FIG. 8 is an example of metadata corresponding to a task node according to an embodiment of the present application;

fig. 9 is a block diagram of an electronic device according to an embodiment of the present application.

Detailed Description

Generally, when the API of an application to be tested needs to be tested through a plurality of test tasks, a user needs to compile a code to organize the execution logic relationship among the plurality of test tasks, which not only has a high requirement on the code compiling capability of the user, but also needs to occupy a large amount of time of the user, and has low testing efficiency and high testing cost.

In the prior art, in order to reduce the operation cost of a user, some people propose to abstract a script test case into a test task, and then multiplex a code release pipeline of a code release platform to arrange a plurality of test tasks. However, at present, the code release pipelines of most code release platforms only support two execution logics, namely serial and parallel, the flexibility is poor, and the actual test requirements cannot be met. When testing of other execution logic is required, a user is required to write code to organize execution logic relationships between multiple test tasks.

In order to solve or partially solve the above technical problems, embodiments of the present application provide a new application testing scheme. In the technical scheme provided by the embodiment of the application, a user can perform custom arrangement on the test logic among a plurality of test tasks through the flow chart drawing operation and the task binding operation on the flow configuration interface, and then execute the plurality of test tasks according to the test logic arranged by the user so as to test the application to be tested. Therefore, the test scheme provided by the embodiment of the application realizes that the user-defined arrangement of the test flows of a plurality of test tasks can be completed based on simple interface operation, and has the advantages of high test flexibility and low test cost.

To facilitate understanding of the present solution, the terms referred to in the present solution are explained first:

API: for enabling communication and data exchange between two separate software systems.

API test: one type of software testing for validating an API focuses primarily on the service logic layer of the software architecture, and testing is typically accomplished using a test tool to call the API or script test methods.

The script test method comprises the following steps: code (also known as scripts) is written to call the API to complete the test.

Arranging: multiple tasks are integrated together through certain logic to create a uniformly coordinated software product.

In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below according to the drawings in the embodiments of the present application. It is to be understood that the embodiments described are only a few embodiments of the present application and not all embodiments. All other embodiments obtained by a person skilled in the art based on the embodiments in the present application without making any creative effort belong to the protection scope of the present application.

Further, in some flows described in the specification, claims, and above-described figures of the present application, a number of operations are included that occur in a particular order, which operations may be performed out of order or in parallel as they occur herein. The sequence numbers of the operations, e.g., 101, 102, etc., are used merely to distinguish between the various operations, and do not represent any order of execution per se. Additionally, the flows may include more or fewer operations, and the operations may be performed sequentially or in parallel. It should be noted that, the descriptions of "first", "second", etc. in this document are used for distinguishing different messages, devices, modules, etc., and do not represent a sequential order, nor limit the types of "first" and "second" to be different.

Before introducing the test method provided by the embodiment of the present application, a test system related to the test method provided by the embodiment of the present application is introduced. As shown in fig. 1, the test system includes: a test terminal 11 and a test management platform 12; wherein the content of the first and second substances,

the test terminal 11 is configured to: according to the flow chart drawing operation of a user on a flow configuration interface, displaying a test flow chart drawn by the user on the flow configuration interface; the test flow chart comprises a plurality of task nodes; according to the task binding operation of the user on the flow configuration interface aiming at each task node in the plurality of task nodes, establishing the binding relationship between each task node and the corresponding test task; generating test flow data according to the test flow chart and the binding relationship; sending the test flow data to the test management platform 12;

the test management platform 12 is configured to: and testing the application to be tested according to the test flow data.

In an example, the application to be tested may be deployed on a pre-launch server.

The test terminal 11 may be any terminal device such as a mobile phone, a tablet computer, a desktop computer, and the like. The test management platform 12 may be specifically composed of one or more test servers.

The specific processing flows of the test terminal 11 and the test management platform 12 in the test system and the interaction process between the two will be described in detail in the following embodiments, and will not be described herein again.

Fig. 2 is a schematic flowchart illustrating a data processing method according to an embodiment of the present application. The main execution body of the method is the test terminal in the test system. As shown in fig. 2, the method includes:

201. and according to the flow chart drawing operation of the user on the flow configuration interface, displaying the test flow chart drawn by the user on the flow configuration interface.

Wherein, the test flow chart comprises a plurality of task nodes.

202. And establishing a binding relationship between each task node and the corresponding test task according to the task binding operation of the user on the process configuration interface aiming at each task node in the plurality of task nodes.

203. And generating test flow data according to the test flow chart and the binding relationship.

204. And sending the test flow data to a test management platform.

In the above 201, the test flowchart includes a plurality of process nodes and a connection line with an arrow connecting the process nodes, and the plurality of process nodes includes the plurality of task nodes. Generally, the plurality of process nodes further includes: a start node and an end node. The starting node is used for starting the flow corresponding to the test flow chart, and the ending node is used for ending the flow corresponding to the test flow chart.

The test terminal may provide a flow configuration interface on its display, on which the user performs flow diagram drawing operations. The flow diagram rendering operation is for setting a plurality of task nodes and a logical relationship between the plurality of task nodes. In one example, the user can custom draw the graphic style of the task node in the flow configuration interface according to the requirement, such as: circular, rectangular, diamond, etc. It should be noted that, in the embodiment of the present application, the operation on the interface may specifically be a mouse operation or a touch screen operation, which is not specifically limited in the embodiment of the present application. That is, the flowchart drawing operation may be a mouse operation or a touch screen operation.

In another example, to improve user drawing efficiency, task node templates may be provided to the user at the flow configuration interface for direct invocation by the user. Specifically, the process configuration interface includes: the node selection area and the flow chart drawing area. The method may further include:

205. and displaying a task node template in the node selection area for a user to select.

Correspondingly, in the above 201, "drawing an operation according to a flowchart of a user on a flow configuration interface, and displaying a test flowchart drawn by the user on the flow configuration interface" includes:

2011. and in response to a dragging operation that a user drags the task node template from the node selection area to the flow chart drawing area, displaying the task node template in the flow chart drawing area to serve as one of the plurality of task nodes.

In this embodiment, a user may obtain a plurality of task nodes in a flow chart drawing area through multiple dragging operations of the task node template in the node selection area. After the task node template is dragged to the flow chart drawing area, the user can also perform fine adjustment operation on the task node template, for example: and performing fine adjustment operations such as enlarging, reducing and replacing colors, and the user can also perform displacement operation on the task node template so as to change the position of the task node template in the flow chart drawing area.

The graph style of the task node template may be automatically generated by the test management platform or designed in advance by the user, which is not specifically limited in the embodiment of the present application.

In a simple test flow chart shown in fig. 3, the task nodes (including the first task node 301 and the second task node 302) are connected in series by a connection line. Thus, the execution logic between the plurality of task nodes is also serial logic.

In 202, in an actual application, the task binding operation may be executed after the drawing of the test flowchart is finished, or may be executed before the drawing of the test flowchart is finished, which is not specifically limited in this embodiment of the application.

The binding relationship between the task node and the test task is essentially as follows: the specific format of the binding relationship between the node information of the task node and the task information of the test task may be < node information of the task node, task information of the test task >. The node information may include: node identification information, such as a node number; the task information may include: task identification information, such as a task ID number. Generally, the test tasks bound by each of the plurality of task nodes are different. Of course, the test tasks bound by some task nodes in the plurality of task nodes may also be the same, which is not specifically limited in this embodiment of the present application.

In 203, the test flow chart and the binding relationship are converted into a specified data format which is easy to store, transmit and analyze, so as to obtain test flow data.

In an implementation, the data format may be JSON (JSON object Notation) data format, which is a lightweight data exchange format.

Of course, in actual application, other data formats that need to be converted may be selected according to actual needs, and this is not specifically limited in the embodiment of the present application.

In 204, in practical application, a saving control and/or an executing control may be further displayed on the process configuration interface. And responding to the triggering operation of the user for the storage control, sending the test flow data to the test management platform so as to be stored by the test management platform, and subsequently, after receiving an execution request of the user for the test flow data, testing the application to be tested according to the test flow data by the test management platform. And responding to the triggering operation of the user for the execution control, sending an execution request to the test management platform, wherein the execution request carries the test flow data, and the test management platform receives the test flow data, stores the test flow data and tests the application to be tested according to the test flow data. The step of testing the application to be tested refers to testing an application interface API of the application to be tested.

According to the technical scheme, a user can perform custom arrangement on the test logic among the plurality of test tasks through the flow chart drawing operation and the task binding operation of the flow configuration interface, and then execute the plurality of test tasks according to the test logic arranged by the user so as to test the application to be tested. Therefore, the test scheme provided by the embodiment of the application realizes that the user-defined arrangement of the test flows of a plurality of test tasks can be completed based on simple interface operation, and has the advantages of high test flexibility and low test cost.

In practical applications, when a test scenario is complex, a logic node for defining execution logic between the plurality of task nodes is also required in the test flowchart. In one example, the test flow diagram further includes: a logical node; the logic node is used for defining execution logic among the plurality of task nodes. Wherein the execution logic may include: parallel, merged, exclusive, cyclic, one-by-one, etc. The number of the logical nodes may be one or more. The method may further include:

206. and determining branch execution conditions corresponding to at least one post branch corresponding to the logic node in the test flow chart according to the condition configuration operation of the user on the flow configuration interface aiming at the logic node.

In 203, "generating test flow data according to the test flow chart and the binding relationship" may specifically include:

2031. and generating test flow data according to the test flow chart, the binding relationship and the branch execution condition.

At 206 above, in the test flow diagram, the logical node corresponds to a pre-branch and a post-branch. The execution sequence of the logic node is prior to the flow node on the post branch and is later than the flow node on the pre branch.

Generally, in the test flow chart, one or more post branches corresponding to the logical nodes may be provided, and when one post branch corresponds to a logical node, a plurality of pre branches corresponding to the logical node are provided; when the corresponding post branch of the logical node is multiple, the corresponding pre branch of the logical node is one. The post branch is executed only when the branch execution condition corresponding to the post branch is satisfied.

In an implementation manner, in the above 206, "determining, according to the condition configuration operation of the user on the flow configuration interface for the logic node, a branch execution condition corresponding to each of at least one post-branch corresponding to the logic node in the test flow chart" may specifically be implemented by:

2061. responding to the triggering operation of the user on the flow configuration interface aiming at the logic node, and popping up a condition configuration floating layer on the flow configuration interface.

And the condition configuration floating layer displays a branch execution condition input box corresponding to each post branch in at least one post branch corresponding to the logic node.

2062. And determining the branch execution condition corresponding to each of at least one post branch corresponding to the logic node in the test flow chart according to the input operation of the user aiming at the branch execution condition input box.

In actual application, the branch execution condition input by the user can be displayed in the branch execution condition input box in response to the input operation of the user in the branch execution condition input box; and responding to the triggering operation of the confirmation control displayed by the condition configuration floating layer by the user, and determining the branch execution condition displayed in each branch execution condition input box as the branch execution condition corresponding to the corresponding post branch.

In addition, in response to the triggering operation of the confirmation control displayed by the user for the condition configuration floating layer, the condition configuration floating layer can be closed on the process configuration interface, so that the user can conveniently perform subsequent editing operation.

In practice, the logical type of the logical node may include, but is not limited to: parallel logic types, merge logic types, exclusive logic types, loop logic types, and one-by-one logic types. The logic node of the parallel logic type is corresponding to a preposed branch and a plurality of postpositional branches and is used for executing the plurality of postpositional branches in parallel; the logic node of the merging logic type is corresponding to a plurality of prepositive branches and a postpositive branch and is used for merging the execution structures of the prepositive branches; the logic node of the exclusive logic type is corresponding to a preposed branch and a plurality of postpositional branches, and the execution logic of the plurality of postpositional branches is exclusive logic, namely only one of the plurality of postpositional branches is executed; the logic node of the circulation logic type is corresponding to a front branch and two rear branches, and one rear branch of the two rear branches is connected to the task node on the front branch so as to circularly execute the task node on the front branch; the logic node of one-by-one logic type is corresponding to a preposed branch and a plurality of postpositional branches for executing the plurality of postpositional branches one by one.

Taking the logic node a1 with parallel logic types as an example, the logic node a1 includes: the branch execution conditions of the two post branches are the same, and the branch execution conditions are the execution completion of the flow nodes on the pre branch.

Taking the logic node a2 with the logic type as merge as an example, the logic node a2 includes: two front branches and one rear branch, the branch execution condition of the rear branch is: and the flow nodes on each of the two front branches are executed and completed.

Typically, logical nodes with logic types in parallel are used with logical nodes with logic types in merge. As shown in fig. 4, two back branches of a parallel logical node 401 (i.e., a logical node whose logical type is parallel) are merged by a merge logical node 404 (i.e., a logical node whose logical type is merge). A first task node 402 and a second task node 403 are respectively arranged on two rear branches of the parallel logic node 401.

Taking the logical node B with the logical type as a loop as an example, the logical node B includes: the system comprises a front branch and two rear branches, wherein the branch execution condition of one rear branch is that the circulation frequency of a flow node (generally a task node) on the front branch reaches a preset frequency, and the branch execution condition of the other rear branch is that the flow node on the front branch does not reach the preset frequency.

Taking the logic type as the logic node C one by one as an example, the logic node C includes: the system comprises a front branch, a first rear branch and a second rear branch, wherein the branch execution condition of the first rear branch is that the flow node on the front branch is executed completely, and the branch execution condition of the second rear branch is that the flow node on the first rear branch is executed completely.

Taking the logic node D with the logic type as the exclusive logic node as an example, the logic node D includes: the system comprises a front branch, a first rear branch and a second rear branch, wherein the branch execution condition of the first rear branch is that the execution result of a flow node on the front branch meets a preset condition; the branch execution condition of the second post branch is that the execution result of the flow node on the pre branch does not meet the preset addition.

In one implementation, the plurality of task nodes includes a first task node. In 202, "establishing a binding relationship between the first task node and the corresponding test task according to the task binding operation of the user on the flow configuration interface for the first task node" may specifically be implemented by adopting the following steps:

2021. and responding to the triggering operation of the user on the flow configuration interface aiming at the first task node, and displaying a plurality of test tasks for the user to select.

2022. And responding to the selection operation of the user for a first test task in the plurality of test tasks, and establishing a binding relationship between the first task node and the first test task.

In the above 2021, the displaying of the plurality of test tasks may specifically be displaying task information for each of the plurality of test tasks. The task information may include: and identifying information of the task. The task identification information may include: task name, task ID number, etc.

The task information for the plurality of test tasks may be obtained from a test management platform. The test management platform stores a plurality of test tasks which are edited by the user and/or other users in advance, so that the reuse of the test tasks is facilitated, the test cost is reduced, and the test efficiency is improved. That is, the plurality of test tasks stored by the test management platform can be regarded as test assets, and any user can directly obtain the test assets for use.

The plurality of test tasks include: test tasks previously created by the user and/or test tasks previously created by other users.

In practical application, task information of a plurality of test tasks can be directly displayed on the flow configuration interface, or a test task floating layer is popped up on the flow configuration interface, and the task information of the plurality of test tasks is displayed on the test task floating layer.

In practical applications, the plurality of test tasks may include: the test task based on code calling application interface and the test task based on test tool calling application interface.

The test task based on the code calling application interface is tested by calling the application interface through the code when the test task is executed; the test task based on the application interface called by the test tool refers to that the application interface is called by the test tool to perform the test when the tester task is executed.

In an example, the plurality of test tasks bound by the plurality of task nodes include a test task that calls the application interface based on code and/or a test task that calls the application interface based on a test tool.

In 2022, the selection operation may be a click operation for the first test task.

In order to facilitate the creation of the test task by the user, the method may further include:

207. a first task editing interface is provided.

Wherein, the first task editing interface displays an execution command input box.

208. Displaying the execution command input by the user in the execution command input box in response to the input operation of the user for the execution command input box.

209. And generating a test task based on a code calling application interface according to the execution command.

The test task may include the execution command.

210. And sending the test task based on the code calling application interface to the test management platform for storage for subsequent use.

The first task editing interface is used for editing the test tasks based on the code calling application interface.

Wherein the executing command comprises: and storing the script test case required to be executed by the test task in a code warehouse.

In actual application, all script test cases corresponding to the application to be tested can be stored in a code warehouse in advance. All script test cases written by users aiming at the application to be tested in history can be stored in the code warehouse.

In particular, the code repository may be configured with a plurality of branches for the applications to be tested, with different branches being used to test different aspects of the applications to be tested. Therefore, the first task editing interface may further be provided with a branch input box, and in response to an input operation performed by a user on the branch input box, the branch input box displays a branch name input by the user. Correspondingly, a test task based on code calling is generated according to the execution command and the branch name. The test task comprises the execution command and the branch name.

Of course, the user may also input a task name in a task name input box displayed on the first task editing interface. And generating a test task based on code calling according to the execution command and the task name. The test task includes an execution command and a task name.

In order to facilitate a user to correspondingly modify the script test case to adapt to the test task of the user, the first task editing interface may further display a configuration input box, and the method may further include:

211. and responding to the triggering operation of the user for the configuration input box, and displaying the configuration identification information of each of the plurality of parameter configurations for the user to select.

212. In response to the user's selection operation for the configuration identification information of a first parameter configuration of the plurality of parameter configurations, displaying the configuration identification information of the first parameter configuration at the configuration input box.

The first parameter configuration is used for updating parameters of script test cases which need to be executed by the test tasks based on the code calling application interface. The first parameter configuration may include a plurality of parameters, each parameter including: parameter names and parameter values, such as: the test environment is pre (pre environment). When the script test case is updated based on the first parameter configuration, if the test environment in the script test case is online (online environment), the parameter value online of the test environment in the script test case is modified to be pre.

The configuration identification information of each of the plurality of parameter configurations may be acquired from the test management platform side. The test management platform stores a plurality of parameter configurations and configuration identification information thereof which are obtained by the user and/or other users through editing in advance, so that the multiplexing of test tasks is facilitated, the test cost is reduced, and the test efficiency is improved. That is, the multiple parameter configurations stored by the test management platform can be regarded as test assets, and all authorized users can directly obtain and use the test assets.

The selection operation may be a click operation.

The "generating a test task based on a code invocation application interface according to the execution command" in 209 may specifically include:

and generating the test task based on the code calling application interface according to the execution command and the configuration identification information configured by the first parameter.

The test task comprises the execution command and configuration identification information of the first parameter configuration. Therefore, in the process of executing the test according to the test flow data, the subsequent test management platform can modify the script test case related to the test task according to the first parameter configuration, and then perform the test based on the modified script test case.

Further, the method may further include:

213. a configuration editing interface is provided.

214. And generating parameter configuration according to a plurality of parameters input by the user on the configuration editing interface.

Wherein the parameter configuration comprises the plurality of parameters.

215. And sending the parameter configuration to a test management platform for storage for subsequent use.

In one example, after receiving the parameter configuration, the test server may generate configuration identification information for the parameter configuration, so as to uniquely identify the parameter configuration, and store the parameter configuration and the configuration identification information thereof in an associated manner. In another example, a user may enter a configuration name as configuration identification information at a configuration editing interface; and subsequently, the parameter configuration and the configuration identification information thereof are sent to a test management platform for storage.

Specifically, a preset number of parameter input boxes can be displayed on a configuration interface, so that a user can input a preset number of parameters; in addition, a control can be added to the parameter input boxes displayed on the configuration interface, and one or more parameter input boxes are added and displayed in response to the triggering operation of the user on the control, so that the user can input parameters.

Optionally, the method may further include:

213. and providing a second task editing interface.

And the second task editing interface displays a useful example set input box.

214. And responding to the triggering operation of the user on the use case set input box, and displaying the identification information of the use case sets of the plurality of use case sets for the user to select.

Wherein the use case set comprises a plurality of tool test use cases.

215. And responding to the selection operation of the user for the use case set identification information of a first use case set in the plurality of use case sets, and displaying the use case set identification information of the first use case set in the use case set input box.

216. And generating a test task based on a test tool calling application interface according to the case set identification information of the first case set.

217. And sending the test task based on the application interface called by the test tool to the test management platform for storage for subsequent use.

The multiple use cases may be edited by the user and/or other users in advance. The test task comprises use case set identification information of the first use case set. In an example, a task name may also be included in the test task, and the task name may be input by the user at the second task editing interface. When the test system is applied, the test task is executed, that is, all tool test cases in the case set corresponding to the test task are executed.

The test tasks created through the first task editing interface and the second task editing interface are stored on the test management platform, and when a subsequent user binds the tasks, the test tasks can be directly obtained from the test management platform side.

In the test execution process of the test management platform, aiming at the test task based on the code calling API, the container is started according to the execution command in the test task to execute the test task. And calling the testing tool to execute the testing task by initiating an http request aiming at the testing task based on the API called by the testing tool.

Optionally, in order to facilitate the user to view the test result of the test task, the method may further include:

218. and displaying the test flow chart on a test result interface.

219. And receiving the test result of the test task sent by the test management platform in the process of testing the application to be tested by the test management platform according to the test flow data.

220. And displaying the test result in an area associated with the task node bound by the test task on the test result interface.

In step 219, the test management platform may send the test result of each test task to the test terminal after the test tasks corresponding to the plurality of task nodes are all completed; or after any task node in the plurality of task nodes completes the test, sending the test result of the test task to the test terminal.

In 220, in an example, the test result may be displayed in an area associated with the task node to which the test task is bound directly on a test result interface. In another example, the test result may be displayed in an area associated with a task node to which the test task is bound in response to a result viewing operation triggered by a user for that task node, such as: a nearby area.

Further, the test result includes failure case information. The method can further comprise the following steps:

221. and responding to the triggering operation of the user on the failed use case information, and sending a failed use case re-execution request to the test server.

And the failed use case re-execution request carries the information of the failed use case. The failure case information may include: and using case identification information.

Further, the method may further include:

222. and displaying the re-execution control on the test result interface.

223. And responding to the triggering operation of the user for the re-execution control, and sending a re-execution request to a test management platform to request the test server to re-execute the test on the application to be tested according to the test flow data.

Further, the method may further include:

224. and displaying an interruption execution control on the test result interface.

225. And responding to the triggering operation of the user for the interruption execution control, and sending an interruption request to a test management platform to request the test server to interrupt the test.

In practice, before the steps of the embodiments are performed, the test application initialization may be performed. That is, the test application for testing the application to be tested is initialized to the test management platform, and the subsequent test management platform can implement the processing steps involved in the above embodiments. Typically, test application initialization includes test application branch synchronization, mirroring construction of containers, from the code repository. Wherein the mirror image is constructed according to synchronously obtained branch information of the test application branch. During testing, each test task may be performed by one container. The mirror image of the container is automatically constructed when the branches are synchronized, so that the mirror image is directly used for creating the container in subsequent execution, and the waiting time of each execution is saved.

Because one set of API usually only corresponds to one test application, the execution of the application initialization is not required to be repeatedly executed. In addition, the webhook mode can be supported to trigger test case synchronization when the test application branch changes (for example, test cases are added, deleted and modified), that is, the test management platform is informed that a test case has changed.

Fig. 5 is a flowchart illustrating an application testing method according to another embodiment of the present application. The method is suitable for the test management platform. As shown in fig. 5, the method includes:

501. and acquiring test flow data.

The test flow data are generated by the test terminal according to the binding relationship between each task node in the test flow chart and the corresponding test task; the test flow chart comprises a plurality of task nodes; the test flow chart is generated by the test terminal according to the flow chart drawing operation of the user on the flow configuration interface; and the binding relationship is established by the test terminal according to the task binding operation of the user on each task node in the process configuration interface.

502. And testing the application to be tested according to the test flow data.

In one example, the

steps

501 and 502 may be executed after receiving an execution request sent by the test terminal for the test flow data, that is, in response to a manual operation by the user. Alternatively, the

above steps

501 and 502 are performed under automatic triggering of a periodic trigger mechanism set by the user in advance.

In another example, the

steps

501 and 502 may be executed after receiving an execution request sent by a third party application publishing platform where the application to be tested is located, that is, the third party application publishing platform may trigger the execution of the test process through an API interface; alternatively, the

steps

501 and 502 may be triggered to be executed when it is monitored that the API interface of the application to be tested on the third-party publishing platform is changed. Therefore, the problem of test flow cracking is solved.

In an implementation manner, the step 502 of "testing the application to be tested according to the test flow data" can be implemented by the following steps:

5021. and determining the test tasks bound to the task nodes according to the test flow data.

5022. And acquiring a test case required by the test task.

5023. And generating an execution code according to the test flow data and the test case.

5024. And running the execution code to test the application to be tested.

In 5021, the binding relationship between the task nodes and the test tasks is determined according to the test flow data, and the test tasks bound to the plurality of task nodes are determined according to the binding relationship.

In 5022, the required test case is obtained according to the case set or the execution command in the test task.

In 5023, the test flow data is analyzed into a code model, and an execution code is generated according to the code model and the test case.

And running the execution code to test the application to be tested, namely executing a plurality of test tasks according to execution logic among a plurality of test tasks defined by the test flow chart to test the application to be tested. Specifically, each node in the test flow graph is executed in turn. When the currently executed node is a task node, inquiring the execution result of the task node, determining whether the execution of the test task corresponding to the task node is finished according to the execution result, and if the execution is finished, continuing to execute the next node in the test flow chart; and when the currently executed node is a logic node, determining the current post branch required to be executed according to the branch execution condition of the logic node. And when the currently executed node is the end node, ending the test.

Here, it should be noted that: the content of each step in the method provided by the embodiment of the present application, which is not described in detail in the foregoing embodiment, may refer to the corresponding content in the foregoing embodiment, and is not described herein again. In addition, the method provided in the embodiment of the present application may further include, in addition to the above steps, other parts or all of the steps in the above embodiments, and specific reference may be made to corresponding contents in the above embodiments, which is not described herein again.

It is to be added that in practice only one test task is sometimes involved in a test at a time. The user can trigger a test for a certain test task at the test terminal, or trigger a test for a certain test task after receiving an execution request sent by a third-party application release platform where the application to be tested is located; or, a test may be triggered for a certain test task when it is monitored that the API interface of the application to be tested on the third-party publishing platform changes.

In practical applications, the test management platform is provided with a task definition and management device, as shown in fig. 6, the task definition and management device may include:

the application initialization module 601, whose functions are: the code testing application is initialized to a testing management platform (also called API management platform), including application branch synchronization, mirror image construction and pulling of script cases, and meanwhile, a webhook mode is supported to trigger case synchronization when branches are changed. Because one set of API usually only corresponds to one test application, the execution of the application initialization is not required to be repeatedly executed.

A parameter configuration module 602, which functions to: and defining parameter configuration required by case execution. The parameter configuration can be reused under various test scenes such as single case execution, batch execution, task execution, multiple task arrangement execution and the like, and is equal to the assets in the test process.

The task editing module has the functions of: defining a test task (which can be regarded as a task entity), and creating the test task based on a test tool calling an API interface requires a user to select one or more cases on a platform to form a case set; the test task based on code call API requires the user to fill in the branch name, the configuration identification information of the corresponding parameter configuration, and the execution command. The task can also be configured with a periodic execution time to meet the requirement of task timing test. In addition, the test task also supports functions of interruption, rerun-only failure case and the like to improve the test efficiency.

A task execution module 604, which functions to: a test task is performed once.

The test management platform is also provided with a visual task arrangement device. As shown in fig. 7, the visual task orchestration device includes: visualization arrangement module 605, metadata arrangement module 606, model analysis module 607, flow execution module 608, task execution module 604, and result query module 609. Wherein, the first and the second end of the pipe are connected with each other,

the visualization orchestration module 605 functions to: and defining each execution stage in the arrangement flow as a component, and arranging the flow in a visual component dragging mode. The visualization component comprises a starting node, an ending node, a task node, a logic node and the like.

The metadata arranging module 606 functions as: the process is defined by means of JSON metadata, and the components are defined in an array named elements. Each component of the visualization corresponds to an element in the elements, and the result of the visualization is actually interacting with the backend through the metadata. The start node and the end node are fixed; the definition of the corresponding metadata of the task node (also called task linker) is shown in fig. 8, which includes: type, task name, task unique ID, target component, process instance unique ID, and the like.

Where type refers to the type of task, for example: calling the type of API based on the testing tool or calling the type of API based on the code; the task unique ID is used for identifying a task to be operated, and the target component represents the next component planned to be operated after the task is successfully operated; the process instance unique ID is used to identify which process instance the current task originated from, and this data is typically generated when the corresponding test task executes. The user forms a record for each saving of the metadata, so that history tracing can be realized.

The model analysis module 607 functions to: and analyzing the elements array, and analyzing the metadata in the elements array into a code model which can be executed by a flow execution module in the arrangement engine.

A flow execution module 608, which functions to: and sequentially initiating a thread to execute each component according to the code model.

A task execution module 604, which functions to: when the component is a task linker, the task execution module 604 in the task definition and management device executes the test task, and after the test task is executed, the result query module 609 polls the task result, and when the task is executed, the process execution module 608 executes the next component.

A result query module 609, which functions to: and in the execution process, the result query of a single component is realized, the execution log is recorded, the execution result of the flow can be queried in the flow execution process or after the flow is completed, and the result is rendered on a page in a visual flow chart mode. And also supports the direct operation of interruption, rerun failure use case and the like on the task in the process.

The specific implementation of each module can refer to the corresponding content in each embodiment, and is not described herein again.

To sum up, the application test scheme provided by the embodiment of the application has the following beneficial effects:

1. in cost, a unified machine management container is provided, the machine cost and the cost of manually maintaining the machine are removed, and the mirror image construction cost of each execution is completely removed through automatic branch synchronization.

2. In the aspect of arrangement semantics, the task arrangement is realized through an arrangement engine, and various logics such as serial logic, parallel logic, circulation logic, exclusive logic and the like are supported.

3. Functionally, API test tasks in two modes of test tool calling and script calling are supported, failed cases are directly rerun on task or task arrangement flows, and the flows are completed after parallel task results are aggregated.

4. The execution of the task or the arrangement flow is triggered through an interface on a third-party code release platform and also triggered when the API is changed, so that the problem of test flow splitting is solved.

5. The test efficiency is improved and the test cost is reduced by the unified management of assets, the task arrangement realizes the automatic trigger change and the timing trigger by multiplexing the test cases and logically arranging the test tasks, the development personnel are helped to improve the test efficiency, the API stability is maintained, and the test process is enhanced.

The technical scheme provided by the embodiment of the application is described below by taking the application to be tested as the cloud computing service application as an example:

generally, API interfaces of cloud computing service applications include, but are not limited to: the method comprises the steps of creating an API (application programming interface) for the cloud computing resources, deleting an API (application programming interface) for the cloud computing resources and updating an API for the cloud computing resources. In an example, the cloud computing resource may be: the container resources are provided for use by the customer.

The test user can draw the test flow chart on a flow editing interface provided by the test user, bind corresponding test tasks aiming at task nodes in the test flow chart, and set corresponding branch execution conditions aiming at logic nodes in the test flow chart, so as to generate test flow data. The tool test case or the script test case related to the test task is used for testing an API (application programming interface) of the cloud computing service application.

And sending the generated test flow data to a test management platform for storage, and subsequently executing a test according to the pre-stored test flow data under manual trigger of a user, under automatic trigger of a periodic trigger mechanism preset by the user, under trigger of a third-party application release platform or under automatic trigger when monitoring that an API (application programming interface) of a cloud computing service application deployed on the third-party application release platform (such as the interface or a back-end code of the interface) is changed.

Fig. 9 shows a schematic structural diagram of an electronic device according to an embodiment of the present application. As shown in fig. 9, the electronic device includes a memory 1101 and a processor 1102. The memory 1101 may be configured to store other various data to support operations on the electronic device. Examples of such data include instructions for any application or method operating on the electronic device. The memory 1101 may be implemented by any type or combination of volatile or non-volatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.

The memory 1101 is used for storing programs;

the processor 1102 is coupled to the memory 1101, and configured to execute the program stored in the memory 1101, so as to implement the application testing method provided by each of the above method embodiments.

Further, as shown in fig. 9, the electronic device further includes: communication components 1103, display 1104, power components 1105, audio components 1106, and the like. Only some of the components are schematically shown in fig. 9, and the electronic device is not meant to include only the components shown in fig. 9.

Accordingly, the present application further provides a computer-readable storage medium storing a computer program, where the computer program can implement the steps or functions of the application testing method provided by the above method embodiments when executed by a computer.

The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one position, or may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.

Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware. With this understanding in mind, the above-described technical solutions may be embodied in the form of a software product, which can be stored in a computer-readable storage medium such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present application.

Claims

1. An application testing method is suitable for a testing terminal, and comprises the following steps:

according to the task binding operation of the user on the process configuration interface aiming at each task node in the plurality of task nodes, establishing a binding relation between each task node and a corresponding test task;

sending the test flow data to a test management platform;

2. The method of claim 1, wherein the test flow graph further comprises: a logical node; the logic node is used for defining execution logic among the plurality of task nodes;

the method further comprises the following steps:

determining branch execution conditions corresponding to at least one post branch corresponding to the logic node in the test flow chart according to the condition configuration operation of the user on the flow configuration interface aiming at the logic node;

generating test flow data according to the test flow chart and the binding relationship, wherein the test flow data comprises:

and generating test flow data according to the test flow chart, the binding relationship and the branch execution condition.

3. The method of claim 2, wherein the logical type of the logical node comprises: parallel logic type, merge logic type, exclusive logic type, loop logic type, one-by-one logic type.

4. The method of any of claims 1-3, wherein a first task node is included in the plurality of task nodes;

according to the task binding operation of the user on the flow configuration interface aiming at the first task node, establishing a binding relation between the first task node and the corresponding test task, wherein the binding relation comprises the following steps:

responding to the triggering operation of the user on the flow configuration interface aiming at the first task node, and displaying a plurality of test tasks for the user to select;

and responding to the selection operation of the user for a first test task in the plurality of test tasks, and establishing a binding relationship between the first task node and the first test task.

5. The method of claim 4, wherein the plurality of test tasks includes: the test task based on code calling application interface and the test task based on test tool calling application interface.

6. The method of claim 4, further comprising:

providing a first task editing interface;

displaying an execution command input by the user within the execution command input box in response to an input operation of the user for the execution command input box; the execution command includes: storing the script test case to be executed by the test task in a code warehouse;

generating a test task based on a code calling application interface according to the execution command;

and sending the test task based on the code calling application interface to the test management platform for storage for subsequent use.

7. The method of claim 6, wherein the first task editing interface further displays a configuration input box; the method further comprises the following steps:

responding to the triggering operation of the user for the configuration input box, and displaying configuration identification information of each of a plurality of parameter configurations for the user to select;

in response to the user's selection operation for configuration identification information of a first parameter configuration in the plurality of parameter configurations, displaying the configuration identification information of the first parameter configuration in the configuration input box; the first parameter configuration is used for updating the parameters of the script test case which needs to be executed by the test task based on the code calling application interface;

generating a test task based on code calling according to the execution command, wherein the test task comprises the following steps:

8. The method of claim 4, further comprising:

providing a second task editing interface; the second task editing interface displays a useful case set input box;

responding to the triggering operation of the user for the use case set input box, and displaying respective use case set identification information of a plurality of use case sets for the user to select; the case set comprises a plurality of tool test cases;

responding to the selection operation of the user for the use case set identification information of a first use case set in the plurality of use case sets, and displaying the use case set identification information of the first use case set in the use case set input box;

generating a test task based on a test tool calling application interface according to the case set identification information of the first case set;

and sending the test task based on the application interface called by the test tool to the test management platform for storage for subsequent use.

9. The method of any of claims 1 to 3, further comprising:

displaying the test flow chart on a test result interface;

receiving a test result of the test task sent by the test management platform in the process that the test management platform tests the application to be tested according to the test flow data;

and displaying the test result in an area associated with the task node bound by the test task on the test result interface.

10. The method of any of claims 1 to 3, wherein generating test flow data from the test flow graph and the binding relationship comprises:

generating metadata corresponding to each task node in the plurality of task nodes according to the test flow chart and the binding relationship; the metadata includes: task information of a test task bound by a corresponding task node and node information of a next node of the task node;

and generating test flow data according to the metadata corresponding to the plurality of task nodes.

11. An application testing method is suitable for a test management platform, and comprises the following steps:

acquiring test flow data; the test flow data is generated by the test terminal according to the test flow chart and the binding relationship between each task node and the corresponding test task in the plurality of task nodes; the test flow chart comprises a plurality of task nodes; the test flow chart is generated by the test terminal according to the flow chart drawing operation of a user on a flow configuration interface; the binding relationship is established by the test terminal according to the task binding operation of the user on the flow configuration interface aiming at each task node;

and testing the application to be tested according to the test flow data.

12. The method of claim 11, wherein testing an application under test according to the test flow data comprises:

determining the test tasks bound to the plurality of task nodes according to the test flow data;

obtaining a test case required by the test task;

generating an execution code according to the test flow data and the test case;

and running the execution code to test the application to be tested.

13. An application testing system, comprising: the system comprises a test terminal and a test management platform;

the test terminal is used for: according to the flow chart drawing operation of a user on a flow configuration interface, displaying a test flow chart drawn by the user on the flow configuration interface; the test flow chart comprises a plurality of task nodes; according to the task binding operation of the user on the flow configuration interface aiming at each task node in the plurality of task nodes, establishing the binding relationship between each task node and the corresponding test task; generating test flow data according to the test flow chart and the binding relationship; sending the test flow data to the test management platform;

14. An electronic device, comprising: a memory and a processor, wherein,

the memory is used for storing programs;

the processor, coupled to the memory, is configured to execute the program stored in the memory to implement the application testing method of any one of claims 1 to 12.