A method and device for configuring node information of a test case

Abstract

The present disclosure provides a method and device for configuring node information of a test case, wherein the method comprises: obtaining a use case list corresponding to the test case, wherein the use case list contains at least one type of use case node corresponding to the test case, wherein at least one type includes a first type use case node, and the first type use case node is a use case node that does not have a corresponding sub-use case node; when it is determined that the pre-dependency information of the first type use case node needs to be updated, the first type use case node is changed to a second type use case node; the second type use case node is a use case node that has at least one sub-use case node; and node information is configured for at least one sub-use case node of the changed second type use case node, wherein the configured node information is used to update the pre-dependency information of the second type use case node.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to a method and device for configuring node information of a test case. Background Art

[0002] Before any application is released online, it needs to be regression tested, and the application is released only when it is determined that the application has passed the test. Using test cases to perform regression testing on applications is a common regression testing method. Users can create various test cases related to the application and determine whether the application meets the release conditions based on the pass rate of the application corresponding to various test cases.

[0003] However, in the prior art, after editing a use case node included in a successfully created test case, other use case nodes will be affected, resulting in a significant drawback of node editing. Summary of the invention

[0004] The embodiments of the present disclosure at least provide a method and device for configuring node information of a test case.

[0005] In a first aspect, an embodiment of the present disclosure provides a node information configuration of a test case, including:

[0006] Obtain a use case list corresponding to the test case, wherein the use case list includes at least one type of use case node corresponding to the test case, wherein the at least one type includes a first type of use case node, and the first type of use case node is a use case node that does not have a corresponding sub-use case node;

[0007] In the case where it is determined that the pre-dependency information of the first type use case node needs to be updated, the first type use case node is changed to a second type use case node; the second type use case node is a use case node having at least one child use case node;

[0008] For at least one sub-use case node of the changed second-type use case node, node information configuration is performed, wherein the configured node information is used to update the pre-dependency information of the second-type use case node.

[0009] In a possible implementation, the pre-dependency information includes at least one of the following: a pre-dependency condition, a pre-dependency step, and a step execution result of the pre-dependency step, and different pre-dependency information corresponds to different types of use case nodes.

[0010] In a possible implementation, obtaining a use case list corresponding to the test case includes:

[0011] Obtaining a use case node graph corresponding to the test case, wherein the use case node graph includes node assignments of each use case node corresponding to the test case and dependency relationships between each of the use case nodes;

[0012] Determine the node type of each of the use case nodes, and generate a use case list corresponding to the test case based on the node type, the node value assignment and the dependency relationship.

[0013] In a possible implementation, generating a use case list corresponding to the test case according to the node type, the node value assignment, and the dependency relationship includes:

[0014] For a first type of use case node, based on the node position of the first type of use case node and the dependency relationship, determine each preceding dependency node corresponding to the first type of use case node; determine the preceding dependency information of the first type of use case node according to the node type and node value corresponding to each preceding dependency node;

[0015] For the second type use case node, based on the dependency relationship, determine each sub-use case node of the second type use case node, and based on the node type and node assignment of each sub-use case node, determine the pre-dependency condition and execution step information of the second type use case node; the execution step information includes each pre-dependency step, each post-dependency step and the step execution result corresponding to each step of the second type use case node;

[0016] Based on the determined pre-dependency information of each first-type use case node and the pre-dependency conditions and execution step information of each second-type use case node, a use case list corresponding to the test case is determined.

[0017] In a possible implementation, when it is determined that the pre-dependency information of the first-type use case node needs to be updated, changing the first-type use case node to a second-type use case node includes:

[0018] In response to a trigger operation on a first type of use case node in the use case list, a node editing page corresponding to the first type of use case node is generated and displayed; the node editing page displays the pre-dependency information corresponding to the first type of use case node, and the displayed pre-dependency information is not editable; the node editing page displays a first form of target button; the first form of target button is used to indicate updating the pre-dependency information of the first type of use case node;

[0019] In response to a trigger operation on the target button, the first type use case node is changed to a second type use case node, and the form of the target button is converted to a second form for indicating that the update has been completed or is in progress; wherein the sub-use case node corresponding to the changed second type use case node includes a target sub-use case node having an initial node assignment determined according to the prerequisite dependency information.

[0020] In a possible implementation manner, the configuring node information for at least one sub-use case node of the changed second-type use case node includes:

[0021] For a target sub-use case node in at least one sub-use case node of the changed second-type use case node, obtain the input first target assignment for the target sub-use case node, and use the first target assignment to replace the initial node assignment of the target sub-use case node to obtain the target sub-use case node with completed node information configuration; and / or

[0022] In response to a subnode generation request for the changed second-type use case node, a newly created sub-use case node with a default node assignment is displayed, and the second target assignment of the newly created sub-use case node is obtained, and the default node assignment of the newly created sub-use case node is replaced with the second target assignment to obtain a newly created sub-use case node with completed node information configuration.

[0023] In a possible implementation manner, after configuring the node information of at least one sub-use case node of the changed second-type use case node, the method further includes:

[0024] In response to a trigger operation on the second-type target button displayed in the node editing page, the changed second-type use case node is restored to the first-type use case node, and the form of the target button is restored to the first form.

[0025] In a second aspect, the embodiment of the present disclosure further provides a node information configuration device for a test case, including:

[0026] An acquisition module, configured to acquire a use case list corresponding to a test case, wherein the use case list includes at least one type of use case node corresponding to the test case, wherein the at least one type includes a first type of use case node, and the first type of use case node is a use case node that does not have a corresponding sub-use case node;

[0027] An updating module, configured to change the first type of use case node to a second type of use case node when it is determined that the pre-dependency information of the first type of use case node needs to be updated; the second type of use case node is a use case node having at least one child use case node;

[0028] A configuration module is used to configure node information for at least one sub-use case node of the changed second-type use case node, wherein the configured node information is used to update the pre-dependency information of the second-type use case node.

[0029] In a possible implementation, the pre-dependency information includes at least one of the following: a pre-dependency condition, a pre-dependency step, and a step execution result of the pre-dependency step, and different pre-dependency information corresponds to different types of use case nodes.

[0030] In a possible implementation, the acquisition module is used to acquire a use case node graph corresponding to the test case, wherein the use case node graph includes node assignments of each use case node corresponding to the test case and dependency relationships between each of the use case nodes;

[0031] Determine the node type of each of the use case nodes, and generate a use case list corresponding to the test case based on the node type, the node value assignment and the dependency relationship.

[0032] In a possible implementation, the acquisition module is used to determine, for a first type use case node, each preceding dependency node corresponding to the first type use case node based on the node position of the first type use case node and the dependency relationship; and determine the preceding dependency information of the first type use case node according to the node type and node value corresponding to each preceding dependency node;

[0033] For the second type use case node, based on the dependency relationship, determine each sub-use case node of the second type use case node, and based on the node type and node assignment of each sub-use case node, determine the pre-dependency condition and execution step information of the second type use case node; the execution step information includes each pre-dependency step, each post-dependency step and the step execution result corresponding to each step of the second type use case node;

[0034] Based on the determined pre-dependency information of each first-type use case node and the pre-dependency conditions and execution step information of each second-type use case node, a use case list corresponding to the test case is determined.

[0035] In a possible implementation, the update module is used to generate and display a node editing page corresponding to the first type of use case node in the use case list in response to a trigger operation on the first type of use case node; the node editing page displays the pre-dependency information corresponding to the first type of use case node, and the displayed pre-dependency information is not editable; the node editing page displays a first form of target button; the first form of target button is used to indicate updating the pre-dependency information of the first type of use case node;

[0036] In response to a trigger operation on the target button, the first type use case node is changed to a second type use case node, and the form of the target button is converted to a second form for indicating that the update has been completed or is in progress; wherein the sub-use case node corresponding to the changed second type use case node includes a target sub-use case node having an initial node assignment determined according to the prerequisite dependency information.

[0037] In a possible implementation, the configuration module is used to obtain the input first target assignment for the target sub-use case node in at least one sub-use case node of the changed second-type use case node, and use the first target assignment to replace the initial node assignment of the target sub-use case node to obtain the target sub-use case node for which the node information configuration is completed; and / or

[0038] In response to a subnode generation request for the changed second-type use case node, a newly created sub-use case node with a default node assignment is displayed, and the second target assignment of the newly created sub-use case node is obtained, and the default node assignment of the newly created sub-use case node is replaced with the second target assignment to obtain a newly created sub-use case node with completed node information configuration.

[0039] In a possible implementation, the device further includes:

[0040] A restoration module is used to restore the changed second-type use case node to the first-type use case node and restore the form of the target button to the first form in response to a trigger operation of a second-form target button displayed on the node editing page after configuring node information for at least one sub-use case node of the changed second-type use case node.

[0041] In a third aspect, an optional implementation of the present disclosure further provides a computer device, a processor, and a memory, wherein the memory stores machine-readable instructions executable by the processor, and the processor is used to execute the machine-readable instructions stored in the memory, and when the machine-readable instructions are executed by the processor, the machine-readable instructions perform the steps of the above-mentioned first aspect, or any possible implementation of the first aspect.

[0042] In a fourth aspect, an optional implementation of the present disclosure further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed, the steps of the above-mentioned first aspect, or any possible implementation of the first aspect are executed.

[0043] For a description of the effects of the node information configuration device, computer equipment, and computer-readable storage medium of the above test case, please refer to the description of the node information configuration method of the above test case, which will not be repeated here.

[0044] The node information configuration method and device of the test case provided by the embodiment of the present disclosure, since the second type of use case node includes a sub-use case node, and the sub-use case node can determine the pre-dependency information of the parent node, so for the first type of use case node whose pre-dependency information needs to be modified, by changing it to a second type of use case node, and then configuring the node information of the sub-use case node of the changed second type of use case node, not only can the pre-dependency information of the first type of use case node before the change be modified, but also it can avoid directly modifying the pre-node that determines the pre-dependency information of the first type of use case node, resulting in the problem of affecting other use case nodes that rely on the pre-dependency information, and realizes that the modification of the pre-dependency information of the first type of use case node before the change can only be for the first type of use case node, thereby improving the independence and pertinence of the modification of the pre-dependency information.

[0045] In order to make the above-mentioned objectives, features and advantages of the present disclosure more obvious and easy to understand, preferred embodiments are specifically cited below and described in detail with reference to the attached drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the following is a brief introduction to the drawings required for use in the embodiments. The drawings herein are incorporated into the specification and constitute a part of the specification. These drawings illustrate embodiments consistent with the present disclosure and are used together with the specification to illustrate the technical solutions of the present disclosure. It should be understood that the following drawings only illustrate certain embodiments of the present disclosure and should not be regarded as limiting the scope. For ordinary technicians in this field, other relevant drawings can also be obtained based on these drawings without creative work.

[0047] Figure 1 A schematic diagram of a use case node provided by an embodiment of the present disclosure is shown;

[0048] Figure 2 A flowchart of a method for configuring node information of a test case provided by an embodiment of the present disclosure is shown;

[0049] Figure 3 A schematic diagram of a use case node diagram provided by an embodiment of the present disclosure is shown;

[0050] Figure 4 A schematic diagram showing a use case list provided by an embodiment of the present disclosure;

[0051] Figure 5A schematic diagram showing a display node editing page provided by an embodiment of the present disclosure is shown;

[0052] Figure 6 A schematic diagram showing another display node editing page provided by an embodiment of the present disclosure is shown;

[0053] Figure 7 A schematic diagram showing a comparison of a use case node diagram before and after a change provided by an embodiment of the present disclosure;

[0054] Figure 8 A schematic diagram of a node information configuration device for a test case provided by an embodiment of the present disclosure is shown;

[0055] Fig. 9 A schematic diagram of the structure of a computer device provided by an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0056] In order to make the purpose, technical scheme and advantages of the embodiments of the present disclosure clearer, the technical scheme in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, rather than all of the embodiments. The components of the embodiments of the present disclosure generally described and shown here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present disclosure is not intended to limit the scope of the present disclosure claimed for protection, but merely represents the selected embodiments of the present disclosure. Based on the embodiments of the present disclosure, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present disclosure.

[0057] In addition, the terms "first", "second", etc. in the description and claims of the embodiments of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchangeable where appropriate, so that the embodiments described herein can be implemented in an order other than that illustrated or described herein.

[0058] The "multiple or several" mentioned in this article refers to two or more. "And / or" describes the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects are in an "or" relationship.

[0059] According to research, when using a mind map or a use case list to create test cases for application regression testing, for a use case node included in a created test case, the node value corresponding to the use case node can usually be used as the pre-dependency information of multiple subsequent use case nodes, such as Figure 1 FIG. 1 is a schematic diagram of a use case node provided by an embodiment of the present disclosure, wherein the node value corresponding to the use case node A (ie, X goes to the homepage of Y) can be used as the pre-dependency information corresponding to the subsequent use case node B and the subsequent use case node C.

[0060] If there is a need to modify the pre-dependency information of any subsequent use case node, most of the existing technologies directly modify the use case node corresponding to the pre-dependency information of the subsequent use case node. In this way, although the pre-dependency information corresponding to the subsequent use case node is successfully modified, the pre-dependency information of other subsequent use case nodes corresponding to the modified use case node also becomes the modified information at the same time. Figure 1 Take the three use case nodes in as an example to illustrate, if there is a need to modify the pre-dependency information of the subsequent use case node B, the initialization node assignment corresponding to the use case node A will be directly modified (that is, X goes to Y's homepage) to meet the demand. In this way, the pre-dependency information of the subsequent use case node C is also changed from the initialization node assignment to the modified use case node assignment.

[0061] In summary, the existing pre-dependency information modification technology has significant modification drawbacks.

[0062] Based on the above research, the present disclosure provides a node information configuration method and device for a test case. Since the second-type use case node includes a sub-use case node, and the sub-use case node can determine the pre-dependency information of the parent node, for the first-type use case node whose pre-dependency information needs to be modified, by changing it to a second-type use case node, and then configuring the node information of the sub-use case node of the changed second-type use case node, not only can the pre-dependency information of the first-type use case node before the change be modified, but also the problem of directly modifying the pre-node that determines the pre-dependency information of the first-type use case node, resulting in the impact on other use case nodes that rely on the pre-dependency information, is avoided. The modification of the pre-dependency information of the first-type use case node before the change can be only for the first-type use case node, thereby improving the independence and pertinence of the modification of the pre-dependency information.

[0063] The defects existing in the above solutions are the results obtained by the inventor after practice and careful research. Therefore, the discovery process of the above problems and the solutions proposed by the present disclosure for the above problems below should be the contributions made by the inventor to the present disclosure during the disclosure process.

[0064] It should be noted that similar reference numerals and letters denote similar items in the following drawings, and therefore, once an item is defined in one drawing, further definition and explanation thereof is not required in subsequent drawings.

[0065] It should be noted that the specific terms mentioned in the embodiments of the present disclosure include:

[0066] Case use case node: a type of use case node in a test case. The specific format can be case: node assignment + sub-use case node;

[0067] Toast prompt: It is a type of message box in the Android system, a simple message prompt box, and a mechanism used to display prompt information in Android; the idea of ​​the Toast class is to be as inconspicuous as possible while still displaying information to the user.

[0068] To facilitate understanding of the present embodiment, a node information configuration method for a test case disclosed in the embodiment of the present disclosure is first introduced in detail. The executor of the node information configuration method for the test case provided in the embodiment of the present disclosure is generally a computer device with certain computing capabilities. In some possible implementation methods, the node information configuration method for the test case can be implemented by a processor calling computer-readable instructions stored in a memory.

[0069] The node information configuration method of the test case provided by the embodiment of the present disclosure is described below by taking a computer device as an example of an execution subject.

[0070] like Figure 2 As shown, it is a flowchart of a method for configuring node information of a test case provided by an embodiment of the present disclosure, which may include the following steps:

[0071] S201: Obtain a use case list corresponding to the test case, where the use case list contains at least one type of use case node corresponding to the test case, where the at least one type includes a first type use case node, which is a use case node that does not have a corresponding sub-use case node.

[0072] Here, the test case is a case created by the user for regression testing of the application to be tested. For example, a test case is created based on the order in which the application interface is displayed by the application to be tested; a test case is created based on a certain application function of the application to be tested, such as logging in to an authorized account to enter the target function page.

[0073] A test case may include multiple use case nodes, and different use case nodes may have different node types. Specifically, use case nodes of various node types may include but are not limited to the following: use case nodes of pre-dependency type, use case nodes of step type, use case nodes of use case grouping type, use case nodes of step execution result type, first type use case nodes, and second type use case nodes. Use case nodes of step type may also include use case nodes of pre-dependency step type and use case nodes of post-step type. Use case nodes of the same node type may include multiple use case nodes, and multiple use case nodes may include some use case nodes in a parallel relationship.

[0074] Among them, the use case node of the pre-dependent condition type can be a use case node with the format of "PC: node assignment". The first type of use case node is a use case node that does not have a corresponding child use case node, and for the first type of use case node, its corresponding parent node, parent node of the parent node, etc. cannot be a second type of use case node, that is, for the first type of use case node, there cannot be a second type of use case node in each use case node before the use case node, and there cannot be a child use case node after the use case node, otherwise the use case node is not a first type of use case node. Specifically, the first type of use case node can also be called a leaf use case node.

[0075] The second type of use case node is a use case node having at least one child use case node. Specifically, the second type of use case node may be a case use case node.

[0076] A complete test case can be presented in the form of a use case list or in the form of a use case node diagram in mind map mode (also called a strict mind map). Figure 3 FIG. 1 is a schematic diagram of a use case node diagram provided by an embodiment of the present disclosure, wherein: Figure 3 There are 12 use case nodes in it, use case node 1 is a use case grouping type use case node, use case node 2 is a use case node of a pre-dependency condition type, use case node 3 is a use case node of a pre-dependency step type, use case node 4 is a first type use case node, use case node 5 is a second type use case node, use case nodes 6, 7, 8, 9, 10, 11 and 12 are all sub-use case nodes corresponding to use case node 5, among which use case node 6 is a use case node of a pre-dependency condition type corresponding to use case node 5, use case nodes 7, 8, 9 are all use case nodes of a step type, and use case nodes 10, 11 and 12 are all use case nodes of a step execution result type. And, in Figure 3In the example, the node value of use case node 1 is to check user permissions, use case node 2 is PC: M is the first account, N is the second account, the node value of use case node 3 is H goes to K's homepage, the node value of use case node 4 is successfully entered into the homepage, the use case node 5 is case: register a new account to operate, click the target button "follow", the use case node 6 is PC: the user registers the account himself, the use case node 7 is ts: the first click, the use case node 8 is ts: the second to fourth clicks, the use case node 9 is ts: the fifth click, the node value of use case node 10 is to send a request to follow, the node value of use case node 11 is tosat prompt has been sent, and the node value of use case node 12 is no pop-up window and no tosat prompt.

[0077] The use case list may be a list that displays relevant information of various types of use case nodes in various test cases corresponding to the target application in list mode. The use case list may be a list including multiple rows and columns. A use case node corresponds to a row in the use case list, and relevant information of a use case node may be displayed in each column respectively. Each row corresponding to each use case node in the same test case may be folded and hidden in a row corresponding to the test case. The sub-use case nodes corresponding to the second type use case nodes may also be folded and hidden in a row corresponding to the second type use case nodes. Each use case node in a test case except for the use case grouping type use case nodes may be folded and hidden in a row corresponding to the use case grouping type use case nodes. The use case grouping type use case nodes may be hidden in a row corresponding to the identifier of the corresponding test case. For example, the identifier may be an identifier related to the central theme of the test case or an identifier related to the use case name of the test case. The relevant information of the use case node may include the initial assignment of the use case node, the prerequisite dependency conditions, the use case text / steps corresponding to the use case node, the step execution results, the associated scripts of the use case node, the associated requirements of the use case node, the operations that can be performed on the use case node (including renaming, deleting, moving, etc.), the priority of the use case node, etc.; among which, the text / steps corresponding to the use case node may include the prerequisite dependency steps and the post-predetermined dependency steps, and the step execution results may include the step execution results of the prerequisite dependency steps and the step execution results of the post-predetermined dependency steps.

[0078] like Figure 4 As shown, it is a schematic diagram of a use case list provided by an embodiment of the present disclosure. It includes the central theme corresponding to the test case, the strict mind map corresponding to the test case, the use case classification use case node, the PC pre-dependency condition use case node, and the shared step use case node. The shared step use case node includes a use case node corresponding to the execution result of the shared step and a case use case node. Only the use case node corresponding to the execution result of the shared step and the case use case node have some relevant information. Figure 4In the example, there is also a search box for searching for use case nodes (or test cases), a search box for filtering by priority, a search box for selecting tags for searching, a first button for creating a new use case, a second button for creating a new group, and a return button for returning to the previous layer. The relevant information corresponding to the use case node can be 8 columns, each corresponding to the name, priority, pre-dependency condition, use case text / step, step execution result, associated script, associated requirement, and operation. If each use case node has no corresponding relevant information under a column, it can be represented by "-".

[0079] In specific implementation, when the user directly creates various types of use case nodes included in each test case for the target application in the form of a use case list, the use case list can be directly obtained when the user completes the creation.

[0080] S202: When it is determined that the pre-dependency information of the first type use case node needs to be updated, the first type use case node is changed to a second type use case node; the second type use case node is a use case node having at least one child use case node.

[0081] Here, the pre-dependency information can be assigned to the nodes corresponding to each pre-node of the first type of use case node. Some of the sub-use case nodes of the second type of use case node can determine the pre-dependency information of the second type of use case node. For example, a sub-use case node of the pre-dependency condition type can determine the pre-dependency condition of the second type of use case node; a sub-use case node of the pre-dependency step type can determine the pre-dependency step of the second type of use case node.

[0082] The first type of use case node that needs to update the pre-dependency information may be a node that shares the use case node corresponding to the pre-dependency information with other use case nodes. Figure 3 In , use case node 4 and use case node 5 share use case node 3, that is, the node corresponding to use case node 3 is assigned the previous dependency information shared by use case node 4 and use case node 5; Figure 3 In the example, the node value corresponding to the use case node 2 may also be the previous dependency information shared by the use case node 4 and the use case node 5.

[0083] Even if the pre-dependency information corresponding to the first type of use case node is only the pre-dependency information corresponding to the use case node, if there is a need to modify the pre-dependency information, it can also be modified using the method provided in the embodiment of the present disclosure.

[0084] The pre-dependency information that needs to be updated may include multiple, for example, Figure 3If the pre-dependency information corresponding to the use case node 4 needs to be modified, the node assignment corresponding to at least one of the use case nodes 4 and 5 can be modified. The specific pre-dependency information that needs to be modified can be determined according to the actual modification requirements and is not limited here.

[0085] In specific implementation, when there is a need to modify any first-type use case node in a test case, it can be converted into a second-type use case node according to the node value of the first-type use case node. Figure 3 Taking the modification of the pre-dependency information of the first type use case node 4 in the example, the use case node 4 can be converted into a second type use case node "case: successfully enter the home page + sub-use case node" according to the node assignment of successfully entering the home page.

[0086] Furthermore, after the first type of use case node is changed to the second type of use case node, the sub-use case node corresponding to the changed second type of use case node at least includes a sub-use case node corresponding to the pre-dependency information, specifically, it may include a sub-use case node of a pre-dependency condition type, a sub-use case node of a step type, and a use case node for representing the step execution result corresponding to the sub-use case node of the step type (i.e., a use case node of a step execution result type); the sub-use case node of the step type may be a sub-use case node of a pre-dependency step type. Among them, the node assignment corresponding to the sub-use case node of the pre-dependency condition type may be a default assignment, for example, please enter the required pre-dependency condition; or, it may be a node assignment of a use case node related to the pre-dependency condition type in the pre-dependency information corresponding to the first type of use case node. The node assignment of the sub-use case node of the step type may also be a default assignment, for example, please enter the step to be executed; or, it may be a node assignment of the use case node of the pre-dependency step type in the pre-dependency information corresponding to the first type of use case node. The node assignment of the use case node of the step execution result type may be a default assignment, for example, please enter the required step execution result; or, it may be a node assignment corresponding to the first type of use case node.

[0087] Still Figure 3 Taking the modification of the pre-dependency information of the first type use case node 4 in as an example, after changing the use case node 4 to the second type use case node, the node assignment corresponding to the sub-use case node of its pre-dependency condition type can be the node assignment corresponding to the use case node 2, the node assignment corresponding to the sub-use case node of the step type can be the node assignment corresponding to the use case node 3, and the node assignment of the use case node of the step execution result type can be the node assignment corresponding to the use case node 4.

[0088] The number of use case nodes of each of the three node types can be determined based on the pre-dependency information of the first type of use case node and the number of use case nodes corresponding to each of the three node types. For example, if the number of use case nodes of the pre-dependency condition type corresponding to the pre-dependency information of the first type of use case node is 2, then the number of sub-use case nodes of the pre-dependency condition type included in the sub-use case node corresponding to the changed second type of use case node is also 2.

[0089] Furthermore, in a specific implementation, the sub-use case nodes corresponding to the changed second-type use case nodes may include, in addition to the above three types of use case nodes, use case nodes of the post-step type and use case nodes for representing the step execution results corresponding to the sub-use case nodes of the post-step type, and the node assignments of the two types of use case nodes may be default values. The node type and number of sub-use case nodes corresponding to the changed second-type use case nodes may be set according to the pre-dependency information and the actual change information.

[0090] S203: Perform node information configuration for at least one sub-use case node of the changed second-type use case node, wherein the configured node information is used to update the pre-dependency information of the second-type use case node.

[0091] During specific implementation, for each use case node in at least one sub-use case node of the changed second type use case node, the node information of the sub-use case node can be configured, that is, the node value of each use case node can be changed.

[0092] Here, since the sub-use case nodes of the changed second type use case nodes include sub-use case nodes corresponding to the pre-dependency information, the pre-dependency information of the second type use case nodes can be updated by configuring the node information of the sub-use case nodes.

[0093] In this way, since the second type use case node includes child use case nodes, and the child use case nodes can determine the pre-dependency information of the parent node, for the first type use case node whose pre-dependency information needs to be modified, by changing it to a second type use case node, and then configuring the node information of the child use case nodes of the changed second type use case node, not only can the pre-dependency information of the first type use case node before the change be modified, but also it can avoid directly modifying the pre-node that determines the pre-dependency information of the first type use case node, resulting in the problem of affecting other use case nodes that depend on the pre-node. It is achieved that the modification of the pre-dependency information of the first type use case node before the change can only be targeted at the first type use case node, thereby improving the independence and pertinence of the modification of the pre-dependency information.

[0094] In one embodiment, the pre-dependency information includes at least one of the following: a pre-dependency condition, a pre-dependency step, a step execution result of a pre-dependency step, and a use case grouping, etc. Different pre-dependency information corresponds to different types of use case nodes.

[0095] Different pre-dependency information corresponds to different types of use case nodes, that is, different pre-dependency information is determined by the node assignment of different types of use case nodes. Specifically, the pre-dependency condition can be a node assignment for a use case node of the pre-dependency condition type, the pre-dependency step can be a node assignment for a use case node of the pre-dependency step type, the step execution result of the pre-dependency step can be a node assignment for a use case node of the step execution result type, and the use case grouping can be a node assignment for a use case node of the use case grouping type.

[0096] In a specific implementation, the node assignments of each use case node located before the first type use case node may be the pre-dependency information of the use case node.

[0097] In one embodiment, S201 may be implemented according to the following steps:

[0098] S201 - 1 : Obtain a use case node graph corresponding to the test case, where the use case node graph includes node assignments of each use case node corresponding to the test case and dependency relationships between each use case node.

[0099] Here, the dependency relationship between each use case node is used to characterize the corresponding order of each use case node. Due to different usage habits of different users (use case creators), some users tend to create test cases by creating a use case node diagram, and some users tend to create test cases by creating a use case list. Therefore, if it is determined that the user creates the test case by creating a use case node diagram, you can first obtain the use case node diagram corresponding to the test case. For specific use case node diagrams, please refer to Figure 3 shown.

[0100] S201-2: Determine the node type of each use case node, and generate a use case list corresponding to the test case based on the node type, node assignment and dependency relationship.

[0101] During specific implementation, the node type of the use case node with the case identifier can be determined as the second type use case node, the node type of the use case node that does not include a sub-use case node and whose previous use case node does not include a second type use case node can be determined as the first type use case node, the node type of the use case node with the PC identifier can be determined as the prerequisite dependency type, the node type of the use case node located between the prerequisite type use case node and the first type use case node can be determined as the prerequisite dependency step type, and the node type corresponding to the first use case node in the use case node diagram can be determined as the use case grouping type.

[0102] Furthermore, a use case list corresponding to the test case may be generated according to the node type and node value of each use case node and the dependency relationship between each use case node.

[0103] In one embodiment, the generation of a use case list corresponding to the test case according to the node type, node value assignment and dependency relationship in S201-2 may be implemented according to the following steps:

[0104] S201-2-1: For a first type of use case node, based on the node position and dependency relationship of the first type of use case node, determine each predecessor dependency node corresponding to the first type of use case node; according to the node type and node value corresponding to each predecessor dependency node, determine the predecessor dependency information of the first type of use case node.

[0105] During specific implementation, for each first type use case node in the use case node diagram, the use case nodes preceding the first type use case node can be determined based on the node position of the first type use case node and the dependency relationship between the use case nodes, and the use case nodes preceding the first type use case node can be respectively used as the predecessor dependency nodes corresponding to the first type use case node. Then, based on the node type of each determined predecessor dependency node, it can be determined which type of predecessor dependency information of the first type use case node each predecessor dependency node corresponds to. For example, in the case where the node type corresponding to the predecessor dependency node is a predecessor dependency condition type, it can be determined that the predecessor use case node corresponds to the predecessor dependency condition in the predecessor dependency information. Furthermore, the node values ​​corresponding to each predecessor dependency node can be assigned as various predecessor dependency information of the first type use case node.

[0106] For example, Figure 3 As shown, based on the node position of use case node 4 and the dependency relationships corresponding to use case nodes 1, 2, 3 and 4, it can be determined that use case nodes 1, 2, 3 are the respective predecessor dependency nodes corresponding to use case node 4. Afterwards, the node values ​​corresponding to use case nodes 1, 2, 3 can be assigned as the predecessor dependency information of use case node 4, that is, the relevant information of use case node 4 can be obtained.

[0107] S201-2-2: For the second type use case node, based on the dependency relationship, determine each sub-use case node of the second type use case node, and based on the node type and node assignment of each sub-use case node, determine the pre-dependency conditions and execution step information of the second type use case node; the execution step information includes each pre-dependency step, each post-dependency step and the step execution results corresponding to each step corresponding to the second type use case node.

[0108] Here, the execution step information may include a preceding dependent step, a step execution result of the preceding dependent step, a succeeding dependent step, and a step execution result of the succeeding dependent step.

[0109] In specific implementation, for each second type use case node in the use case node diagram, each sub-use case node of the second type use case node can be determined according to the dependency relationship corresponding to the second type use case node, and then, based on the node type of each sub-use case node, a sub-use case node corresponding to the pre-dependency condition type, a sub-use case node corresponding to the pre-dependency step type, a sub-use case node corresponding to the step execution result type, and a sub-use case node corresponding to the post-step type can be determined. Among them, the sub-use case node corresponding to the step execution result type can include a sub-use case node corresponding to the pre-step execution result type and a sub-use case node corresponding to the post-step execution result type.

[0110] Furthermore, based on the node value assignment of the determined sub-use case node corresponding to the pre-dependency type, the pre-dependency of the second type use case node can be determined, and based on the node value assignment of the determined sub-use case node corresponding to the pre-dependency step type and the sub-use case node corresponding to the pre-step execution result type, the pre-dependency step and the step execution result of the pre-dependency step can be determined; and based on the node value assignment of the sub-use case node of the post-step type and the sub-use case node corresponding to the post-step execution result type, each post-dependency step and the step execution result corresponding to the post-dependency step can be determined. That is, the execution step information of the second type use case node can be obtained.

[0111] S201-2-3: Based on the determined pre-dependency information of each first-type use case node, and the pre-dependency conditions and execution step information of each second-type use case node, determine a use case list corresponding to the test case.

[0112] During specific implementation, each use case node can be regarded as a row in a use case list. For each first-type use case node, the information corresponding to each column of the first-type use case node can be determined based on the prerequisite dependency information of the first-type use case node; for each second-type use case node, the information corresponding to each column of the second-type use case node can be determined based on the prerequisite dependency conditions and execution step information of the second-type use case node; for other types of use case nodes, the information corresponding to each column of the use case node can be determined based on the node value of each use case node. Specifically, for other types of use case nodes, the node value of the use case node can be used as the information of the name column, and the information on each column can be set to empty or the default value, or can be modified by the user.

[0113] In one embodiment, S202 may be implemented according to the following steps:

[0114] S202 - 1 : In response to a trigger operation on a first type of use case node in the use case list, generate and display a node editing page corresponding to the first type of use case node.

[0115] The node editing page displays the pre-dependency information corresponding to the first type use case node, and the displayed pre-dependency information is not editable; the node editing page displays a first form target button; the first form target button is used to indicate an update to the pre-dependency information of the first type use case node.

[0116] Here, the triggering operation for the first type of use case node in the use case list may be a single-click operation or a double-click operation by the user at any position in the row where the first type of use case node is located.

[0117] The above-mentioned node editing page may include a pre-dependency display box displaying the pre-dependency of the first type of use case node, a step display box displaying the pre-dependency steps, and a step execution result display box displaying the step execution results of the pre-dependency steps, and the display box and the information displayed in the display box are not editable.

[0118] In addition, the node editing page may also include a node name display box that displays the node name of the first type use case node (i.e., the node assignment of the first type use case node), a corresponding group selection box that displays the first type use case node, a priority selection box, a label information input box, a remark information input box, an associated information box, an associated script box, and an attachment information box. The various display boxes and the information in the display boxes involved here can be set to allow editing or not to allow editing, which is not limited here. In addition, it may also include a confirm button for confirming that the changes are completed and a cancel button for canceling the changes.

[0119] Specifically, all relevant information of the first type use case node may be displayed in the node editing page.

[0120] The target button can be specifically a lock button, and the first state is that the lock is in the closed state. The first state of the target button is used to indicate that the pre-dependency information of the first type of use case node is updated, that is, by clicking the first state of the target button, the pre-dependency information of the first type of use case node can be changed.

[0121] In specific implementation, in response to a trigger operation on a first type of use case node in the use case list, a node editing page corresponding to the first type of use case node can be generated based on all relevant information of the first type of use case node displayed in the use case list, and the node editing page can be displayed at a preset position in the use case list, for example, on the right side, left side, or middle of the use case list.

[0122] like Figure 5 FIG. 1 is a schematic diagram of a display node editing page provided by an embodiment of the present disclosure. Figure 5 The information displayed in the node name display box is the home page of H to K. The group selection box displays selection marks for selecting groups upward and downward. The priority displayed in the priority selection box is pending. The information displayed in the pre-dependency display box is that M is the first account and N is the second account. The information displayed in the step display box is the home page of H to K. The information displayed in the step execution result display box is that the home page is successfully entered. The corresponding default information is displayed in the label information input box, the remark information input box, the associated information box, the associated script box and the attachment information. For details, see Figure 5 .

[0123] In addition to the first type of use case nodes, in response to a trigger operation on any other use case node in the use case list, a node editing page corresponding to the other use case node may be generated based on the relevant information of the other use case node, and the node editing page may be displayed at a preset position in the use case list. The information displayed on the node editing page corresponding to the other use case node may be edited directly, or may require a trigger operation on the target button in subsequent S202-2 to be performed before editing is allowed, which is not limited here.

[0124] S202 - 2 : In response to a trigger operation on a target button, the first type use case node is changed to a second type use case node, and the form of the target button is converted to a second form for indicating that the update has been completed or is in progress.

[0125] Among them, the sub-use case nodes corresponding to the changed second-type use case nodes include target sub-use case nodes with initial node assignments determined according to the pre-dependency information.

[0126] Here, the trigger operation for the target button can be a single click operation or double click operation of the target button by the user. The step of changing the first type use case node to the second type use case node is to add the "case" mark to the information of the first type use case node in the node name display box on the node editing page, and add the "ts" mark to the information in the step display box as the target sub-use case node corresponding to the changed second type use case node, that is, to assign the initial node value of the use case node of the pre-dependent step type corresponding to the pre-dependent information as the node value of the target sub-use case node.

[0127] And all information on the node editing page is allowed to be edited. Specifically, the information in each display frame corresponding to the pre-dependency information of the changed second type use case node must be in a state of allowing editing.

[0128] The second form may specifically be that the identification lock is in an open state, which is used to indicate that the update of the pre-dependency information corresponding to the first type use case node has been completed, or the update of the pre-dependency information corresponding to the first type use case node is in progress.

[0129] like Figure 6 FIG. 1 is a schematic diagram of another display node editing page provided by an embodiment of the present disclosure. Figure 6 The node editing page shown in is the page corresponding to changing the first type use case node to the second type use case node. Figure 6 The step display box in the target sub-use case node corresponds to the target sub-use case node, which is "ts: Figure 5 Step display box”, that is, ts: H goes to K’s home page; Figure 6 The pre-dependency display box in the also corresponds to a target sub-use case node, where M is the first account, N is the second account and is editable. A button for adding a new step can also be displayed below the step execution box. By clicking the button, the user can add a sub-use case node corresponding to the changed second type use case node. In addition, a picture addition mark can be added to the step display box and the step execution result display box. The user can enter the picture selection page by clicking the mark.

[0130] In specific implementation, in response to the trigger operation on the target button, the step of changing the first type use case node to the second type use case node is executed to generate the following Figure 6 The node editing page corresponding to the change of the first type use case node to the second type use case node is shown, and the information displayed at any position in the node editing page is allowed to be edited.

[0131] Furthermore, after the user completes editing of the pre-dependency information displayed on the node editing page, that is, after configuring the node information of at least one sub-use case node of the changed second-type use case node, the user can click the OK button, and then, in response to the click operation, the user can complete the update of the information corresponding to the changed second-type use case node displayed in the use case list based on the edited pre-dependency information. And, based on the updated use case list, the use case node diagram of the test case corresponding to the changed second-type use case node can be updated.

[0132] Alternatively, the user can also click the Cancel button to cancel the editing of the pre-dependency information of the first type of use case node before the change, and Figure 6 The node editing page shown is restored to Figure 5 Alternatively, the display of the node editing page can be directly canceled, and after the next trigger operation for the first type use case node is responded to, the node editing page can be directly displayed as shown in FIG. Figure 5 The node editing page is shown.

[0133] In one embodiment, for S203, during the specific implementation, for the target sub-use case node in at least one sub-use case node of the changed second type use case node, the first target assignment for the target sub-use case node entered by the user in the step display box in the node boundary page is obtained, and the initial node assignment of the target sub-use case node is replaced with the first target assignment to obtain the target sub-use case node with completed node information configuration.

[0134] For example, Figure 6 The step display box corresponding to the target sub-use case node displayed in the display box can modify the information "ts: H goes to K's homepage" in the display box to the new information "ts: K goes to Y's homepage", and assign "K goes to Y's homepage" as the first target value. Then, the initial node assignment "H goes to K's homepage" of the target sub-use case node corresponding to the step display box can be replaced with "K goes to Y's homepage" to obtain the target sub-use case node with the node information configuration completed. For another example, for Figure 6 In the pre-dependency display box corresponding to the target sub-use case node shown in , the information "M is the first account, N is the second account" in the display box can be modified to the new information "You need to register an account yourself", and "You need to register an account yourself" is used as the first target assignment. Then, you can use "You need to register an account yourself" to replace the initial node assignment "M is the first account, N is the second account" of the target sub-use case node corresponding to the pre-dependency to obtain the target sub-use case node with completed node information configuration.

[0135] Alternatively, a request may be generated in response to a subnode of the changed second type use case node, that is, in response to a user clicking on the Figure 6 The operation of the button for adding a new step is shown, which determines that the user has initiated a sub-node generation request and responds to the request by displaying a new sub-use case node with a default node assignment. The new sub-use case node is a newly created sub-use case node, which can include a sub-use case node of a post-dependent step type and a sub-use case node of a corresponding step execution result type. The default node assignment of a sub-use case node of a post-dependent step type can be "Please enter a new step", and the default node assignment of a sub-use case node of a step execution result type corresponding to a sub-use case node of a post-dependent step type can be "Please enter the step execution result". Specifically, Figure 6 A new step display box and a corresponding step execution result display box corresponding to the newly created sub-use case node are generated in the step display box in the node editing page shown. The step display box displays "ts: Please enter a new step" and the step execution result display box displays "Please enter the step execution result".

[0136] Furthermore, the information for the newly created sub-use case node input by the user in the new step display box on the node editing page can be obtained, and used as the second target assignment of the newly created sub-use case node of the post-dependent step type, and the second target assignment is used to replace the default node assignment of the newly created sub-use case node, and the information entered by the user in the step execution result display box corresponding to the new step display box on the node editing page can be obtained, and used as the node assignment of the newly created sub-use case node of the step execution result type, thereby obtaining a newly created sub-use case node with completed node information configuration.

[0137] Based on the steps mentioned in this embodiment, it is possible to edit the sub-use case nodes of the changed second-type use case nodes, that is, to edit the preceding dependency information, and to edit the subsequent steps corresponding to the changed second-type use case nodes by creating new sub-use case nodes.

[0138] Furthermore, after the user has completed the configuration of node information for at least one sub-use case node of the changed second-type use case node, the user can click the OK button; then, in response to the click operation, based on the edited pre-dependency information and the node assignment corresponding to the newly created sub-use case node, the user can complete the update of the information corresponding to the changed second-type use case node displayed in the use case list, and generate each row of information corresponding to the newly created sub-use case node, thereby updating the use case list. In addition, based on the updated use case list, the use case node diagram of the test case corresponding to the changed second-type use case node can be updated.

[0139] In one embodiment, after configuring node information for at least one sub-use case node of the changed second-type use case node and completing the update of the use case list, it is also possible to respond to the trigger operation of the second-form target button displayed in the node editing page, specifically, respond to the click operation of the second-form target button displayed in the node editing page; then the changed second-type use case node can be restored to the first-type use case node, and the editing of the pre-dependency information of the first-type use case node corresponding to the changed second-type use case node is canceled. No matter how many times the user edits the pre-dependency information corresponding to the first-type use case node, after the user clicks the second-form target button, the pre-dependency information corresponding to the first-type use case node is restored to the initial pre-dependency information. However, the node assignment corresponding to the changed second-type use case node and the node assignment of each sub-use case node corresponding to the second-type use case node can be saved in a preset location so as to be directly obtained when needed later.

[0140] like Figure 7 FIG. 1 is a schematic diagram showing a comparison of a use case node diagram before and after a change provided by an embodiment of the present disclosure, wherein the use case node Figure 1 This is the use case node diagram before the change. The use case node Figure 2 This is the changed use case node diagram. Figure 1 After modifying the pre-dependency information corresponding to the step execution result of the first type of use case node in area C1 of the shared step, the use case node Figure 2 The second type use case node at the area c1 in the example, and the two sub use case nodes corresponding to the second type use case node; the use case node Figure 1 The second type of use case node and its corresponding sub-use case node in the area D1 in the example can be a use case node Figure 2 The first type use case node at area d1 in the changed state can be restored to the first type use case node at area d1 after canceling the editing of the pre-dependency information corresponding to the second type use case node at area D1.

[0141] Those skilled in the art will appreciate that, in the above method of specific implementation, the order in which the steps are written does not imply a strict execution order and does not constitute any limitation on the implementation process. The specific execution order of the steps should be determined by their functions and possible internal logic.

[0142] Based on the same inventive concept, the embodiment of the present disclosure also provides a node information configuration device for a test case corresponding to the node information configuration method for a test case. Since the principle of solving the problem by the device in the embodiment of the present disclosure is similar to the node information configuration method for the above-mentioned test case in the embodiment of the present disclosure, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be repeated.

[0143] like Figure 8 FIG. 1 is a schematic diagram of a node information configuration device for a test case provided by an embodiment of the present disclosure, including:

[0144] An acquisition module 801 is used to acquire a use case list corresponding to a test case, wherein the use case list includes at least one type of use case node corresponding to the test case, wherein the at least one type includes a first type of use case node, and the first type of use case node is a use case node that does not have a corresponding sub-use case node;

[0145] An updating module 802, configured to change the first type of use case node to a second type of use case node when it is determined that the pre-dependency information of the first type of use case node needs to be updated; the second type of use case node is a use case node having at least one child use case node;

[0146] The configuration module 803 is used to configure node information for at least one sub-use case node of the changed second-type use case node, wherein the configured node information is used to update the pre-dependency information of the second-type use case node.

[0147] In a possible implementation, the pre-dependency information includes at least one of the following: a pre-dependency condition, a pre-dependency step, and a step execution result of the pre-dependency step, and different pre-dependency information corresponds to different types of use case nodes.

[0148] In a possible implementation, the acquisition module 801 is used to acquire a use case node graph corresponding to the test case, wherein the use case node graph includes node assignments of each use case node corresponding to the test case and dependencies between each of the use case nodes;

[0149] Determine the node type of each of the use case nodes, and generate a use case list corresponding to the test case based on the node type, the node value assignment and the dependency relationship.

[0150] In a possible implementation, the acquisition module 801 is used to determine, for a first type use case node, each preceding dependency node corresponding to the first type use case node based on the node position of the first type use case node and the dependency relationship; determine the preceding dependency information of the first type use case node according to the node type and node value corresponding to each preceding dependency node;

[0151] For the second type use case node, based on the dependency relationship, determine each sub-use case node of the second type use case node, and based on the node type and node assignment of each sub-use case node, determine the pre-dependency condition and execution step information of the second type use case node; the execution step information includes each pre-dependency step, each post-dependency step and the step execution result corresponding to each step of the second type use case node;

[0152] Based on the determined pre-dependency information of each first-type use case node and the pre-dependency conditions and execution step information of each second-type use case node, a use case list corresponding to the test case is determined.

[0153] In a possible implementation, the update module 802 is used to generate and display a node editing page corresponding to the first type of use case node in the use case list in response to a trigger operation on the first type of use case node; the node editing page displays the pre-dependency information corresponding to the first type of use case node, and the displayed pre-dependency information is not editable; the node editing page displays a first form of target button; the first form of target button is used to indicate that the pre-dependency information of the first type of use case node is updated;

[0154] In response to a trigger operation on the target button, the first type use case node is changed to a second type use case node, and the form of the target button is converted to a second form for indicating that the update has been completed or is in progress; wherein the sub-use case node corresponding to the changed second type use case node includes a target sub-use case node having an initial node assignment determined according to the prerequisite dependency information.

[0155] In a possible implementation, the configuration module 803 is used to obtain the input first target assignment for the target sub-use case node in at least one sub-use case node of the changed second-type use case node, and use the first target assignment to replace the initial node assignment of the target sub-use case node to obtain the target sub-use case node for which the node information configuration is completed; and / or

[0156] In response to a subnode generation request for the changed second-type use case node, a newly created sub-use case node with a default node assignment is displayed, and the second target assignment of the newly created sub-use case node is obtained, and the default node assignment of the newly created sub-use case node is replaced with the second target assignment to obtain a newly created sub-use case node with completed node information configuration.

[0157] In a possible implementation, the device further includes:

[0158] The restoration module 804 is used to restore the changed second-type use case node to the first-type use case node and restore the form of the target button to the first form in response to a trigger operation of a second-form target button displayed on the node editing page after configuring node information for at least one sub-use case node of the changed second-type use case node.

[0159] For descriptions of the processing flow of each module in the device and the interaction flow between each module, reference may be made to the relevant descriptions in the above method embodiment, which will not be described in detail here.

[0160] The present disclosure also provides a computer device, such as Fig. 9 FIG. 1 is a schematic diagram of a computer device structure provided by an embodiment of the present disclosure, including:

[0161] A processor 91 and a memory 92; the memory 92 stores machine-readable instructions executable by the processor 91, and the processor 91 is used to execute the machine-readable instructions stored in the memory 92. When the machine-readable instructions are executed by the processor 91, the processor 91 performs the following steps: S201: Obtain a use case list corresponding to the test case, the use case list contains at least one type of use case node corresponding to the test case, at least one type includes a first type use case node, and the first type use case node is a use case node that does not have a corresponding sub-use case node; S202: When it is determined that the pre-dependency information of the first type use case node needs to be updated, change the first type use case node to a second type use case node; the second type use case node is a use case node with at least one sub-use case node; and S203: For at least one sub-use case node of the changed second type use case node, configure node information, wherein the configured node information is used to update the pre-dependency information of the second type use case node.

[0162] The above-mentioned memory 92 includes internal memory 921 and external memory 922; the memory 921 here is also called internal memory, which is used to temporarily store the calculation data in the processor 91 and the data exchanged with the external memory 922 such as the hard disk. The processor 91 exchanges data with the external memory 922 through the internal memory 921.

[0163] The specific execution process of the above instructions can refer to the steps of the node information configuration method of the test case described in the embodiment of the present disclosure, which will not be repeated here.

[0164] The present disclosure also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the node information configuration method for the test case described in the above method embodiment are executed. The storage medium can be a volatile or non-volatile computer-readable storage medium.

[0165] The computer program product of the node information configuration method for the test case provided in the embodiment of the present disclosure includes a computer-readable storage medium storing program code, and the instructions included in the program code can be used to execute the steps of the node information configuration method for the test case described in the above method embodiment. For details, please refer to the above method embodiment, which will not be repeated here.

[0166] The computer program product may be implemented in hardware, software or a combination thereof. In one optional embodiment, the computer program product is embodied as a computer storage medium, and in another optional embodiment, the computer program product is embodied as a software product, such as a software development kit (SDK) and the like.

[0167] Those skilled in the art can clearly understand that, for the convenience and simplicity of description, the specific working process of the device described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here. In the several embodiments provided in the present disclosure, it should be understood that the disclosed device and method can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, and the indirect coupling or communication connection of the device or unit can be electrical, mechanical or other forms.

[0168] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0169] In addition, each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0170] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium that is executable by a processor. Based on this understanding, the technical solution of the present disclosure, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present disclosure. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0171] Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present disclosure, which are used to illustrate the technical solutions of the present disclosure, rather than to limit them. The protection scope of the present disclosure is not limited thereto. Although the present disclosure is described in detail with reference to the above-described embodiments, ordinary technicians in the field should understand that any technician familiar with the technical field can still modify the technical solutions recorded in the above-described embodiments within the technical scope disclosed in the present disclosure, or can easily think of changes, or make equivalent replacements for some of the technical features therein; and these modifications, changes or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present disclosure, and should be included in the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be based on the protection scope of the claims.

Claims

1. A method for configuring node information of a test case, characterized in that: include: Obtain a use case list corresponding to the test case, wherein the use case list includes at least one type of use case node corresponding to the test case, wherein the at least one type includes a first type of use case node, and the first type of use case node is a use case node that does not have a corresponding sub-use case node; In the case where it is determined that the pre-dependency information of the first type use case node needs to be updated, the first type use case node is changed to a second type use case node; the second type use case node is a use case node having at least one child use case node; For at least one sub-use case node of the changed second-type use case node, node information configuration is performed, wherein the configured node information is used to update the pre-dependency information of the second-type use case node.

2. The method according to claim 1, characterized in that The pre-dependency information includes at least one of the following: a pre-dependency condition, a pre-dependency step, and a step execution result of a pre-dependency step. Different pre-dependency information corresponds to different types of use case nodes.

3. The method according to claim 2, characterized in that The obtaining of a list of use cases corresponding to the test case includes: Obtaining a use case node graph corresponding to the test case, wherein the use case node graph includes node assignments of each use case node corresponding to the test case and dependency relationships between each of the use case nodes; Determine the node type of each of the use case nodes, and generate a use case list corresponding to the test case based on the node type, the node value assignment and the dependency relationship.

4. The method according to claim 3, characterized in that The step of generating a use case list corresponding to the test case according to the node type, the node value assignment and the dependency relationship includes: For a first type of use case node, based on the node position of the first type of use case node and the dependency relationship, determine each preceding dependency node corresponding to the first type of use case node; determine the preceding dependency information of the first type of use case node according to the node type and node value corresponding to each preceding dependency node; For the second type use case node, based on the dependency relationship, determine each sub-use case node of the second type use case node, and based on the node type and node assignment of each sub-use case node, determine the pre-dependency condition and execution step information of the second type use case node; the execution step information includes each pre-dependency step, each post-dependency step and the step execution result corresponding to each step of the second type use case node; Based on the determined pre-dependency information of each first-type use case node and the pre-dependency conditions and execution step information of each second-type use case node, a use case list corresponding to the test case is determined.

5. The method according to claim 2, characterized in that: The step of changing the first type of use case node to a second type of use case node when it is determined that the pre-dependency information of the first type of use case node needs to be updated includes: In response to a trigger operation on a first type of use case node in the use case list, a node editing page corresponding to the first type of use case node is generated and displayed; the node editing page displays the pre-dependency information corresponding to the first type of use case node, and the displayed pre-dependency information is not editable; the node editing page displays a first form of target button; the first form of target button is used to indicate updating the pre-dependency information of the first type of use case node; In response to a trigger operation on the target button, the first type use case node is changed to a second type use case node, and the form of the target button is converted to a second form for indicating that the update has been completed or is in progress; wherein the sub-use case node corresponding to the changed second type use case node includes a target sub-use case node having an initial node assignment determined according to the prerequisite dependency information.

6. The method according to claim 5, characterized in that The configuring node information for at least one sub-use case node of the changed second-type use case node includes: For a target sub-use case node in at least one sub-use case node of the changed second-type use case node, obtain the input first target assignment for the target sub-use case node, and use the first target assignment to replace the initial node assignment of the target sub-use case node to obtain the target sub-use case node with completed node information configuration; and / or In response to a subnode generation request for the changed second-type use case node, a newly created sub-use case node with a default node assignment is displayed, and the second target assignment of the newly created sub-use case node is obtained, and the default node assignment of the newly created sub-use case node is replaced with the second target assignment to obtain a newly created sub-use case node with completed node information configuration.

7. The method according to claim 6, characterized in that After configuring the node information of at least one sub-use case node of the changed second-type use case node, the method further includes: In response to a trigger operation on the second-type target button displayed in the node editing page, the changed second-type use case node is restored to the first-type use case node, and the form of the target button is restored to the first form.

8. A node information configuration device for a test case, characterized in that: include: An acquisition module, configured to acquire a use case list corresponding to a test case, wherein the use case list includes at least one type of use case node corresponding to the test case, wherein the at least one type includes a first type of use case node, and the first type of use case node is a use case node that does not have a corresponding sub-use case node; An updating module, configured to change the first type of use case node to a second type of use case node when it is determined that the pre-dependency information of the first type of use case node needs to be updated; the second type of use case node is a use case node having at least one child use case node; A configuration module is used to configure node information for at least one sub-use case node of the changed second-type use case node, wherein the configured node information is used to update the pre-dependency information of the second-type use case node.

9. A computer device, characterized in that: include: A processor and a memory, wherein the memory stores machine-readable instructions executable by the processor, and the processor is used to execute the machine-readable instructions stored in the memory. When the machine-readable instructions are executed by the processor, the processor executes the steps of the node information configuration method for the test case according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program. When the computer program is executed by a computer device, the computer device executes the steps of the node information configuration method for a test case according to any one of claims 1 to 7.

Images