CN114564402A - Task flow testing method and device, readable medium and electronic equipment - Google Patents
Task flow testing method and device, readable medium and electronic equipment Download PDFInfo
- Publication number
- CN114564402A CN114564402A CN202210204885.1A CN202210204885A CN114564402A CN 114564402 A CN114564402 A CN 114564402A CN 202210204885 A CN202210204885 A CN 202210204885A CN 114564402 A CN114564402 A CN 114564402A
- Authority
- CN
- China
- Prior art keywords
- task flow
- task
- test
- target
- node
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The disclosure relates to a method, a device, a readable medium and an electronic device for testing a task flow, which relate to the technical field of electronic information processing, and the method comprises the following steps: and receiving a task editing instruction, analyzing the task editing instruction to establish a plurality of task flow nodes according to a specified sequence, and configuring the attribute information of each task flow node. And converting each task process node into resource data in a preset format, and exporting the resource data to a preset engine. And integrating the unit test script corresponding to each task flow node and the total test script into an automatic test framework of a preset engine. And calling an automatic test framework in a preset engine, generating and executing a test project, wherein the test project is used for determining task flow nodes corresponding to the task flows according to the resource data when each task flow runs, and calling unit test scripts corresponding to the task flow nodes. The method and the device can quickly verify the integrity and the correctness of the task flow.
Description
Technical Field
The present disclosure relates to the field of electronic information processing technologies, and in particular, to a method and an apparatus for testing a task flow, a readable medium, and an electronic device.
Background
With the continuous development of electronic information technology, various game-like applications are appearing in the application market. For scenario-like gaming applications, the key is the player's experience with the mission scenario. If the scenario of the task is incomplete and unsmooth, the quality of the game application is seriously affected. During the development process, task scenarios of game applications are usually complex, for example, a dominant line scenario includes dozens of scenario tasks, and also includes many branch line scenario tasks, level tasks, achievement tasks, daily tasks, and the like. A tester needs to test whether the game application is complete and smooth, a large amount of time is usually spent, and the efficiency and the accuracy are difficult to guarantee.
Disclosure of Invention
This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
In a first aspect, the present disclosure provides a method for testing a task flow, where the method includes:
receiving a task editing instruction, analyzing the task editing instruction to establish a plurality of task flow nodes according to a specified sequence, and configuring attribute information of each task flow node, wherein each task flow node corresponds to one task flow;
converting each task process node into resource data in a preset format, and exporting the resource data to a preset engine, wherein the resource data comprises attribute information and sequence of the task process node;
integrating a unit test script corresponding to each task flow node and a total test script into an automatic test framework of the preset engine, wherein the total test script is used for maintaining a plurality of unit test scripts, and the unit test scripts are used for verifying the corresponding task flows;
and calling the automatic test framework in the preset engine, generating and executing a test project, wherein the test project is used for determining a task flow node corresponding to each task flow according to the resource data when each task flow runs, and calling the unit test script corresponding to the task flow node.
In a second aspect, the present disclosure provides a device for testing a task flow, the device including:
the editing module is used for receiving a task editing instruction, analyzing the task editing instruction to establish a plurality of task flow nodes according to a specified sequence, and configuring attribute information of each task flow node, wherein each task flow node corresponds to one task flow;
the export module is used for converting each task flow node into resource data in a preset format and exporting the resource data to a preset engine, wherein the resource data comprises attribute information and sequence of the task flow node;
the integrated module is used for integrating a unit test script corresponding to each task flow node and a total test script into an automatic test framework of the preset engine, wherein the total test script is used for maintaining a plurality of unit test scripts, and the unit test scripts are used for verifying the corresponding task flows;
and the test module is used for calling the automatic test framework in the preset engine, generating and executing a test project, wherein the test project is used for determining task flow nodes corresponding to the task flows according to the resource data when each task flow runs, and calling the unit test scripts corresponding to the task flow nodes.
In a third aspect, the present disclosure provides a computer readable medium having stored thereon a computer program which, when executed by a processing apparatus, performs the steps of the method of the first aspect of the present disclosure.
In a fourth aspect, the present disclosure provides an electronic device comprising:
a storage device having a computer program stored thereon;
processing means for executing the computer program in the storage means to implement the steps of the method of the first aspect of the present disclosure.
According to the technical scheme, the method comprises the steps of firstly receiving a task editing instruction, establishing a plurality of task flow nodes according to the task editing instruction and a designated sequence, and configuring corresponding attribute information, wherein each task flow node corresponds to one task flow. And then, converting each task flow node into resource data in a preset format, and exporting the resource data to a preset engine. And integrating the unit test script corresponding to each task flow node and the total test script for maintaining the plurality of unit test scripts into an automatic test framework. And finally, calling an automatic test framework in a preset engine, generating and executing a test project, and calling a unit test script corresponding to each task flow when each task flow runs. According to the method and the device, the task flow nodes are established, and the association between the task flow nodes and the unit test scripts is obtained to obtain the test engineering, so that the automatic test of the task flow is realized, and the integrity and the correctness of the task flow can be rapidly verified.
Additional features and advantages of the disclosure will be set forth in the detailed description which follows.
Drawings
The above and other features, advantages and aspects of various embodiments of the present disclosure will become more apparent by referring to the following detailed description when taken in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numbers refer to the same or similar elements. It should be understood that the drawings are schematic and that elements and features are not necessarily drawn to scale. In the drawings:
FIG. 1 is a flow diagram illustrating a method of testing a task flow in accordance with an exemplary embodiment;
FIG. 2 is a schematic diagram illustrating a task editor in accordance with an illustrative embodiment;
FIG. 3 is a flow diagram illustrating another method of testing a task flow in accordance with an exemplary embodiment;
FIG. 4 is a flow diagram illustrating another method of testing a task flow in accordance with an exemplary embodiment;
FIG. 5 is a flow diagram illustrating another method of testing a task flow in accordance with an exemplary embodiment;
FIG. 6 is a schematic diagram illustrating a method of testing a task flow in accordance with an exemplary embodiment;
FIG. 7 is a schematic diagram illustrating a task editor in accordance with an illustrative embodiment;
FIG. 8 is a block diagram of a testing device illustrating a task flow according to an exemplary embodiment;
FIG. 9 is a block diagram of a testing device illustrating another task flow according to an exemplary embodiment;
FIG. 10 is a block diagram of a testing device illustrating another task flow according to an exemplary embodiment;
FIG. 11 is a block diagram of a testing device illustrating another task flow according to an exemplary embodiment;
FIG. 12 is a block diagram illustrating an electronic device in accordance with an example embodiment.
Detailed Description
Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and the embodiments of the disclosure are for illustration purposes only and are not intended to limit the scope of the disclosure.
It should be understood that the various steps recited in the method embodiments of the present disclosure may be performed in a different order, and/or performed in parallel. Moreover, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this respect.
The term "include" and variations thereof as used herein are open-ended, i.e., "including but not limited to". The term "based on" is "based, at least in part, on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions for other terms will be given in the following description.
It should be noted that the terms "first", "second", and the like in the present disclosure are only used for distinguishing different devices, modules or units, and are not used for limiting the order or interdependence of the functions performed by the devices, modules or units.
It is noted that references to "a", "an", and "the" modifications in this disclosure are intended to be illustrative rather than limiting, and that those skilled in the art will recognize that "one or more" may be used unless the context clearly dictates otherwise.
The names of messages or information exchanged between devices in the embodiments of the present disclosure are for illustrative purposes only, and are not intended to limit the scope of the messages or information.
All actions of acquiring signals, information or data in the present disclosure are performed under the premise of complying with the corresponding data protection regulation policy of the country of the location and obtaining the authorization given by the owner of the corresponding device.
Before introducing the method, the apparatus, the readable medium, and the electronic device for testing task flows provided by the present disclosure, an application scenario related to each embodiment of the present disclosure is first introduced, where the application scenario may be a task scenario in a game application that is edited by a task editor, where the task scenario may include a plurality of task flows, one task flow may be understood as one task, such as a scenario task, a branch scenario task, a level task, an achievement task, a daily task, and the like, the task flow may also be understood as one subtask, such as a scenario subtask, a level subtask, an achievement subtask, and the like in the scenario subtask, and the task flow may also be understood as one behavior, such as a browsing conversation behavior, an interaction behavior, a movement behavior, and the like in the scenario subtask. The game application is developed based on a preset engine, which may be, for example, a Unity engine, a unregengine, a Frostbite engine, a Source engine, a Cocos engine, etc., and the disclosure is not limited thereto. The task editor is embedded in the preset engine and can directly interact with the preset engine.
FIG. 1 is a flow diagram illustrating a method for testing a task flow, according to an exemplary embodiment, which, as shown in FIG. 1, includes the steps of:
For example, a task editor may receive a task editing instruction, and the task editor may be provided with a corresponding UI (english: user interface, chinese: user interface), as shown in fig. 2, a planner may trigger the task editing instruction in the UI interface through dragging, clicking, entering, and the like, and the task editing instruction may include information of each task flow, a task type, and a specified sequence between multiple task flows. After receiving the task editing instruction, the task editor can analyze the task editing instruction to extract the information, task type and assigned sequence of each task flow, then establish corresponding task flow nodes for each task flow, and configure the attribute information of the task flow nodes corresponding to the task flow according to the information of each task flow. And finally, the plurality of task flow nodes can be sequentially connected according to a designated sequence, so that the task flow node corresponding to the task flow executed earlier points to the task flow node corresponding to the task flow executed later. For example, the pointing relationship may be represented by a unidirectional arrow, a parent node and a child node in a tree structure, or a pointer, which is not specifically limited by the present disclosure. As shown in the left presentation area in fig. 2, which includes 4 task flow nodes, the designated order is represented by a unidirectional arrow, i.e., "Start" → "behavior: dialog with the angerolo doctor "→" behavior: dialog with a friend of a coma "→" behavior: go to home ".
In an example, each task flow node can be displayed in the task editor, and the connection relationship (namely, the designated sequence) among the task flow nodes can also be displayed, so that a planning person can conveniently view, edit and check each task flow. In order to facilitate the preset engine or other platforms to obtain the relevant information of each task flow, each task flow node may be serialized to convert the resource data into the resource data in the preset format commonly used in the preset engine, and the resource data is exported to the preset engine. Specifically, the resource data may include attribute information and sequence of each task flow node, that is, the resource data may describe both the task flow node and a connection relationship between the task flow node and other task flow nodes. Resource data may also be understood as abstract processing of task flow nodes. Taking the example that the preset engine is an Urealengine 4, the preset format may be a DataAsset format, each task process node may be converted into a DataAsset type resource, and then a plurality of DataAsset type resources may be exported to the UnrealEngine 4 for serialization to obtain data in a Json format, so as to achieve the purpose of abstracting the task process nodes, and enable the preset engine or other platforms to read the resource data.
And 103, integrating the unit test scripts corresponding to the task flow nodes and the total test scripts into an automatic test framework of a preset engine, wherein the total test scripts are used for maintaining a plurality of unit test scripts, and the unit test scripts are used for verifying the corresponding task flows.
And 104, calling an automatic test framework in a preset engine, generating and executing a test project, wherein the test project is used for determining task flow nodes corresponding to the task flows according to the resource data when each task flow runs, and calling unit test scripts corresponding to the task flow nodes.
For example, a corresponding unit test script may be established for each task flow node, and the unit test script is used to verify the corresponding task flow, for example, the unit test script may be used to test whether the corresponding task flow enters normally, may also be used to test whether the corresponding task flow ends normally, and may also be used to test whether the sequence of the task flows is correct. Meanwhile, a total test script for all task flows can be established, the total test script can maintain a plurality of unit test scripts, for example, each unit test script can be called in sequence according to a specified sequence, and the execution result of each unit test script can be recorded. The corresponding relationship between the unit test scripts and the task flow nodes can be determined according to the task identifiers, and a relationship table can be established for storing the corresponding relationship between each unit test script and the corresponding task flow node. The unit test scripts and the total test scripts corresponding to the task flow nodes can be integrated into the preset engine, so that all the unit test scripts and the total test scripts are integrated into an automatic test framework of the preset engine. Finally, an automated testing framework in a preset engine can be called through the continuous integration tool, so that a testing project is generated. Taking the preset engine as the unregealengine 4 as an example, the unregealengine 4 may integrate all the unit test scripts and the total test script into an automated test framework in a command line command, or a Gauntlet automated test tool may integrate all the unit test scripts and the total test script into the automated test framework, and accordingly, the continuous integration tool may invoke the automated test framework in a batch processing manner, where the continuous integration tool may be, for example, Teamcity, Jenkins, and the like, and the disclosure does not specifically limit this. Further, the persistent integration tool may perform a test project to verify the overall task flow. The testing engineering can acquire the resource data from the preset engine under the condition that any task flow is detected to run, determine a task flow node corresponding to the task flow according to the resource data, and further call a unit testing script corresponding to the task flow node, so that the task flow is verified. Therefore, the testing engineering is obtained by establishing the task flow nodes and the association between the task flow nodes and the unit testing script, the automatic testing of the task flow is realized, and the integrity and the correctness of the task flow can be quickly verified.
Fig. 3 is a flowchart illustrating another method for testing a task flow according to an exemplary embodiment, and as shown in fig. 3, the task edit instruction may include: a type editing instruction, a sequence editing instruction and an information editing instruction, and accordingly, the step 101 can be implemented by the following steps:
For example, after receiving the task editing instruction, the task editor may parse the task editing instruction to obtain the specified sequence, the task type corresponding to each task flow, and the information of each task flow. Specifically, the task editing instruction may include a type editing instruction, a sequence editing instruction, and an information editing instruction. And aiming at the type editing instruction, the task editor analyzes the type editing instruction to obtain a task type corresponding to each task flow, and then a task flow node corresponding to the task flow is established according to the task type corresponding to each task flow. The task type may be, for example, an interaction type, a presentation type, an action type, or the like, and a corresponding task flow node template may be established in advance for each task type, and then, according to the task type corresponding to each task flow, the task flow node template corresponding to the task flow is determined, and a corresponding task flow node is established accordingly.
And aiming at the sequential editing instruction, the task editor analyzes the sequential editing instruction to obtain a specified sequence, and then a plurality of task flow nodes can be sequentially connected according to the specified sequence, wherein the task flow node corresponding to the task flow executed earlier points to the task flow node corresponding to the task flow executed later. For example, the designated sequence is represented by a one-way arrow, and the sequence of the task flow nodes located at the starting point of the one-way arrow is earlier than the sequence of the task flow nodes located at the ending point of the one-way arrow, that is, the task flow corresponding to the task flow node located at the starting point of the one-way arrow is executed first, and the task flow corresponding to the task flow node located at the ending point of the one-way arrow is executed later.
Further, for the information editing instruction, the task editor analyzes the information editing instruction to obtain a specified sequence, and obtains information of each task flow, and then may configure attribute information of a task flow node corresponding to the task flow according to the information of each task flow, where the attribute information may include: at least one of task identification, task type, task description and completion condition, and may further include: completion reward, task name, node type, entry condition, completion condition, pre-task identifier (task identifier of previous task flow), post-task identifier (task identifier of next task flow), main task identifier (task identifier of task flow to which the task flow belongs), level identifier, and the like. The attribute information of the task flow node may be configured in, for example, the attribute area on the right side in fig. 2, and "behavior: the attribute information of the task flow node going to the home "may include: master task identification (denoted as Parent session Id): 10104. task identity (expressed as Id): 1010403, task Type (denoted as Session Type): dominant line scenario class, Node Type (denoted Action Node Type): action base class node, Pre-task identity (denoted as Pre Session Id): 1010402, Post task identification (denoted Post Session Id): 1010404, entry Conditions (denoted Accept Conditions): 0Array elements, completion Conditions (expressed as Complete Conditions): 1Array elements, task Name (denoted Name): "home-to-home", Level identification (identified as Level Id): null, task description (denoted Mission Obj): "return to home, learn more about the volume system", entry condition description (denoted as session Accept Desc): null, completion condition description (denoted as Mission Complete Desc): and (4) is empty.
FIG. 4 is a flow diagram illustrating another method for testing a task flow, according to an example embodiment, as shown in FIG. 4, step 102 may include:
And 1022, forming resource data files by the resource data corresponding to each task flow node according to the specified sequence, and exporting the resource data files to a preset engine.
For example, in order to enable the related information of each task flow to be used across platforms, each task flow node may be serialized to be converted into resource data in a preset format commonly used in a preset engine. Each task flow node corresponds to one resource data. And then, forming resource data files by the resource data corresponding to each task flow node according to the specified sequence, and exporting the resource data files to a preset engine. That is to say, the resource data file integrates the resource data corresponding to all the task flow nodes, and also includes the sequence (i.e. the designated sequence) among the resource data. In this way, the preset engine can directly acquire the relevant information of the task flow node, and other platforms (for example, a persistent integration tool) can also acquire the relevant information of the task flow node from the preset engine. Specifically, the resource data can describe both the task flow node and the connection relationship between the task flow node and other task flow nodes, so that the resource data file can describe all task flows as a whole. Taking the example that the preset engine is an unregealengine 4, the preset format may be a DataAsset format, and each task flow node may be converted into a DataAsset type resource as resource data. The plurality of resource data can then be integrated into a Json format resource data file, and then exported to UnrealEngine 4.
Fig. 5 is a flowchart illustrating another testing method for task flows according to an exemplary embodiment, and as shown in fig. 5, the implementation of step 104 may include:
and 1041, calling the total test script and the unit test script corresponding to each task flow node from the automatic test framework through the continuous integration tool in a batch processing mode, and generating a test project.
For example, the continuous integration tool may invoke the total test script and the unit test script corresponding to each task flow node from the automated test framework in a batch processing manner, so as to construct a test project including the total test script and all the unit test scripts. Specifically, the persistent integration tool may be, for example, Teamcity, Jenkins, etc., which is not specifically limited by the present disclosure. Further, a trigger mode may be set by the continuous integration tool to control the execution of the test project. The trigger mode may include a trigger period, which may be understood as a timing to periodically perform a test project, and/or a trigger condition. For example, the trigger period may be 24 hours, and the continuous integration tool performs the test project every 24 hours. The trigger condition can also be understood as a test program being executed if the trigger condition is met. For example, the trigger condition may be that an operation logic (which may be understood as an operation code) corresponding to any task flow is changed, the persistent integration tool may detect whether the operation logic corresponding to each task flow is changed in real time, and if the change is detected, execute a test project once.
In one implementation, step 1042 may include:
step 1) calling a total test script through a test project.
And 2) determining a target task process node corresponding to the currently executed target task process according to the resource data through the total test script, and calling a target unit test script corresponding to the target task process node to verify the target task process.
And 3) repeatedly executing the step 2) until the test engineering is interrupted or the test engineering is finished.
And 4) outputting a test result.
The specific implementation process of the test engineering is specifically described as follows:
the test engineering can call a total test script firstly, the total test script can acquire a currently executed target task flow, then a target task flow node corresponding to the target task flow and a task identifier of the target task flow node can be determined from the resource data file, and further, a corresponding target unit test script can be determined according to the task identifier of the target task flow node. The master test script may then invoke the target unit test script to verify whether the target task flow is executing correctly. And continuously and repeatedly executing the process until the test engineering is interrupted or the test engineering is finished, and finally outputting a test result. The test engineering interruption may be understood as an interruption of a unit test script, that is, a task flow corresponding to the unit test script is not completed. The test engineering is completed, which means that all task flows are completed. The test results may include a variety of information: whether the interruption exists, the task identification corresponding to the unit test script which generates the interruption exists, the log generated by the unit test script which generates the interruption exists, and the like. The mode of outputting the test result may be to generate a test report from the test result, and then store the test report in a designated location, or send the test report to the terminal device bound to the test project in the form of a mail, a short message, or the like, which is not specifically limited by the disclosure.
As shown in fig. 6, the task editor receives the task editing instruction, creates N task flow nodes by parsing the task editing instruction, obtains resource data by format conversion, and exports the resource data to the default engine. Meanwhile, the unit test script 1, the unit test script 2 to the unit test script N, and the total test script (not shown in fig. 6) corresponding to the N task flow nodes are integrated into the automated test framework. And the continuous integration tool generates a test project by calling the automatic test framework and executes the test project. And in the execution process of the test engineering, determining and calling a unit test script corresponding to the currently running task flow by reading the resource data, and finally outputting a test result.
In another implementation, the implementation of step 2) may include:
and step A, receiving indication information sent by the server through the total test script, and analyzing a task identifier of a target task flow included in the indication information.
And step B, determining a target task process node in the resource data according to the task identifier of the target task process through the total test script, and determining a target unit test script according to the target task process node.
And step C, calling the target unit test script through the total test script to verify the target task flow.
Taking the network game application as an example, the network game application comprises a plurality of task flows, the network game application runs on the terminal device, and the server controls the execution of each task flow in the network game application through the indication information. The continuous integration tool can carry out data transmission with a server and terminal equipment. The server sends indication information to the terminal equipment, the indication information comprises a task identifier of a target task flow which needs to be executed currently, and the terminal equipment analyzes the indication information to execute the target task flow. Meanwhile, the general test script in the test engineering can also obtain the indication information and analyze the task identifier of the target task flow included in the indication information. And then, the total test script determines a target task flow node from the resource data file according to the task identifier of the target task flow and determines a target unit test script corresponding to the target task flow node. And finally, calling the target unit test script by the total test script to verify whether the target task flow is executed correctly.
In yet another implementation, step C may include:
step C1, monitoring the operation data generated in the process of executing the target task flow through the total test script, wherein the operation data comprises: initial running data generated when the target task flow is entered, and/or ending running data generated when the target task flow is completed.
Step C2, the target unit test script is called by the total test script, so that the target unit test script verifies whether the running data matches with the target task flow node.
For example, the specific implementation of verifying whether the target task flow is executed correctly may be to monitor the operation data generated by the terminal device in the process of executing the target task flow through the total test script. The running data may include initial running data generated when the target task flow is entered, intermediate running data generated when the target task flow is executed, and ending running data generated when the target task flow is completed. Specifically, the initial operation data may include, for example: the entry information displayed on the control is displayed when the target task flow is entered, the initial state (such as grade, blood volume, money, precious stones and the like) of the player when the target task flow is entered, the completed task list when the target task flow is entered, and the like. The intermediate operational data may include, for example: the motion trail of the player when the target mission process is executed (for example, moving from point A to point B, and then from point B to point C), and the operation record of the player when the target mission process is executed (for example, releasing skill a, using prop B, etc.). The end-of-run data may include, for example: and displaying the completion information displayed on the control when the target task flow is completed, the completion state of the player when the target task flow is completed, and the prop list (or the reward list) of the player when the target task flow is completed.
The master test script may then invoke the target unit test script with the run data as an entry to enable the target unit test script to verify whether the run data matches the target task flow nodes. Specifically, whether the running data is matched with the attribute information of the target task flow node or not can be verified. For example, it may be verified whether the entry information displayed on the display control matches the task name and task description of the target task flow node when entering the target task flow, and it may also be verified whether the item list of the player matches the completion award of the target task flow node when completing the target task flow. Specifically, when a user enters a certain level, whether an ID corresponding to the level is correct or not can be verified, whether the type of a task flow node corresponding to the level is a level type node or not can be verified, whether star-level task description corresponding to the level is correctly displayed or not can be verified, whether a pre-posed task entering the level is currently completed or not can be verified, and the like. For another example, when a user completes a certain level, it may be verified whether the previous task of the level is finished at present, whether the reward of the level is correctly issued, whether the star-level task description corresponding to the level is correctly displayed, whether the star-level task corresponding to the level is finished, whether the ID corresponding to the next level can be acquired, and the like.
Taking a plurality of task flow nodes shown in the task editor shown in fig. 7 as an example, the task flow nodes include two task flow node sequences, one of which is: "gateway star level root node" → "tasks: star level one "→" task: star level two "→" tasks: and (5) star level three. The other group is: "star reward root node" → "mission _ checkpoint reward (first): first-time clearance first-pass reward "→" mission _ level reward: one-star-one-star prize "→" mission _ checkpoint prize: two stars and two stars prize "→" mission _ checkpoint prize: three stars and three stars reward ".
With what is currently being performed is "task: the task flow corresponding to star level two is taken as an example, "task: the task name in the attribute information of star level two is "star level two", and the task is described as "arrival at a convenience store within 10 minutes". The total test script can monitor the entry information displayed on the display control when entering the task process, and the entry information is' star level two: arrival at a convenience store within 10 minutes. The total test script may convert "star level two: arrival at a convenience store within 10 minutes "call as entry" task: and a unit test script corresponding to star level two. The unit test script determines "star level two: arrival at a convenience store within 10 minutes "star class two" and "arrival at a convenience store within 10 minutes" are respectively shown, and it can be judged that the entry information matches the task name and the task description.
As another example, currently performed is "task _ level reward: one-star reward "corresponding task flow," task _ checkpoint reward: the completed reward in the attribute information of one-star reward is '1X item'. The master test script may listen to the player's bonus list when the task flow is completed. The total test script may call the rewards list as an entry to call "task _ level rewards: and the unit test script corresponds to the one-star reward, and determines whether the number of the X props in the reward list is increased by 1, if the number of the X props in the reward list is increased by 1, the reward list can be judged to be matched with the completed reward, and if the number of the X props in the reward list is not increased by 1, the reward list can be judged not to be matched with the completed reward.
To sum up, a task editing instruction is received first, so as to establish a plurality of task flow nodes according to a specified sequence according to the task editing instruction, and corresponding attribute information is configured, where each task flow node corresponds to one task flow. And then, converting each task flow node into resource data in a preset format, and exporting the resource data to a preset engine. And integrating the unit test script corresponding to each task flow node and the total test script for maintaining the plurality of unit test scripts into an automatic test framework. And finally, calling an automatic test framework in a preset engine, generating and executing a test project, and calling a unit test script corresponding to each task flow when each task flow runs. According to the method and the device, the task flow nodes are established, and the association between the task flow nodes and the unit test scripts is obtained to obtain the test engineering, so that the automatic test of the task flow is realized, and the integrity and the correctness of the task flow can be rapidly verified.
Fig. 8 is a block diagram illustrating a testing apparatus of a task flow according to an exemplary embodiment, and as shown in fig. 8, the apparatus 200 may include:
the editing module 201 is configured to receive a task editing instruction, parse the task editing instruction to establish a plurality of task flow nodes according to a specified sequence, and configure attribute information of each task flow node, where each task flow node corresponds to one task flow.
The export module 202 is configured to convert each task flow node into resource data in a preset format, and export the resource data to a preset engine, where the resource data includes attribute information and sequence of the task flow node.
And the integration module 203 is configured to integrate the unit test scripts corresponding to each task flow node and the total test script into an automated test framework of a preset engine, where the total test script is used to maintain a plurality of unit test scripts, and the unit test scripts are used to verify corresponding task flows.
The testing module 204 is configured to invoke an automated testing framework in a preset engine, generate and execute a testing project, where the testing project is configured to determine a task flow node corresponding to each task flow according to the resource data when each task flow runs, and invoke a unit testing script corresponding to the task flow node.
FIG. 9 is a block diagram illustrating another task flow testing apparatus according to an exemplary embodiment, where, as shown in FIG. 9, the task edit instruction includes: the type editing instruction, the sequence editing instruction and the information editing instruction, and accordingly, the editing module 201 may include:
the first parsing sub-module 2011 is configured to parse the type editing instruction to obtain a task type corresponding to each task process, and establish a task process node corresponding to the task process according to the corresponding task type.
The second parsing sub-module 2012 is configured to parse the order editing instruction to obtain a specified order, and connect the plurality of task flow nodes according to the specified order.
The third parsing submodule 2013 is configured to parse the information editing instruction to obtain information of each task flow, and configure attribute information of a task flow node corresponding to the task flow according to the information of the task flow, where the attribute information includes: at least one of task identification, task type, task description and completion condition.
Fig. 10 is a block diagram illustrating another testing apparatus for task flow according to an example embodiment, and as shown in fig. 10, the export module 202 may include:
the conversion sub-module 2021 is configured to convert each task flow node according to a preset format, so as to obtain resource data corresponding to the task flow node.
The export submodule 2022 is configured to combine the resource data corresponding to each task flow node into a resource data file according to the specified order, and export the resource data file to the preset engine.
Fig. 11 is a block diagram illustrating another task flow testing apparatus according to an example embodiment, and as shown in fig. 11, the testing module 204 may include:
the generating submodule 2041 is configured to invoke the total test script and the unit test script corresponding to each task flow node from the automated test framework in a batch processing manner through the persistent integration tool, so as to generate a test project.
The execution submodule 2042 is configured to execute a test project according to a preset trigger mode, where the trigger mode includes: a trigger period, and/or a trigger condition.
In one implementation, the execution submodule 2042 may be configured to perform the following steps:
step 1) calling a total test script through a test project.
And 2) determining a target task flow node corresponding to the currently executed target task flow according to the resource data through the total test script, and calling a target unit test script corresponding to the target task flow node to verify the target task flow.
And 3) repeatedly executing the step 2) until the test engineering is interrupted or the test engineering is finished.
And 4) outputting a test result.
In another implementation, step 2) may include:
and step A, receiving the indication information sent by the server through the total test script, and analyzing the task identifier of the target task flow included in the indication information.
And step B, determining a target task flow node in the resource data according to the task identifier of the target task flow through the total test script, and determining a target unit test script according to the target task flow node.
And step C, calling the target unit test script through the total test script to verify the target task flow.
In yet another implementation, step C may include:
step C1, monitoring the operation data generated in the process of executing the target task flow through the total test script, wherein the operation data comprises: initial running data generated when the target task flow is entered, and/or ending running data generated when the target task flow is completed.
Step C2, the target unit test script is called by the total test script, so that the target unit test script verifies whether the running data matches with the target task flow node.
With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.
In summary, the present disclosure first receives a task editing instruction, so as to establish a plurality of task flow nodes according to a specified sequence according to the task editing instruction, and configure corresponding attribute information, where each task flow node corresponds to one task flow. And then, converting each task flow node into resource data in a preset format, and exporting the resource data to a preset engine. And integrating the unit test script corresponding to each task flow node and the total test script for maintaining the plurality of unit test scripts into an automatic test framework. And finally, calling an automatic test framework in a preset engine, generating and executing a test project, and calling a unit test script corresponding to each task flow when each task flow runs. According to the method and the system, the task flow nodes are established, and the association between the task flow nodes and the unit test scripts is obtained to obtain the test engineering, so that the automatic test of the task flow is realized, and the integrity and the correctness of the task flow can be quickly verified.
Referring now to fig. 12, a schematic structural diagram of an electronic device (which may be understood as the execution subject of the disclosed embodiments) 300 suitable for implementing the disclosed embodiments is shown. The terminal device in the embodiments of the present disclosure may include, but is not limited to, a mobile terminal such as a mobile phone, a notebook computer, a digital broadcast receiver, a PDA (personal digital assistant), a PAD (tablet computer), a PMP (portable multimedia player), a vehicle terminal (e.g., a car navigation terminal), and the like, and a fixed terminal such as a digital TV, a desktop computer, and the like. The electronic device shown in fig. 12 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.
As shown in fig. 12, the electronic device 300 may include a processing means (e.g., a central processing unit, a graphics processor, etc.) 301 that may perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)302 or a program loaded from a storage means 308 into a Random Access Memory (RAM) 303. In the RAM 303, various programs and data necessary for the operation of the electronic apparatus 300 are also stored. The processing device 301, the ROM 302, and the RAM 303 are connected to each other via a bus 304. An input/output (I/O) interface 305 is also connected to bus 304.
Generally, the following devices may be connected to the I/O interface 305: input devices 306 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; an output device 307 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage devices 308 including, for example, magnetic tape, hard disk, etc.; and a communication device 309. The communication means 309 may allow the electronic device 300 to communicate wirelessly or by wire with other devices to exchange data. While fig. 12 illustrates an electronic device 300 having various means, it is to be understood that not all illustrated means are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided.
In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program carried on a non-transitory computer readable medium, the computer program containing program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication means 309, or installed from the storage means 308, or installed from the ROM 302. The computer program, when executed by the processing device 301, performs the above-described functions defined in the methods of the embodiments of the present disclosure.
It should be noted that the computer readable medium in the present disclosure can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.
In some embodiments, the terminal devices, servers may communicate using any currently known or future developed network Protocol, such as HTTP (HyperText Transfer Protocol), and may interconnect with any form or medium of digital data communication (e.g., a communications network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the Internet (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed network.
The computer readable medium may be embodied in the electronic device; or may exist separately without being assembled into the electronic device.
The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: receiving a task editing instruction, analyzing the task editing instruction to establish a plurality of task flow nodes according to a specified sequence, and configuring attribute information of each task flow node, wherein each task flow node corresponds to one task flow; converting each task process node into resource data in a preset format, and exporting the resource data to a preset engine, wherein the resource data comprises attribute information and sequence of the task process node; integrating a unit test script corresponding to each task flow node and a total test script into an automatic test framework of the preset engine, wherein the total test script is used for maintaining a plurality of unit test scripts, and the unit test scripts are used for verifying the corresponding task flows; and calling the automatic test framework in the preset engine, generating and executing a test project, wherein the test project is used for determining a task flow node corresponding to each task flow according to the resource data when each task flow runs, and calling the unit test script corresponding to the task flow node.
Computer program code for carrying out operations for the present disclosure may be written in any combination of one or more programming languages, including but not limited to an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules described in the embodiments of the present disclosure may be implemented by software or hardware. The name of a module does not in some cases form a limitation on the module itself, for example, an editing module may also be described as a "module that establishes a task flow node and configures attribute information".
The functions described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), systems on a chip (SOCs), Complex Programmable Logic Devices (CPLDs), and the like.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
Example 1 provides a method of testing a task flow, including: receiving a task editing instruction, analyzing the task editing instruction to establish a plurality of task flow nodes according to a specified sequence, and configuring attribute information of each task flow node, wherein each task flow node corresponds to one task flow; converting each task flow node into resource data in a preset format, and exporting the resource data to a preset engine, wherein the resource data comprises attribute information and sequence of the task flow node; integrating a unit test script corresponding to each task flow node and a total test script into an automatic test framework of the preset engine, wherein the total test script is used for maintaining a plurality of unit test scripts, and the unit test scripts are used for verifying the corresponding task flows; and calling the automatic test framework in the preset engine, generating and executing a test project, wherein the test project is used for determining a task flow node corresponding to each task flow according to the resource data when each task flow runs, and calling the unit test script corresponding to the task flow node.
Example 2 provides the method of example 1, the task editing instructions comprising: a type editing instruction, a sequence editing instruction and an information editing instruction; the receiving a task editing instruction, analyzing the task editing instruction to establish a plurality of task flow nodes according to a specified sequence, and configuring attribute information of each task flow node, including: analyzing the type editing instruction to obtain a task type corresponding to each task flow, and establishing a task flow node corresponding to the task flow according to the corresponding task type; analyzing the sequence editing instruction to obtain the designated sequence, and connecting a plurality of task process nodes according to the designated sequence; analyzing the information editing instruction to obtain the information of each task flow, and configuring the attribute information of the task flow node corresponding to the task flow according to the information of the task flow, wherein the attribute information comprises: at least one of task identification, task type, task description and completion condition.
Example 3 provides the method of example 1, wherein converting, by the task editor, each of the task flow nodes into resource data in a preset format and exporting the resource data to a preset engine, includes: converting each task flow node according to the preset format to obtain the resource data corresponding to the task flow node; and forming resource data files by the resource data corresponding to each task flow node according to the designated sequence, and exporting the resource data files to the preset engine.
Example 4 provides the method of example 1, the invoking, by the persistent integration tool, the automated testing framework in the preset engine, generating and executing a testing project, including: calling the total test script and the unit test script corresponding to each task flow node from the automatic test framework through a continuous integration tool in a batch processing mode to generate the test engineering; executing the test engineering according to a preset trigger mode, wherein the trigger mode comprises the following steps: a trigger period, and/or a trigger condition.
Example 5 provides the method of example 4, the performing the test engineering, comprising: calling the total test script through the test engineering; determining a target task flow node corresponding to a currently executed target task flow according to the resource data through the total test script, and calling a target unit test script corresponding to the target task flow node to verify the target task flow; repeating the steps of determining a target task flow node corresponding to a currently executed target task flow according to the resource data through the total test script and calling a target unit test script corresponding to the target task flow node until the test engineering is interrupted or the test engineering is executed; and outputting a test result.
Example 6 provides the method of example 5, where determining, by the total test script according to the resource data, a target task flow node corresponding to a currently executed target task flow, and calling a target unit test script corresponding to the target task flow node includes: receiving indication information sent by a server through the total test script, and analyzing a task identifier of the target task process included in the indication information; determining the target task process node in the resource data according to the task identifier of the target task process through the total test script, and determining the target unit test script according to the target task process node; and calling the target unit test script through the total test script so as to verify the target task flow.
Example 7 provides the method of example 6, the invoking, by the master test script, the target unit test script to validate the target task flow, comprising: monitoring running data generated in the process of executing the target task flow through the total test script, wherein the running data comprises: starting running data generated when the target task flow is entered and/or finishing running data generated when the target task flow is finished; and calling the target unit test script through the total test script so that the target unit test script verifies whether the running data is matched with the target task flow node.
Example 8 provides a testing apparatus of a task flow, according to one or more embodiments of the present disclosure, including: the editing module is used for receiving a task editing instruction, analyzing the task editing instruction to establish a plurality of task flow nodes according to a specified sequence, and configuring attribute information of each task flow node, wherein each task flow node corresponds to one task flow; the export module is used for converting each task flow node into resource data in a preset format and exporting the resource data to a preset engine, wherein the resource data comprises attribute information and sequence of the task flow node; the integrated module is used for integrating the unit test scripts corresponding to the task flow nodes and the total test scripts into an automatic test framework of the preset engine, wherein the total test scripts are used for maintaining a plurality of the unit test scripts, and the unit test scripts are used for verifying the corresponding task flows; and the test module is used for calling the automatic test framework in the preset engine, generating and executing a test project, wherein the test project is used for determining task flow nodes corresponding to the task flows according to the resource data when each task flow runs, and calling the unit test scripts corresponding to the task flow nodes.
Example 9 provides a computer-readable medium, on which is stored a computer program that, when executed by a processing device, implements the steps of the method of any one of examples 1 to 7, in accordance with one or more embodiments of the present disclosure.
Example 10 provides, in accordance with one or more embodiments of the present disclosure, an electronic device comprising: a storage device having a computer program stored thereon; processing means for executing the computer program in the storage means to carry out the steps of the method of any one of examples 1 to 7.
The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the disclosure herein is not limited to the particular combination of features described above, but also encompasses other embodiments in which any combination of the features described above or their equivalents does not depart from the spirit of the disclosure. For example, the above features and (but not limited to) the features disclosed in this disclosure having similar functions are replaced with each other to form the technical solution.
Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims. With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.
Claims (10)
1. A method for testing a task flow, the method comprising:
receiving a task editing instruction, analyzing the task editing instruction to establish a plurality of task flow nodes according to a specified sequence, and configuring attribute information of each task flow node, wherein each task flow node corresponds to one task flow;
converting each task process node into resource data in a preset format, and exporting the resource data to a preset engine, wherein the resource data comprises attribute information and sequence of the task process node;
integrating a unit test script corresponding to each task flow node and a total test script into an automatic test framework of the preset engine, wherein the total test script is used for maintaining a plurality of unit test scripts, and the unit test scripts are used for verifying the corresponding task flows;
and calling the automatic test framework in the preset engine, generating and executing a test project, wherein the test project is used for determining a task flow node corresponding to each task flow according to the resource data when each task flow runs, and calling the unit test script corresponding to the task flow node.
2. The method of claim 1, wherein the task editing instructions comprise: a type editing instruction, a sequence editing instruction and an information editing instruction; the receiving a task editing instruction, analyzing the task editing instruction to establish a plurality of task flow nodes according to a specified sequence, and configuring attribute information of each task flow node, including:
analyzing the type editing instruction to obtain a task type corresponding to each task flow, and establishing a task flow node corresponding to the task flow according to the corresponding task type;
analyzing the sequence editing instruction to obtain the designated sequence, and connecting a plurality of task process nodes according to the designated sequence;
analyzing the information editing instruction to obtain the information of each task flow, and configuring the attribute information of the task flow node corresponding to the task flow according to the information of the task flow, wherein the attribute information comprises: at least one of task identification, task type, task description and completion condition.
3. The method according to claim 1, wherein the converting each task flow node into resource data in a preset format and exporting the resource data to a preset engine comprises:
converting each task flow node according to the preset format to obtain the resource data corresponding to the task flow node;
and forming resource data files by the resource data corresponding to each task flow node according to the designated sequence, and exporting the resource data files to the preset engine.
4. The method of claim 1, wherein the invoking the automated test framework in the pre-defined engine, generating and executing a test project, comprises:
calling the total test script and the unit test script corresponding to each task flow node from the automatic test framework through a continuous integration tool in a batch processing mode to generate the test engineering;
executing the test engineering according to a preset trigger mode, wherein the trigger mode comprises the following steps: a trigger period, and/or a trigger condition.
5. The method of claim 4, wherein said performing said test engineering comprises:
calling the total test script through the test engineering;
determining a target task flow node corresponding to a currently executed target task flow according to the resource data through the total test script, and calling a target unit test script corresponding to the target task flow node to verify the target task flow;
repeating the steps of determining a target task flow node corresponding to a currently executed target task flow according to the resource data through the total test script and calling a target unit test script corresponding to the target task flow node until the test engineering is interrupted or the test engineering is executed;
and outputting a test result.
6. The method according to claim 5, wherein the determining, by the total test script, a target task flow node corresponding to a currently executed target task flow according to the resource data, and calling a target unit test script corresponding to the target task flow node comprises:
receiving indication information sent by a server through the total test script, and analyzing a task identifier of the target task process included in the indication information;
determining the target task process node in the resource data according to the task identifier of the target task process through the total test script, and determining the target unit test script according to the target task process node;
and calling the target unit test script through the total test script so as to verify the target task flow.
7. The method of claim 6, wherein said invoking said target unit test script by said master test script to validate said target task flow comprises:
monitoring running data generated in the process of executing the target task flow through the total test script, wherein the running data comprises: starting running data generated when the target task flow is entered and/or finishing running data generated when the target task flow is finished;
and calling the target unit test script through the total test script so that the target unit test script verifies whether the running data is matched with the target task flow node.
8. A task flow testing apparatus, comprising:
the editing module is used for receiving a task editing instruction, analyzing the task editing instruction to establish a plurality of task flow nodes according to a specified sequence, and configuring attribute information of each task flow node, wherein each task flow node corresponds to one task flow;
the export module is used for converting each task flow node into resource data in a preset format and exporting the resource data to a preset engine, wherein the resource data comprises attribute information and sequence of the task flow node;
the integrated module is used for integrating the unit test scripts corresponding to the task flow nodes and the total test scripts into an automatic test framework of the preset engine, wherein the total test scripts are used for maintaining a plurality of the unit test scripts, and the unit test scripts are used for verifying the corresponding task flows;
and the test module is used for calling the automatic test framework in the preset engine, generating and executing a test project, wherein the test project is used for determining task flow nodes corresponding to the task flows according to the resource data when each task flow runs, and calling the unit test scripts corresponding to the task flow nodes.
9. A computer-readable medium, on which a computer program is stored, characterized in that the program, when being executed by processing means, carries out the steps of the method of any one of claims 1 to 7.
10. An electronic device, comprising:
a storage device having a computer program stored thereon;
processing means for executing the computer program in the storage means to carry out the steps of the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210204885.1A CN114564402A (en) | 2022-03-03 | 2022-03-03 | Task flow testing method and device, readable medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210204885.1A CN114564402A (en) | 2022-03-03 | 2022-03-03 | Task flow testing method and device, readable medium and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114564402A true CN114564402A (en) | 2022-05-31 |
Family
ID=81717341
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210204885.1A Pending CN114564402A (en) | 2022-03-03 | 2022-03-03 | Task flow testing method and device, readable medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114564402A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114757156A (en) * | 2022-06-14 | 2022-07-15 | 成都飞机工业（集团）有限责任公司 | Method, device, equipment and medium for compiling aircraft system test instruction |
-
2022
- 2022-03-03 CN CN202210204885.1A patent/CN114564402A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114757156A (en) * | 2022-06-14 | 2022-07-15 | 成都飞机工业（集团）有限责任公司 | Method, device, equipment and medium for compiling aircraft system test instruction |
| CN114757156B (en) * | 2022-06-14 | 2022-10-25 | 成都飞机工业（集团）有限责任公司 | Method, device, equipment and medium for compiling aircraft system test instruction |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111159049B (en) | Automatic interface testing method and system | |
| CN111581291A (en) | Data processing method and device, electronic equipment and readable medium | |
| CN110716853A (en) | Test script recording method, application program testing method and related device | |
| CN113553257B (en) | Test method, device, storage medium and electronic equipment | |
| CN111382228A (en) | Method and apparatus for outputting information | |
| CN109902251A (en) | Scheme Choice method, apparatus, terminal and readable storage medium storing program for executing based on decision tree | |
| CN112231663A (en) | Data acquisition method, device, equipment and storage medium combining RPA and AI | |
| CN112597047A (en) | Test method, test device, electronic equipment and computer readable medium | |
| CN111190657B (en) | Activity configuration method and device, readable medium and electronic equipment | |
| CN110659870A (en) | Business audit test method, device, equipment and storage medium | |
| CN112015654A (en) | Method and apparatus for testing | |
| CN111752834A (en) | Automatic testing method and device | |
| CN114564402A (en) | Task flow testing method and device, readable medium and electronic equipment | |
| CN112988600A (en) | Service scene testing method and device, electronic equipment and storage medium | |
| CN115022328B (en) | Server cluster, testing method and device of server cluster and electronic equipment | |
| CN111324470A (en) | Method and device for generating information | |
| CN113360365B (en) | Flow test method and flow test system | |
| CN115391204A (en) | Test method and device for automatic driving service, electronic equipment and storage medium | |
| CN112487416A (en) | Business process verification method and device and electronic equipment | |
| CN112306858A (en) | Test method and device and electronic equipment | |
| CN112328340B (en) | Model process display method, device, electronic equipment and storage medium | |
| CN111831531B (en) | Test method and device | |
| CN115242606B (en) | Data processing method, device, server, storage medium and program product | |
| CN114416210B (en) | Method, device, medium and equipment for simulating decision flow | |
| CN115587019A (en) | Pressure testing method, device, system, medium and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |