CN113297063B - Use case generation method, device, server and storage medium - Google Patents
Use case generation method, device, server and storage medium Download PDFInfo
- Publication number
- CN113297063B CN113297063B CN202010504770.5A CN202010504770A CN113297063B CN 113297063 B CN113297063 B CN 113297063B CN 202010504770 A CN202010504770 A CN 202010504770A CN 113297063 B CN113297063 B CN 113297063B
- Authority
- CN
- China
- Prior art keywords
- use case
- log
- seed
- log chain
- 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
- 238000000034 method Methods 0.000 title claims abstract description 71
- 238000012360 testing method Methods 0.000 claims abstract description 180
- 230000002159 abnormal effect Effects 0.000 claims abstract description 71
- 230000005856 abnormality Effects 0.000 claims description 10
- 238000004891 communication Methods 0.000 description 13
- 238000010586 diagram Methods 0.000 description 8
- 238000005065 mining Methods 0.000 description 5
- 238000012545 processing Methods 0.000 description 3
- 238000012216 screening Methods 0.000 description 3
- 230000015556 catabolic process Effects 0.000 description 2
- 238000009795 derivation Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000013528 artificial neural network Methods 0.000 description 1
- 238000012804 iterative process Methods 0.000 description 1
- 230000035772 mutation Effects 0.000 description 1
- 238000011282 treatment Methods 0.000 description 1
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
-
- 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/3692—Test management for test results analysis
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 application provides a use case generation method, a device, a server and a storage medium, wherein the method comprises the following steps: acquiring seed cases; acquiring a first derivative case derived from a seed case; determining a seed log chain generated by executing a test on the service system by using the seed use case, and a first log chain generated by executing a test on the service system by using a first derivative use case; comparing the seed log chain with the first log chain, and determining a target use case of which the log information of the first log chain has new error information at least compared with the log information of the seed log chain from first derivative use cases based on a comparison result; deriving a target use case parameter of the target use case based at least on the seed use case, and deriving a second derived use case; and determining a use case which causes the business system to be abnormal from the second derivative use case, wherein the use case is suitable for the abnormal test of the business system. The embodiment of the application can efficiently generate the use cases suitable for the anomaly test in batches.
Description
Technical Field
The embodiment of the application relates to the technical field of testing, in particular to a method and a device for generating a use case, a server and a storage medium.
Background
To ensure operation of the business system, various types of tests, including anomaly tests, need to be performed on the business system. The abnormal test is a test process for testing the business system by adopting error operation, error data and other means, so that the business system has program breakdown, log disorder and other abnormal conditions.
The exception test needs to use cases suitable for the exception test, at present, based on the derivation of a large number of cases, the derived cases are mainly used for testing a service system, then whether the service system is abnormal or not is observed, so that the cases suitable for the exception test are expected to be obtained from the derived cases, the cases suitable for the exception test cannot be obtained in a high-efficiency batch mode, and therefore, in order to improve the efficiency of the exception test, how to efficiently generate the cases suitable for the exception test in a batch mode becomes a problem to be solved urgently by a person skilled in the art.
Disclosure of Invention
In view of the above, the embodiments of the present application provide a method, an apparatus, a server, and a storage medium for generating use cases applicable to anomaly testing in high-efficiency batch.
In order to achieve the above object, the embodiment of the present application provides the following technical solutions:
A use case generation method, wherein the method comprises:
Acquiring a first derivative case derived from a seed case;
Determining a seed log chain generated by executing a test on the service system by using the seed use case, and a first log chain generated by executing a test on the service system by using a first derivative use case;
Comparing the seed log chain with the first log chain, and determining a target use case of which the log information of the first log chain has new error information at least compared with the log information of the seed log chain from first derivative use cases based on a comparison result;
deriving a target use case parameter of the target use case based at least on the seed use case, and deriving a second derived use case;
and determining a use case which causes the business system to be abnormal from the second derivative use case, wherein the use case is suitable for the abnormal test of the business system.
The embodiment of the application also provides a use case generating device, which comprises:
The first deriving module is used for obtaining a first deriving use case derived from the seed use case;
the log chain determining module is used for determining a seed log chain generated by executing a test on the service system by using the seed use case and a first log chain generated by executing the test on the service system by using a first derivative use case;
the target use case determining module is used for comparing the seed log chain with the first log chain, and determining a target use case in which the log information of the first log chain has new error information at least compared with the log information of the seed log chain from the first derivative use case based on a comparison result;
The second deriving module is used for deriving the target use case parameters of the target use case at least based on the seed use case and deriving a second derived use case;
And the use case determining module is used for determining the use case which causes the business system to be abnormal from the second derivative use case, and the use case is suitable for the abnormal test of the business system.
The embodiment of the application also provides a server, which comprises: at least one memory and at least one processor; the memory stores one or more computer-executable instructions that the processor invokes to perform the use case generation method as described above.
Embodiments of the present application also provide a storage medium storing one or more computer-executable instructions for performing a use case generation method as described above.
The use case generation method provided by the embodiment of the application can acquire the first derivative use case derived from the seed use case, and compare the seed log chain generated by executing the test on the service system by the seed use case with the first log chain generated by executing the test on the service system by the first derivative use case; based on the comparison result, the embodiment of the application can determine the target use case with new error information of the log information of the first log chain at least compared with the log information of the seed log chain from the first derivative use case, wherein the target use case can be considered as the use case with possibility of being applicable to abnormal test; therefore, the embodiment of the application can derive the target use case parameters of the target use case at least based on the seed use case, derive the second derived use case and enlarge the number of use cases with possibility of being applicable to abnormal test; furthermore, the use cases causing the abnormality of the service system are determined from the second derivative use cases, so that the number of the generated use cases suitable for the abnormality test can be increased. Therefore, in the embodiment of the present application, since the target use case is a use case having a possibility of being applicable to an anomaly test, and the target use case parameter is a use case parameter from which the target use case is derived in the seed use case, the second derived use case is further derived based on the target use case parameter.
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 application;
FIG. 2 is a flow chart of deriving a second derivation use case according to an embodiment of the present application;
FIG. 3 is an exemplary diagram of an iterative derived second derived use case provided by an embodiment of the present application;
FIG. 4 is another flowchart of a use case generating method according to an embodiment of the present application;
FIG. 5 is a flowchart of a method for generating a use case according to an embodiment of the present application;
FIG. 6 is an exemplary diagram of an abnormal case generation process provided by an embodiment of the present application;
FIG. 7 is a block diagram of a use case generating device according to an embodiment of the present application;
FIG. 8 is a further block diagram of a use case generating apparatus according to an embodiment of the present application;
fig. 9 is an alternative block diagram of a server provided in an embodiment of the present application.
Detailed Description
The traditional way of generating use cases suitable for exception testing is mainly: and (3) deriving a plurality of use cases by using the seed use cases as a basis, manually screening the use cases suitable for the abnormality test from the derived use cases, for example, testing a service system by using the derived use cases, and manually observing whether the service system is abnormal based on program breakdown, log disorder and the like of the derived use cases, thereby manually screening the use cases suitable for the abnormality test from the derived use cases. The method for generating the use cases suitable for the anomaly test involves a large amount of manual observation and screening work, and clearly has the problem of low use case generation efficiency; meanwhile, the scope of the generated use cases is limited to the use cases derived from the seed use cases, so that the number of the generated use cases suitable for the anomaly test is limited, and batch generation of the use cases cannot be realized.
Based on the above, the embodiment of the application provides a use case generation method, a device, a server and a storage medium, which are used for efficiently generating use cases suitable for exception test in batches. The following description of the embodiments of the present application 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 application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
In an optional implementation, fig. 1 shows an optional flow of a use case generating method provided by an embodiment of the present application, where the flow may be executed by a server, and referring to fig. 1, the flow may include:
step S100, a first derivative case derived from the seed case is obtained.
In an alternative implementation, the seed use case may be a use case suitable for normal testing; the server may determine the seed use case from the generated use cases applicable to the normal test, for example, the seed use case is any one of the generated use cases applicable to the normal test, or the seed use case is a use case selected from the generated use cases applicable to the normal test. It should be noted that, the normal test is a process of testing the service system by means of normal operation, normal data, etc., the normal test needs to be applied to a use case suitable for the normal test, whereas the abnormal test is a process of testing the service system by means of error operation, error data, etc., and the abnormal test needs to be applied to a use case suitable for the abnormal test.
In the embodiment of the application, the first derivative case can be derived based on the seed case, and in the optional implementation of deriving the first derivative case based on the seed case, the embodiment of the application can adjust the case parameters in the seed case, for example, the case parameters in the seed case are subjected to operations such as mutation (modification), combination and the like to obtain the first derivative case, and one case parameter after the seed case adjustment can correspond to one first derivative case derived, so that the embodiment of the application can obtain a plurality of first derivative cases;
Optionally, the seed use case may include contents such as a test input, test data, and an expected result, where the test input, the test data, and the expected result have a plurality of use case parameters; in one example of combining the use case parameters of the seed use case to obtain the first derivative use case, assuming that the test input of the seed use case has three parameters of a, b and c, and the data type of each parameter is int/boolen/String, theoretically, the parameters of a, b and c can have multiple parameter combinations, and the use case corresponding to each parameter combination can be used as the first derivative use case; where int is an identifier defining an integer type variable, boolen is a value deposited by a boolean object or a value to be converted into a boolean value, string represents the data type of the String;
Of course, in the embodiment of the present application, the use case parameters of the seed use case may be modified (i.e., mutated) to obtain the first derivative use case; in an alternative implementation, the embodiment of the application may utilize a preset multi-factor model, derive a plurality of first derived use cases based on the seed use cases, and the multi-factor model may associate a plurality of variation factors for modifying use case parameters, so as to modify use case parameters in the seed use cases.
Step S110, determining a seed log chain generated by executing a test on the service system by using the seed use case and a first log chain generated by executing a test on the service system by using a first derivative use case.
The first derivative case may have a case suitable for normal test, a case suitable for abnormal test, a case suitable for possibility of abnormal test, and the like, for convenience of explanation, in the embodiment of the present application, a use case having a possibility of being suitable for an anomaly test in the first derivative use case is referred to as a target use case;
In general, the number of cases applicable to the exception test in the first derivative case is smaller than that of the target case, and even if no case applicable to the exception test exists in the first derivative case, the cases applicable to the exception test are directly determined from the first derivative case, and only a small number of cases applicable to the exception test are often obtained, or no case applicable to the exception test is obtained; the target use case cannot be directly used as the use case suitable for the abnormal test, but the target use case has the possibility of being suitable for the abnormal test, and the target use case occupies a certain proportion in the first derivative use case, so that in order to generate the use cases suitable for the abnormal test in a high-efficiency batch manner, the embodiment of the application can determine the target use case with the possibility of being suitable for the abnormal test from the first derivative use case, thereby digging more use cases suitable for the abnormal test based on the target use case, and providing possibility for realizing the efficient batch generation of the use cases suitable for the abnormal test.
Based on this, the embodiment of the application can perform a test on the service system by the seed use case, obtain the generated seed log chain, perform a test on the service system by the first derivative use case, and obtain the generated first log chain, so that the target use case with possibility of being applicable to the abnormal test can be determined from the first derivative use case by comparing the first log chain with the seed log chain, thereby providing possibility for expanding the range of mining to use cases applicable to the abnormal test.
In an alternative implementation, the process of executing the test on the service system by one use case involves multiple execution nodes of the service system, and each execution node completes respective execution logic, so that the service system finally outputs the test result. When a service system is tested by using a use case (such as a seed use case, a first derivative use case and the like), the embodiment of the application can collect log information of each execution node of the service system involved in the execution test, and link the log information according to the execution sequence of the execution nodes to obtain a log chain generated by the execution test of the use case on the service system;
A log chain may be understood as a sequential data chain comprising log information of executing nodes; the embodiment of the application can collect the log information of each execution node of the service system involved in the execution test when the service system is tested by the seed use case, and link the log information according to the execution sequence of the execution nodes, thereby determining a seed log chain generated by the execution test of the service system by the seed use case; for example, a seed log chain may be expressed as: [ debug, execution node 1] = > [ debug, execution node 2] = > [ wave, execution node 3] = > [ error, execution node 4], wherein debug represents debug, wave represents warning, error represents error; from the seed log chain of the above example, the seed 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 nodes represented by the seed log chain are execution nodes 1,2, 3, and 4; the execution sequence of the execution nodes is as follows: executing node 1-executing node 2-executing node 3-executing node 4; in the above example, warn 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.
Similarly, when the first derivative case is used for testing the service system, the embodiment of the application can collect log information of each execution node of the service system related to the execution test, and link the log information in the execution sequence of the execution nodes, so as to determine the first log chain generated by the execution of the test on the service system by the first derivative case.
And step S120, comparing the seed log chain with the first log chain, and determining a target use case in which the log information of the first log chain has new error information at least compared with the log information of the seed log chain from the first derivative use case based on the comparison result.
Based on the obtained seed log chain and the first log chain, in an alternative implementation, embodiments of the present application may determine a target use case having a likelihood of being suitable for an anomaly test from the first derivative use case by comparing the first log chain and the seed log chain.
Optionally, the embodiment of the present application may define the target use case to be: in the first derivative use case, the log information of the first log chain is at least a use case with new error information compared with the log information of the seed log chain. Thus, in an alternative implementation of determining the target use case from the first derivative use case, the embodiment of the present application may compare the first log chain with the seed log chain, if it is determined that the log information of the first log chain has new error information at least compared with the log information of the seed log chain, the first derivative use case having the first log chain is the target use case, that is, the log information of the first log chain has redundant new error (error information) compared with the log information of the seed log chain, and the first derivative use case having the first log chain may be the target use case.
In a further alternative implementation, a case suitable for the exception test may also exist in the first derivative case, and the embodiment of the present application may also determine a case suitable for the exception test directly from the first derivative case, for example, the embodiment of the present application may analyze the first log chain and determine a case suitable for the exception test directly from the first derivative case; the embodiment of the application can define the use cases suitable for the exception test as follows: use cases that cause an exception to the business system, such as a program crash to the business system, and/or use cases that cause a log disorder to the business system due to a process restart; therefore, in the embodiment of the application, if it is determined that the program crash information exists in the log information of the first log chain, and/or if the log information is disordered due to the process restarting of the first log chain, the first derivative case with the first log chain is a case suitable for the exception test.
And step S130, deriving a target use case parameter of the target use case at least based on the seed use case, and deriving a second derived use case.
The target use case is determined from the first derivative use case, which is obtained by adjusting use case parameters for the seed use case, and after the target use case is determined, the target use case parameter of the target use case derived from the seed use case can be determined, namely the target use case parameter is the use case parameter of the target use case obtained by adjusting the seed use case. It can be understood that, the target use case parameters in the seed use case are adjusted to obtain the target use case with possibility of being applicable to the abnormal test, so that the target use case parameters in the seed use case are adjusted differently for multiple times, or the use case inheritance is performed by using the target use case parameters based on the target use case, so that more potential use cases applicable to the abnormal test can be possibly mined, and therefore, the embodiment of the application can derive more use cases (the embodiment of the application can be called as a second derived use case) based on the target use case parameters, so as to provide possibility for mining more use cases applicable to the abnormal test.
And step 140, determining a use case which causes the business system to be abnormal from the second derivative use cases, wherein the use case is suitable for the abnormal test of the business system.
Alternatively, the use cases applicable to the anomaly test may be: use cases that cause an exception to the business system, such as a program crash to the business system, and/or use cases that cause a log disorder to the business system due to a process restart; after the second derivative use case is obtained, the use case which causes the business system to be abnormal can be determined from the second derivative use case, so that the use case suitable for the abnormal test of the business system is obtained; compared with the case suitable for the abnormal test determined directly from the first derivative case, the case suitable for the abnormal test is determined from the second derivative case, and more cases suitable for the abnormal test can be mined.
In an optional implementation of determining a use case suitable for an exception test from the second derivative use cases, the embodiment of the present application may determine a second log chain generated by performing a test on the service system with the second derivative use case, and if program crash information exists in log information of the second log chain and/or the log information of the second log chain is disordered due to process restart, the embodiment of the present application may determine that the second derivative use case with the second log chain is a use case suitable for an exception test.
The use case generation method provided by the embodiment of the application can acquire the first derivative use case derived from the seed use case, and compare the seed log chain generated by executing the test on the service system by the seed use case with the first log chain generated by executing the test on the service system by the first derivative use case; based on the comparison result, the embodiment of the application can determine the target use case with new error information of the log information of the first log chain at least compared with the log information of the seed log chain from the first derivative use case, wherein the target use case can be considered as the use case with possibility of being applicable to abnormal test; therefore, the embodiment of the application can derive the target use case parameters of the target use case at least based on the seed use case, derive the second derived use case and enlarge the number of use cases with possibility of being applicable to abnormal test; furthermore, the use cases causing the abnormality of the service system are determined from the second derivative use cases, so that the number of the generated use cases suitable for the abnormality test can be increased. Therefore, in the embodiment of the present application, since the target use case is a use case having a possibility of being applicable to an anomaly test, and the target use case parameter is a use case parameter from which the target use case is derived in the seed use case, the second derived use case is further derived based on the target use case parameter.
In an optional implementation of determining a target use case from the first derivative use cases, if the execution nodes and the execution sequences of the first log chain and the seed log chain are consistent, and the log information of the first log chain has new error information compared with the log information of the seed log chain, the embodiment of the application can determine the first derivative use case with the first log chain as the first target use case; the first target use case may be an alternative form of the target use case in the embodiment of the present application, and although the first target use case is not directly used as a use case suitable for the anomaly test, the first target use case has a strong possibility of being suitable for the anomaly test.
For the first target use case, the second derivative use case can be derived according to the embodiment of the application, and in an alternative implementation, the embodiment of the application can derive the target use case parameters of the first target use case based on the seed use case, and iteratively derive the second derivative use case based on the first target use case. In an optional implementation, fig. 2 illustrates an optional flow of deriving the second derivative case provided in an embodiment of the present application, and as shown in fig. 2, the flow may include:
And step 200, in the first iteration, the target use case parameters in the first target use case are adjusted for a plurality of times, and a second derivative use case derived from the first iteration is obtained.
In the embodiment of the application, when iterating for the first time, the target use case parameters of the first target use case can be derived based on the seed use case, the target use case parameters in the first target use case are adjusted (such as modified) for a plurality of times based on the first target use case, so as to obtain the second derived use case derived by the first iteration, specifically, the target use case parameters in the first target use case are adjusted for a single time, so that one derived second derived use case can be obtained, and a plurality of derived second derived use cases can be obtained by adjusting the target use case parameters in the first target use case for a plurality of times.
For example, as shown in fig. 3, the use case parameters of the seed use case 1 are modified differently, so as to obtain first derivative use cases 11, 12, 13 and 14, and if the first derivative use case 13 is a first target use case, the first target use case is obtained by modifying the use case parameter M in the seed use case; that is, when the seed use case parameter M is modified, a use case offspring with a strong possibility of being suitable for the abnormal test is derived, and then, after the first target use case is obtained, the embodiment of the application can modify the use case parameter M in the first target use case as many times as possible based on the first target use case when the first target use case is iterated, so that more use case offspring with a strong possibility of being suitable for the abnormal test are inherited, and more use cases suitable for the abnormal test are mined from the use case offspring. For example, as shown in fig. 3, in the first iteration process, the embodiment of the present application may modify the use case parameter M in the first derivative use case 13 as many times as possible, to obtain the second derivative use cases 131,132,133 derived in the first iteration.
Step S210, when the iteration is not performed for the first time, determining a log chain generated by executing a test on the service system by the second derived use case derived from the previous iteration, determining a use case in which the log information of the log chain has new error information at least compared with the log information of the seed log chain in the second derived use case derived from the previous iteration, and performing multiple times of adjustment on the target use case parameters in the determined use case to obtain the second derived use case derived from the current iteration.
When the method is not used for the first iteration, the use case with the possibility of being suitable for abnormal test can be determined from the second derived use case derived from the last iteration; in an alternative implementation, the embodiment of the present application may perform a test on the service system by using the second derived case derived from the previous iteration, so as to obtain a generated log chain, compare the obtained log chain with the seed log chain, and if the log information of the log chain has new error information at least compared with the log information of the seed log chain, determine that the second derived case derived from the previous iteration with the log chain is a case suitable for the possibility of abnormal test. After determining a use case suitable for abnormal test possibility from the second derived use cases derived in the previous iteration, the embodiment of the application can adjust the target use case parameters in the use case for multiple times to obtain the second derived use cases derived in the current iteration.
For example, as shown in fig. 3, in the second iteration, if the second derivative case 132 is a case suitable for the possibility of the anomaly test in the second derivative case derived in the first iteration, the embodiment of the present application may modify the target case parameter M in the second derivative case 132 multiple times to obtain the second derivative case derived in the second iteration.
The embodiment of the application can set the iteration times of the iteration process, for example, the iteration times are set to be the set times, that is, the iteration ends after the set times are carried out, the specific numerical value of the set times can be set according to the actual situation, and the embodiment of the application is not limited.
Further, the embodiment of the application can determine the use case suitable for the anomaly test from the second derived use case derived from each iteration. In an alternative implementation, for a second derived use case derived for each iteration, embodiments of the present application may determine a second log chain generated by performing a test on a business system with the second derived use case; if program crash information exists in the log information of the second log chain, and/or if the log information of the second log chain is disordered due to process restarting, the second derivative use case with the second log chain can be determined to be the use case suitable for exception testing.
On the basis of determining the first target use case, the embodiment of the application can also provide other possible manners of deriving the second derived use case, and in an alternative implementation, the embodiment of the application can derive the target use case parameter of the first target use case based on the seed use case, and the target use case parameter in the seed use case is adjusted for multiple times to obtain the second derived use case derived from the seed use case; it can be understood that, if the first target use case is obtained by adjusting the target use case parameters of the seed use case, the embodiment of the present application may perform a homogeneous operation (i.e. perform multiple adjustments on the target use case parameters in the seed use case again) on the seed use case to obtain more use case offspring with a strong likelihood of being applicable to the anomaly test, so as to mine more use cases applicable to the anomaly test from the use case offspring. Based on a second derived use case derived from the seed use case, the embodiment of the application can determine a second log chain generated by executing a test on the service system by using the second derived use case, and if program crash information exists in log information of the second log chain and/or the log information of the second log chain is disordered due to process restarting, the embodiment of the application can determine that the second derived use case with the second log chain is a use case suitable for abnormal test.
In another alternative implementation, the target use case may be a second target use case, the second target use case having a moderate likelihood of being suitable for exception testing; after comparing a first log chain with a seed log chain, if the first log chain has new node branches compared with the seed log chain (it can be understood that the first log chain and the seed log chain can both represent execution nodes of a service system, so that the first log chain and the seed log chain can both have one or more execution node branches, where the embodiment of the application determines that the first log chain has redundant new execution node branches compared with the seed log chain), and the log information of the first log chain has new error information compared with the log information of the seed log chain, then the first derivative example with the first log chain is determined to be a second target example. Aiming at the second target use case, the embodiment of the application can execute the homogeneous operation of obtaining the second target use case on the seed use case to obtain more use case offspring with moderate possibility of being suitable for abnormal test. Optionally, fig. 4 shows another flow of the use case generating method provided by the embodiment of the present application, as shown in fig. 4, the flow may include:
step S300, obtaining seed use cases.
Step S310, deriving a first derived use case of the seed use case based on the use case parameters of the seed use case.
Step S320, determining a seed log chain generated by executing a test on the service system by using the seed use case, and determining a first log chain generated by executing a test on the service system by using the first derivative use case.
Step S330, comparing the seed log chain with the first log chain, if the first log chain has a new node branch compared with the seed log chain and the log information of the first log chain has new error information compared with the log information of the seed log chain, determining that the first derivative use case having the first log chain is the second target use case.
And step S340, determining target use case parameters of a second target use case derived from the seed use cases, and adjusting the target use case parameters of the seed use cases for a plurality of times to obtain a second derived use case derived from the seed use cases.
And step S350, determining a second log chain generated by executing the test on the service system by using the second derivative case.
Step S360, if program crash information exists in the log information of the second log chain, and/or the log information is disordered due to process restarting of the second log chain, determining that the second derived use case with the second log chain is a use case suitable for exception testing.
In the embodiment of the application, after the second target use case with moderate possibility of being suitable for the abnormal test is determined from the first derivative use case, the target use case parameters of the second target use case can be derived based on the seed use case, and multiple homogeneous operations of the second target use case can be obtained for the seed use case, so that more use case offspring with moderate possibility of being suitable for the abnormal test can be obtained, more use cases suitable for the abnormal test can be further mined from the use case offspring, and the range of the use cases suitable for the abnormal test can be enlarged and obtained by mining.
It may be understood that, if the log information of the first log chain does not have new error information compared with the log information of the seed log chain, the embodiment of the present application may determine that the first derivative case having the first log chain is a non-target case, and may not process the first derivative case of the non-target case; in a more specific optional implementation, if the first log chain is consistent with the execution node and the execution sequence of the seed log chain, and the log information of the first log chain has no new error information compared with the log information of the seed log chain, the first derivative case with the first log chain is a non-target case, and the non-target case does not have a possibility of being suitable for an abnormal test;
in other optional implementations, if the first log chain has a new node branch compared to the seed log chain and the log information of the first log chain does not have new error information compared to the log information of the seed log chain, the first derivative use case having the first log chain is a non-target use case.
In a more complete alternative implementation, fig. 5 illustrates a further flow of the use case generating method provided by the embodiment of the present application, as shown in fig. 5, where the flow may include:
Step S400, obtaining seed use cases.
Step S410, deriving a first derived use case of the seed use case based on the use case parameters of the seed use case.
Step S420, determining a seed log chain generated by executing a test on the service system by using the seed use case, and determining a first log chain generated by executing a test on the service system by using the first derivative use case.
Step S430, if program crash information exists in the log information of the first log chain, and/or the log information is disordered due to process restarting of the first log chain, determining that the first derived use case with the first log chain is a use case suitable for exception testing.
Step S440, if the execution nodes and the execution order of the first log chain are consistent with each other, and the log information of the first log chain has new error information compared with the log information of the seed log chain, determining the first derivative case having the first log chain as the first target case.
Step S450, deriving a target use case parameter of the first target use case at least based on the seed use case, and iteratively deriving a second derived use case based on the first target use case; and adjusting the target use case parameters of the first target use case derived from the seed use case for multiple times to obtain a second derived use case derived from the seed use case.
Aiming at the first target use case determined in the step S440, the embodiment of the application inherits more use case offspring with stronger possibility of being suitable for abnormal test through the target use case parameters based on the first target use case; for more specific iterative processes, reference is made to the descriptions of the corresponding parts above, and no further description is given here.
Meanwhile, the embodiment of the application can derive the target use case parameters of the first target use case based on the seed use case, and execute the homogeneous operation of obtaining the first target use case on the seed use case so as to obtain more use case offspring with stronger possibility of being suitable for abnormal test.
Step S460, if the first log chain has a new node branch compared with the seed log chain and the log information of the first log chain has new error information compared with the log information of the seed log chain, determining that the first derivative use case having the first log chain is the second target use case.
And step S470, adjusting the target use case parameters of the second target use case derived from the seed use case for a plurality of times to obtain a second derived use case derived from the seed use case.
For the second target use case determined in step S460, the embodiment of the present application may derive the target use case parameter of the second target use case based on the seed use case, and perform the homogeneous operation for obtaining the second target use case on the seed use case, so as to obtain more use case offspring with moderate possibility of being suitable for the anomaly test.
And step S480, determining a second log chain generated by executing the test on the service system by using the second derivative case.
Step S490, if there is program crash information in the log information of the second log chain, and/or if the log information of the second log chain is disordered due to process restart, determining that the second derived use case having the second log chain is a use case suitable for exception testing.
For the second derived use case derived in the embodiment of the present application, for example, based on the second derived use case derived in step S450 and/or step S470, the embodiment of the present application may perform a test on the service system by using the second derived use case to obtain a generated second log chain, and if program crash information exists in log information of the second log chain, and/or if the log information of the second log chain is disordered due to process restart, it may be determined that the second derived use case having the second log chain is a use case suitable for an exception test.
As further shown in fig. 5, the process may further include:
step S500, if the log information of the first log chain does not have new error information compared with the log information of the seed log chain, determining the first derivative use case with the first log chain as a non-target use case.
In the process of comparing the first log chain with the seed log chain, if the log information of the first log chain has no new error information compared with the log information of the seed log chain, the first derivative use case with the first log chain can be determined to be a non-target use case, and the non-target use case can be not processed by the embodiment of the application.
According to the embodiment of the application, the target use case parameters of the target use case are derived based on the seed use case, the second derived use case is further derived, the range of mining the use cases applicable to the abnormal test is enlarged, and compared with the use cases applicable to the abnormal test which are directly mined from the first derived use case derived from the seed use case, the use cases applicable to the abnormal test can be mined more, and the effect of efficiently and batched generating the use cases applicable to the abnormal test is realized. Meanwhile, by comparing the first log chain corresponding to the first derivative case with the seed log chain corresponding to the seed case, the embodiment of the application can determine the possibility that each first derivative case is suitable for the abnormal test, and carry out different subsequent treatments on the first derivative case with different possibilities, thereby achieving the effect of more accurately mining the case suitable for the abnormal test.
As an optional implementation, an embodiment of the present application may define a sharpening relation rule, where the sharpening relation rule may define log chain characteristics of a heterogeneous case and a target case, for example, the sharpening relation rule may at least define:
The log information of the use case is at least compared with the log information of the seed log chain, and the use case is a target use case; the definition of the second target use case may refer to the corresponding part of the foregoing, and will not be repeated here;
program crash information exists in the log information of the use case, and/or the log information is disordered due to process restarting, so that the use case is suitable for exception testing.
Based on the defined rule of the sharp relation, fig. 6 shows an example of an abnormal case generation process provided by the embodiment of the present application, referring to fig. 6:
After determining the seed use case, the embodiment of the application can derive the first derivative use case of the seed use case based on the seed use case;
Meanwhile, aiming at the seed use case, the embodiment of the application can execute the test on the service system based on the seed use case, collect the log information of the execution node of the service system when executing the test, and link the log information into a seed log chain according to the execution sequence of the execution node; for any first derivative case, the embodiment of the application can execute a test on the service system based on the first derivative case, thereby collecting log information of an execution node of the service system when the test is executed, and linking the log information into a first log chain according to the execution sequence of the execution node;
furthermore, the embodiment of the application can compare the first log chain with the seed log chain, and determine the use case applicable to the abnormal test from the first derivative use cases based on the preset rule of the sharp change relation, and has the target use case applicable to the possibility of the abnormal test, the non-target use case and the like;
For the determined target use case, the embodiment of the application can derive the target use case parameters of the target use case based on the seed use case, and carry out use case inheritance so as to derive a second derived use case; for example, for a first target use case, the embodiment of the present application may derive a target use case parameter of the first target use case based on the seed use case, iteratively derive a second derived use case based on the first target use case, and perform a homogeneous operation for deriving the first target use case on the seed use case to derive the second derived use case;
Based on the derived second derived use case, the embodiment of the application can determine a second log chain generated by executing the test on the service system by the second derived use case, and if program crash information exists in the second log chain and/or log information is disordered due to process restarting, the second derived use case with the second log chain is the use case suitable for abnormal test.
According to the embodiment of the application, the use cases suitable for the abnormal test are mined from the first derivative use cases, the use cases suitable for the abnormal test can be mined from the second derivative use cases further derivative, the range of the use cases suitable for the abnormal test can be widened, and the efficient batch generation of the use cases suitable for the abnormal test can be realized.
The foregoing describes several embodiments of the present application, 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 application disclosed and disclosed.
The description of the use case generating device provided by the embodiment of the present application 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 application. 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.
Optionally, fig. 7 shows a block diagram of a use case generating apparatus provided by an embodiment of the present application, as shown in fig. 7, where the apparatus may include:
a first deriving module 100, configured to obtain a first derived use case derived from a seed use case;
a log chain determining module 110, configured to determine a seed log chain generated by performing a test on the service system with the seed use case, and a first log chain generated by performing a test on the service system with the first derivative use case;
the target use case determining module 120 is configured to compare the seed log chain with the first log chain, and determine, from the first derivative use case, a target use case in which the log information of the first log chain has new error information at least compared with the log information of the seed log chain based on a result of the comparison;
A second deriving module 130, configured to derive a target use case parameter of the target use case based at least on the seed use case, and derive a second derived use case;
and the use case determining module 140 is configured to determine a use case that causes an abnormality in the service system from the second derivative use cases, where the use case is applicable to an abnormality test of the service system.
Optionally, the target use case determining module 120 is configured to determine, from the first derivative use cases, a target use case in which the log information of the first log chain has new error information at least compared to the log information of the seed log chain based on the result of the comparison, where the target use case includes:
If the first log chain is consistent with the execution node and the execution sequence of the seed log chain, and the log information of the first log chain has new error information compared with the log information of the seed log chain, determining a first derivative use case with the first log chain as a first target use case.
Optionally, based on the first target use case, the second deriving module 130 is configured to derive a target use case parameter of the target use case based at least on the seed use case, and derive a second derived use case, including:
And iteratively deriving a second derived use case based on the first target use case at least based on the target use case parameter.
Optionally, the second deriving module 130 is configured to iteratively derive a second derived case based on at least the target case parameter and based on the first target case, where the second derived case includes:
In the first iteration, the target use case parameters in the first target use case are adjusted for a plurality of times to obtain a second derived use case derived from the first iteration, wherein the target use case parameters in the first target use case are adjusted once to obtain a derived second derived use case;
and when the iteration is not the first time, determining a log chain generated by executing the test on the service system by the second derived case derived from the previous iteration, determining that the log information of the log chain is at least more than the case with new error information compared with the log information of the seed log chain in the second derived case derived from the previous iteration, and carrying out multiple times of adjustment on the target case parameters in the determined case to obtain the second derived case derived from the current iteration.
Optionally, in another optional implementation of the target use case, the target use case may be a second target use case; the target use case determining module 120, configured to determine, from the first derivative use cases, a target use case in which the log information of the first log chain has new error information at least compared to the log information of the seed log chain, based on the result of the comparison, includes:
And if the first log chain has new node branches compared with the seed log chain and the log information of the first log chain has new error information compared with the log information of the seed log chain, determining a first derivative use case with the first log chain as a second target use case.
In another optional implementation of deriving the second derivative case by the second deriving module 130 based on the first target case and/or the second target case, the second deriving module 130 is configured to derive the target case parameter of the target case based at least on the seed case, and derive the second derivative case includes:
And adjusting the target use case parameters in the seed use case for multiple times to obtain a second derivative use case derived from the seed use case.
Based on the obtained second derivative case, in an optional implementation, the case determining module 140 is configured to determine, from the second derivative case, a case that causes an abnormality in the service system, where the case includes:
Determining a second log chain generated by testing the service system by the second derivative case;
if program crash information exists in the log information of the second log chain, and/or the log information is disordered due to process restarting of the second log chain, determining that the second derived use case with the second log chain is the use case causing the exception of the service system.
Optionally, fig. 8 shows a further block diagram of a use case generating apparatus according to an embodiment of the present application, and in conjunction with fig. 7 and fig. 8, the apparatus may further include:
the use case direct determination module 150 is configured to determine that the first derivative use case having the first log chain is a use case that causes an exception in the service system if program crash information exists in log information of the first log chain and/or if the log information of the first log chain is disordered due to process restart.
Optionally, as shown in fig. 8, the use case generating apparatus may further include:
The non-target use case determining module 160 is configured to determine that the first derivative use case having the first log chain is a non-target use case if the log information of the first log chain does not have new error information compared to the log information of the seed log chain.
Optionally, the embodiment of the present application does not process the non-target use cases.
In an alternative implementation, the non-target use case determining module 160 is configured to determine that the first derivative use case having the first log chain is a non-target use case if the log information of the first log chain does not have new error information compared to the log information of the seed log chain, including:
If the first log chain is consistent with the execution node and the execution sequence of the seed log chain, and the log information of the first log chain has no new error information compared with the log information of the seed log chain, determining that a first derivative use case with the first log chain is a non-target use case;
And/or the number of the groups of groups,
And if the first log chain has new node branches compared with the seed log chain and the log information of the first log chain does not have new error information compared with the log information of the seed log chain, determining that the first derivative use case with the first log chain is a non-target use case.
Optionally, the first deriving module 100, configured to obtain a first derivative case derived from a seed case may include:
and obtaining a seed use case, and deriving a first derivative use case of the seed use case based on the use case parameters of the seed use case.
The use case generating device provided by the embodiment of the application can realize efficient and batch generation of the use cases suitable for the anomaly test.
The embodiment of the application also provides a server, and optionally, the server can load the use case generating device in a program form so as to realize the use case generating method provided by the embodiment of the application. In an alternative implementation, fig. 9 shows an alternative block diagram of a server provided by an embodiment of the present application, where, as shown in fig. 9, 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 application, 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; obviously, the communication connection illustrations of the illustrated processor 1, communication interface 2, memory 3 and communication bus 4 are only optional;
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 application, 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 application.
The embodiment of the application also provides a storage medium which can store one or more computer executable instructions for executing the use case generating method provided by the embodiment of the application.
Although the embodiments of the present application are disclosed above, the present application 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 application, and the scope of the application should be assessed accordingly to that of the appended claims.
Claims (14)
1. A use case generation method, wherein the method comprises:
Acquiring a first derivative case derived from a seed case;
Determining a seed log chain generated by executing a test on the service system by using the seed use case, and a first log chain generated by executing a test on the service system by using a first derivative use case;
Comparing the seed log chain with the first log chain, and determining a target use case of which the log information of the first log chain has new error information at least compared with the log information of the seed log chain from first derivative use cases based on a comparison result;
deriving a target use case parameter of the target use case based at least on the seed use case, and deriving a second derived use case;
and determining a use case which causes the business system to be abnormal from the second derivative use case, wherein the use case is suitable for the abnormal test of the business system.
2. The use case generating method according to claim 1, wherein the determining, from the first derivative use case, that the log information of the first log chain has new error information at least compared to the log information of the seed log chain based on the result of the comparison includes:
If the first log chain is consistent with the execution node and the execution sequence of the seed log chain, and the log information of the first log chain has new error information compared with the log information of the seed log chain, determining a first derivative use case with the first log chain as a first target use case.
3. The use case generating method according to claim 2, wherein the deriving the target use case parameter of the target use case based at least on the seed use case, the deriving the second derived use case includes:
And iteratively deriving a second derived use case based on the first target use case at least based on the target use case parameter.
4. A use case generating method according to claim 3, wherein said iteratively deriving a second derived use case based on said first target use case based at least on said target use case parameter comprises:
In the first iteration, the target use case parameters in the first target use case are adjusted for a plurality of times to obtain a second derived use case derived from the first iteration, wherein the target use case parameters in the first target use case are adjusted once to obtain a derived second derived use case;
and when the iteration is not the first time, determining a log chain generated by executing the test on the service system by the second derived case derived from the previous iteration, determining that the log information of the log chain is at least more than the case with new error information compared with the log information of the seed log chain in the second derived case derived from the previous iteration, and carrying out multiple times of adjustment on the target case parameters in the determined case to obtain the second derived case derived from the current iteration.
5. The use case generating method according to claim 1, wherein the determining, from the first derivative use case, that the log information of the first log chain has new error information at least compared to the log information of the seed log chain based on the result of the comparison includes:
And if the first log chain has new node branches compared with the seed log chain and the log information of the first log chain has new error information compared with the log information of the seed log chain, determining a first derivative use case with the first log chain as a second target use case.
6. The use case generating method according to claim 2 or 5, wherein the deriving the target use case parameter of the target use case based at least on the seed use case, the deriving the second derived use case includes:
And adjusting the target use case parameters in the seed use case for multiple times to obtain a second derivative use case derived from the seed use case.
7. The use case generating method according to claim 1, wherein the determining, from the second derivative use cases, a use case that causes an abnormality in a business system includes:
Determining a second log chain generated by testing the service system by the second derivative case;
if program crash information exists in the log information of the second log chain, and/or the log information is disordered due to process restarting of the second log chain, determining that the second derived use case with the second log chain is the use case causing the exception of the service system.
8. The use case generating method according to claim 1, wherein the method further comprises:
if program crash information exists in the log information of the first log chain, and/or the log information is disordered due to process restarting of the first log chain, determining a first derivative use case with the first log chain as a use case for causing the exception of the service system.
9. The use case generating method according to claim 1, wherein the method further comprises:
And if the log information of the first log chain does not have new error information compared with the log information of the seed log chain, determining that the first derivative use case with the first log chain is a non-target use case.
10. The use case generating method according to claim 9, wherein the determining that the first derivative use case having the first log chain is a non-target use case if the log information of the first log chain does not have new error information compared to the log information of the seed log chain includes:
If the first log chain is consistent with the execution node and the execution sequence of the seed log chain, and the log information of the first log chain has no new error information compared with the log information of the seed log chain, determining that a first derivative use case with the first log chain is a non-target use case;
And/or the number of the groups of groups,
And if the first log chain has new node branches compared with the seed log chain and the log information of the first log chain does not have new error information compared with the log information of the seed log chain, determining that the first derivative use case with the first log chain is a non-target use case.
11. The use case generating method according to claim 1, wherein the acquiring the first derivative use case derived from the seed use case includes:
and obtaining a seed use case, and deriving a first derivative use case of the seed use case based on the use case parameters of the seed use case.
12. A use case generating apparatus, wherein the apparatus comprises:
The first deriving module is used for obtaining a first deriving use case derived from the seed use case;
the log chain determining module is used for determining a seed log chain generated by executing a test on the service system by using the seed use case and a first log chain generated by executing the test on the service system by using a first derivative use case;
the target use case determining module is used for comparing the seed log chain with the first log chain, and determining a target use case in which the log information of the first log chain has new error information at least compared with the log information of the seed log chain from the first derivative use case based on a comparison result;
The second deriving module is used for deriving the target use case parameters of the target use case at least based on the seed use case and deriving a second derived use case;
And the use case determining module is used for determining the use case which causes the business system to be abnormal from the second derivative use case, and the use case is suitable for the abnormal test of the business system.
13. A server, wherein the server comprises: at least one memory and at least one processor; the memory stores one or more computer-executable instructions that the processor invokes to perform the use case generation method of any of claims 1-11.
14. A storage medium, wherein the storage medium stores one or more computer-executable instructions, the one or more computer-executable instructions are for performing the use case generation method of any of claims 1-11.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010504770.5A CN113297063B (en) | 2020-06-05 | 2020-06-05 | Use case generation method, device, server and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010504770.5A CN113297063B (en) | 2020-06-05 | 2020-06-05 | Use case generation method, device, server and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113297063A CN113297063A (en) | 2021-08-24 |
| CN113297063B true CN113297063B (en) | 2024-11-05 |
Family
ID=77318108
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010504770.5A Active CN113297063B (en) | 2020-06-05 | 2020-06-05 | Use case generation method, device, server and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113297063B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113297058A (en) * | 2020-04-27 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Case generation method, test method, device and server |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113297058A (en) * | 2020-04-27 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Case generation method, test method, device and server |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140325278A1 (en) * | 2013-04-25 | 2014-10-30 | Verizon Patent And Licensing Inc. | Method and system for interactive and automated testing between deployed and test environments |
| CN106339312B (en) * | 2015-07-17 | 2021-01-12 | 腾讯科技（深圳）有限公司 | API test method and system |
| CN110908888B (en) * | 2018-09-17 | 2023-06-30 | 百度在线网络技术（北京）有限公司 | Server testing method and device |
| CN110737584A (en) * | 2019-08-30 | 2020-01-31 | 深圳壹账通智能科技有限公司 | Service data testing method and device based on block chain and computer equipment |
| CN110727597B (en) * | 2019-10-15 | 2023-03-10 | 杭州安恒信息技术股份有限公司 | Method for checking invalid code completion case based on log |
-
2020
- 2020-06-05 CN CN202010504770.5A patent/CN113297063B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113297058A (en) * | 2020-04-27 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Case generation method, test method, device and server |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113297063A (en) | 2021-08-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3101841B1 (en) | Method, system and computer readable medium for network management automation | |
| CN114124567A (en) | Cloud service processing method based on big data vulnerability mining and artificial intelligence system | |
| Georgoulakos et al. | Evolutionary multi-objective optimization of business process designs with pre-processing | |
| CN111459796B (en) | Automated testing method, apparatus, computer device and storage medium | |
| CN113297063B (en) | Use case generation method, device, server and storage medium | |
| JP6888737B2 (en) | Learning devices, learning methods, and programs | |
| CN116028886A (en) | BIM-based data processing method, system and cloud platform | |
| CN114527974B (en) | Method and device for realizing business function of software product and computer equipment | |
| Kaur et al. | Various techniques to detect and predict faults in software system: survey | |
| CN113918374B (en) | Root cause analysis method, device and equipment of operation and maintenance system | |
| CN108446220B (en) | Test case generation method and device | |
| CN113711265A (en) | Block chain transaction tracing method and device | |
| CN113064674B (en) | Method and device for expanding state machine logic, storage medium and electronic device | |
| WO2012115007A1 (en) | Fault tree analysis system, fault tree analysis method and programme | |
| Cristescu et al. | Flexible framework for stimuli redundancy reduction in functional verification using artificial neural networks | |
| CN117729119A (en) | Equipment operation data processing method and system for edge computing gateway | |
| US11636132B1 (en) | Systems and methods for automatically deriving data transformation criteria | |
| US11520691B2 (en) | Test procedure systems and methods | |
| CN112015633B (en) | Test excitation multi-platform multiplexing method, device, equipment and storage medium | |
| CN115796228A (en) | Operator fusion method, device, equipment and storage medium | |
| CN114662116A (en) | Service operation vulnerability searching method based on big data and cloud deep learning system | |
| CN113297058A (en) | Case generation method, test method, device and server | |
| Kaen et al. | Feature selection approach for improving the accuracy of software bug prediction | |
| Pomares-Angelino et al. | Automated modelling of deadlock-free petri nets using duplicated transition labels | |
| CN106227878B (en) | Searching method and device |
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 |