Test scenario generation method, device, electronic device and computer storage medium

Abstract

The present application provides a method, device, electronic device and computer storage medium for generating a test scenario, the method comprising: first, obtaining user operation information of each user using the tested software; then, performing correlation analysis on every two functions in the tested software according to the user operation information of the user, and obtaining analysis results; then, performing statistics on typical user operations and atypical user operations, and obtaining the use scenario of the tested software, the use frequency of typical user operations under the use scenario of the tested software, and the use frequency of atypical user operations; finally, generating a test scenario of the tested software according to the use scenario of the tested software, the use frequency of typical user operations under the use scenario of the tested software, and the use frequency of atypical user operations. The generated test scenario can be made more targeted, and the noise data generated by user misoperation under large data volume can be effectively eliminated.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a method, device, electronic device and computer storage medium for generating a test scenario. Background Art

[0002] At present, in the process of testing and designing customer-oriented software systems, test design methods such as equivalence class, boundary value, and scenario method are usually used. The scenario method is to simulate the scenario when the user operates the software, which is mainly used to test the combined use of multiple functions. This test design method relies on the tester's in-depth understanding of the software business. When the number of single software functions increases and the business process becomes more and more complex, it is difficult to ensure the quality of test case design and the consistency of test cases designed by different testers. Summary of the invention

[0003] In view of this, the present application provides a method, device, electronic device and computer storage medium for generating a test scenario, which can make the generated test scenario more targeted and effectively eliminate the noise data generated by user errors under large amounts of data. Subsequently, the causes of user errors can be analyzed through statistics of atypical operations to guide the optimization of the software system user interface.

[0004] The first aspect of the present application provides a method for generating a test scenario, comprising:

[0005] For each user who uses the software under test, user operation information of the user is obtained; wherein the user operation information includes information of each operation performed by the user from opening the software under test to closing the software under test;

[0006] Performing a correlation analysis on every two functions in the tested software according to the user operation information of the user to obtain an analysis result; wherein the analysis result includes: the first function is related to the second function or the first function is not related to the second function; the first function is any function in the tested software; the second function is any function in the tested software except the first function;

[0007] The typical user operations and the atypical user operations are counted to obtain the usage scenario of the tested software, the usage frequency of the typical user operations in the usage scenario of the tested software, and the usage frequency of the atypical user operations; wherein the atypical user operations are operations that include both the unrelated first function and the second function; and the typical user operations are operations other than the atypical user operations;

[0008] A test scenario for the software under test is generated according to the usage scenario of the software under test, the usage frequency of the typical user operations in the usage scenario of the software under test, and the usage frequency of the atypical user operations.

[0009] Optionally, performing a correlation analysis on every two functions in the tested software according to the user operation information of the user to obtain an analysis result includes:

[0010] According to the functions and sequence used by the user from opening the software under test to closing the software under test, a function correlation matrix of the software under test is obtained;

[0011] For every two functions in the function correlation matrix of the tested software, calculating the correlation between the two functions;

[0012] Determining whether the correlation between the two functions is less than a threshold;

[0013] If it is determined that the correlation between the two functions is less than a threshold value, then it is determined that the two functions are not correlated;

[0014] If it is determined that the correlation between the two functions is not less than the threshold, it is determined that the two functions are correlated.

[0015] Optionally, the counting of typical user operations and atypical user operations to obtain usage scenarios of the tested software, usage frequencies of the typical user operations in the usage scenarios of the tested software, and usage frequencies of the atypical user operations include:

[0016] Scenarios where the functions used by users, the order in which the functions are used, the return status of each function, and the failure information of failed functions are consistent are counted as one usage scenario;

[0017] For each of the usage scenarios, based on all typical user operations and atypical user operations, statistics are obtained to obtain the usage frequency of the typical user operations and the usage frequency of the atypical user operations in the usage scenario.

[0018] Optionally, the threshold is set or changed in advance by a technician.

[0019] A second aspect of the present application provides a test scenario generation device, including:

[0020] An acquisition unit, configured to acquire user operation information of each user who uses the software under test; wherein the user operation information includes information of each operation performed by the user from opening the software under test to closing the software under test;

[0021] an analysis unit, configured to perform a correlation analysis on every two functions in the tested software according to the user operation information of the user, and obtain an analysis result; wherein the analysis result includes: the first function is related to the second function or the first function is not related to the second function; the first function is any function in the tested software; the second function is any function in the tested software except the first function;

[0022] A statistical unit, used to collect statistics on typical user operations and atypical user operations to obtain usage scenarios of the tested software, usage frequencies of the typical user operations in the usage scenarios of the tested software, and usage frequencies of the atypical user operations; wherein the atypical user operations are operations that include both unrelated first functions and second functions; and the typical user operations are operations other than the atypical user operations;

[0023] A generating unit is used to generate a test scenario for the software under test according to a usage scenario of the software under test, a usage frequency of the typical user operation in the usage scenario of the software under test, and a usage frequency of the atypical user operation.

[0024] Optionally, the analysis unit includes:

[0025] A matrix determination unit, used to obtain a function correlation matrix of the software under test according to the functions and sequence used by the user from opening the software under test to closing the software under test;

[0026] A calculation unit, used for calculating the correlation between two functions for each two functions in the function correlation matrix of the software under test;

[0027] A judging unit, used to judge whether the correlation between the two functions is less than a threshold;

[0028] a determining unit, configured to determine that the two functions are not correlated if the determining unit determines that the correlation between the two functions is less than a threshold;

[0029] The determining unit is further configured to determine that the two functions are correlated if the judging unit determines that the correlation between the two functions is not less than a threshold value.

[0030] Optionally, the statistical unit includes:

[0031] The first statistical subunit is used to count scenarios where the functions used by the user, the order of using the functions, the return status of each function, and the failure information of the failed function are consistent as the same usage scenario;

[0032] The second statistical subunit is used for obtaining, for each of the usage scenarios, the usage frequency of the typical user operations and the usage frequency of the atypical user operations in the usage scenario based on all the typical user operations and the atypical user operations.

[0033] Optionally, the threshold is set or changed in advance by a technician.

[0034] A third aspect of the present application provides an electronic device, including:

[0035] one or more processors;

[0036] a storage device having one or more programs stored thereon;

[0037] When the one or more programs are executed by the one or more processors, the one or more processors implement the test scenario generation method as described in any one of the first aspects.

[0038] A fourth aspect of the present application provides a computer storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the method for generating a test scenario as described in any one of the first aspects is implemented.

[0039] It can be seen from the above scheme that the present application provides a method, device, electronic device and computer storage medium for generating a test scenario, wherein the method for generating a test scenario comprises: first, for each user using the software under test, obtaining the user operation information of the user; wherein the user operation information comprises the information of each operation of the user from opening the software under test to closing the software under test; then, according to the user operation information of the user, a correlation analysis is performed on every two functions in the software under test to obtain an analysis result; wherein the analysis result comprises: the first function is related to the second function or the first function is not related to the second function; the first function is any one function in the software under test; The second function is any function in the tested software except the first function; then the typical user operations and atypical user operations are counted to obtain the usage scenario of the tested software, the usage frequency of the typical user operations in the usage scenario of the tested software, and the usage frequency of the atypical user operations; wherein the atypical user operations are operations that simultaneously include the unrelated first function and second function; the typical user operations are operations other than the atypical user operations; finally, according to the usage scenario of the tested software, the usage frequency of the typical user operations in the usage scenario of the tested software, and the usage frequency of the atypical user operations, the test scenario of the tested software is generated. The generated test scenario can be made more targeted, and the noise data generated by user misoperation under large data volume can be effectively excluded. In the future, the causes of user misoperation can be analyzed through statistics of atypical operations to guide the optimization of the software system user interface. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0041] Figure 1 A specific flow chart of a method for generating a test scenario provided in an embodiment of the present application;

[0042] Figure 2 A specific flow chart of a method for function correlation analysis provided by another embodiment of the present application;

[0043] Figure 3 A specific flow chart for obtaining statistics on usage scenarios of the tested software, usage frequencies of typical user operations in the usage scenarios of the tested software, and usage frequencies of atypical user operations in another embodiment of the present application;

[0044] Figure 4 A schematic diagram of a test scenario generation device provided in another embodiment of the present application;

[0045] Figure 5 A schematic diagram of an analysis unit provided in another embodiment of the present application;

[0046] Figure 6 A schematic diagram of a statistical unit provided in another embodiment of the present application;

[0047] Figure 7 A schematic diagram of an electronic device for implementing a method for generating a test scenario provided in another embodiment of the present application. DETAILED DESCRIPTION

[0048] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0049] It should be noted that the concepts of "first", "second", etc. mentioned in this application are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units, and the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "including one..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0050] The present application embodiment provides a method for generating a test scenario, such as Figure 1 As shown, the specific steps include:

[0051] S101. For each user who uses the software under test, obtain user operation information of the user.

[0052] The user operation information includes information about each operation performed by the user from opening the software under test to closing the software under test, for example: the user's session identifier, the functions used, the time each function was used, the return status of each function, and the specific failure information of the failed function, etc.

[0053] S102: performing a correlation analysis on every two functions in the tested software according to the user operation information, and obtaining an analysis result.

[0054] The analysis results include: the first function is related to the second function or the first function is not related to the second function; the first function is any function in the tested software; the second function is any function in the tested software except the first function.

[0055] Optionally, in another embodiment of the present application, an implementation of step S102 is as follows: Figure 2 As shown, including:

[0056] S201. Obtain a function correlation matrix of the software under test according to the functions and sequence used by the user from opening to closing the software under test.

[0057] S202: For every two functions in the function correlation matrix of the tested software, calculate the correlation between the two functions.

[0058] The calculation formula for calculating the correlation between two functions is: the number of times a user uses both function A and function B in one login / the number of times a user uses function A)*100%.

[0059] S203: Determine whether the correlation between the two functions is less than a threshold.

[0060] The threshold is set or changed in advance by the technicians, and its value is not limited.

[0061] Specifically, if it is determined that the correlation between the two functions is less than the threshold, step S204 is executed; if it is determined that the correlation between the two functions is not less than the threshold, step S205 is executed.

[0062] S204: Determine that the two functions are not related.

[0063] S205: Determine whether two functions are related.

[0064] S103 , collecting statistics on typical user operations and atypical user operations to obtain usage scenarios of the tested software, usage frequencies of typical user operations in the usage scenarios of the tested software, and usage frequencies of atypical user operations.

[0065] The atypical user operation is an operation that includes both an unrelated first function and a second function; and the typical user operation is an operation other than the atypical user operation.

[0066] Specifically, after all atypical user operations are marked, all remaining user operations are marked as typical user operations.

[0067] Optionally, in another embodiment of the present application, an implementation of step S103 is as follows: Figure 3 As shown, including:

[0068] S301. Count the scenarios in which the functions used by the user, the order in which the functions are used, the return status of each function, and the failure information of the failed functions are all the same as the same usage scenario.

[0069] S302: For each usage scenario, based on all typical user operations and atypical user operations, obtain statistics on the usage frequency of typical user operations and the usage frequency of atypical user operations in the usage scenario.

[0070] S104: Generate a test scenario for the software under test according to the usage scenario of the software under test, the usage frequency of typical user operations in the usage scenario of the software under test, and the usage frequency of atypical user operations.

[0071] It can be understood that in the specific implementation process of this application, the test scenario of the software under test is generated.

[0072] It can be seen from the above scheme that the present application provides a method for generating a test scenario: first, for each user who uses the software under test, obtain the user's user operation information; wherein the user operation information includes information about each operation performed by the user from opening the software under test to closing the software under test; then, according to the user operation information of the user, perform a correlation analysis on every two functions in the software under test to obtain an analysis result; wherein the analysis result includes: the first function is related to the second function or the first function is not related to the second function; the first function is any function in the software under test; the second function is any function in the software under test except the first function; then, perform statistics on typical user operations and atypical user operations to obtain the use scenario of the software under test, the use frequency of typical user operations in the use scenario of the software under test, and the use frequency of atypical user operations; wherein the atypical user operation is an operation that includes both the unrelated first function and the second function; the typical user operation is an operation other than a typical user operation; finally, according to the use scenario of the software under test, the use frequency of typical user operations in the use scenario of the software under test, and the use frequency of atypical user operations, generate a test scenario for the software under test. This can make the generated test scenarios more targeted and effectively eliminate the noise data generated by user errors under large amounts of data. Subsequently, the causes of user errors can be analyzed through statistics of atypical operations to guide the optimization of the software system user interface.

[0073] Another embodiment of the present application provides a device for generating a test scenario, such as Figure 4 As shown, specifically including:

[0074] The acquisition unit 401 is used to acquire user operation information of each user who uses the software under test.

[0075] The user operation information includes information about each operation performed by the user from opening the software under test to closing the software under test.

[0076] The analyzing unit 402 is used to perform a correlation analysis on every two functions in the tested software according to the user operation information of the user to obtain an analysis result.

[0077] The analysis results include: the first function is related to the second function or the first function is not related to the second function; the first function is any function in the tested software; the second function is any function in the tested software except the first function.

[0078] Optionally, in another embodiment of the present application, an implementation of the analysis unit 402 is as follows: Figure 5 As shown, including:

[0079] The matrix determination unit 501 is used to obtain a function correlation matrix of the software under test according to the functions and sequence used by the user in the process from opening the software under test to closing the software under test.

[0080] The calculation unit 502 is used to calculate the correlation between two functions for each two functions in the function correlation matrix of the tested software.

[0081] The judging unit 503 is used to judge whether the correlation between two functions is less than a threshold.

[0082] The threshold is set or changed in advance by the technicians, and its value is not limited.

[0083] The determination unit 504 is configured to determine that the two functions are not correlated if the determination unit 503 determines that the correlation between the two functions is less than a threshold value.

[0084] The determining unit 504 is further configured to determine that the two functions are correlated if the determining unit 503 determines that the correlation between the two functions is not less than a threshold value.

[0085] For the specific working process of the units disclosed in the above embodiments of the present application, please refer to the corresponding method embodiments, such as Figure 2 As shown, no further description is given here.

[0086] The statistical unit 403 is used to collect statistics on typical user operations and atypical user operations to obtain usage scenarios of the tested software, usage frequencies of typical user operations in the usage scenarios of the tested software, and usage frequencies of atypical user operations.

[0087] The atypical user operation is an operation that includes both an unrelated first function and a second function; and the typical user operation is an operation other than the atypical user operation.

[0088] Optionally, in another embodiment of the present application, an implementation of the statistical unit 403 is as follows: Figure 6 As shown, including:

[0089] The first statistical subunit 601 is used to count scenarios in which the functions used by the user, the order of using the functions, the return status of each function, and the failure information of the failed functions are all the same as the same usage scenario.

[0090] The second statistical subunit 602 is used for obtaining the usage frequency of typical user operations and the usage frequency of atypical user operations in each usage scenario based on all typical user operations and atypical user operations.

[0091] For the specific working process of the units disclosed in the above embodiments of the present application, please refer to the corresponding method embodiments, such as Figure 3 As shown, no further description is given here.

[0092] The generating unit 404 is used to generate a test scenario for the software under test according to the usage scenario of the software under test, the usage frequency of typical user operations in the usage scenario of the software under test, and the usage frequency of atypical user operations.

[0093] For the specific working process of the units disclosed in the above embodiments of the present application, please refer to the corresponding method embodiments, such as Figure 1 As shown, no further description is given here.

[0094] It can be seen from the above scheme that the present application provides a test scenario generation device: first, the acquisition unit 401 acquires the user operation information of each user who uses the tested software; wherein the user operation information includes the information of each operation of the user from opening the tested software to closing the tested software; then, the analysis unit 402 performs a correlation analysis on every two functions in the tested software according to the user operation information of the user to obtain an analysis result; wherein the analysis result includes: the first function is related to the second function or the first function is not related to the second function; the first function is any function in the tested software; the second function is any function in the tested software except any function except the first function; the statistical unit 403 then counts the typical user operations and the atypical user operations to obtain the usage scenario of the tested software, the usage frequency of the typical user operations under the usage scenario of the tested software, and the usage frequency of the atypical user operations; wherein the atypical user operation is an operation that includes the unrelated first function and the second function at the same time; the typical user operation is an operation other than the atypical user operation; finally, the generating unit 404 generates the test scenario of the tested software according to the usage scenario of the tested software, the usage frequency of the typical user operations under the usage scenario of the tested software, and the usage frequency of the atypical user operations. The generated test scenario can be made more targeted, and the noise data generated by the user's misoperation under large data volume can be effectively excluded. In the future, the causes of the user's misoperation can be analyzed by statistics of atypical operations to guide the optimization of the software system user interface.

[0095] Another embodiment of the present application provides an electronic device, such as Figure 7 As shown, including:

[0096] One or more processors 701.

[0097] The storage device 702 stores one or more programs.

[0098] When the one or more programs are executed by the one or more processors 701, the one or more processors 701 implement the method for generating a test scenario as described in any one of the above embodiments.

[0099] Another embodiment of the present application provides a computer storage medium on which a computer program is stored, wherein when the computer program is executed by a processor, the method for generating a test scenario as described in any one of the above embodiments is implemented.

[0100] In the above embodiments disclosed in the present application, it should be understood that the disclosed apparatus and method can also be implemented in other ways. The apparatus and method embodiments described above are merely schematic. For example, the flowcharts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the apparatus, method and computer program product according to multiple embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of a code, and the module, program segment or a part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of boxes in the block diagram and / or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.

[0101] In addition, each functional module in each embodiment of the present disclosure can be integrated together to form an independent part, or each module can exist separately, or two or more modules can be integrated to form an independent part. If the function is implemented in the form of a software functional module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present disclosure is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including several instructions to enable a computer device (which can be a personal computer, a live broadcast device, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present disclosure. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, RandomAccess Memory), disk or optical disk and other media that can store program code.

[0102] The present application can be implemented or used by professionals and technicians. Various modifications to these embodiments will be apparent to professionals and technicians in the field, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for generating a test scenario, characterized in that: include: For each user who uses the software under test, user operation information of the user is obtained; wherein the user operation information includes information of each operation performed by the user from opening the software under test to closing the software under test; Performing a correlation analysis on every two functions in the tested software according to the user operation information of the user to obtain an analysis result; wherein the analysis result includes: the first function is related to the second function or the first function is not related to the second function; the first function is any function in the tested software; the second function is any function in the tested software except the first function; The typical user operations and the atypical user operations are counted to obtain the usage scenario of the tested software, the usage frequency of the typical user operations in the usage scenario of the tested software, and the usage frequency of the atypical user operations; wherein the atypical user operations are operations that include both the unrelated first function and the second function; and the typical user operations are operations other than the atypical user operations; Generate a test scenario for the software under test according to the usage scenario of the software under test, the usage frequency of the typical user operation in the usage scenario of the software under test, and the usage frequency of the atypical user operation; Wherein, the correlation analysis is performed on every two functions in the tested software according to the user operation information of the user, and the analysis results obtained include: According to the functions and sequence used by the user from opening the software under test to closing the software under test, a function correlation matrix of the software under test is obtained; For every two functions in the function correlation matrix of the tested software, calculating the correlation between the two functions; Determining whether the correlation between the two functions is less than a threshold; If it is determined that the correlation between the two functions is less than a threshold value, then it is determined that the two functions are not correlated; If it is determined that the correlation between the two functions is not less than the threshold, it is determined that the two functions are correlated.

2. The generation method according to claim 1, characterized in that: The counting of typical user operations and atypical user operations to obtain the usage scenario of the tested software, the usage frequency of the typical user operations in the usage scenario of the tested software, and the usage frequency of the atypical user operations include: Scenarios where the functions used by users, the order in which the functions are used, the return status of each function, and the failure information of failed functions are consistent are counted as one usage scenario; For each of the usage scenarios, based on all typical user operations and atypical user operations, statistics are obtained to obtain the usage frequency of the typical user operations and the usage frequency of the atypical user operations in the usage scenario.

3. The generation method according to claim 1, characterized in that: The threshold is set or changed in advance by a technician.

4. A test scenario generating device, characterized in that: include: An acquisition unit, configured to acquire user operation information of each user who uses the software under test; wherein the user operation information includes information of each operation performed by the user from opening the software under test to closing the software under test; an analysis unit, configured to perform a correlation analysis on every two functions in the tested software according to the user operation information of the user, and obtain an analysis result; wherein the analysis result includes: the first function is related to the second function or the first function is not related to the second function; the first function is any function in the tested software; the second function is any function in the tested software except the first function; A statistical unit, used to collect statistics on typical user operations and atypical user operations to obtain usage scenarios of the tested software, usage frequencies of the typical user operations in the usage scenarios of the tested software, and usage frequencies of the atypical user operations; wherein the atypical user operations are operations that include both unrelated first functions and second functions; and the typical user operations are operations other than the atypical user operations; A generating unit, configured to generate a test scenario for the software under test according to a usage scenario of the software under test, a usage frequency of the typical user operation in the usage scenario of the software under test, and a usage frequency of the atypical user operation; Wherein, the analysis unit comprises: A matrix determination unit, used to obtain a function correlation matrix of the software under test according to the functions and sequence used by the user from opening the software under test to closing the software under test; A calculation unit, used for calculating the correlation between two functions for each two functions in the function correlation matrix of the software under test; A judging unit, used to judge whether the correlation between the two functions is less than a threshold; a determining unit, configured to determine that the two functions are not correlated if the determining unit determines that the correlation between the two functions is less than a threshold; The determining unit is further configured to determine that the two functions are correlated if the judging unit determines that the correlation between the two functions is not less than a threshold value.

5. The generating device according to claim 4, characterized in that: The statistical unit comprises: The first statistical subunit is used to count scenarios where the functions used by the user, the order of using the functions, the return status of each function, and the failure information of the failed function are consistent as the same usage scenario; The second statistical subunit is used for obtaining, for each of the usage scenarios, the usage frequency of the typical user operations and the usage frequency of the atypical user operations in the usage scenario based on all the typical user operations and the atypical user operations.

6. The generating device according to claim 5, characterized in that The threshold is set or changed in advance by a technician.

7. An electronic device, characterized in that: include: one or more processors; a storage device having one or more programs stored thereon; When the one or more programs are executed by the one or more processors, the one or more processors implement the test scenario generation method as described in any one of claims 1 to 3.

8. A computer storage medium, characterized in that: A computer program is stored thereon, wherein when the computer program is executed by a processor, the method for generating a test scenario as claimed in any one of claims 1 to 3 is implemented.

Images