CN113297058B - A use case generation method, testing method, device and server - Google Patents
A use case generation method, testing method, device and server Download PDFInfo
- Publication number
- CN113297058B CN113297058B CN202010346540.0A CN202010346540A CN113297058B CN 113297058 B CN113297058 B CN 113297058B CN 202010346540 A CN202010346540 A CN 202010346540A CN 113297058 B CN113297058 B CN 113297058B
- Authority
- CN
- China
- Prior art keywords
- use case
- log chain
- log
- seed
- case
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Prevention of errors by analysis, debugging or testing of software
- G06F11/3668—Testing of software
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Prevention of errors by analysis, debugging or testing of software
- G06F11/3668—Testing of software
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the invention provides a use case generation method, a test method, a device and a server, wherein the method comprises the steps of obtaining seed use cases; the method comprises the steps of obtaining a seed use case, obtaining a derived use case of the seed use case based on the seed use case, determining a first log chain generated by executing a test on a service system by the seed use case and a second log chain generated by executing a test on the service system by the derived use case, comparing the first log chain with the second log chain, and determining a target use case from the derived use case according to a log chain comparison result. The embodiment of the invention can improve the use case generation efficiency and the comprehensiveness of executing the test on the service system.
Description
Technical Field
The embodiment of the invention relates to the technical field of testing, in particular to a use case generation method, a test device and a server.
Background
In order to ensure the operation of the service system, various types of tests need to be carried out on the service system based on use cases, and the use cases can be regarded as descriptions of test tasks and mainly comprise test input, test data, expected results and the like related to the test tasks.
The batch generation of use cases is a main method of use case generation, specifically, a plurality of derivative use cases can be derived from seed use cases on the basis of setting seed use cases, and further use cases useful for testing can be screened from the derivative use cases. At present, the above screening process is mainly implemented by manual screening, which makes the efficiency of use case generation extremely low, so how to provide a use case generation scheme to improve the use case generation efficiency becomes a problem to be solved by those skilled in the art.
Disclosure of Invention
In view of this, the embodiment of the invention provides a use case generating method, a test device and a server, so as to improve use case generating efficiency.
In order to achieve the above object, the embodiment of the present invention provides the following technical solutions:
In a first aspect, an embodiment of the present invention provides a method for generating a use case, including:
Acquiring seed cases;
Deriving a derived use case of the seed use case based on the seed use case;
determining a first log chain generated by executing a test on a service system by using the seed use case and a second log chain generated by executing the test on the service system by using the derivative use case;
Comparing the first log chain with the second log chain;
and determining a target use case from the derivative use cases according to the log chain comparison result.
In a second aspect, an embodiment of the present invention provides a testing method, including:
Acquiring seed cases;
Deriving a derived use case of the seed use case based on the seed use case;
determining a first log chain generated by executing a test on a service system by using the seed use case and a second log chain generated by executing the test on the service system by using the derivative use case;
Comparing the first log chain with the second log chain;
determining a target use case from the derivative use cases according to the log chain comparison result;
and executing the test on the service system by using the seed use case and the use case in the target use case.
In a third aspect, an embodiment of the present invention provides a use case generating apparatus, including:
The acquisition module is used for acquiring seed cases;
the deriving module is used for deriving the derived use cases of the seed use cases based on the seed use cases;
the log chain determining module is used for determining a first log chain generated by executing a test on the service system by using the seed use case and a second log chain generated by executing the test on the service system by using the derivative use case;
A comparison module for comparing the first log chain and the second log chain;
and the determining module is used for determining a target use case from the derivative use cases according to the log chain comparison result.
In a fourth aspect, embodiments of the present invention provide a server comprising at least one memory storing one or more computer-executable instructions and at least one processor invoking the one or more computer-executable instructions to perform a use case generation method as described above or to perform a test method as described above.
After the seed use case is obtained, the use case generation method provided by the embodiment of the invention can derive the derived use case of the seed use case based on the seed use case, and in order to supplement the test layer which cannot be covered by the seed use case when testing the service system, the embodiment of the invention needs to screen out the derived use case from target use cases which are different from the seed use case and can supplement the seed use case; in order to achieve the purpose, the embodiment of the invention can determine a first log chain generated by using a seed case to execute a test on a service system and determine a second log chain generated by using a derivative case to execute the test on the service system, so that the first log chain and the second log chain are compared to obtain a log chain comparison result, the log chain comparison result can reflect the difference between the seed case and the derivative case in the test layer when the seed case is executed on the service system, the difference can reflect the test layer which can be covered by the derivative case but not covered by the seed case, and the embodiment can determine the target case which is different from the seed case and can supplement the test layer which can not be covered by the seed case from the derivative case based on the difference reflected by the log chain comparison result, thereby realizing the automatic screening of the target case which is useful for the test from the derivative case and improving the comprehensiveness of the target case in executing the test on the service system. Therefore, the use case generation method provided by the embodiment of the invention can realize automatic screening of target use cases, improve use case generation efficiency and improve the comprehensiveness of executing test on the service system.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only embodiments of the present application, and that other drawings can be obtained according to the provided drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flowchart of a use case generation method provided in an embodiment of the present invention;
FIG. 2 is an exemplary diagram of determining derived examples provided by embodiments of the present invention;
FIG. 3 is a flowchart of determining a target use case from derived use cases according to an embodiment of the present invention;
FIG. 4 is another flow chart of determining a target use case from derived use cases according to an embodiment of the present invention;
FIG. 5 is a flowchart of a case screening based on a target case according to an embodiment of the present invention;
FIG. 6 is an exemplary diagram of a use case generation process provided by an embodiment of the present invention;
FIG. 7 is a block diagram of a use case generating device according to an embodiment of the present invention;
Fig. 8 is a block diagram of a server according to an embodiment of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
As is known from the background art, batch generation of use cases is a main way of use case generation, in the case of setting seed use cases, a plurality of derived use cases can be obtained by adjusting the use case parameters of the seed use cases (such as modifying, combining and other processing), but the derived use cases which are not useful for testing exist, such as the derived use cases have useless use cases which are repeated with the seed use cases or are the same as the testing layers of the seed use cases for testing the service system, so that the number of the use cases which cannot be covered by the seed use cases when testing the service system is enriched in order to supplement the testing layers of the seed use cases, the number of the use cases which are different from the seed use cases and are used for testing the service system in the plurality of testing layers is needed to be selected, and the target use cases which are different from the seed use cases can be supplemented are needed in the embodiment of the invention. However, the screening process is currently mainly implemented by manual screening, which results in low use case generation efficiency.
In order to solve the above problems, the embodiment of the invention provides an improved use case generation method, which realizes automatic screening of the derived use cases, reduces the workload of screening the derived use cases and improves the use case generation efficiency under the condition that the derived use cases are derived based on seed use cases.
In an optional implementation, an optional flow of the use case generating method provided by the embodiment of the present invention may be shown in fig. 1, where the flow may be executed by a server, and referring to fig. 1, the flow may include:
s11, obtaining seed cases.
Alternatively, the server may obtain a seed use case from the generated use cases, e.g., the seed use case is any of the generated use cases, or the seed use case is a use case selected from the generated use cases.
Alternatively, the seed use case may be a normal use case. The normal use case refers to a use case used for normal testing of the service system, the normal testing is used for testing the processing of the service system for the normal condition, whereas the abnormal use case refers to a use case used for abnormal testing of the service system, the abnormal testing is used for testing the processing of the service system for the abnormal condition, such as testing the response of the service system for the wrong operation and the wrong message.
S12, deriving the derivative use case of the seed use case based on the seed use case.
In an alternative implementation, the embodiment of the invention can be based on the seed use case, and the use case parameters of the seed use case are adjusted (such as mutation, combination and other treatments are performed), so that the derivative use case of the seed use case is derived, and one derivative use case can be derived by once adjusting the use case parameters of the seed use case.
Alternatively, the seed use case may include a test input of the seed use case, contents such as test data and an expected result, where the test input, the test data and the expected result have a plurality of use case parameters, and in one example of combining the use case parameters of the seed use case to obtain a derivative use case, assuming that the test input of the seed use case a has three parameters a, b and c, and a data type of each parameter is int/boolen/String, theoretically the parameters a, b and c may have a plurality of parameter combinations, and each use case corresponding to each parameter combination may be used as a derivative use case, where int is an identifier defining an integer type variable, boolen is a value stored by a boolean object or a value to be converted into a boolean value, and String represents a data type of a character String.
Of course, in the embodiment of the present invention, the use case parameters of the seed use case may be modified (i.e., mutated) to obtain a derivative use case, and in general, the use cases corresponding to different modified use case parameters may be used as different derivative use cases. In an alternative implementation, the embodiment of the invention can utilize a preset multi-factor model to modify the use case parameters of the seed use case to obtain a derived use case, the multi-factor model can be associated with a plurality of variation factors to modify the use case parameters of the seed use case, and as an example, referring to fig. 2, the embodiment of the invention can input the seed use case into the multi-factor model, so that the multi-factor model can carry out a plurality of different modifications on the use case parameters of the seed use case based on the associated plurality of variation factors to derive a plurality of derived use cases.
S13, determining a first log chain generated by executing testing on the service system by the seed use case and a second log chain generated by executing testing on the service system by the derivative use case.
The embodiment of the invention can respectively execute the test on the service system based on the seed use case and each derivative use case, and can understand that a plurality of execution nodes of the service system are involved in the execution process of one use case, and each execution node completes respective execution logic, so that the service system finally outputs the test result, and the test on the service system can be realized. In the execution process of use cases (such as seed use cases, derivative use cases and the like), the embodiment of the invention can collect the log information of the execution nodes of the service system related to the use case execution process, and link the log information according to the execution sequence of the execution nodes to obtain a log chain generated by the execution use cases.
It should be noted that a log chain may be understood as a sequential data chain including log information of the execution nodes. The embodiment of the invention can collect log information of the execution nodes of the service system related in the seed use case execution process when the seed use case is used for executing the test on the service system, and link the log information according to the execution sequence of the execution nodes, so as to obtain a first log chain generated by executing the test on the service system according to the seed use case, for example, the first log chain can be represented as [ debug, the execution node 1] = > [ debug, the execution node 2] = > [ wash, the execution node 3] = > [ error, the execution node 4], wherein the debug represents debugging, the wash represents warning, the error represents errors, the first log chain can record the execution node of the service system related in the seed use case execution process, and the log information of the execution nodes can be obtained, for example, the execution nodes represented by the first log chain are represented by the execution nodes 1,2, 3 and 4, the execution sequence of the execution nodes is represented by the execution nodes 1-execution nodes 2-3-4, the execution nodes are represented by the log information of the first log chain, and the log information of the first log chain can be further recorded by the log information of the execution nodes in the seed use case execution nodes, and the error information in the first log chain is recorded in the execution nodes in the seed use of the example.
Similarly, when the service system is tested by the derivative use case, the embodiment of the invention can collect the log information of the execution nodes of the service system related in the execution process of the derivative use case and link the log information according to the execution sequence of the execution nodes, thereby obtaining a second log chain generated by the execution test of the derivative use case on the service system. For the specific content of the second log chain, reference is made to the introduction of the first log chain, and details are not repeated here. It should be noted that, when a plurality of derivative cases are derived based on a seed case, the embodiment of the present invention may perform a test on the service system by using each derivative case, so as to generate a second log chain corresponding to each derivative case, and obtain a plurality of second log chains.
S14, comparing the first log chain with the second log chain.
The embodiment of the invention can compare the first log chain with the second log chain corresponding to each derivative case to obtain the log chain comparison result, and the log chain comparison result can reflect the difference between the seed case and the derivative case in the test layer when the test is executed on the service system, and particularly, the difference can reflect the test layer which can be covered by the derivative case but not covered by the seed case.
In an alternative implementation, the first log chain may include an execution order of the execution nodes of the service system related to the seed case execution process and log information of the execution nodes, and the second log chain may include an execution order of the execution nodes of the service system related to the derivative case execution process and log information of the execution nodes. By comparing the first log chain with the second log chain, whether the execution sequences of the execution nodes in the first log chain and the second log chain are the same or not can be obtained, and the results of whether the log information of the execution nodes in the first log chain and the second log chain are the same or not can be obtained, so that the difference of the seed use case and the derivative use case in the test layer when the test is executed on the service system is reflected.
S15, determining a target use case from the derivative use cases according to the log chain comparison result.
The log chain comparison result obtained in the step S14 can reflect the difference between the seed use case and the derived use case in the test layer when the test is performed on the service system, and the difference can embody the test layer which can be covered by the derived use case but cannot be covered by the seed use case. In an alternative implementation, the target use case, which is different from the seed use case and can supplement the test layer that cannot be covered by the seed use case, may include at least one case:
The method comprises the steps that a use case which accords with a first service scene of a service system tested by a seed use case and is not repeated with the seed use case is derived and used as a target use case; for convenience of explanation, the embodiment of the invention refers to a service scenario of a service system tested by a seed use case as a first service scenario, and needs to test the service system under different service scenarios when the service system is tested, and the embodiment of the invention uses the derivative use case as a target use case, so that the service system can be tested by using a target use case different from the seed use case under the condition that the service scenario of the service system tested by the seed use case accords with the first service scenario of the service system, enriches the number of usable use cases under the first service scenario, so that the target use case can supplement the test level of the seed use case which cannot be covered by the first service scenario, and can promote the test comprehensiveness of the service system;
The derivative case is used as a target case, and can cover an abnormal service scene which is not matched with the first service scene of the service system tested by the seed case, so that the derivative case is most likely to cover an abnormal condition ignored by a user, and the derivative case is used as the target case, so that the target case can supplement the abnormal test under the service scene which cannot be covered by the seed case, and the testing comprehensiveness of the service system can be improved.
After the seed use case is obtained, the use case generation method provided by the embodiment of the invention can derive the derived use case of the seed use case based on the seed use case, and in order to supplement the test layer which cannot be covered by the seed use case when testing the service system, the embodiment of the invention needs to screen out the derived use case from target use cases which are different from the seed use case and can supplement the seed use case; in order to achieve the purpose, the embodiment of the invention can determine a first log chain generated by using a seed case to execute a test on a service system and determine a second log chain generated by using a derivative case to execute the test on the service system, so that the first log chain and the second log chain are compared to obtain a log chain comparison result, the log chain comparison result can reflect the difference between the seed case and the derivative case in the test layer when the seed case is executed on the service system, the difference can reflect the test layer which can be covered by the derivative case but not covered by the seed case, and the embodiment can determine the target case which is different from the seed case and can supplement the test layer which can not be covered by the seed case from the derivative case based on the difference reflected by the log chain comparison result, thereby realizing the automatic screening of the target case which is useful for the test from the derivative case and improving the comprehensiveness of the target case in executing the test on the service system. Therefore, the use case generation method provided by the embodiment of the invention can realize automatic screening of target use cases, improve use case generation efficiency and improve the comprehensiveness of executing test on the service system.
In an alternative implementation, the target use case determined from the derived use cases may be a use case of the derived use case that matches the first business scenario of the business system tested by the seed use case and that does not overlap with the seed use case. In the embodiment of the present invention, taking an example that the log chain includes an execution order of the execution nodes of the service system related to the use case execution process and log information of the execution nodes (i.e., the first log chain may include an execution order of the execution nodes of the service system related to the seed use case execution process and log information of the execution nodes; the second log chain may include an execution order of the execution nodes of the service system related to the derivative use case execution process and log information of the execution nodes), fig. 3 shows an optional process for determining the target use case from the derivative use case, as shown in fig. 3, the process may include:
step S21, comparing whether the execution sequence of the execution nodes in the second log chain and the first log chain is the same, and whether the log information of the execution nodes in the second log chain and the first log chain is the same.
In the embodiment of the invention, whether the seed use case or the derivative use case is aimed at, the execution sequence of the execution node can embody the service logic sequence of the service system related to the use case execution process, for example, the execution sequence of the execution node in the first log chain can embody the service logic sequence of the service system related to the seed use case execution process. It should be noted that if the service logic sequence of the service system related to the execution process of the seed use case is consistent with the service logic sequence of the service system related to the execution process of the derivative use case, the seed use case is consistent with (e.g. identical to) the service scenario of the service system tested by the derivative use case, otherwise, if the service logic sequence of the service system related to the execution process of the seed use case is inconsistent with the service scenario of the service system tested by the derivative use case, the seed use case is inconsistent with the service scenario of the service system tested by the derivative use case. That is, by comparing whether the execution order of the execution nodes in the second log chain and the first log chain is the same, the embodiment of the invention can determine whether the service scenario of the service system tested by the derived case and the seed case is consistent, that is, the embodiment of the invention can determine whether the service scenario of the service system tested by the derived case is consistent with the first service scenario.
In order to confirm whether the derived case matches the service scenario of the service system tested by the seed case or not while comparing whether the derived case matches the service scenario of the service system tested by the seed case or not, in an alternative implementation, the embodiment of the invention may compare whether the log information of the execution node in the second log chain and the first log chain is the same, if the execution order of the execution node in the second log chain and the first log chain is the same, and the log information of the execution node is the same, the derived case and the seed case are repeated, otherwise, if the execution order of the execution node in the second log chain and the first log chain is the same, but the log information of the execution node is different, the derived case matches the service scenario of the service system tested by the seed case, but does not match the seed case, and the derived case may be a different seed case, and may supplement the seed case on the test layer which cannot be covered by the first service scenario.
In an alternative implementation, the log information of the execution node may include the number of times the execution node is called and error information (error), and the fact that the second log chain is different from the log information of the execution node in the first log chain may be that, for example, the number of times the execution node is called in the second log chain is different from the number of times the execution node is called in the first log chain, and/or that the log information of the second log chain has new error information compared with the log information of the first log chain, and that the log information of the second log chain has new error information compared with the log information of the first log chain may be understood as that the log information of the second log chain has additional new error information compared with the log information of the first log chain.
Step S22, if the execution order of the execution nodes in the second log chain is the same as that of the execution nodes in the first log chain, and the log information of the execution nodes in the second log chain is different from that of the execution nodes in the first log chain, taking the derivative use case corresponding to the second log chain as a target use case.
For any second log chain, if the execution order of the second log chain is the same as that of the execution nodes in the first log chain and the log information of the execution nodes in the second log chain is different from that of the execution nodes in the first log chain, the derivative use case corresponding to the second log chain can be considered as a target use case which accords with the first service scene of the service system tested by the seed use case and is not repeated by the seed use case.
Step S23, if the execution sequences of the execution nodes in the second log chain and the first log chain are the same, and the log information of the execution nodes in the second log chain and the first log chain are the same, repeating the derived use case corresponding to the second log chain with the seed use case, and deleting the derived use case corresponding to the second log chain.
For any second log chain, if the execution sequence of the second log chain is the same as that of the execution node in the first log chain, and the log information of the execution node in the second log chain is the same as that of the execution node in the first log chain, the derived use case corresponding to the second log chain is the use case repeated with the seed use case, the derived use case corresponding to the second log chain is not the target use case, and the derived use case corresponding to the second log chain can be deleted.
Based on the flow shown in fig. 3, the embodiment of the invention can screen out the target use cases which are consistent with the first service scene of the service system tested by the seed use cases and are not repeated by the seed use cases from a plurality of derivative use cases, thereby enriching the number of the use cases which can be used in the first service scene, realizing coverage on a plurality of test layers of the service system in the first service scene, improving the use case generation efficiency and improving the test comprehensiveness of the service system.
In a more specific optional implementation, the first service scenario of the service system which is screened from the derivative cases and tested by the seed case according to the embodiment of the invention, and the target case which is not repeated by the seed case can be a new normal case or an abnormal case which is matched with the first service scenario of the service system which is tested by the seed case. The method comprises the steps of obtaining a first service scene, obtaining a first service instance, obtaining a derivative use case, screening new normal use cases which are consistent with the first service scene from the derivative use cases, enriching the number of use cases which are normally tested on the service system in the first service scene, and thus covering normal tests of a plurality of layers which are related on the service system in the first service scene, screening abnormal use cases which are consistent with the first service scene from the derivative use cases, enriching the number of use cases which are normally tested on the service system in the first service scene, and thus covering abnormal tests of a plurality of layers which are related on the service system in the first service scene.
In a specific implementation, taking an example that log information in a log chain includes the called times and error information of an execution node, determining, from derived use cases, a new normal use case that matches a first service scenario of a service system tested by a seed use case may be:
And if the execution sequence of the execution nodes in the second log chain is the same as that of the execution nodes in the first log chain, and the log information of the second log chain has no new error information compared with the log information of the first log chain, when the called times of the execution nodes in the second log chain are different from those of the execution nodes in the first log chain, taking the derivative use case corresponding to the second log chain as the new normal use case of the first service scene.
It can be understood that the execution order of the execution nodes in the second log chain is the same as that of the execution nodes in the first log chain, so that the service scenario of the service system tested by the derivative case corresponding to the second log chain is consistent with the first service scenario of the service system tested by the seed case, the log information of the second log chain is compared with the log information of the first log chain, no new error information exists, so that the derivative case corresponding to the second log chain is a normal case, but the called times of the execution nodes in the second log chain are different from those of the execution nodes in the first log chain, so that the derivative case corresponding to the second log chain is not repeated with the seed case.
In an alternative implementation, an alternative implementation of determining, from the derived use cases, an abnormal use case that matches the first business scenario of the business system tested by the seed use case may be:
and if the execution sequence of the execution nodes in the second log chain is the same as that of the execution nodes in the first log chain and the log information of the second log chain has new error information compared with the log information of the first log chain, taking the derivative case corresponding to the second log chain as the abnormal case of the first business scene.
It can be understood that the execution sequence of the execution nodes in the second log chain is the same as that of the execution nodes in the first log chain, so that the service scene of the service system tested by the derivative case corresponding to the second log chain is identical to the first service scene of the service system tested by the seed case, the log information of the second log chain has new error information compared with the log information of the first log chain, so that the derivative case corresponding to the second log chain is an abnormal case, and the embodiment of the invention takes the derivative case corresponding to the second log chain as a target case, so that the number of abnormal cases of the first service scene can be enriched.
The embodiment of the invention can determine the difference between the seed use case and the derived use case in the test layer when the test is executed on the service system by comparing the first log chain with the second log chain, the difference can embody the test layer which can be covered by the derived use case but not covered by the seed use case, so the embodiment of the invention can determine the target use case which accords with the first service scene of the service system tested by the seed use case and is not repeated by the seed use case from the derived use case, the method and the system realize the enrichment of the number of the use cases in the first service scene, achieve the purpose of screening target use cases useful for testing from the derived use cases, reduce the workload of screening the derived use cases, improve the use case generation efficiency and promote the comprehensiveness of executing the test on the service system. Further, the selected target use case may be a new normal use case or an abnormal use case of the first service scenario.
In another alternative implementation, the target use case determined from the derived use case may be an abnormal use case that does not conform to the first business scenario of the business system tested by the seed use case. In an optional implementation, according to a log chain comparison result of the first log chain and the second log chain, the embodiment of the invention can determine a target use case which is not consistent with the first service scene and is an abnormal use case from the plurality of derivative use cases. The abnormal cases which are not matched with the first business scenario can cover the artificially ignored abnormal situations, so that the abnormal test under the business scenario which cannot be covered by the seed cases is supplemented.
Alternatively, taking the example that the log chain includes the execution order of the execution nodes and the log information of the execution nodes, fig. 4 shows another optional flow of determining the target use case from the derived use cases, as shown in fig. 4, the flow may include:
Step S31, comparing whether the execution sequence of the execution nodes in the second log chain and the first log chain is the same, and whether the log information of the second log chain has new error information compared with the log information of the first log chain.
Based on comparison of the execution sequence of the execution nodes of the second log chain and the first log chain, the embodiment of the invention can judge whether the service scene of the service system tested by the derivative case corresponding to the second log chain accords with the first service scene or not, and meanwhile, the embodiment of the invention can compare whether new error information exists in the log information of the second log chain compared with the log information of the first log chain or not so as to judge whether the derivative case corresponding to the second log chain is an abnormal case or not.
Step S32, if the execution order of the execution nodes in the second log chain is different from that of the execution nodes in the first log chain, and the log information of the second log chain has new error information compared with the log information of the first log chain, taking the derivative use case corresponding to the second log chain as the target use case.
For any second log chain, if the execution order of the execution nodes of the second log chain is different from that of the first log chain, the service scene of the service system tested by the derivative case corresponding to the second log chain is not consistent with the first service scene, and further, if new error information exists in the log information of the second log chain compared with the log information of the first log chain, the derivative case corresponding to the second log chain is an abnormal case compared with the seed case, so that the embodiment of the invention can determine the abnormal case inconsistent with the first service scene from the derivative cases.
Step S33, if the execution order of the execution nodes in the second log chain is different from that of the execution nodes in the first log chain, and the log information of the second log chain has no new error information compared with the log information of the first log chain, deleting the derivative case corresponding to the second log chain.
The embodiment of the invention can screen the abnormal use cases which are inconsistent with the first service scene of the seed use case test service system from the derivative use cases, supplement the abnormal test under the service scene which cannot be covered by the seed use case, and enrich the abnormal use cases for testing the service system.
In an alternative implementation, the embodiment of the invention can also support the manual screening of the target use cases based on the target use cases determined from a plurality of derivative use cases, so that the finally screened use cases are obtained. Alternatively, fig. 5 shows a flow of artificial filtering of use cases based on target use cases, and reference may be made to:
and S40, performing de-duplication on the target use case.
And S41, marking the example attribute of the target example after the duplication removal, and displaying.
And step S42, screening the displayed use cases to determine the finally screened use cases.
The number of target cases screened from the derived cases may be plural, where there may be duplicate cases, the embodiment of the invention can remove the weight of the target use cases screened from the derivative use cases, and ensure that the target use cases after the weight removal are not repeated.
The target use case can have use case attributes which are consistent with the first service scene of the seed use case test service system, are inconsistent with the first service scene, are normal use cases, are abnormal use cases and the like, and for the target use case determined from the derivative use cases, the embodiment of the invention can determine the use case attribute corresponding to the target use case, so that the target use case after the duplication removal is marked and displayed, and based on the displayed target use case with the use case attribute, the embodiment of the invention can determine the finally screened use case based on the screening operation of a user.
Optionally, in the case of deriving multiple derived cases based on seed cases by using a multi-factor model, for the target cases after duplication removal, the embodiment of the invention can also store the cases after duplication removal in a case library, so that the embodiment of the invention can update the model parameters of the multi-factor model based on the cases in the case library, thereby enabling the derived cases derived based on the multi-factor model to be more accurate.
As an alternative implementation, fig. 6 shows an example of a use case generation procedure provided by an embodiment of the present invention, and referring to fig. 6:
after determining the seed use case, the embodiment of the invention can utilize a multi-factor model to derive a plurality of derived use cases based on the seed use case;
meanwhile, aiming at the seed use case, the embodiment of the invention can carry out test on the service system by the seed use case, thereby collecting the log information of the execution nodes of the service system involved in the execution process of the seed use case and linking the log information into a first log chain according to the execution sequence of the execution nodes;
Furthermore, the embodiment of the invention can compare the first log chain with the second log chain, and determine a target use case from derived use cases based on a preset metamorphic relation rule, for example, the target use case is a use case which accords with the first service scene of the seed use case test service system and is not repeated with the seed use case, and/or the target use case is an abnormal use case which does not accord with the first service scene of the seed use case test service system, etc., and it is to be noted that the metamorphic relation rule can be defined by determining a rule of the target use case which accords with the first service scene of the seed use case test service system and is not repeated with the seed use case from the derived use case, and/or determining a rule of the abnormal use case which does not accord with the first service scene from the derived use case, and the preset metamorphic relation rule can refer to description of the corresponding part of the foregoing, and is not repeated here;
The determined target use cases can be saved in a use case library after being de-duplicated, and model parameters of the multi-factor model can be updated based on the use cases in the use case library.
Optionally, after the target use case is de-duplicated, the embodiment of the invention can also mark the use case attribute of the target use case and display the use case attribute, so that based on the screening of the displayed use case by a user, the embodiment of the invention can determine the finally screened use case from the displayed use case. Of course, as an alternative implementation, the embodiment of the present invention may also directly use the target use case as the use case obtained by final screening after the target use case is deduplicated.
In an alternative application example, in conjunction with the flow shown in fig. 3 and fig. 4, taking the first service scenario of the seed case test service system as an example of testing the first function opening of the service system (the first function may be a specific function of the service system, or may be any function, for example, the first function is a user comment function of the service system, etc., which is not limited in this embodiment of the present invention), after deriving a plurality of derived cases based on the seed case, the embodiment of the present invention may determine a first log chain generated by performing the test of opening the first function on the service system with the seed case, and determine a second log chain generated by performing the test on the service system with the derived case.
As an alternative implementation of determining a target use case, after comparing a first log chain and a second log chain, if a service scenario of a service system tested by a derivative use case corresponding to the second log chain is a first service scenario and the derivative use case is not repeated with a seed use case, the embodiment of the invention can take the derivative use case as the target use case;
In a more specific implementation, if the service scenario of the service system tested by the derivative case is also that the first function of the test service system is started, if the log information of the second log chain has no new error information compared with the log information of the first log chain, and the called times of the execution nodes in the second log chain are different from the called times of the execution nodes in the first log chain, the embodiment of the invention can use the derivative case as a new normal case for starting the first function of the test service system, and if the service scenario of the service system tested by the derivative case is that the first function of the test service system is started, the embodiment of the invention can use the derivative case as an abnormal case for starting the first function of the test service system if the log information of the second log chain has new error information compared with the log information of the first log chain.
In another optional implementation of determining the target use case, after comparing the first log chain and the second log chain, if the service scenario of the service system tested by the derived use case corresponding to the second log chain is not the first service scenario and the derived use case is an abnormal use case, the embodiment of the present invention may use the derived use case as the target use case, in one example, if the service scenario of the service system tested by the derived use case is the first function shutdown of the tested service system, it is explained that the service scenario of the service system tested by the derived use case is inconsistent with the first service scenario, and in this case, if the log information of the second log chain has new error information compared with the log information of the first log chain, the derived use case may be used as the abnormal use case of the first function shutdown of the tested service system.
In an alternative implementation, the embodiment of the invention further provides a testing method, after determining the target case based on, for example, the flow shown in fig. 1, the embodiment of the invention uses the seed case and the cases in the target case to perform testing on the service system, it can be understood that the seed case and the target case can be regarded as useful cases for performing testing on the service system, in an alternative implementation, the embodiment of the invention can store the seed case and the target case in a test case set, thereby performing testing on the service system based on the cases in the test case set, and since the target case can cover the test layer that the seed case cannot cover, a test case set is formed based on the seed case and the target case, the test is performed on the service system by the cases in the test case set, and the test comprehensiveness of the service system can be improved.
The description of the use case generating device provided by the embodiment of the present invention is presented below, and the use case generating device described below may be regarded as a functional module required to be set by a server to implement the use case generating method provided by the embodiment of the present invention. The contents of the case generating apparatus described below may be referred to in correspondence with the contents of the case generating method described above.
In an alternative implementation, fig. 7 shows an alternative block diagram of a use case generating apparatus provided by an embodiment of the present invention, where the apparatus may include:
An obtaining module 100, configured to obtain a seed use case;
A deriving module 110, configured to derive a derived use case of the seed use case based on the seed use case;
The log chain determining module 120 is configured to determine a first log chain generated by performing a test on a service system with the seed use case, and a second log chain generated by performing a test on the service system with the derivative use case;
A comparison module 130 for comparing the first log chain and the second log chain;
And the determining module 140 is configured to determine a target use case from the derived use cases according to the log chain comparison result.
Optionally, the determining module 140, configured to determine, according to the log chain comparison result, a target use case from the derived use cases may include:
and determining a target use case which accords with the first service scene of the service system tested by the seed use case and is not repeated with the seed use case from the derivative use cases according to the log chain comparison result.
Optionally, the log chain may include an execution sequence of an execution node of the service system related to the seed use case or the derivative use case execution process and log information of the execution node, and the comparison module 130 may include:
Comparing whether the execution sequence of the execution nodes in the second log chain and the first log chain is the same, and whether the log information of the execution nodes in the second log chain and the first log chain is the same.
Optionally, the determining module 140, configured to determine, from the derived use cases, a target use case that matches the first service scenario of the service system tested by the seed use case and is not repeated by the seed use case according to the log chain comparison result, may include:
if the execution sequence of the execution nodes in the second log chain is the same as that of the execution nodes in the first log chain and the log information of the execution nodes in the second log chain is different from that of the execution nodes in the first log chain, taking a derivative use case corresponding to the second log chain as a target use case;
And if the execution sequence of the execution nodes in the second log chain is the same as that of the execution nodes in the first log chain, and the log information of the execution nodes in the second log chain is the same as that of the execution nodes in the first log chain, repeating the derivative use cases corresponding to the second log chain with the seed use cases, and deleting the derivative use cases corresponding to the second log chain.
Optionally, in an aspect, the determining module 140, configured to, if the execution order of the execution nodes in the second log chain and the first log chain is the same and the log information of the execution nodes in the second log chain and the first log chain is different, take a derivative case corresponding to the second log chain as a target case, may include:
and if the execution sequence of the execution nodes in the second log chain is the same as that of the execution nodes in the first log chain, and the log information of the second log chain has no new error information compared with the log information of the first log chain, taking the derivative case corresponding to the second log chain as the new normal case of the first service scene when the called times of the execution nodes in the second log chain are different from those of the execution nodes in the first log chain.
Optionally, on the other hand, the determining module 140, configured to, if the execution order of the execution nodes in the second log chain and the first log chain is the same and the log information of the execution nodes in the second log chain and the first log chain is different, take a derivative case corresponding to the second log chain as a target case, may include:
and if the execution sequence of the execution nodes in the second log chain is the same as that of the execution nodes in the first log chain and the log information of the second log chain has new error information compared with the log information of the first log chain, taking the derivative case corresponding to the second log chain as the abnormal case of the first business scene.
In another optional implementation, the determining module 140, configured to determine, according to the log chain comparison result, a target use case from the derived use cases may include:
And according to the log chain comparison result, determining a target use case which is inconsistent with the first service scene of the service system tested by the seed use case and has new error information in the log information of the second log chain compared with the log information of the first log chain from the derivative use cases.
Optionally, the determining module 140, configured to determine, from the derivative use cases, a target use case that is inconsistent with the first service scenario of the service system tested by the seed use case and has new error information in the log information of the second log chain compared with the log information of the first log chain according to the log chain comparison result, may include:
If the execution order of the execution nodes in the second log chain is different from that of the execution nodes in the first log chain, and new error information exists in the log information of the second log chain compared with that of the first log chain, taking a derivative use case corresponding to the second log chain as a target use case;
and if the execution sequence of the execution nodes in the second log chain is different from that of the execution nodes in the first log chain, and the log information of the second log chain has no new error information compared with the log information of the first log chain, deleting the derivative case corresponding to the second log chain.
Optionally, the use case generating device provided by the embodiment of the present invention may be further used for:
The method comprises the steps of carrying out weight removal on the target use cases, marking the use case attribute of the target use cases after weight removal, carrying out display, screening the displayed use cases, and determining the finally screened use cases.
Optionally, further, the deriving module 110, configured to derive the derived use case of the seed use case based on the seed use case, may include:
based on the seed use case, modifying the use case parameters of the seed use case by using a preset multi-factor model to obtain a derived use case;
after the target use case is de-duplicated, the use case generating device provided by the embodiment of the invention can be further used for:
And updating the model parameters of the multi-factor model according to the use cases in the use case library, and storing the target use cases after the duplication removal by the seed use cases.
The embodiment of the invention also provides a testing device which can execute the test on the service system by using the seed use case and the use case in the target use case after the use case generating device determines the target use case.
The embodiment of the invention can determine a first log chain generated by using the seed case to perform testing on a service system and a second log chain generated by using the derivative case to perform testing on the service system, thereby comparing the first log chain with the second log chain to obtain a log chain comparison result, and the log chain comparison result can reflect the difference of the test level of the seed case and the derivative case when the service system is tested, the difference can reflect the test level of the seed case which can be covered but the seed case can not be covered, so that the embodiment of the invention can determine the first log chain generated by using the seed case to perform testing on the service system and the second log chain generated by using the derivative case to perform testing on the service system, thereby automatically improving the target of the seed case which can not be covered and the target of the seed case can not be used to perform testing on the service system. Therefore, the use case generation method provided by the embodiment of the invention can realize automatic screening of target use cases, improve use case generation efficiency and improve the comprehensiveness of executing test on the service system.
The embodiment of the invention also provides a server which can realize the use case generation method provided by the embodiment of the invention through loading the use case generation device in a program form. In an alternative implementation, fig. 8 shows an alternative block diagram of a server provided by an embodiment of the invention, which may comprise, with reference to fig. 8, at least one processor 1, at least one communication interface 2, at least one memory 3 and at least one communication bus 4;
in the embodiment of the invention, the number of the processor 1, the communication interface 2, the memory 3 and the communication bus 4 is at least one, and the processor 1, the communication interface 2 and the memory 3 complete the communication with each other through the communication bus 4;
alternatively, the communication interface 2 may be an interface of a communication module for performing network communication;
Alternatively, the processor 1 may be a CPU (central processing unit), GPU (Graphics Processing Unit, graphics processor), NPU (embedded neural network processor), FPGA (Field Programmable GATE ARRAY ), TPU (tensor processing unit), AI chip, application-specific ASIC (Application SPECIFIC INTEGRATED Circuit), or one or more integrated circuits configured to implement embodiments of the present invention, or the like.
The memory 3 may comprise a high-speed RAM memory or may further comprise a non-volatile memory, such as at least one disk memory.
The memory 3 stores one or more computer executable instructions, and the processor 1 invokes the one or more computer executable instructions to execute the use case generating method provided by the embodiment of the present invention.
Optionally, in the server provided by the embodiment of the present invention, the memory may also store one or more computer executable instructions for performing the test method provided by the embodiment of the present invention, so that the processor may call the one or more computer executable instructions to perform the test method provided by the embodiment of the present invention.
The embodiment of the invention also provides a storage medium, which can store one or more computer executable instructions, wherein the one or more computer executable instructions are used for executing the use case generation method provided by the embodiment of the invention or the test method provided by the embodiment of the invention.
The foregoing describes several embodiments of the present invention, and the various alternatives presented by the various embodiments may be combined, cross-referenced, with each other without conflict, extending beyond what is possible embodiments, all of which are considered to be embodiments of the present invention disclosed and disclosed.
Although the embodiments of the present invention are disclosed above, the present invention is not limited thereto. Various changes and modifications may be made by one skilled in the art without departing from the spirit and scope of the invention, and the scope of the invention should be assessed accordingly to that of the appended claims.
Claims (13)
1. A use case generation method comprises the following steps:
Acquiring seed cases;
Deriving a derived use case of the seed use case based on the seed use case, wherein the derived use case is obtained by adjusting use case parameters of the seed use case based on the seed use case;
determining a first log chain generated by executing a test on a service system by using the seed use case and a second log chain generated by executing the test on the service system by using the derivative use case;
comparing the first log chain with the second log chain comprises the steps of comparing whether the execution sequence of the execution nodes in the second log chain with the execution sequence of the execution nodes in the first log chain are the same, and comparing whether the log information of the execution nodes in the second log chain with the log information of the execution nodes in the first log chain are the same;
And determining a target use case from the derived use cases according to the log chain comparison result, wherein the target use case is a use case which is determined from the derived use cases, is different from the seed use case and supplements a test layer which cannot be covered by the seed use case.
2. The use case generating method of claim 1, wherein the determining the target use case from the derived use cases according to the log chain comparison result comprises:
and determining a target use case which accords with the first service scene of the service system tested by the seed use case and is not repeated with the seed use case from the derivative use cases according to the log chain comparison result.
3. The use case generating method according to claim 2, wherein the log chain comprises the execution sequence of the execution nodes of the business system related to the seed use case or derivative use case execution process and log information of the execution nodes.
4. The use case generating method according to claim 3, wherein the determining, from the derived use cases, a target use case that matches the first service scenario of the service system tested by the seed use case and is not repeated by the seed use case according to the log chain comparison result includes:
if the execution sequence of the execution nodes in the second log chain is the same as that of the execution nodes in the first log chain and the log information of the execution nodes in the second log chain is different from that of the execution nodes in the first log chain, taking a derivative use case corresponding to the second log chain as a target use case;
And if the execution sequence of the execution nodes in the second log chain is the same as that of the execution nodes in the first log chain, and the log information of the execution nodes in the second log chain is the same as that of the execution nodes in the first log chain, repeating the derivative use cases corresponding to the second log chain with the seed use cases, and deleting the derivative use cases corresponding to the second log chain.
5. The use case generating method according to claim 4, wherein if the execution order of the execution nodes in the second log chain and the first log chain is the same and the log information of the execution nodes in the second log chain and the first log chain is different, the use case generating method includes, as the target use case, the derivative use case corresponding to the second log chain:
and if the execution sequence of the execution nodes in the second log chain is the same as that of the execution nodes in the first log chain, and the log information of the second log chain has no new error information compared with the log information of the first log chain, taking the derivative case corresponding to the second log chain as the new normal case of the first service scene when the called times of the execution nodes in the second log chain are different from those of the execution nodes in the first log chain.
6. The use case generating method according to claim 4, wherein if the execution order of the execution nodes in the second log chain and the first log chain is the same and the log information of the execution nodes in the second log chain and the first log chain is different, the use case generating method includes, as the target use case, the derivative use case corresponding to the second log chain:
and if the execution sequence of the execution nodes in the second log chain is the same as that of the execution nodes in the first log chain and the log information of the second log chain has new error information compared with the log information of the first log chain, taking the derivative case corresponding to the second log chain as the abnormal case of the first business scene.
7. The use case generating method according to claim 1, wherein the determining the target use case from the derived use cases according to the log chain comparison result includes:
And according to the log chain comparison result, determining a target use case which is inconsistent with the first service scene of the service system tested by the seed use case and has new error information in the log information of the second log chain compared with the log information of the first log chain from the derivative use cases.
8. The use case generating method according to claim 7, wherein the determining, from the derived use cases, a target use case that is inconsistent with the first service scenario of the service system tested by the seed use case and has new error information in the log information of the second log chain compared with the log information of the first log chain according to the log chain comparison result comprises:
If the execution order of the execution nodes in the second log chain is different from that of the execution nodes in the first log chain, and new error information exists in the log information of the second log chain compared with that of the first log chain, taking a derivative use case corresponding to the second log chain as a target use case;
and if the execution sequence of the execution nodes in the second log chain is different from that of the execution nodes in the first log chain, and the log information of the second log chain has no new error information compared with the log information of the first log chain, deleting the derivative case corresponding to the second log chain.
9. The use case generating method according to any one of claims 1 to 8, further comprising:
Performing de-duplication on the target use case;
marking the example attribute of the target example after the duplication removal and displaying the example attribute;
And screening the displayed use cases to determine the final screened use cases.
10. The use case generating method according to claim 9, wherein the deriving the derived use case of the seed use case based on the seed use case comprises:
based on the seed use case, modifying the use case parameters of the seed use case by using a preset multi-factor model to obtain a derived use case;
The method further comprises the steps of:
And updating the model parameters of the multi-factor model according to the use cases in the use case library, and storing the target use cases after the duplication removal by the seed use cases.
11. A method of testing, comprising:
Acquiring seed cases;
Deriving a derived use case of the seed use case based on the seed use case, wherein the derived use case is obtained by adjusting use case parameters of the seed use case based on the seed use case;
determining a first log chain generated by executing a test on a service system by using the seed use case and a second log chain generated by executing the test on the service system by using the derivative use case;
comparing the first log chain with the second log chain comprises the steps of comparing whether the execution sequence of the execution nodes in the second log chain with the execution sequence of the execution nodes in the first log chain are the same, and comparing whether the log information of the execution nodes in the second log chain with the log information of the execution nodes in the first log chain are the same;
Determining a target use case from the derived use cases according to log chain comparison results, wherein the target use case is a use case which is determined from the derived use cases, is different from the seed use case and supplements a test layer which cannot be covered by the seed use case;
and executing the test on the service system by using the seed use case and the use case in the target use case.
12. A use case generating apparatus, comprising:
The acquisition module is used for acquiring seed cases;
The deriving module is used for deriving a derived use case of the seed use case based on the seed use case, wherein the derived use case is obtained by adjusting use case parameters of the seed use case based on the seed use case;
the log chain determining module is used for determining a first log chain generated by executing a test on the service system by using the seed use case and a second log chain generated by executing the test on the service system by using the derivative use case;
The comparison module is used for comparing whether the execution sequence of the execution nodes in the first log chain and the second log chain is the same or not, and whether the log information of the execution nodes in the second log chain and the first log chain is the same or not;
And the determining module is used for determining a target use case from the derived use cases according to the log chain comparison result, wherein the target use case is a use case which is determined from the derived use cases, is different from the seed use case and supplements a test layer which cannot be covered by the seed use case.
13. A server comprising at least one memory storing one or more computer-executable instructions and at least one processor invoking the one or more computer-executable instructions to perform the use case generation method of any of claims 1-10 or to perform the test method of claim 11.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010346540.0A CN113297058B (en) | 2020-04-27 | 2020-04-27 | A use case generation method, testing method, device and server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010346540.0A CN113297058B (en) | 2020-04-27 | 2020-04-27 | A use case generation method, testing method, device and server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113297058A CN113297058A (en) | 2021-08-24 |
| CN113297058B true CN113297058B (en) | 2024-12-24 |
Family
ID=77318057
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010346540.0A Active CN113297058B (en) | 2020-04-27 | 2020-04-27 | A use case generation method, testing method, device and server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113297058B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113297063B (en) * | 2020-06-05 | 2024-11-05 | 阿里巴巴集团控股有限公司 | A use case generation method, device, server and storage medium |
| CN115617682A (en) * | 2022-10-29 | 2023-01-17 | 重庆长安汽车股份有限公司 | Test case design method, device, equipment and medium for autonomous driving scenarios |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113297063A (en) * | 2020-06-05 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Use case generation method and device, server and storage medium |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9898387B2 (en) * | 2014-03-21 | 2018-02-20 | Ca, Inc. | Development tools for logging and analyzing software bugs |
| CN109460349B (en) * | 2018-09-19 | 2021-09-21 | 武汉达梦数据库股份有限公司 | Test case generation method and device based on log |
| CN110221965B (en) * | 2019-05-09 | 2023-01-20 | 创新先进技术有限公司 | Test case generation method, test case generation device, test case testing method, test case testing device, test equipment and test system |
| CN110175120B (en) * | 2019-05-20 | 2020-11-27 | 北京理工大学 | A Reinforcement Learning-Based Fuzzy Test Case Adaptive Mutation Method and Device |
| CN110727597B (en) * | 2019-10-15 | 2023-03-10 | 杭州安恒信息技术股份有限公司 | A method for troubleshooting invalid code completion use cases based on logs |
-
2020
- 2020-04-27 CN CN202010346540.0A patent/CN113297058B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113297063A (en) * | 2020-06-05 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Use case generation method and device, server and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113297058A (en) | 2021-08-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112286779B (en) | Test task processing method and device, storage medium and computer equipment | |
| US7917895B2 (en) | Automated software testing and validation system | |
| US7493522B2 (en) | Model independent input reduction | |
| CN110737584A (en) | Service data testing method and device based on block chain and computer equipment | |
| CN103473076B (en) | The dissemination method of a kind of code release and system | |
| CN109032850B (en) | On-site device debugging system and on-site device debugging method | |
| CN111158656B (en) | Test code generation method and device based on fruit tree method | |
| US11481440B2 (en) | System and method for processing metadata to determine an object sequence | |
| CN107080945B (en) | Method and device for testing artificial intelligence behaviors in game and electronic equipment | |
| CN107729227A (en) | Application testing range determining method, system, server and storage medium | |
| CN108595342A (en) | Unit test method and device | |
| CN113590454B (en) | Test method, device, computer equipment and storage medium | |
| CN107741903A (en) | Application compatibility method of testing, device, computer equipment and storage medium | |
| CN109753289B (en) | Art resource merging method and device, electronic equipment and storage medium | |
| WO2018145559A1 (en) | Method and system for generating continuous integration pipeline | |
| CN113297058B (en) | A use case generation method, testing method, device and server | |
| CN111708712A (en) | User behavior test case generation method, flow playback method and electronic equipment | |
| CN108459951A (en) | test method and device | |
| JP2010128583A (en) | Test-facilitating design apparatus, its method and program | |
| CN115176233B (en) | Performing tests in deterministic order | |
| CN113792026A (en) | Deployment method and device of database script and computer readable storage medium | |
| US11663113B2 (en) | Real time fault localization using combinatorial test design techniques and test case priority selection | |
| CN112395199B (en) | Distributed software instance testing method and software development platform based on cloud computing | |
| CN112463620B (en) | Coverage rate test method and device in android software integration test | |
| CN112685275A (en) | Algorithm strategy searching method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |