CN113297058A - Case generation method, test method, device and server - Google Patents
Case generation method, test method, device and server Download PDFInfo
- Publication number
- CN113297058A CN113297058A CN202010346540.0A CN202010346540A CN113297058A CN 113297058 A CN113297058 A CN 113297058A CN 202010346540 A CN202010346540 A CN 202010346540A CN 113297058 A CN113297058 A CN 113297058A
- Authority
- CN
- China
- Prior art keywords
- case
- log chain
- use case
- log
- seed
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 61
- 238000010998 test method Methods 0.000 title claims abstract description 7
- 238000012360 testing method Methods 0.000 claims abstract description 158
- 230000002159 abnormal effect Effects 0.000 claims description 31
- 238000012216 screening Methods 0.000 claims description 23
- 238000009795 derivation Methods 0.000 claims description 3
- 230000006870 function Effects 0.000 description 14
- 239000013589 supplement Substances 0.000 description 14
- 238000004891 communication Methods 0.000 description 13
- 238000010586 diagram Methods 0.000 description 6
- 238000012545 processing Methods 0.000 description 5
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000001502 supplementing effect Effects 0.000 description 2
- 238000013528 artificial neural network Methods 0.000 description 1
- 230000035772 mutation Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the invention provides a case generation method, a test method, a device and a server, wherein the method comprises the following steps: acquiring a seed case; deriving a derived use case for the seed use case based on the seed use case; determining a first log chain generated by executing the test on the business system by using the seed case and a second log chain generated by executing the test on the business system by using the derived case; comparing the first log chain with the second log chain; and determining a target use case from the derived use cases according to the log chain comparison result. The embodiment of the invention can improve the generation efficiency of the use case and improve the comprehensiveness of the test execution of the service system.
Description
Technical Field
The embodiment of the invention relates to the technical field of testing, in particular to a case generation method, a test device and a server.
Background
In order to ensure the operation of the business system, various types of tests need to be performed on the business system based on the use cases, and the use cases can be regarded as descriptions of the test tasks and mainly include test input, test data, expected results and other contents related to the test tasks.
The batch generation of the use cases is a main mode for generating the use cases, and specifically, on the basis of setting the seed use cases, a plurality of derived use cases can be derived through the seed use cases, and then the use cases which are useful for testing are screened from the derived use cases. At present, the screening process is mainly implemented by manual screening, which makes the efficiency of generating the use cases extremely low, and therefore, how to provide a use case generation scheme to improve the efficiency of generating the use cases becomes a problem that needs to be solved by the technical staff in the field.
Disclosure of Invention
In view of this, embodiments of the present invention provide a method, a device and a server for generating a use case, so as to improve the efficiency of generating a use case.
In order to achieve the above purpose, the embodiments of the present invention provide the following technical solutions:
in a first aspect, an embodiment of the present invention provides a use case generation method, including:
acquiring a seed case;
deriving a derived use case for the seed use case based on the seed use case;
determining a first log chain generated by executing the test on the business system by using the seed case and a second log chain generated by executing the test on the business system by using the derived case;
comparing the first log chain with the second log chain;
and determining a target use case from the derived 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 a seed case;
deriving a derived use case for the seed use case based on the seed use case;
determining a first log chain generated by executing the test on the business system by using the seed case and a second log chain generated by executing the test on the business system by using the derived case;
comparing the first log chain with the second log chain;
determining a target use case from the derived use cases according to the log chain comparison result;
and executing 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 generation apparatus, including:
the acquisition module is used for acquiring a seed case;
a derivation module, configured to derive a derived use case 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 the test on the business system by using the seed case and a second log chain generated by executing the test on the business system by using the derived case;
the comparison module is used for comparing the first log chain with the second log chain;
and the determining module is used for determining a target use case from the derived use cases according to the log chain comparison result.
In a fourth aspect, an embodiment of the present invention provides a server, including at least one memory and at least one processor, where the memory stores one or more computer-executable instructions, and the processor calls the one or more computer-executable instructions to execute the use case generation method as described above or execute the test method as described above.
According to the case generation method provided by the embodiment of the invention, after the seed case is obtained, the derived case of the seed case can be derived based on the seed case, and in order to supplement the test level which cannot be covered by the seed case when a business system is tested, the embodiment of the invention needs to screen out the target case which is different from the seed case and can supplement the seed case from the derived case; in order to achieve the purpose, the embodiment of the invention can determine a first log chain generated by performing the test on the business system by using the seed case and determine a second log chain generated by performing the test on the business system by using the derived case, 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 of the test level of the seed case and the derived case when the test is executed on the service system, and the difference can reflect the test level which can be covered by the derived case but can not be covered by the seed case, so that based on the difference reflected by the log chain comparison result, the embodiment of the invention can determine the target case which is different from the seed case and can supplement the test level which can not be covered by the seed case from the derived case, automatically screen out the target case which is useful for the test from the derived case, and improve the comprehensiveness of the target case in executing the test on the service system. Therefore, the case generation method provided by the embodiment of the invention can realize automatic screening of the target case, improve the case generation efficiency and improve the comprehensiveness of the test execution 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 needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of a use case generation method according to an embodiment of the present invention;
fig. 2 is an exemplary diagram for determining a derived use case according to an embodiment of the present invention;
fig. 3 is a flowchart for determining a target use case from derived use cases according to an embodiment of the present invention;
fig. 4 is another flowchart for determining a target use case from derived use cases according to an embodiment of the present invention;
fig. 5 is a flowchart of screening use cases based on target use cases 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 generation apparatus 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 technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
As can be known from the background art, batch generation of use cases is a main way of use case generation, and under the condition of setting seed use cases, a plurality of derived use cases can be obtained by adjusting use case parameters of the seed use cases (for example, performing modification, combination and other processing); however, the derived cases obtained have cases which are useless for testing, for example, the derived cases have a useless case which is the same as the seed case or the same as the test level of the seed case for executing the test on the service system, and the number of cases which are different from the seed case and can be used for supplementing the seed case to execute the test on the service system is enriched on a test level which cannot be covered by the seed case when the service system is tested. However, currently, the screening process is mainly implemented by manual screening, which results in low efficiency of use case generation.
In order to solve the above problem, embodiments of the present invention provide an improved use case generation method, which, when a derived use case is derived based on a seed use case, implements automatic screening of the derived use case, reduces workload for screening the derived use case, and improves use case generation efficiency.
In an alternative implementation, an optional flow of the use case generation method provided in the embodiment of the present invention may be as shown in fig. 1, where the flow may be executed by a server, and with reference to fig. 1, the flow may include:
and S11, acquiring a seed case.
Optionally, the server may obtain a seed use case from the generated use cases, for example, the seed use case is any one of the generated use cases, or the seed use case is a use case selected from the generated use cases.
Optionally, the seed use case may be a normal use case. The normal case is used for testing the normal condition of the service system; otherwise, the exception case refers to a case used for performing an exception test on the service system, where the exception test is used for testing the processing of the service system to an exception condition, for example, testing the reaction of the service system to an error operation and an error message.
S12, deriving a derived use case of the seed use case based on the seed use case.
The seed case can be used as a basis for obtaining a derivative case in the embodiment of the invention; in an optional implementation, the embodiment of the present invention may adjust (for example, perform mutation, combination, and the like) the use case parameters of the seed use case based on the seed use case, so as to derive a derived use case of the seed use case, and one derived use case may be derived by adjusting the use case parameters of the seed use case once.
Optionally, the seed case may include content such as test input, test data, expected result, and the like of the seed case, and the test input, the test data, and the expected result have a plurality of case parameters; in an example of obtaining a derivative case by combining case parameters of a seed case, assuming that three parameters a, b and c are input for testing the seed case a, and the data type of each parameter is int/coolen/String, theoretically, the parameters a, b and c can be combined by multiple parameters, and a case corresponding to each parameter combination can be used as a derivative case; where int is an identifier defining an integer type variable, coolen is a value deposited by a boolean object or a value to be converted into a boolean value, String represents the data type of a String.
Of course, the embodiment of the present invention may also modify (i.e., mutate) the use case parameters of the seed use case to obtain derived use cases, and generally speaking, the modified use cases corresponding to different use case parameters may be used as different derived use cases. In an optional implementation, the embodiment of the present invention may modify the use case parameters of the seed use case by using a preset multi-factor model to obtain a derived use case; the multi-factor model can be associated with a plurality of variation factors so as to modify the use case parameters of the seed use case; for example, referring to fig. 2, the seed case may be input into the multi-factor model according to the embodiment of the present invention, so that the multi-factor model may modify the case parameters of the seed case for multiple times based on the associated multiple variation factors to derive multiple derived cases.
S13, determining a first log chain generated by the test executed on the business system by the seed case, and determining a second log chain generated by the test executed on the business system by the derived case.
The embodiment of the invention can respectively execute the test on the service system based on the seed case and each derived case, and can understand that one case execution process involves a plurality of execution nodes of the service system, 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 the use case (for example, a seed use case, a derived use case, and the like), the embodiment of the present invention may collect log information of an execution node of a business system related to the use case execution process, and link the log information according to the execution sequence of the execution node to obtain a log chain generated by the execution use case.
It should be noted that the log chain may be understood as a sequential data chain including log information of the execution node. The embodiment of the invention can collect the log information of the execution node of the service system related in the execution process of the seed case when the seed case is used for executing the test on the service system, and link the log information according to the execution sequence of the execution node, thereby obtaining a first log chain generated by executing the test on the service system by the seed case; for example, the first log chain may be represented as: [ debug, execution node 1] - > [ debug, execution node 2] - > [ war, execution node 3] - > [ error, execution node 4], where debug denotes debug, war denotes warning, and error denotes error; as can be seen from the first log chain in the above example, the first log chain may record the execution nodes of the service system involved in the execution process of the seed use case, the execution sequence of the execution nodes, and the log information of the execution nodes; for example, in the above example, the execution node represented by the first log chain is: executing nodes 1, 2, 3 and 4, wherein the execution sequence of the executing nodes is as follows: executing node 1, executing node 2, executing node 3, executing node 4; meanwhile, in the above example, war is warning information in the log information of the execution node 3, and error is error information in the log information of the execution node 4; further, the log information of the executing node in the first log chain can also record: and in the process of executing the test on the service system by using the seed case, the called times of the execution node are obtained.
Similarly, when the business system is tested by the derived use case, the embodiment of the invention can collect the log information of the execution node of the business system involved in the execution process of the derived use case, and link the log information according to the execution sequence of the execution node, thereby obtaining the second log chain generated by the test of the business system by the derived use case. For the specific content of the second log chain, reference may be made to the above description of the first log chain, and details thereof are not repeated here. It should be noted that, when a plurality of derived cases are derived based on the seed case, the embodiment of the present invention may respectively perform a test on the service system with each derived case, so as to generate a second log chain corresponding to each derived case, and obtain a plurality of second log chains.
S14, comparing the first log chain and the second log chain.
The embodiment of the invention can compare the first log chain with the second log chain corresponding to each derived case to obtain the log chain comparison result, and the log chain comparison result can reflect the difference of the test level of the seed case and the derived case when the test is executed on the service system, and concretely, the difference can reflect the test level which can be covered by the derived case but can not be covered by the seed case.
In an optional implementation, the first log chain may include an execution sequence of 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 execution nodes of the business system involved in the derived use case execution process, and log information of the execution nodes. Comparing the first log chain with the second log chain can obtain the results of whether the execution sequence of the execution nodes in the first log chain is the same as that of the execution nodes in the second log chain, whether the log information of the execution nodes in the first log chain is the same as that of the execution nodes in the second log chain and the like, so that the difference of the test level of the seed case and the derived case in the process of executing the test on the service system is reflected.
And S15, determining a target use case from the derived use cases according to the log chain comparison result.
Based on the fact that the log chain comparison result obtained in the step S14 can reflect the difference between the seed case and the derived case in the test executed on the service system, and the difference can embody the test layer which can be covered by the derived case but cannot be covered by the seed case, the embodiment of the present invention can determine the target case which is different from the seed case and can supplement the test layer which cannot be covered by the seed case from the derived case according to the log chain comparison result, so as to realize the purpose of screening out the useful target case for the test from the derived case. In an optional implementation, a target case that is different from the seed case and can supplement a test level that cannot be covered by the seed case may include at least one of:
a case which is consistent with a first service scene of a service system for testing the seed case and is not repeated with the seed case in the derived case is used as a target case; for convenience of description, the service scenario of the service system tested by the seed case is referred to as a first service scenario, and it should be noted that when the service system is tested, the service system needs to be tested in different service scenarios; according to the embodiment of the invention, the derived case is used as the target case, so that the target case different from the seed case can be used for testing the service system under the condition of conforming to the first service scene of the service system for testing the seed case, the number of usable cases in the first service scene is enriched, the target case can supplement the test layer which cannot be covered by the seed case in the first service scene, and the test comprehensiveness of the service system can be improved; optionally, the target use case described in this paragraph may be a new normal use case or an abnormal use case of the first service scenario;
the derived case is not consistent with the first service scene of the service system for the seed case test, is a case of an abnormal case and serves as a target case; the derived case is used as a target case, and can cover an abnormal service scene which is not consistent with a first service scene of a service system for seed case testing, so that the derived case is likely to cover an abnormal condition which is ignored by a user.
According to the case generation method provided by the embodiment of the invention, after the seed case is obtained, the derived case of the seed case can be derived based on the seed case, and in order to supplement the test level which cannot be covered by the seed case when a business system is tested, the embodiment of the invention needs to screen out the target case which is different from the seed case and can supplement the seed case from the derived case; in order to achieve the purpose, the embodiment of the invention can determine a first log chain generated by performing the test on the business system by using the seed case and determine a second log chain generated by performing the test on the business system by using the derived case, 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 of the test level of the seed case and the derived case when the test is executed on the service system, and the difference can reflect the test level which can be covered by the derived case but can not be covered by the seed case, so that based on the difference reflected by the log chain comparison result, the embodiment of the invention can determine the target case which is different from the seed case and can supplement the test level which can not be covered by the seed case from the derived case, automatically screen out the target case which is useful for the test from the derived case, and improve the comprehensiveness of the target case in executing the test on the service system. Therefore, the case generation method provided by the embodiment of the invention can realize automatic screening of the target case, improve the case generation efficiency and improve the comprehensiveness of the test execution on the service system.
In an alternative implementation, the target use case determined from the derived use cases may be: and deriving the use case which is consistent with the first service scene of the service system tested by the seed use case and is not repeated with the seed use case. In the embodiment of the present invention, taking the example that the log chain includes the execution sequence of the execution nodes of the business system related to the use case execution process and the log information of the execution nodes (that is, the first log chain may include the execution sequence of the execution nodes of the business system related to the seed use case execution process and the log information of the execution nodes; and the second log chain may include the execution sequence of the execution nodes of the business system related to the derivative use case execution process and the log information of the execution nodes), fig. 3 shows an optional flow for determining the target use case from the derivative use case, as shown in fig. 3, the flow may include:
step S21, comparing whether 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 whether 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.
In the embodiment of the invention, no matter aiming at the seed use case or the derived use case, 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 nodes in the first log chain may be embodied as a service logic sequence of the service system involved in the execution process of the seed use case. It should be noted that, if the service logic sequence of the service system related to the execution process of the seed case and the derived case is consistent, the seed case conforms to (if is the same as) the service scenario of the service system tested by the derived case; on the contrary, if the business logic sequence of the business system involved in the execution process of the seed case and the derived case is inconsistent, the business scenario of the business system tested by the seed case and the derived case is inconsistent. That is to say, by comparing whether 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, the embodiment of the present invention can determine whether the service scenario of the service system tested by the derived use case and the seed use case is consistent, that is, the embodiment of the present invention can determine whether the service scenario of the service system tested by the derived use case is consistent with the first service scenario.
In order to confirm whether the derived use case and the seed use case are repeated or not while comparing whether the service scenes of the service systems tested by the derived use case and the seed use case are consistent or not, in an optional implementation, the embodiment of the invention can compare whether log information of an execution node in a second log chain is the same as that of an execution node in a first log chain or not; 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 is also the same, the derived use case and the seed use case are repeated; on the contrary, 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, but the log information of the execution nodes is different, it is indicated that the derived case is consistent with the service scenario of the service system for seed case testing, but is not repeated with the seed case, and the derived case can be a case which is different from the seed case and can supplement the test layer which can not be covered by the seed case in the first service scenario.
In an alternative implementation, the log information of the execution node may include the called times of the execution node and error information (error), and the second log chain may be different from the log information of the execution node in the first log chain, for example: 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, and/or the log information of the second log chain has new error information compared with the log information of the first log chain; the log information of the second log chain has new error information compared with the log information of the first log chain can 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 derived use case corresponding to the second log chain as a target use case.
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 different from that of the execution node in the first log chain, the derived use case corresponding to the second log chain may be considered as: and the target use case conforms to the first service scene of the service system tested by the seed use case and is not repeated with the seed use case.
Step S23, 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, the derived use case corresponding to the second log chain is repeated with the seed use case, and the derived use case corresponding to the second log chain is deleted.
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 case corresponding to the second log chain is a case which is repeated with the seed case, the derived case corresponding to the second log chain is not used as a target case, and the derived 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 cases which are consistent with the first service scene of the service system for seed case testing and are not repeated with the seed cases from the plurality of derived cases, thereby enriching the number of the cases which can be used in the first service scene, covering a plurality of testing layers of the service system in the first service scene, improving the generation efficiency of the cases and improving the testing comprehensiveness of the service system.
In a more specific optional implementation, the target use case screened from the derived use cases in the embodiment of the present invention matches the first service scenario of the service system for seed use case testing, and the target use case that is not repeated with the seed use case may be: and the new normal use case or the abnormal use case is consistent with the first service scene of the service system for the seed use case test. Screening out a new normal case which is consistent with the first service scene from the derived cases, and enriching the number of cases for normally testing the service system in the first service scene so as to cover the normal tests of the service system in a plurality of layers related to the first service scene; and screening abnormal cases which are consistent with the first service scene from the derived cases, so that the number of cases for performing abnormal tests on the service system in the first service scene can be enriched, and the abnormal tests of a plurality of layers related to the service system in the first service scene are covered.
In a specific implementation, taking the example that the log information in the log chain includes the called times and the error information of the execution node, an optional implementation of determining, from the derived use cases, a new normal use case that conforms to the first service scenario of the service system for seed use case testing may be:
and if the execution sequence of the execution nodes in the second log chain is the same as that of the first log chain and no new error information exists in the log information of the second log chain compared with the log information of the first log chain, taking a derived case corresponding to the second log chain as a new normal case of the first service scene when 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.
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, which indicates that the service scenario of the service system tested by the derived use case corresponding to the second log chain conforms to the first service scenario of the service system tested by the seed use case; compared with the log information of the first log chain, the log information of the second log chain has no new error information, and the derived 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 the called times of the execution nodes in the first log chain, so that the derived case corresponding to the second log chain is not repeated with the seed case; therefore, compared with the seed case which is a new normal case of the first service scene, the derived case corresponding to the second log chain is used as the target case in the embodiment of the present invention, so that the number of normal cases of the first service scene can be enriched.
In an alternative implementation, one optional implementation of determining, from the derived use cases, an abnormal use case that matches the first service scenario of the service system for seed use case testing 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 a derived use case corresponding to the second log chain as an abnormal use case of the first service 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, which indicates that the service scenario of the service system tested by the derived use case corresponding to the second log chain conforms to the first service scenario of the service system tested by the seed use case; compared with the log information of the first log chain, the log information of the second log chain has new error information, and the derived use case corresponding to the second log chain is the abnormal use case.
According to the embodiment of the invention, the first log chain is compared with the second log chain, so that the difference of the test level of the seed case and the derived case when the business system is tested can be determined, and the difference can reflect the test level which can be covered by the derived case but cannot be covered by the seed case. Further, the screened 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 cases may be: and the abnormal case is not in accordance with the first service scene of the service system of the seed case test. 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 present invention may determine, from the plurality of derived use cases, a target use case that is inconsistent with the first service scenario and is an abnormal use case. The abnormal case which is not in accordance with the first business scene can cover the abnormal condition which is ignored artificially, thereby supplementing the abnormal test under the business scene which can not be covered by the seed case.
Optionally, taking the example that the log chain includes the execution sequence of the execution nodes and the log information of the execution nodes, fig. 4 shows another optional process for determining the target use case from the derived use cases, as shown in fig. 4, the process may include:
step S31, comparing whether 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 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 the 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 derived case corresponding to the second log chain is consistent with the first service scene; meanwhile, the embodiment of the invention can compare whether the log information of the second log chain has new error information compared with the log information of the first log chain to judge whether the derived case corresponding to the second log chain is an abnormal case.
And 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 derived use case corresponding to the second log chain as a target use case.
For any second log chain, if the execution sequence of the execution nodes of the second log chain is different from that of the execution nodes of the first log chain, the service scenario of the service system tested by the derived case corresponding to the second log chain is described and is not consistent with the first service scenario; further, 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 corresponding to the second log chain is an abnormal use case compared with the seed use case; therefore, the embodiment of the invention can determine the abnormal use case which is not in accordance with the first service scene from the derived use cases.
And 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 there is no new error information in the log information of the second log chain compared with the log information of the first log chain, deleting the derived use case corresponding to the second log chain.
The embodiment of the invention can screen the abnormal cases which are not in accordance with the first service scene of the seed case test service system from the derived cases, supplements the abnormal tests in the service scene which can not be covered by the seed cases, and enriches the abnormal cases for testing the service system.
In optional implementation, based on a target case determined from a plurality of derived cases, the embodiment of the invention can also support artificial screening of the target case, so as to obtain a finally screened case; because the number of the target cases is greatly reduced compared with the number of the derived cases, the manual screening is carried out based on the target cases, the screening workload can be greatly reduced, and the case generation efficiency is improved. Optionally, fig. 5 shows a process of artificially screening use cases based on target use cases, which may refer to:
and step S40, carrying out duplicate removal on the target use case.
And step S41, marking the use case attribute of the de-duplicated target use case, and displaying the marked use case attribute.
And step S42, screening the displayed use cases, and determining the finally screened use cases.
The number of the target use cases screened from the derived use cases may be multiple, wherein repeated use cases may exist.
The target case can have case attributes such as conformity, nonconformity, normal case, abnormal case and the like with the first service scene of the seed case test service system, and aiming at the target case determined from the derived case, the embodiment of the invention can determine the case attribute corresponding to the target case, so that the case attribute is marked on the target case after the duplication is removed, and the case attribute is displayed; 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 the user.
Optionally, in the case that a plurality of derived cases are derived based on the seed case by using the multi-factor model, for the target case after the deduplication, the embodiment of the present invention may further store the use case after the deduplication in a use case library; therefore, the embodiment of the invention can update the model parameters of the multi-factor model based on the use cases in the use case library, so that the derived use cases derived based on the multi-factor model are more accurate.
As an alternative implementation, fig. 6 shows an example of a use case generation process provided in the embodiment of the present invention, and refer to fig. 6:
after determining the seed use case, the embodiment of the invention can derive a plurality of derived use cases based on the seed use case by using a multi-factor model;
meanwhile, aiming at the seed case, the embodiment of the invention can test the service system by the seed case, thereby collecting the log information of the execution node of the service system related in the execution process of the seed case and linking the log information into a first log chain according to the execution sequence of the execution node; aiming at any derived use case, the embodiment of the invention can test the service system by the derived use case, thereby collecting the log information of the execution nodes of the service system related in the execution process of the derived use case, and linking the log information into a second log chain according to the execution sequence of the execution nodes;
furthermore, the first log chain and the second log chain can be compared, and a target case is determined from the derived cases based on a preset metamorphic relation rule, for example, the target case is a case which is consistent with the first service scene of the seed case test service system and is not repeated with the seed case, and/or the target case is an abnormal case which is not consistent with the first service scene of the seed case test service system; it should be noted that the metamorphic relation rule may define: determining a rule of a target case which is consistent with a first service scene of a test service system of the seed case and is not repeated with the seed case from the derived cases, and/or determining a rule of an abnormal case which is inconsistent with the first service scene from the derived cases, wherein the preset metamorphic relation rule can refer to the description of the corresponding part, and is not repeated here;
and the determined target use case can be stored in a use case library after being subjected to de-duplication, and model parameters of the multi-factor model can be updated based on the use case in the use case library.
Optionally, further, after the target use case is deduplicated, the embodiment of the present invention may also mark and display the use case attribute for the target use case; therefore, based on the screening of the user on the displayed use cases, the embodiment of the invention can determine the finally screened use cases from the displayed use cases. Of course, as an alternative implementation, in the embodiment of the present invention, the target use case may also be directly used as the use case obtained by the final screening after the deduplication is performed.
In an optional application example, with reference to the flows shown in fig. 3 and fig. 4, taking a first service scenario of a seed case testing service system as an example of starting a first function of the testing 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, and the like, which is not limited in this embodiment of the present invention), after a plurality of derivative cases are derived based on the seed case, the embodiment of the present invention may determine a first log chain generated by executing a test of starting the first function on the service system with the seed case, and determine a second log chain generated by executing a test on the service system with the derivative cases.
As an optional implementation of determining the target use case, after comparing the first log chain and the second log chain, if a service scenario of a service system for testing a derived use case corresponding to the second log chain is the first service scenario and the derived use case is not repeated with the seed use case, the embodiment of the present invention may use the derived use case as the target use case; in an example, if a service scenario of a service system for a derived case test is also started for testing a first function of the service system, it indicates that the service scenario of the service system for the derived case test is consistent with the first service scenario, and at this time, if the derived case is not repeated with a seed case, the embodiment of the present invention may use the derived case as a target case;
in a more specific implementation, in a case that a service scenario of a service system for a derived case test is also for testing a first function of the service system to be started, if there is no new error information in the log information of the second log chain compared to the log information of the first log chain, and the called number of execution nodes in the second log chain is different from the called number of execution nodes in the first log chain, the embodiment of the present invention may use the derived case as a new normal case for testing the first function of the service system to be started; and under the condition that the service scene of the service system for testing the derived use case is to test the first function start of the 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, the embodiment of the invention can take the derived use case as an abnormal use case for testing the first function start of the service system.
In another optional implementation of determining the target use case, after comparing the first log chain with the second log chain, if the service scenario of the service system of the derived use case test 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 an example, if the service scenario of the service system tested by the derived use case is that the first function of the service system is closed, it indicates that the service scenario of the service system tested by the derived use case is not consistent with the first service scenario, and at this time, 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 an abnormal use case for testing that the first function of the service system is closed.
In an optional implementation, an embodiment of the present invention further provides a testing method, where after a target use case is determined based on, for example, the flow shown in fig. 1, the embodiment of the present invention performs a test on the service system by using the seed use case and a use case in the target use case; it can be understood that the seed case and the target case can be regarded as useful cases for performing tests on the business system, in an optional implementation, the seed case and the target case can be stored in the test case set, so that the business system is tested based on the cases in the test case set, and as the target case can cover a test layer which cannot be covered by the seed case, a test case set is formed based on the seed case and the target case, and the cases in the test case set are used for performing tests on the business system, so that the test comprehensiveness of the business system can be improved.
In the following, a use case generating apparatus provided in the embodiment of the present invention is introduced, and the use case generating apparatus described below may be regarded as a functional module that is required to be provided by a server to implement the use case generating method provided in the embodiment of the present invention. The contents of the use case generation apparatus described below and the contents of the use case generation method described above may be referred to in correspondence with each other.
In an alternative implementation, fig. 7 shows an alternative block diagram of a use case generation apparatus provided in an embodiment of the present invention, where the apparatus may include:
an obtaining module 100, configured to obtain a seed case;
a derivation module 110, configured to derive a derived use case of the seed use case based on the seed use case;
a log chain determining module 120, configured to determine a first log chain generated by performing a test on the business system with the seed use case, and a second log chain generated by performing a test on the business system with the derived use case;
a comparing module 130, configured to compare the first log chain with 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 is configured to determine a target use case from the derived use cases according to a log chain comparison result, and may include:
and according to the log chain comparison result, determining a target case which is consistent with a first service scene of a service system tested by the seed case and is not repeated with the seed case from the derived case.
Optionally, the log chain may include: the execution sequence of the execution nodes of the business system related to the execution process of the seed use case or the derived use case and the log information of the execution nodes; the comparing module 130 is configured to compare the first log chain with the second log chain, and may include:
and comparing whether 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 whether 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.
Optionally, the determining module 140 is configured to determine, according to the log chain comparison result, a target use case that conforms to the first service scenario of the service system for seed use case testing and is not duplicated with the seed use case from the derived use cases, and 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 derived 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 derived use case corresponding to the second log chain and the seed use case, and deleting the derived use case corresponding to the second log chain.
Optionally, on one hand, the determining module 140 is configured to, if the execution sequence of the execution node in 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 different from that of the execution node in the first log chain, take a derived use case corresponding to the second log chain as a target use case, and 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 derived use case corresponding to the second log chain as a new normal use case of the first service scene when 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.
Optionally, on the other hand, the determining module 140 is configured to, if the execution sequence of the execution node in 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 different from that of the execution node in the first log chain, take a derived use case corresponding to the second log chain as a target use case, and 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 a derived use case corresponding to the second log chain as an abnormal use case of the first service scene.
In another alternative implementation, the determining module 140 is configured to determine a target use case from the derived use cases according to the log chain comparison result, and may include:
and according to the log chain comparison result, determining a target case which is not in accordance with the first service scene of the service system tested by the seed case and has new error information compared with the log information of the first log chain in the log information of the second log chain from the derived case.
Optionally, the determining module 140 is configured to determine, from the derived use cases, a target use case that is not in accordance with the first service scenario of the service system tested by the seed use case and has new error information compared with the log information of the first log chain in the log information of the second log chain according to the log chain comparison result, and the determining module may include:
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 new error information compared with the log information of the first log chain, taking a derived 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 no new error information exists in the log information of the second log chain compared with the log information of the first log chain, deleting the derived use case corresponding to the second log chain.
Optionally, the use case generating device provided in the embodiment of the present invention may be further configured to:
carrying out duplicate removal on the target use case; marking the case attributes of the de-duplicated target case, and displaying; and screening the displayed use cases to determine the finally screened use cases.
Optionally, the deriving module 110 is configured to derive a derived use case of the seed use case based on the seed use case, and may include:
modifying the use case parameters of the seed use case by utilizing a preset multi-factor model based on the seed use case to obtain a derived use case;
after the target use case is deduplicated, the use case generation apparatus provided in the embodiment of the present invention may be further configured to:
and updating the model parameters of the multi-factor model according to the use cases in the use case library, and storing the de-duplicated target use case by the seed use case.
The embodiment of the invention also provides a testing device, which can execute the test on the business system by using the seed case and the case in the target case after the case generating device determines the target case.
After the seed case is obtained, the case generation device provided by the embodiment of the invention can derive the derived case of the seed case based on the seed case, and in order to supplement the test level which cannot be covered by the seed case when testing the service system, the embodiment of the invention needs to screen out the target case which is different from the seed case and can supplement the seed case from the derived case; in order to achieve the purpose, the embodiment of the invention can determine a first log chain generated by performing the test on the business system by using the seed case and determine a second log chain generated by performing the test on the business system by using the derived case, 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 of the test level of the seed case and the derived case when the test is executed on the service system, and the difference can reflect the test level which can be covered by the derived case but can not be covered by the seed case, so that based on the difference reflected by the log chain comparison result, the embodiment of the invention can determine the target case which is different from the seed case and can supplement the test level which can not be covered by the seed case from the derived case, automatically screen out the target case which is useful for the test from the derived case, and improve the comprehensiveness of the target case in executing the test on the service system. Therefore, the case generation method provided by the embodiment of the invention can realize automatic screening of the target case, improve the case generation efficiency and improve the comprehensiveness of the test execution on the service system.
The embodiment of the invention also provides a server, and the server can realize the use case generation method provided by the embodiment of the invention through the use case generation device in a loading program form. In an alternative implementation, fig. 8 shows an alternative block diagram of a server provided in an embodiment of the present invention, and referring to fig. 8, the server may include: 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 present 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 mutual communication through the communication bus 4; it is clear that the illustrated communication connection illustration of the processor 1, the communication interface 2, the memory 3 and the communication bus 4 is only optional;
optionally, 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), a GPU (Graphics Processing Unit), an NPU (embedded neural network processor), an FPGA (Field Programmable Gate Array), a TPU (tensor Processing Unit), an AI chip, an asic (application Specific Integrated circuit), or one or more Integrated circuits configured to implement the embodiments of the present invention.
The memory 3 may comprise a high-speed RAM memory and may also 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 calls the one or more computer-executable instructions to execute the use case generation method provided by the embodiment of the present invention.
Optionally, in the server provided in the embodiment of the present invention, the memory may also store one or more computer-executable instructions for executing the testing method provided in the embodiment of the present invention, so that the processor may call the one or more computer-executable instructions to execute the testing method provided in the embodiment of the present invention.
The embodiment of the present invention further provides a storage medium, where the storage medium may store one or more computer-executable instructions, where the one or more computer-executable instructions are used to execute the use case generation method provided in the embodiment of the present invention, or to execute the test method provided in the embodiment of the present invention.
While various embodiments of the present invention have been described above, various alternatives described in the various embodiments can be combined and cross-referenced without conflict to extend the variety of possible embodiments that can be considered disclosed and disclosed in connection with the embodiments of the present invention.
Although the embodiments of the present invention have been disclosed, the present invention is not limited thereto. Various changes and modifications may be effected therein by one skilled in the art without departing from the spirit and scope of the invention as defined in the appended claims.
Claims (13)
1. A use case generation method comprises the following steps:
acquiring a seed case;
deriving a derived use case for the seed use case based on the seed use case;
determining a first log chain generated by executing the test on the business system by using the seed case and a second log chain generated by executing the test on the business system by using the derived case;
comparing the first log chain with the second log chain;
and determining a target use case from the derived use cases according to the log chain comparison result.
2. The use case generation method of claim 1, wherein the determining a target use case from the derived use cases according to the log chain comparison result comprises:
and according to the log chain comparison result, determining a target case which is consistent with a first service scene of a service system tested by the seed case and is not repeated with the seed case from the derived case.
3. The use case generation method of claim 2, the log chain comprising: the execution sequence of the execution nodes of the business system related to the execution process of the seed use case or the derived use case and the log information of the execution nodes; the comparing the first log chain and the second log chain comprises:
and comparing whether 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 whether 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.
4. The use case generation method according to claim 3, wherein the determining, from the derived use cases, a target use case that conforms to a first service scenario of a service system tested by the seed use case and is not repeated with 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 derived 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 derived use case corresponding to the second log chain and the seed use case, and deleting the derived use case corresponding to the second log chain.
5. The use case generation method according to claim 4, wherein 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 derived use case corresponding to the second log chain as the target use case includes:
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 derived use case corresponding to the second log chain as a new normal use case of the first service scene when 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.
6. The use case generation method according to claim 4, wherein 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 derived use case corresponding to the second log chain as the target use case includes:
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 a derived use case corresponding to the second log chain as an abnormal use case of the first service scene.
7. The use case generation method according to claim 1, wherein the determining a 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 case which is not in accordance with the first service scene of the service system tested by the seed case and has new error information compared with the log information of the first log chain in the log information of the second log chain from the derived case.
8. The use case generation method according to claim 7, wherein the determining, from the derived use cases, the 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 includes:
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 new error information compared with the log information of the first log chain, taking a derived 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 no new error information exists in the log information of the second log chain compared with the log information of the first log chain, deleting the derived use case corresponding to the second log chain.
9. The use case generation method according to any one of claims 1 to 8, further comprising:
carrying out duplicate removal on the target use case;
marking the case attributes of the de-duplicated target case, and displaying;
and screening the displayed use cases to determine the finally screened use cases.
10. The use case generation method of claim 9, wherein deriving the derived use case of the seed use case based on the seed use case comprises:
modifying the use case parameters of the seed use case by utilizing a preset multi-factor model based on the seed use case to obtain a derived use case;
the method further comprises the following steps:
and updating the model parameters of the multi-factor model according to the use cases in the use case library, and storing the de-duplicated target use case by the seed use case.
11. A method of testing, comprising:
acquiring a seed case;
deriving a derived use case for the seed use case based on the seed use case;
determining a first log chain generated by executing the test on the business system by using the seed case and a second log chain generated by executing the test on the business system by using the derived case;
comparing the first log chain with the second log chain;
determining a target use case from the derived use cases according to the log chain comparison result;
and executing test on the service system by using the seed use case and the use case in the target use case.
12. A use case generation apparatus, comprising:
the acquisition module is used for acquiring a seed case;
a derivation module, configured to derive a derived use case 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 the test on the business system by using the seed case and a second log chain generated by executing the test on the business system by using the derived case;
the comparison module is used for comparing the first log chain with the second log chain;
and the determining module is used for determining a target use case from the derived use cases according to the log chain comparison result.
13. A server comprising at least one memory and at least one processor, the memory storing one or more computer-executable instructions that are invoked by the processor 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 CN113297058A (en) | 2020-04-27 | 2020-04-27 | Case generation method, test method, device and server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010346540.0A CN113297058A (en) | 2020-04-27 | 2020-04-27 | Case generation method, test method, device and server |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113297058A true CN113297058A (en) | 2021-08-24 |
Family
ID=77318057
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010346540.0A Pending CN113297058A (en) | 2020-04-27 | 2020-04-27 | Case generation method, test method, device and server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113297058A (en) |
Cited By (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 |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150269060A1 (en) * | 2014-03-21 | 2015-09-24 | Ca, Inc. | Development tools for logging and analyzing software bugs |
| CN109460349A (en) * | 2018-09-19 | 2019-03-12 | 武汉达梦数据库有限公司 | A kind of method for generating test case and device based on log |
| CN110175120A (en) * | 2019-05-20 | 2019-08-27 | 北京理工大学 | A kind of fuzz testing use-case TSP question method and apparatus based on intensified learning |
| CN110221965A (en) * | 2019-05-09 | 2019-09-10 | 阿里巴巴集团控股有限公司 | Test cases technology, test method, device, equipment and system |
| CN110727597A (en) * | 2019-10-15 | 2020-01-24 | 杭州安恒信息技术股份有限公司 | Method for completing use case based on log troubleshooting invalid codes |
| CN113297063A (en) * | 2020-06-05 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Use case generation method and device, server and storage medium |
-
2020
- 2020-04-27 CN CN202010346540.0A patent/CN113297058A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150269060A1 (en) * | 2014-03-21 | 2015-09-24 | Ca, Inc. | Development tools for logging and analyzing software bugs |
| CN109460349A (en) * | 2018-09-19 | 2019-03-12 | 武汉达梦数据库有限公司 | A kind of method for generating test case and device based on log |
| CN110221965A (en) * | 2019-05-09 | 2019-09-10 | 阿里巴巴集团控股有限公司 | Test cases technology, test method, device, equipment and system |
| CN110175120A (en) * | 2019-05-20 | 2019-08-27 | 北京理工大学 | A kind of fuzz testing use-case TSP question method and apparatus based on intensified learning |
| CN110727597A (en) * | 2019-10-15 | 2020-01-24 | 杭州安恒信息技术股份有限公司 | Method for completing use case based on log troubleshooting invalid codes |
| CN113297063A (en) * | 2020-06-05 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Use case generation method and device, server and storage medium |
Non-Patent Citations (2)
| Title |
|---|
| NAIPENG LI等: "Machine remaining useful life prediction considering unit-to-unit variability", 《2017 IEEE INTERNATIONAL CONFERENCE ON PROGNOSTICS AND HEALTH MANAGEMENT (ICPHM)》, 3 August 2017 (2017-08-03), pages 103 * |
| 杨红等: "基于模型检测技术的变异测试用例生成方法", 《计算机科学》, no. 45, 15 November 2018 (2018-11-15), pages 488 - 493 * |
Cited By (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 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7917895B2 (en) | Automated software testing and validation system | |
| CN104252481B (en) | The dynamic check method and apparatus of master-slave database consistency | |
| JP2018185808A (en) | Apparatus for and method of testing smart agreement based on block chain | |
| JP6723989B2 (en) | Data driven inspection framework | |
| CN104461693B (en) | Virtual machine update method and system under a kind of desktop cloud computing environment | |
| CN107741903A (en) | Application compatibility method of testing, device, computer equipment and storage medium | |
| CN107080945B (en) | Method and device for testing artificial intelligence behaviors in game and electronic equipment | |
| CN108595342A (en) | Unit test method and device | |
| US11663113B2 (en) | Real time fault localization using combinatorial test design techniques and test case priority selection | |
| CN115576834A (en) | Software test multiplexing method, system, terminal and medium for supporting fault recovery | |
| CN113297058A (en) | Case generation method, test method, device and server | |
| CN116561003A (en) | Test data generation method, device, computer equipment and storage medium | |
| CN108287788A (en) | A kind of use-case step matching method based on test case, system | |
| CN112988565B (en) | Interface automatic test method, device, computer equipment and storage medium | |
| CN109697161A (en) | A kind of test method of storing process, storage medium and database server | |
| CN113791980A (en) | Test case conversion analysis method, device, equipment and storage medium | |
| CN112783775A (en) | Special character input testing method and device | |
| CN112597023A (en) | Case management method and device based on guide picture, computer equipment and storage medium | |
| CN113176995A (en) | Interface testing method, device, equipment and medium based on testing scene | |
| CN113282482A (en) | Compatibility test method and system for software package | |
| CN113297063A (en) | Use case generation method and device, server and storage medium | |
| Baker et al. | Quality assurance and error identification for the Community Earth System Model | |
| CN109753742A (en) | A kind of Fault Diagnosis of Aeroengines method, system based on unbalanced sample | |
| CN114595159B (en) | Test data generation method, device, equipment and storage medium | |
| TWI710896B (en) | Cloud system and method for integrating a cloud system |
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 |