A scenario-level business process case chain generation and automatic update method

Abstract

The present invention relates to a scenario-level business process case chain generation and automatic update method. By isolating and storing the basic cases, nodes, and transaction chains involved in the business process case chain, a storage network in the form of an associated library is formed in combination with the association relationship between the libraries. When performing deletion and modification operations, the data to be updated can be directly located by querying the data in the associated library. In particular, when only deleting the transaction chain, node, case, or modifying the case content or node name, the content to be updated can be intelligently identified and the data can be synchronously updated in the associated library, thereby realizing direct update without full coverage.

Description

Technical Field

[0001] The present invention relates to the technical field of business scenario testing, and in particular to a scenario-level business process case chain generation and automatic updating method. Background Art

[0002] Test cases are necessary tools for testing transaction businesses. In particular, they require the implementation of scenario-level case chains based on business processes so that test cases can be closer to the actual situation of transaction businesses and obtain more valuable test results.

[0003] The existing technologies for test case generation and business process instantiation currently only involve the generation of scenario-level business process case chains and the direct coverage and update of single cases in the case chains, which cannot meet the requirements for targeted automatic updates of case chains.

[0004] However, in the test scenarios corresponding to actual use, in addition to the update of a case in the case chain, it will also involve the update of a node or even a transaction chain branch. When it is necessary to add a new transaction chain, node, case, or modify a transaction chain or node-related case, a new association relationship must be added. In the prior art, manual updates can only be used to generate new scenario-level business process case chains. In this process, it is necessary to rebind the nodes to the associated cases, and set the combination relationship between nodes according to actual business needs, which is a relatively complicated operation. When only deleting transaction chains, nodes, cases, or modifying case content and node names, since it is only an update to the existing business process case chain and does not involve adding new association relationships, if the full coverage update is still used, it is necessary to repeatedly bind nodes to associated cases and set the combination relationship between nodes, which is extremely inefficient. Summary of the invention

[0005] In order to address the deficiencies of the prior art, the present invention proposes a scenario-level business process case chain generation and automatic update method, which isolates and stores the basic cases, nodes, and transaction chains involved in the business process case chain, and combines the association relationships between the libraries to form a storage network in the form of an associated library. When performing deletion and modification operations, the data to be updated can be directly located by querying the data in the associated library. In particular, when only deleting transaction chains, nodes, and cases, or modifying case content and node names, the content to be updated can be intelligently identified and the data can be synchronously updated in the associated library, thereby realizing direct updates with non-full coverage.

[0006] To achieve the above objectives, the technical solutions adopted by the present invention include:

[0007] A scenario-level business process case chain generation and automatic update method, characterized by comprising:

[0008] S1. Arrange and collect corresponding data of basic cases to form a basic case library, wherein the corresponding data of the basic cases include case ID, case name and case content;

[0009] S2. Arrange the corresponding data of the set nodes to form a node library, wherein the corresponding data of the nodes include node ID, node name and the association relationship between the node and the basic case, and a specific node is bound to one or more specific basic cases through the association relationship between the node and the basic case;

[0010] S3. Arrange the corresponding data of the aggregated transaction chains to form a transaction chain branch library. The corresponding data of the transaction chains include the transaction chain ID, the transaction chain content, and the association relationship between the transaction chain and the nodes. A specific transaction chain determines all the nodes included in the specific transaction chain and the connection order between the nodes through the association relationship between the transaction chain and the nodes.

[0011] S4. Arrange and collect the corresponding data of the scenario cases to form a scenario case library, wherein the corresponding data of the scenario cases include the scenario case ID, the scenario case content, the association relationship between the scenario case and the transaction chain, and the association relationship between the scenario case and the basic case. The specific scenario case determines the transaction chain applied to the specific scenario through the association relationship between the scenario case and the transaction chain, and the specific scenario case determines the basic case applied to the specific scenario through the association relationship between the scenario case and the basic case;

[0012] S51, modifying the corresponding data of a specific basic case in the basic case library, and updating the scenario cases related to the specific basic case;

[0013] S52, modifying the corresponding data of a specific node in the node library, and updating the transaction chain related to the specific node;

[0014] S61. Delete a specific basic case from the basic case library, and delete the scenario cases related to the specific basic case;

[0015] S62. Delete a specific node in the node library, and delete the transaction chain related to the specific node and the scenario cases related to the deleted transaction chain;

[0016] S63. Delete a specific transaction chain in the transaction chain branch library, and delete the scenario cases related to the specific transaction chain.

[0017] Furthermore, all the basic cases applied in the specific scenario belong to the basic cases bound to the nodes included in the transaction chain applied in the specific scenario.

[0018] Furthermore, the association relationship between the scenario case and the basic case is obtained through the following steps:

[0019] Determine the relevant transaction chain based on the relationship between the scenario case and the transaction chain;

[0020] Determine the relevant nodes based on the association relationship between the relevant transaction chain and the nodes;

[0021] Determine a valid basic case set based on the association relationship between the relevant nodes and the basic cases;

[0022] Select basic cases related to the scenario cases from the valid basic case set, and determine the correlation between the scenario cases and the basic cases.

[0023] Furthermore, the scenario cases related to the update of the specific basic case include:

[0024] Determine the scenario case related to the specific base case based on the association relationship between the scenario case and the base case;

[0025] Only the corresponding data of the specific base case in the relevant scenario case is updated.

[0026] Furthermore, the updating of the transaction chain related to the specific node includes:

[0027] Determine the transaction chain related to the specific node based on the association relationship between the transaction chain and the node;

[0028] Only the corresponding data of the specific node in the relevant transaction chain is updated.

[0029] Furthermore, the scenario cases related to deleting the specific basic case include:

[0030] Determine the scenario case related to the specific base case based on the association relationship between the scenario case and the base case;

[0031] Delete the corresponding data of the relevant scenario cases;

[0032] Determine the nodes related to the specific base case based on the association relationship between the nodes and the base case;

[0033] Modify the association between a node and a base case, and delete the binding relationship between the relevant node and the specific base case.

[0034] Furthermore, the scenario cases of deleting the transaction chain related to the specific node and the deleted transaction chain include:

[0035] Determine the transaction chain related to the specific node based on the association relationship between the transaction chain and the node;

[0036] Delete the corresponding data of the relevant transaction chain;

[0037] Determine the scenario cases related to the deleted transaction chain according to the association relationship between the scenario cases and the transaction chain;

[0038] Delete the corresponding data of the relevant scenario cases.

[0039] Furthermore, the scenario cases related to deleting the specific transaction chain include:

[0040] Determine the scenario cases related to the specific transaction chain based on the association between the scenario cases and the transaction chain;

[0041] Delete the corresponding data of the relevant scenario cases.

[0042] The present invention also relates to a computer-readable storage medium, characterized in that a computer program is stored on the storage medium, and the computer program implements the above method when executed by a processor.

[0043] The present invention also relates to an electronic device, characterized in that it comprises a processor and a memory;

[0044] The memory is used to store the corresponding data of the basic case, the corresponding data of the node, the corresponding data of the transaction chain and the corresponding data of the scenario case;

[0045] The processor is used to execute the above method by calling the corresponding data of the basic case, the corresponding data of the node, the corresponding data of the transaction chain and the corresponding data of the scenario case.

[0046] The beneficial effects of the present invention are:

[0047] By adopting the scenario-level business process case chain generation and automatic update method described in the present invention, the basic cases, nodes, and transaction chains involved in the business process case chain are stored in isolation, and a storage network in the form of an associated library is formed in combination with the association relationship between the libraries. When performing deletion and modification operations, the data to be updated can be directly located by querying the data in the associated library. In particular, when only deleting the transaction chain, node, case, or modifying the case content or node name, the content to be updated can be intelligently identified and the data can be synchronously updated in the associated library, thereby realizing direct update without full coverage. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] Figure 1 It is a flow chart of the scenario-level business process case chain generation and automatic updating method of the present invention.

[0049] Figure 2 A schematic diagram of business process case chain generation in a preferred embodiment of the present invention.

[0050] Figure 3a Schematic diagram of corresponding data for modifying a specific base case for a preferred embodiment of the present invention.

[0051] Figure 3b A schematic diagram of modifying corresponding data of a specific node for a preferred embodiment of the present invention.

[0052] Figure 4a Delete specific base case schematic diagrams for the preferred embodiment of the present invention.

[0053] Figure 4b A schematic diagram of deleting a specific node is provided for a preferred embodiment of the present invention.

[0054] Figure 4c A schematic diagram of deleting a specific transaction chain in a preferred embodiment of the present invention. DETAILED DESCRIPTION

[0055] In order to more clearly understand the content of the present invention, it will be described in detail with reference to the drawings and embodiments.

[0056] like Figure 1 The figure is a flow chart of the scenario-level business process case chain generation and automatic update method of the present invention, including:

[0057] S1. Arrange and collect corresponding data of basic cases to form a basic case library, wherein the corresponding data of the basic cases include case ID, case name and case content;

[0058] S2. Arrange the corresponding data of the set nodes to form a node library, wherein the corresponding data of the nodes include node ID, node name and the association relationship between the node and the basic case, and a specific node is bound to one or more specific basic cases through the association relationship between the node and the basic case;

[0059] S3. Arrange the corresponding data of the aggregated transaction chains to form a transaction chain branch library. The corresponding data of the transaction chains include the transaction chain ID, the transaction chain content, and the association relationship between the transaction chain and the nodes. A specific transaction chain determines all the nodes included in the specific transaction chain and the connection order between the nodes through the association relationship between the transaction chain and the nodes.

[0060] S4. Arrange and collect the corresponding data of the scenario cases to form a scenario case library, wherein the corresponding data of the scenario cases include the scenario case ID, the scenario case content, the association relationship between the scenario case and the transaction chain, and the association relationship between the scenario case and the basic case. The specific scenario case determines the transaction chain applied to the specific scenario through the association relationship between the scenario case and the transaction chain, and the specific scenario case determines the basic case applied to the specific scenario through the association relationship between the scenario case and the basic case;

[0061] S51, modifying the corresponding data of a specific basic case in the basic case library, and updating the scenario cases related to the specific basic case;

[0062] S52, modifying the corresponding data of a specific node in the node library, and updating the transaction chain related to the specific node;

[0063] S61. Delete a specific basic case from the basic case library, and delete the scenario cases related to the specific basic case;

[0064] S62. Delete a specific node in the node library, and delete the transaction chain related to the specific node and the scenario cases related to the deleted transaction chain;

[0065] S63. Delete a specific transaction chain in the transaction chain branch library, and delete the scenario cases related to the specific transaction chain.

[0066] Among them, steps S1 to S4 establish a business process case chain generation structure with an isolated storage structure. The data in the scenario case are actually stored in different libraries and combined through mutual association relationships to form a scenario case. Therefore, it can support independent modification and deletion of some of the data without the need for a full update.

[0067] Steps S51 to S63 provide an operation method for modifying or deleting data, which is different from the prior art in that it can perform targeted updates based on the associations between data, and is more efficient.

[0068] like Figure 2The figure shows a schematic diagram of the business process case chain generation under a preferred embodiment of the present invention. Among them, the basic case library stores basic case data, including case ID, case name and case details (case content); the node library stores the nodes passed in the business process, including node ID, node name and the relationship between the node and the basic case library; the transaction chain branch library stores the branches of the business process, including transaction chain ID, transaction chain details (transaction chain content) and the relationship between the transaction chain and the node; the business process scenario case library stores scenario-level business process cases, including scenario case ID, scenario case details (scenario case content) and the relationship between the scenario case and the transaction chain, and the relationship between the scenario case and the basic case. The relationship between the two libraries is represented by a connecting line. Taking the transaction chain A->B->D in the figure as an example, the basic cases a1, a2, b1, b2, b3, d involved in the transaction chain are stored in the basic case library; the nodes A, B and D involved in the transaction chain are stored in the node library, as well as the relationship between the nodes and the basic cases, that is, node A is bound to the basic case (a1, a2), node B is bound to the basic case (b1, b2, b3), and node D is bound to the basic case d. The transaction chain A->B->D and the relationship between the transaction chain and the nodes are stored in the transaction chain branch library, that is, the transaction chain contains nodes (A, B, D). In the business process scenario case library, the scenario-level business process cases (a1->b3->d, a2->b3->d) of the transaction chain are stored, as well as the association between the scenario-level cases and the transaction chain, i.e., the scenario-level cases generated by the transaction chain A->B->D are (a1->b3->d, a2->b3->d); and the association between the transaction chain scenario-level cases and the basic cases, i.e., the scenario-level case a1->b3->d contains the basic case (a1, b3, d), and a2->b3->d contains the basic case (a2, b3, d).

[0069] like Figure 3a The figure shows the corresponding data diagram of modifying a specific basic case in the preferred embodiment of the present invention, taking case a1 as an example. In the basic case library, case No. 1 is modified. Through case No. 1, the associated scenario cases are found in the business process scenario case library as secen No. 1, secen No. 2 and secen No. 3. The content of case No. 1 in each scenario case is modified synchronously (such as Figure 3a Indicated by dashed arrows).

[0070] like Figure 3b The figure shows a schematic diagram of modifying the corresponding data of a specific node in a preferred embodiment of the present invention, taking node A as an example. In the node library, the content of node A is modified. Through nodeNo1, the associated transaction chains are found to be chainNo1 and chainNo2 in the transaction chain branch library. The content of nodeNo1 in each transaction chain is modified synchronously (e.g. Figure 3bIndicated by dashed arrows).

[0071] like Figure 4a The diagram shows a preferred embodiment of the present invention deleting a specific basic case, taking case a1 as an example. In the basic case library, find the case caseNo1 and delete it; through caseNo1, find the binding relationship between the case and the node in the node library and delete it; through caseNo1, find the associated scenario cases secenNo1, secenNo2 and secenNo3 in the business process scenario case library and delete them. The above deletion operation will delete the associated relationship simultaneously, as shown in the figure, all the contents connected by dotted lines will be deleted.

[0072] like Figure 4b The figure shows a schematic diagram of deleting a specific node in a preferred embodiment of the present invention, taking node C as an example. In the node library, find the node nodeNo3 and delete it; through nodeNo3, query the associated transaction chain chainNo1 in the transaction chain branch library and delete it; through chainNo1, query the associated scenario cases secenNo1 and secenNo2 in the business process scenario case library and delete them. The above deletion operation will delete the association relationship simultaneously, as shown in the figure, all the contents connected by dotted lines will be deleted.

[0073] like Figure 4c The diagram shows a preferred embodiment of the present invention for deleting a specific transaction chain, taking the example of deleting the transaction chain A->B->C->B. In the transaction chain branch library, the transaction chain chainNo1 is found and deleted; through chainNo1, the associated scenario cases are found in the business process scenario case library as secenNo1 and secenNo2, which are deleted. The above deletion operation will delete the associated relationship simultaneously, as shown in the figure, all the contents connected by the dotted line will be deleted.

[0074] The above is only a preferred specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed by the present invention should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims

1. A scenario-level business process case chain generation and automatic update method, characterized in that: include: S1. Arrange and collect corresponding data of basic cases to form a basic case library, wherein the corresponding data of the basic cases include case ID, case name and case content; S2. Arrange the corresponding data of the set nodes to form a node library, wherein the corresponding data of the nodes include a node ID, a node name, and an association relationship between the node and a basic case, and the node is bound to one or more basic cases through the association relationship between the node and the basic case; S3. Arrange the corresponding data of the aggregated transaction chains to form a transaction chain branch library. The corresponding data of the transaction chains include the transaction chain ID, the transaction chain content, and the association relationship between the transaction chain and the nodes. The transaction chain determines all the nodes included in the transaction chain and the connection order between the nodes through the association relationship between the transaction chain and the nodes. S4. Arrange and collect the corresponding data of the scenario cases to form a scenario case library, wherein the corresponding data of the scenario cases include the scenario case ID, the scenario case content, the association relationship between the scenario case and the transaction chain, and the association relationship between the scenario case and the basic case. The scenario case determines the transaction chain applied to the scenario through the association relationship between the scenario case and the transaction chain, and the scenario case determines the basic case applied to the scenario through the association relationship between the scenario case and the basic case; S51, modifying the corresponding data of the basic case in the basic case library, and updating the scenario cases related to the basic case; S52, modifying the corresponding data of the node in the node library, and updating the transaction chain related to the node; S61. Delete the basic case in the basic case library, and delete the scenario cases related to the basic case; S62. Delete a node in the node library, and delete the transaction chain related to the node and the scenario cases related to the deleted transaction chain; S63. Delete the transaction chain in the transaction chain branch library, and delete the scenario cases related to the transaction chain at the same time; all the basic cases applied to the scenario belong to the basic cases bound to the nodes included in the transaction chain applied to the scenario; the association relationship between the scenario case and the basic case is obtained through the following steps: Determine the relevant transaction chain based on the relationship between the scenario case and the transaction chain; Determine the relevant nodes based on the association relationship between the relevant transaction chain and the nodes; Determine a valid basic case set based on the association relationship between the relevant nodes and the basic cases; Select basic cases related to the scenario cases from the valid basic case set, and determine the correlation between the scenario cases and the basic cases.

2. The method according to claim 1, characterized in that The scenario cases related to updating the basic case include: Determine the scenario case related to the base case based on the association relationship between the scenario case and the base case; Only the corresponding data of the basic case in the relevant scenario case is updated.

3. The method according to claim 1, characterized in that The transaction chain related to updating the node includes: Determine the transaction chain related to the node according to the association relationship between the transaction chain and the node; Only the corresponding data of the corresponding node in the relevant transaction chain is updated.

4. The method according to claim 1, characterized in that The scenario cases related to deleting the basic case include: Determine the scenario case related to the base case based on the association relationship between the scenario case and the base case; Delete the corresponding data of the relevant scenario cases; Determine the nodes related to the base case according to the association relationship between the nodes and the base case; Modify the association between a node and a base case, and delete the binding relationship between the related node and the base case.

5. The method according to claim 1, characterized in that The scenario cases of deleting the transaction chain related to the node and the deleted transaction chain include: Determine the transaction chain related to the node according to the association relationship between the transaction chain and the node; Delete the corresponding data of the relevant transaction chain; Determine the scenario cases related to the deleted transaction chain according to the association relationship between the scenario cases and the transaction chain; Delete the corresponding data of the relevant scenario cases.

6. The method according to claim 1, characterized in that The scenario cases related to deleting the transaction chain include: Determine the scenario cases related to the transaction chain based on the association between the scenario cases and the transaction chain; Delete the corresponding data of the relevant scenario cases.

7. A computer-readable storage medium, characterized in that: The storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.

8. An electronic device, characterized in that: including a processor and a memory; The memory is used to store the corresponding data of the basic case, the corresponding data of the node, the corresponding data of the transaction chain and the corresponding data of the scenario case; The processor is used to execute the method described in any one of claims 1 to 6 by calling the corresponding data of the basic case, the corresponding data of the node, the corresponding data of the transaction chain and the corresponding data of the scenario case.

Images