Process transaction test quality evaluation method, device and equipment
By arranging and combining the node categories and basic operations of process transactions, the expected scenarios are generated and the scenario coverage rate is calculated, and the problem of inability to accurately measure the scenario-level coverage rate and success rate of process transactions in the existing technology is solved, and the testing efficiency and accuracy.
Patent Information
- Application Number
- CN202411036969.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-31
- Publication Date
- 2024-11-22
AI Technical Summary
The existing technology cannot accurately measure the scenario-level coverage and success rate of process transactions, and cannot meet the needs of machine-controlled computing scenarios of process transactions, resulting in low testing efficiency.
By traversing the transactions of the process to be tested, obtaining the node categories and basic operations, performing arrangement and combination to generate the expected scene, calculating the number of scenes, and generating SQL query statements, counting the matching of the actual execution results and the expected scene table, calculating the scene coverage, and judging Test quality.
It realizes an accurate measurement of the scenario-level coverage and success rate of process-type transactions, improves testing efficiency, ensures comprehensiveness and accuracy of tests, and avoids the risk of omissions from manual analysis.
Smart Images

Figure CN119003344A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of data processing technology, and in particular to a method, device and equipment for evaluating the quality of process transaction testing. Background Art
[0002] At present, in the field of automated testing and data processing, the test quality and test risk assessment methods of process transactions in the financial industry are mainly used for the situation that many transaction processes in the banking and financial industry are long. Only manual feedback cannot guarantee the comprehensiveness of the project's scenario tests, and it is necessary to analyze and calculate scenarios and count scenario coverage through machine control. According to the characteristics of each node, the various scenarios that need to be tested for the transaction are automatically calculated, SQL statement assertions are set, and the transaction test scenario coverage and success rate are calculated by counting the execution traces in the system database table, and the validity of the test execution results is automatically judged; support risk warning settings, calculate according to the project cycle, and notify the relevant person in charge of the test details in the form of scheduled email alerts to ensure that they accurately judge the scenario coverage and test progress of the project and transaction, adjust the test strategy in time, and supplement the uncovered test scenarios of the transaction. At present, the existing technology uses logs to perform comprehensive testing, which can only detect transaction-level coverage and success rate, and cannot accurately measure the scenario-level coverage and success rate of process-type transactions; at the same time, the existing technology analyzes the code files and can only give test suggestions, but cannot accurately calculate the test scenarios and count the scenario coverage, nor can it meet the needs of process-type transaction machine-controlled computing scenarios.
[0003] There is an urgent need for a process transaction test quality assessment method to solve the problem of not being able to accurately measure the scenario-level coverage and success rate of process transactions, not being able to meet the needs of process transaction machine-controlled computing scenarios, and only being able to provide test suggestions, resulting in low test efficiency. Summary of the invention
[0004] In order to solve the problem that the existing technology cannot accurately measure the scenario-level coverage and success rate of process transactions, resulting in the inability to accurately calculate the test scenarios and statistical scenario coverage, the embodiments of this specification provide a method, device and equipment for evaluating the quality of process transaction testing, which can display all possible expected scenarios through permutations and combinations, and calculate the coverage of actual execution results, thereby accurately measuring the scenario-level coverage and success rate of process transactions, giving test suggestions and improving test efficiency.
[0005] In order to solve the above technical problems, the specific technical solutions of this specification are as follows:
[0006] On the one hand, an embodiment of the present specification provides a method for evaluating the quality of a process transaction test, including traversing the process transaction to be tested, obtaining the node category of the process transaction and the basic operation corresponding to each node;
[0007] Arrange and combine at least one node and its corresponding different basic operations to generate expected scenarios and calculate the number of the expected scenarios;
[0008] Generate SQL query statements corresponding to the expected scenarios one by one according to the expected scenarios, and generate an expected scenario table;
[0009] Matching the actual execution results with the SQL query statements in the expected scenario table is counted, and the scenario coverage of the actual execution results is calculated;
[0010] Whether the actual execution result is qualified is judged according to the scenario coverage, and a process transaction test quality assessment result is generated.
[0011] Furthermore, obtaining the node category of the process transaction and the basic operation corresponding to each node further includes:
[0012] The node category includes at least one of the following: acceptance posts, review posts, and accounting posts;
[0013] The basic operations include the operations required for each node. The acceptance position nodes at least include submit, terminate, and suspend; the review position nodes at least include submit and return; and the accounting position nodes at least include submit, return, and resubmit.
[0014] Furthermore, generating the expected scenarios and calculating the number of the expected scenarios further includes,
[0015] The formula for calculating the number of the expected scenarios is:
[0016] M=x a ×y b × c ,
[0017] Among them, a is the number of acceptance position nodes, b is the number of review position nodes, c is the number of accounting position nodes, x is the number of operations supported by acceptance positions, y is the number of operations supported by review positions, and z is the number of operations supported by accounting positions.
[0018] Furthermore, the actual execution result is:
[0019] The actual execution result is obtained by testing the transaction of the process to be tested.
[0020] Furthermore, matching with the SQL query statement in the expected scenario table further includes:
[0021] If the actual execution result matches at least one of the SQL query statements in the expected scenario table, it is recorded that the actual execution result covers the scenario corresponding to at least one of the expected execution results in the expected scenario table.
[0022] Furthermore, calculating the scenario coverage of the actual execution result further includes:
[0023] The SQL query statements are executed one by one according to the expected scenario table, and the number of transactions actually executed N is expressed as:
[0024] N=sum(n1:nM)
[0025] Wherein, 1<=i<=M, i is the expected scene number, and M is the expected scene number;
[0026] If N <= M, it means the test is not sufficient and a progress warning is issued;
[0027] If N>M, determine whether the transaction of the process to be tested has passed the test;
[0028] The number of actually executed scenarios in each transaction of the process to be tested is counted and recorded as ni;
[0029] If ni<m, the test fails and a progress warning is issued;
[0030] If ni>=m, the test passes, where m is the total number of nodes.
[0031] Furthermore, generating a process transaction test quality assessment result further includes:
[0032] The number of scenarios for which the actual execution results are counted is recorded as e;
[0033] Calculate the actual scene coverage α=e÷M,
[0034] The actual test execution days / test cycle is used as the expected scenario coverage.
[0035] If α is less than the expected scenario coverage, the process transaction test quality is unqualified and an early warning is issued;
[0036] If α is greater than the expected scenario coverage, the process transaction test quality is qualified.
[0037] Furthermore, generating a process transaction test quality assessment result further includes:
[0038] The actual number of transactions executed, transaction ratio, and test progress verification results of each process are returned to the front-end page, which is displayed to the tester in the form of a view;
[0039] If the actual scenario coverage is lower than the expected coverage, a progress warning will be issued via email, and the warning information will be returned to the front-end page.
[0040] On the other hand, the embodiment of this specification also provides a process transaction test quality evaluation device, including:
[0041] The node generation module is used to traverse the process transactions to be tested, obtain the node categories of the process transactions and the basic operations corresponding to each node;
[0042] A scenario generation module, used to arrange and combine at least one node and its corresponding different basic operations, generate expected scenarios and calculate the number of the expected scenarios;
[0043] A table generation module, used to generate SQL query statements corresponding to the expected scenarios one by one according to the expected scenarios, and generate an expected scenario table;
[0044] A coverage calculation module is used to count the actual execution results and match them with the SQL query statements in the expected scenario table, and calculate the scenario coverage of the actual execution results;
[0045] The result generation module is used to determine whether the actual execution result is qualified according to the scenario coverage and generate a process transaction test quality assessment result.
[0046] On the other hand, an embodiment of the present specification further provides a computer device, including a memory, a processor, and a computer program stored in the memory, and the processor implements the above method when executing the computer program.
[0047] Finally, the embodiments of this specification also provide a computer storage medium on which a computer program is stored. When the computer program is executed by a processor of a computer device, the above method is executed.
[0048] By using the embodiments of this specification, a test quality and test risk assessment method for process transactions in the industry is realized. In addition, in order to avoid the risk of omissions in the manual demand analysis in the prior art, the process transactions to be tested are traversed, each node in the process transactions is classified, and the basic operations corresponding to each node are counted according to the node category, so as to ensure that all scenarios that need to be tested in the process transactions can be automatically calculated according to the characteristics of the nodes; in order to ensure that all scenarios are obtained, it is necessary to arrange and combine the nodes and their corresponding different basic operations, so as to generate all possible expected scenarios and calculate the number of expected scenarios. At the same time, since many process transactions in the banking and financial industry are long, any The transaction processing is also relatively complex. By classifying the nodes and then arranging and combining them, the amount of calculation required to build the expected scenario can be effectively reduced; according to the expected scenario, an SQL query statement corresponding to the expected scenario is generated one by one, and an expected scenario table is generated by matching the expected scenario and the SQL query statement one by one, so as to achieve full coverage of the scenarios that may appear in the process transaction; the actual execution results obtained in the actual test are counted and then matched with the SQL query statement in the expected scenario table, so as to know which scenarios are covered in the actual execution results, so as to calculate the scenario coverage of the actual execution results, and judge whether the actual execution results are qualified according to the scenario coverage, and generate the process transaction test quality evaluation results. It realizes the automatic judgment of the validity of the test execution results, calculates the transaction test scenario coverage and success rate, improves the evaluation accuracy of the process transaction test, and solves the problem that omissions are easy to occur and the comprehensiveness of the test cannot be checked when facing a long process transaction in the prior art. BRIEF DESCRIPTION OF THE DRAWINGS
[0049] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0050] Figure 1 It is a schematic diagram of an implementation system of a method for evaluating the quality of a process transaction test according to an embodiment of this specification;
[0051] Figure 2 Shown is a flow chart of a method for evaluating process transaction test quality provided by an embodiment of this specification;
[0052] Figure 3 Shown is a schematic diagram of node categories for transaction processes in the embodiments of this specification;
[0053] Figure 4The figure shows the process of generating the quality assessment result of the process transaction test in the embodiment of this specification;
[0054] Figure 5 The figure shows a structural diagram of a process transaction test quality according to an embodiment of the present specification;
[0055] Figure 6 The figure shows a schematic diagram of the structure of a computer device according to an embodiment of the present specification.
[0056]
Description of reference numerals
[0057] 101. Terminal;
[0058] 102. Server;
[0059] 501. Node generation module;
[0060] 502. Scene generation module;
[0061] 503. Table generation module;
[0062] 504. Coverage calculation module;
[0063] 505. result generation module;
[0064] 602. Computer equipment;
[0065] 604. Processing equipment;
[0066] 606. Storage resources;
[0067] 608, driving mechanism;
[0068] 610, input / output module;
[0069] 612. Input devices;
[0070] 614. Output device;
[0071] 616. Presentation equipment;
[0072] 618. Graphical user interface;
[0073] 620, network interface;
[0074] 622, communication link;
[0075] 624. Communication bus. DETAILED DESCRIPTION
[0076] The following will be combined with the drawings in the embodiments of this specification to clearly and completely describe the technical solutions in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this specification.
[0077] It should be noted that the terms "first", "second", etc. in the description and claims of this specification 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 data used in this way can be interchanged where appropriate, so that the embodiments of this specification described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, device, product or equipment that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or equipment.
[0078] like Figure 1 The diagram shows a schematic diagram of the implementation system of a method for evaluating the quality of process transaction testing in an embodiment of the specification, which may include a terminal 101 and a server 102, wherein a communication connection is established between the terminal 101 and the server 102 to enable data interaction. The terminal 101 may send a process transaction to be tested to the server 102, which includes multiple different process transaction nodes, such as acceptance positions, review positions, etc., which may also include basic operations corresponding to multiple different positions, such as submission, termination, suspension, etc. Then the server 102 classifies the nodes in each process transaction to be tested, and then generates all possible expected scenarios according to the categories and different basic operations. And by matching with the actual execution results to calculate the coverage of the actual execution results, the actual execution results can be analyzed whether they are qualified, and the analysis results are sent to the terminal 101 for presentation, generating the results of the process transaction quality evaluation.
[0079] In the embodiments of this specification, the server 102 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDN, Content Delivery Network), and big data and artificial intelligence platforms.
[0080] In an optional embodiment, the terminal 101 may include but is not limited to a smart phone, a desktop computer, a tablet computer, and a laptop computer. Optionally, the operating system running on the electronic device may include but is not limited to Android system, IOS system, Linux, Windows, etc.
[0081] In addition, it should be noted that in practical applications, Figure 1 The application environment shown can be applied to relevant scenarios of process transactions in banking or other financial industries, and this specification does not limit it.
[0082] In order to solve the problems existing in the prior art, the embodiments of this specification provide a method, device, equipment and storage medium for evaluating the quality of process transaction testing. Figure 2 The flowchart of a method for evaluating the quality of a process transaction test provided by an embodiment of this specification is shown in this figure. The process of evaluating the quality of a process transaction test is described in this figure. The order of steps listed in the embodiment is only one way of executing the steps among many orders, and does not represent the only order of execution. When the actual system or device product is executed, it can be executed in the order or in parallel according to the method shown in the embodiment or the accompanying drawings. Specifically, Figure 2 As shown, the method may include:
[0083] Step 201: traverse the process transaction to be tested, obtain the node category of the process transaction and the basic operation corresponding to each node;
[0084] Step 202: performing permutations and combinations on at least one node and its corresponding different basic operations, generating expected scenarios and calculating the number of the expected scenarios;
[0085] Step 203: Generate SQL query statements corresponding to the expected scenarios one by one according to the expected scenarios, and generate an expected scenario table;
[0086] Step 204: Count the actual execution results and match them with the SQL query statements in the expected scenario table, and calculate the scenario coverage of the actual execution results;
[0087] Step 205: Determine whether the actual execution result is qualified according to the scenario coverage, and generate a process transaction test quality assessment result.
[0088] By using the embodiments of this specification, a test quality and test risk assessment method for process transactions in the industry is realized. In addition, in order to avoid the risk of omissions in the manual demand analysis in the prior art, the process transactions to be tested are traversed, each node in the process transactions is classified, and the basic operations corresponding to each node are counted according to the node category, so as to ensure that all scenarios that need to be tested in the process transactions can be automatically calculated according to the characteristics of the nodes; in order to ensure that all scenarios are obtained, it is necessary to arrange and combine the nodes and their corresponding different basic operations, so as to generate all possible expected scenarios and calculate the number of expected scenarios. At the same time, since many process transactions in the banking and financial industry are long, any The transaction processing is also relatively complex. By classifying the nodes and then arranging and combining them, the amount of calculation required to build the expected scenario can be effectively reduced; according to the expected scenario, an SQL query statement corresponding to the expected scenario is generated one by one, and an expected scenario table is generated by matching the expected scenario and the SQL query statement one by one, so as to achieve full coverage of the scenarios that may appear in the process transaction; the actual execution results obtained in the actual test are counted and then matched with the SQL query statement in the expected scenario table, so as to know which scenarios are covered in the actual execution results, so as to calculate the scenario coverage of the actual execution results, and judge whether the actual execution results are qualified according to the scenario coverage, and generate the process transaction test quality evaluation results. It realizes the automatic judgment of the validity of the test execution results, calculates the transaction test scenario coverage and success rate, improves the evaluation accuracy of the process transaction test, and solves the problem that omissions are easy to occur and the comprehensiveness of the test cannot be checked when facing a long process transaction in the prior art.
[0089] In the embodiments of the present specification, firstly, by scanning the log of the system server, with the dimensions of project, schedule and single transaction, that is, the process transactions that have appeared in the system, it is possible to obtain the nodes of all the process transactions that have appeared and the basic operations corresponding to each node, so as to arrange and combine each node and all the operations corresponding to each node to ensure that all possible expected scenarios can be listed, and then generate corresponding tables according to all the expected scenarios, match and verify the actual execution results according to the tables, and check whether all possible situations are covered in the actual execution results. If not, it means that there are omissions or errors in the testing process, thereby achieving the evaluation of the test quality of the process transactions, improving the accuracy of the test, and according to the evaluation results, the supplementary test of the missed scenarios can be easily completed, which greatly improves the efficiency of finding omissions and filling gaps and ensures the comprehensiveness of the testing of each scenario.
[0090] According to one embodiment of this specification, Figure 3 As shown, obtaining the node category of the process transaction and the basic operation corresponding to each node further includes:
[0091] The node category includes at least one of the following: acceptance posts, review posts, and accounting posts;
[0092] The basic operations include the operations required for each node. The acceptance position nodes at least include submit, terminate, and suspend; the review position nodes at least include submit and return; and the accounting position nodes at least include submit, return, and resubmit.
[0093] In the embodiments of the present specification, since many transaction processes in the banking and financial industry are relatively long, different nodes are classified according to positions, which may include positions for deciding whether to accept transactions, positions for reviewing transaction processes, positions for reviewing transaction data, positions for accounting transactions, printing positions, and other multiple nodes. For the convenience of calculation, the node categories can be exemplarily divided into at least one of the following: acceptance positions, review positions, and accounting positions, and each of the nodes will correspond to different basic operations, such as submission, return, re-drawing, suspension, termination, and other operations of each node. By summarizing and counting the process transactions to be tested, various basic operations that may appear in each node can be obtained. By matching them one by one, it can be obtained that the acceptance position nodes at least include submission, termination, suspension, and other operations; the review position nodes at least include submission, return, and other operations; and the accounting position nodes at least include submission, return, re-drawing, and other operations.
[0094] According to an embodiment of the present specification, in order to calculate all expected scenarios, all expected scenarios may be listed one by one. However, in order to improve the efficiency of the evaluation process, the number of the expected scenarios may be calculated by a formula. Specifically, according to an example of the present specification, generating the expected scenarios and calculating the number of the expected scenarios further includes:
[0095] The formula for calculating the number of the expected scenarios is:
[0096] M=x a ×y b × c ,
[0097] Among them, a is the number of acceptance position nodes, b is the number of review position nodes, c is the number of accounting position nodes, x is the number of operations supported by acceptance positions, y is the number of operations supported by review positions, and z is the number of operations supported by accounting positions.
[0098] In the embodiment of this specification, according to the basic operations supported by each type of position, such as the acceptance position supports submission, termination, suspension, etc., the review position supports submission, return, etc., and the accounting position supports submission, return, resubmission, etc., according to the permutation and combination formula M=x a ×yb × c Calculate the expected scenarios, for example, the acceptance post submits - the review passes - the accounting is successful, the acceptance post submits - the review is returned - the acceptance post is terminated, the acceptance post submits - the review passes - the accounting fails and is returned - the accounting post resubmits and other expected scenarios.
[0099] According to an embodiment of the present specification, in order to evaluate the test results of process transactions, it is necessary to first obtain the test results of the process transactions, and the actual execution results are:
[0100] The actual execution result is obtained by testing the transaction of the process to be tested.
[0101] In the embodiments of this specification, channels for obtaining actual execution results include the results obtained by testing the transaction of the process to be tested through the test system, or the execution results obtained when the tester tests a specific scenario. The obtained execution results are counted to generate the actual execution results.
[0102] In the embodiment of the present specification, in order to search for a matching expected scene in the expected scene table, it is necessary to match according to the SQL query statement in the expected scene table. Specifically, matching with the SQL query statement in the expected scene table further includes:
[0103] If the actual execution result matches at least one of the SQL query statements in the expected scenario table, it is recorded that the actual execution result covers the scenario corresponding to at least one of the expected execution results in the expected scenario table.
[0104] In an embodiment of the present specification, in the trace table generated during the actual execution process, the SQL is queried for the execution results one by one in order, all the actual execution scenarios generated during the test process are counted, and the actual execution scenarios are matched one by one with the SQL query statements; further, in the actual matching process, there may be a situation where an actual execution scenario can cover multiple SQL query statements. For example, in the actual execution process, the process transactions involved in the scenarios returned by the acceptance post and the review post may be the same. Therefore, this actual execution scenario can cover the test results of multiple expected scenarios. Because the SQL query statements and the expected scenarios are one-to-one corresponding, matching the actual execution results with the SQL query statements in the expected scenario table can determine which expected scenarios are covered by the actual execution results, and derive which expected scenarios have not been tested, thereby facilitating further testing by testers to ensure the comprehensiveness of the test, thereby solving the problem in the prior art that there is a risk of omissions in the manual demand analysis of process transactions.
[0105] In the embodiment of this specification, in order to determine whether the actual execution result covers enough expected scenarios, the scenario coverage rate can be calculated according to the SQL query statement and the number of actually executed transactions. The calculation of the scenario coverage rate of the actual execution result further includes:
[0106] The SQL query statements are executed one by one according to the expected scenario table, and the number of transactions actually executed N is expressed as:
[0107] N=sum(n1:nM)
[0108] Wherein, 1<=i<=M, i is the expected scene number, and M is the expected scene number;
[0109] If N <= M, it means the test is not sufficient and a progress warning is issued;
[0110] If N>M, determine whether the transaction of the process to be tested has passed the test;
[0111] The number of actually executed scenarios in each transaction of the process to be tested is counted and recorded as ni;
[0112] If ni<m, the test fails and a progress warning is issued;
[0113] If ni>=m, the test passes, where m is the total number of nodes.
[0114] Furthermore, generating the process transaction test quality assessment result further includes:
[0115] The number of scenarios for which the actual execution results are counted is recorded as e;
[0116] Calculate the actual scene coverage α=e÷M,
[0117] The actual test execution days / test cycle is used as the expected scenario coverage.
[0118] If α is less than the expected scenario coverage, the process transaction test quality is unqualified and an early warning is issued;
[0119] If α is greater than the expected scenario coverage, the process transaction test quality is qualified.
[0120] In the embodiments of this specification, in order to facilitate the tester to intuitively obtain the coverage of the actual execution results and the results of each actual execution, the evaluation results need to be presented to the tester, such as Figure 4 As shown, the generated process transaction test quality assessment results further include:
[0121] Step 401: The actual number of transactions executed, the transaction ratio, and the test progress verification result of each process transaction are returned to the front-end page, and the front-end page is displayed to the tester in the form of a view;
[0122] Step 402: If the actual scenario coverage is less than the expected coverage, a progress warning is issued via email, and the warning information is returned to the front-end page.
[0123] The embodiment of this specification also provides a process transaction test quality evaluation device, such as Figure 5 As shown, including,
[0124] The node generation module 501 is used to traverse the process transaction to be tested, obtain the node category of the process transaction and the basic operation corresponding to each node;
[0125] A scenario generation module 502, configured to perform permutations and combinations on at least one node and its corresponding different basic operations, generate an expected scenario and calculate the number of the expected scenarios;
[0126] A table generation module 503 is used to generate SQL query statements corresponding to the expected scenarios one by one according to the expected scenarios, and generate an expected scenario table;
[0127] A coverage calculation module 504 is used to count the actual execution results and match them with the SQL query statements in the expected scenario table, and calculate the scenario coverage of the actual execution results;
[0128] The result generation module 505 is used to determine whether the actual execution result is qualified according to the scenario coverage, and generate a process transaction test quality assessment result.
[0129] Since the principle of solving the problem by the above device is similar to that of the above method, the implementation of the above device can refer to the implementation of the above method, and the repeated parts will not be repeated.
[0130] like Figure 6The structure diagram of the computer device of the embodiment of the present invention is shown. The apparatus in this specification can be the computer device in this embodiment, and executes the method of the above-mentioned specification. The computer device 602 may include one or more processing devices 604, such as one or more central processing units (CPUs), and each processing unit may implement one or more hardware threads. The computer device 602 may also include any storage resource 606, which is used to store any kind of information such as code, settings, data, etc. Non-limitingly, for example, the storage resource 606 may include any one or more combinations of the following: any type of RAM, any type of ROM, flash memory device, hard disk, optical disk, etc. More generally, any storage resource can use any technology to store information. Further, any storage resource can provide volatile or non-volatile retention of information. Further, any storage resource can represent a fixed or removable component of the computer device 602. In one case, when the processing device 604 executes an associated instruction stored in any storage resource or a combination of storage resources, the computer device 602 can perform any operation of the associated instruction. The computer device 602 also includes one or more drive mechanisms 608 for interacting with any storage resources, such as a hard disk drive mechanism, an optical disk drive mechanism, and the like.
[0131] The computer device 602 may also include an input / output module 610 (I / O) for receiving various inputs (via input devices 612) and for providing various outputs (via output devices 614). A specific output mechanism may include a presentation device 616 and an associated graphical user interface (GUI) 618. In other embodiments, the input / output module 610 (I / O), input device 612, and output device 614 may not be included, and the computer device 602 may be used as a computer device in a network. The computer device 602 may also include one or more network interfaces 620 for exchanging data with other devices via one or more communication links 622. One or more communication buses 624 couple the components described above together.
[0132] The communication link 622 may be implemented in any manner, for example, through a local area network, a wide area network (e.g., the Internet), a point-to-point connection, etc., or any combination thereof. The communication link 622 may include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc. governed by any protocol or combination of protocols.
[0133] Corresponds to Figures 2 to 4 The method in the embodiment of the present specification 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 method described above are executed.
[0134] The embodiment of the present specification also provides a computer-readable instruction, wherein when the processor executes the instruction, the program therein causes the processor to execute the following Figures 2 to 4 The method shown.
[0135] It should be understood that in the various embodiments of this specification, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this specification.
[0136] It should also be understood that in the embodiments of this specification, the term "and / or" is only a description of the association relationship of the associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this specification generally indicates that the associated objects before and after are in an "or" relationship.
[0137] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed in this specification can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this specification.
[0138] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0139] In the several embodiments provided in this specification, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, or it can be an electrical, mechanical or other form of connection.
[0140] 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 embodiments of this specification.
[0141] In addition, each functional unit in each embodiment of this specification 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. The above integrated unit may be implemented in the form of hardware or in the form of software functional units.
[0142] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this specification is essentially or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable 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 this specification. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.
[0143] Specific embodiments are used in this specification to illustrate the principles and implementation methods of this specification. The description of the above embodiments is only used to help understand the methods and core ideas of this specification. At the same time, for those skilled in the art, according to the ideas of this specification, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on this specification.
Claims
1. A method for evaluating the quality of process transaction testing, characterized in that: The method comprises, Traverse the process transactions to be tested, obtain the node categories of the process transactions and the basic operations corresponding to each node; Arrange and combine at least one node and its corresponding different basic operations to generate expected scenarios and calculate the number of the expected scenarios; Generate SQL query statements corresponding to the expected scenarios one by one according to the expected scenarios, and generate an expected scenario table; Matching the actual execution results with the SQL query statements in the expected scenario table is counted, and the scenario coverage of the actual execution results is calculated; Whether the actual execution result is qualified is judged according to the scenario coverage, and a process transaction test quality assessment result is generated.
2. The process transaction test quality evaluation method according to claim 1, characterized in that: Obtaining the node category of the process transaction and the basic operations corresponding to each node further includes: The node category includes at least one of the following: acceptance posts, review posts, and accounting posts; The basic operations include the operations required for each node. The nodes of the acceptance type positions at least include submit, terminate, and suspend; the nodes of the review type positions at least include submit and return; and the nodes of the accounting type positions at least include submit, return, and resubmit.
3. The process transaction test quality evaluation method according to claim 1, characterized in that: Generating expected scenarios and calculating the number of the expected scenarios further includes, The formula for calculating the number of the expected scenarios is: M=x a ×y b ×z c , Among them, a is the number of acceptance position nodes, b is the number of review position nodes, c is the number of accounting position nodes, x is the number of operations supported by acceptance positions, y is the number of operations supported by review positions, and z is the number of operations supported by accounting positions.
4. The process transaction test quality evaluation method according to claim 1, characterized in that: The actual execution result is: The actual execution result is obtained by testing the transaction of the process to be tested.
5. The method for evaluating the quality of process transaction testing according to claim 4, characterized in that: Matching with the SQL query statement in the expected scenario table further includes, If the actual execution result matches at least one of the SQL query statements in the expected scenario table, it is recorded that the actual execution result covers the scenario corresponding to at least one of the expected execution results in the expected scenario table.
6. The process transaction test quality evaluation method according to claim 5, characterized in that: Calculating the scenario coverage of the actual execution result further includes: The SQL query statements are executed one by one according to the expected scenario table, and the number of transactions actually executed N is expressed as: N=sum(n1:nM) Wherein, 1<=i<=M, i is the expected scene number, and M is the expected scene number; If N <= M, it means the test is insufficient and a progress warning is issued; If N>M, determine whether the transaction of the process to be tested has passed the test; The number of actually executed scenarios in each transaction of the process to be tested is counted and recorded as ni; If ni<m, the test fails and a progress warning is issued; If ni>=m, the test passes, where m is the total number of nodes.
7. The process transaction test quality evaluation method according to claim 6, characterized in that: Generating process transaction test quality assessment results further includes, The number of scenarios for which the actual execution results are counted is recorded as e; Calculate the actual scene coverage α=e÷M, The actual test execution days / test cycle is used as the expected scenario coverage. If α is less than the expected scenario coverage, the process transaction test quality is unqualified and an early warning is issued; If α is greater than the expected scenario coverage, the process transaction test quality is qualified.
8. The process transaction test quality assessment method according to claim 1, characterized in that: Generating process transaction test quality assessment results further includes, The actual number of transactions executed, transaction ratio, and test progress verification results of each process are returned to the front-end page, which is displayed to the tester in the form of a view; If the actual scenario coverage is lower than the expected coverage, a progress warning will be issued via email, and the warning information will be returned to the front-end page.
9. A device for evaluating the quality of process transaction testing, characterized in that: include, The node generation module is used to traverse the process transactions to be tested, obtain the node categories of the process transactions and the basic operations corresponding to each node; A scenario generation module, used to arrange and combine at least one node and its corresponding different basic operations, generate expected scenarios and calculate the number of the expected scenarios; A table generation module, used to generate SQL query statements corresponding to the expected scenarios one by one according to the expected scenarios, and generate an expected scenario table; A coverage calculation module is used to count the actual execution results and match them with the SQL query statements in the expected scenario table, and calculate the scenario coverage of the actual execution results; The result generation module is used to determine whether the actual execution result is qualified according to the scenario coverage and generate a process transaction test quality assessment result.
10. A computer device comprising a memory, a processor, and a computer program stored in the memory, characterized in that: When the computer program is executed by the processor, the computer program executes the instructions of the method according to any one of claims 1 to 8.
11. A computer storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor of a computer device, the computer program executes the instructions of the method according to any one of claims 1 to 8.
