Test case regression method, device and equipment, medium and product
By classifying system-level chip regression test cases and generating yaml format files, efficient regression testing in complex verification environments is achieved, solving the problem of low regression test cases management and efficiency in complex chip verification, and improving verification efficiency and File management clarity.
Patent Information
- Application Number
- CN202411124590.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-15
- Publication Date
- 2024-12-31
AI Technical Summary
In a complex system-on-chip verification environment, how to efficiently perform differentiated management and quickly regress a large number of regression test cases, collect regression results and coverage have become a huge challenge for verification engineers.
Classify them by compiling options based on regression test cases and generate regression test files in yaml format to generate simulation executable files of multiple regression types. These files are used for regression testing, and support running different types in parallel in the same workspace regression test cases simplify file management and operation processes.
It realizes unified management and personalized management of regression test cases, improves regression testing efficiency, shortens verification cycle, simplifies file management mode, and improves the efficiency of regression testing engineering of system-level chips.
Smart Images
Figure CN119226066A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of regression testing, and in particular to a test case regression method, device, equipment, medium and product. Background Art
[0002] In recent years, integrated circuits have been in a stage of rapid development. Major chip design companies have been working tirelessly to shorten the time to market for chips. However, as the scale of chips continues to expand, how to ensure the correctness and completeness of chip functions has become a huge challenge for verification engineers. In order to accelerate verification, the industry has also proposed a series of verification methods.
[0003] In the chip field, SOC (System on Chip) is called system-level chip, which has obvious advantages in performance, cost, power consumption, reliability, life cycle and scope of application, so it is an inevitable trend in the development of integrated circuit design. The composition of system-level chip can be system-level chip control logic module, microprocessor / microcontroller CPU core module, digital signal processor DSP module, embedded memory module, interface module for external communication, analog front-end module containing ADC / DAC, power supply and power consumption management module, etc. The increasingly complex system-level chip will inevitably correspond to more and more complex SOC verification.
[0004] Due to different compilation and simulation requirements, when regressing SOC test cases, it is necessary to manage the test cases differently. In a complex SOC verification environment, how to manage a large number of regression test cases differently and regress quickly, and collect regression results and coverage has become a huge challenge for verification engineers. Summary of the invention
[0005] Based on the above technical problems, the embodiments of the present application provide a test case regression method, device, equipment, medium and product, aiming at how to simplify and efficiently perform regression testing.
[0006] A first aspect of an embodiment of the present application provides a test case regression method, the method comprising:
[0007] Classify regression test cases based on their compilation options;
[0008] Add regression test cases of multiple regression types to a regression list and generate a regression test file in yaml format;
[0009] When a compile operation is detected, generating multiple regression-type simulation executable files based on the regression test file;
[0010] Perform regression testing using simulation executables of multiple regression types.
[0011] Optionally, the method further comprises:
[0012] When it is detected that the state of the workspace is running, the pre-stored regression test file is read to generate simulation executable files of multiple regression types;
[0013] Perform regression testing using simulation executables for multiple regression types, including:
[0014] Regression testing is performed in the workspace using simulation executables of multiple regression types.
[0015] Optionally, regression testing can be performed using simulation executables of multiple regression types, including:
[0016] A first regression test case belonging to the first regression type and a second regression test case belonging to the second regression type are run in parallel using a simulation executable file of the first regression type and a simulation executable file of the second regression type, so as to implement regression testing of the first regression test case and the second regression test case at the same time.
[0017] Optionally, add regression test cases of multiple regression types to a regression list and generate a regression test file in yaml format, including:
[0018] Add descriptive text for each of the multiple regression types;
[0019] Configure compilation macros for each of the multiple regression types separately;
[0020] A regression test code line is configured for each regression type among the multiple regression types, and each regression test case belonging to the type is defined under the regression test code line configured for the type.
[0021] Optionally, when a compile operation is detected, multiple regression-type simulation executable files are generated based on the regression test file, including:
[0022] identifying a compilation macro configured in the regression test file for each of the plurality of regression types;
[0023] When a compilation macro of a first regression test type is identified, a first simulation executable file with the first regression test type as the file name is generated, and when a compilation macro of a second regression test type is identified, a second simulation executable file with the second regression test type as the file name is generated.
[0024] Optionally, a regression test code line is configured for each regression type of the multiple regression types, and each regression test case belonging to the type is defined under the regression test code line configured for the type, including:
[0025] For each regression test case of the same type, define personalized setting parameters of the regression test case, wherein the personalized setting parameters include at least the following items: the number of times the regression test case is run, simulation process options, case description, and post-processing options after the simulation is completed;
[0026] Perform regression testing using simulation executables for multiple regression types, including:
[0027] For each regression type of simulation executable file, regression testing is performed on the first regression test case according to the first personalized setting parameters of the first regression test case belonging to the type, and regression testing is performed on the second regression test case according to the second personalized setting parameters of the second regression test case belonging to the type.
[0028] A second aspect of an embodiment of the present application provides a test case regression device, the device comprising:
[0029] The classification module classifies regression test cases based on their compilation options;
[0030] The regression test file generation module adds regression test cases of multiple regression types to a regression list and generates a regression test file in yaml format;
[0031] A simulation executable file generation module, which generates simulation executable files of multiple regression types based on the regression test file when a compile operation is detected;
[0032] The regression testing module uses simulation executable files of various regression types to perform regression testing.
[0033] Optionally, the classification module includes:
[0034] The regression test file reading submodule reads the pre-stored regression test file to generate simulation executable files of multiple regression types when detecting that the state of the workspace is running;
[0035] The workspace running submodule uses multiple regression types of simulation executable files to perform regression testing, including: using multiple regression types of simulation executable files to perform regression testing in the workspace;
[0036] Optionally, the regression testing module includes:
[0037] The parallel regression test submodule uses the simulation executable file of the first regression type and the simulation executable file of the second regression type to run the first regression test case belonging to the first regression type and the second regression test case belonging to the second regression type in parallel, so as to achieve regression testing of the first regression test case and the second regression test case at the same time.
[0038] Optionally, the regression test file generation module includes:
[0039] A description text adding submodule is used to add description text to each regression type among multiple regression types;
[0040] A compilation macro configuration submodule configures compilation macros for each of the multiple regression types;
[0041] The code line configuration submodule configures a regression test code line for each regression type among the multiple regression types, and defines each regression test case belonging to the type under the regression test code line configured for the type.
[0042] Optionally, the simulation executable file generation module includes:
[0043] A compile macro identification submodule, identifying the compile macros respectively configured for each regression type in the regression test file;
[0044] The simulation executable file parallel generation submodule generates a first simulation executable file with the first regression test type as the file name when a compilation macro of a first regression test type is identified, and generates a second simulation executable file with the second regression test type as the file name when a compilation macro of a second regression test type is identified.
[0045] Optionally, the regression test file generation module further includes:
[0046] The personalized setting submodule defines personalized setting parameters of each regression test case belonging to the same type, and the personalized setting parameters include at least the following items: the number of times the regression test case is run, the simulation process options, the case description, and the post-processing options after the simulation is completed.
[0047] Optionally, the regression testing module further includes:
[0048] The personalized test submodule performs regression testing on the first regression test case according to the first personalized setting parameters of the first regression test case belonging to the type for the simulation executable file of each regression type, and performs regression testing on the second regression test case according to the second personalized setting parameters of the second regression test case belonging to the type.
[0049] A third aspect of an embodiment of the present application provides an electronic device, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the computer program is executed by the processor, a test case regression method as in the first aspect of an embodiment of the present application is implemented.
[0050] A fourth aspect of an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the test case regression method of the first aspect of the embodiment of the present application is implemented.
[0051] Through the test case regression method of the embodiment of the present application, regression test cases are classified based on the compilation options of the regression test cases; regression test cases of multiple regression types are added to a regression list to generate a regression test file in yaml format; when a compilation operation is detected, simulation executable files of multiple regression types are generated based on the regression test file; and regression testing is performed using the simulation executable files of multiple regression types.
[0052] In this embodiment, the application classifies regression test cases based on the compilation options of the regression test cases, adds them to a regression list, generates a regression test file in yaml format, and generates multiple regression types of simulation executable files based on the regression test file when the compilation operation is detected, and then uses the multiple regression types of simulation executable files to perform regression testing. In this way, the regression test cases are unified into a clearly structured regression test file, and various regression test cases can be regression tested at the same time, which simplifies the file management mode, speeds up the regression test process, and greatly improves the efficiency of the regression test engineering of the system-level chip. BRIEF DESCRIPTION OF THE DRAWINGS
[0053] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the description of the embodiments of the present application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.
[0054] Figure 1 It is a flow chart of a test case regression method proposed in one embodiment of the present application;
[0055] Figure 2 It is a structural block diagram of a test case regression device proposed in one embodiment of the present application;
[0056] Figure 3It is a schematic diagram of an electronic device proposed in an embodiment of the present application. DETAILED DESCRIPTION
[0057] 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 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.
[0058] In the drawings, the size of the constituent elements, the thickness of the layer or the area may be exaggerated for the sake of clarity. Therefore, any implementation of the present disclosure is not necessarily limited to the size shown in the drawings, and the shapes and sizes of the components in the drawings do not reflect the true proportions. In addition, the drawings schematically show ideal examples, and any implementation of the present disclosure is not limited to the shapes or values shown in the drawings.
[0059] Please refer to Figure 1 , Figure 1 This is a flow chart of a test case regression method of the present application. Figure 1 As shown, the method may include steps S101 to S104:
[0060] Step S101: classifying regression test cases based on compilation options of regression test cases;
[0061] Step S102: adding regression test cases of multiple regression types to a regression list to generate a regression test file in yaml format;
[0062] Step S103: when a compile operation is detected, generating multiple regression-type simulation executable files based on the regression test file;
[0063] Step S104: Perform regression testing using simulation executable files of multiple regression types.
[0064] In the prior art, when faced with complex SOC regression test cases, the method usually chosen is to manage regression test cases by compiling regressions separately according to different compilation requirements. This not only generates multiple regression test files that need to be maintained, but also the differences between each regression test file are small, and additional management tables need to be drawn up to clearly distinguish them. Moreover, when performing regression testing, if there are multiple regression test files, since the workspace used for compilation is limited, the usual practice in the prior art is to input different regression test files into the workspace. After a regression test file is completed, the previous compilation is cleared, and a new regression test file is input to recompile for subsequent regression testing. This method not only makes the management of regression test files chaotic, but also slows down the operation process of regression testing. Therefore, the present application proposes a method of generating a regression test file in yaml format, uniformly managing all regression test cases according to the regression test case compilation options, and generating multiple simulation executable files corresponding to the regression type in the same workspace. Since only one regression test file in yaml format is managed, the structure is clear and easy to understand, and the management confusion caused by multiple regression test case files is effectively avoided; at the same time, due to the properties of the regression test file in yaml format, different regression test cases can be managed in a personalized manner, which improves the efficiency of regression test case management. When performing regression testing, various regression tests can be performed smoothly and continuously through the same workspace, which greatly improves the regression testing efficiency of the verifier, thereby shortening the verification cycle of the regression test.
[0065] Step S101: classifying regression test cases based on compilation options of the regression test cases.
[0066] In this embodiment, since complex SOC regression test cases have different compilation requirements and correspond to different compilation options, in order to uniformly and standardizedly manage all regression test cases, it is necessary to first classify the regression test cases that need to be compiled by the same compilation macro according to different compilation options, thereby naturalizing each regression test case into multiple groups of regression case sets with different compilation options.
[0067] Step S102: adding regression test cases of multiple regression types to a regression list to generate a regression test file in yaml format.
[0068] In the prior art, when faced with regression tests with multiple regression types, verifiers usually add test cases to multiple regression lists according to different regression types to generate multiple regression test files. However, in actual operations, the multiple regression test files generated in this way are confusing to manage and complex to operate.
[0069] In this application, a method is proposed to add each regression test case in multiple different regression types to the same regression list, generate a regression test file in yaml format, and classify and integrate each regression test case required for regression testing into it. Therefore, the structure is clear and the management is convenient. According to different regression types, a collection of multiple regression test cases is classified and named, and a custom description can be added according to the specific classification method, and a custom implementation method can be added according to the specific implementation process.
[0070] For example, as shown in the following code, according to different regression types, each regression test case is divided into N sets, namely: type1, type2, ..., typeN, which are distinguished by "regression_type:" in the regression test file. Each paragraph is followed by a specific description and implementation method of the regression test case under the regression type.
[0071]
[0072]
[0073]
[0074] Step S103: when a compile operation is detected, multiple regression-type simulation executable files are generated based on the regression test file.
[0075] In the prior art, during the regression test, the verification personnel usually input the first regression test file into the workspace, generate the corresponding first simulation executable file simv for testing, and after the test is completed, clear the workspace, and then input the second regression test file into the workspace to generate the second simulation executable file simv, wherein the simulation executable files are usually named the same and are successively overwritten during the regression test process. In this way, the files that need to be managed are not very clear, and there are also multiple repeated steps in the entire operation process, which makes the entire regression testing process not smooth and inefficient.
[0076] In this embodiment, after obtaining the regression test file in yaml format in the above steps, a simulation executable file can be generated in the workspace according to the regression test file. The simulation executable file is a file that needs to be run when performing a specific regression test operation. According to the different regression types in the regression test file, multiple different simulation executable files will be generated accordingly. The verification personnel can name the simulation executable file according to the corresponding regression type for standardized management, so that the file management and operation processes are clearer, smoother and more efficient.
[0077] For example, taking the above code as an example, since the newly generated regression test file contains all the regression test cases, and in step S102, it has been divided into type1-typeN, a total of N regression test case sets according to the regression type, after the regression test file is input into the workspace, corresponding N simulation executable files can be generated, and they are named simv.type1, simv.type2, ..., simv.typeN according to their corresponding regression types. In this way, the regression test case sets, regression test files and simulation executable files are all corresponded one by one, forming a clear and coherent file management mode.
[0078] Step S104: Perform regression testing using simulation executable files of multiple regression types.
[0079] In the prior art, as described in step S103, when performing regression testing including multiple regression types, different regression test files need to be input into the workspace in sequence, corresponding simulation executable files are generated, and then regression testing is performed. In the present application, since multiple groups of corresponding simulation executable files have been generated according to different regression use cases in step S103, multiple groups of simulation executable files can be run simultaneously during regression testing, and there is no need to perform secondary input of regression test files, which reduces the complexity of the verification personnel's operation and greatly improves the work efficiency of regression testing.
[0080] In combination with the above embodiments, in one implementation, the present application further provides a test case regression method, in which the above step S101 specifically further includes the following contents:
[0081] First, when it is detected that the state of the workspace is running, the pre-stored regression test file is read to generate simulation executable files of multiple regression types.
[0082] The regression test file needs to be input into the workspace before subsequent operation processes can be carried out, and the problems faced in the prior art also arise from this. Usually, the workspace available to the verifier is extremely limited. Therefore, in the process of using the prior art for regression testing, it is necessary to replace the regression test file to generate simulation executable files that are covered in sequence, so as to complete multiple regression tests of different regression types in a limited workspace.
[0083] In the present application, since the regression test file contains various regression test cases, only one workspace is required. By inputting the regression test file into the workspace once, various simulation executable files of different regression types required for this regression test can be generated when the workspace is running, and they are named according to orderly rules, so that the regression test files and simulation executable files under complex conditions are clear and orderly.
[0084] Then, the regression test is performed using simulation executable files of multiple regression types, including: performing the regression test in the workspace using simulation executable files of multiple regression types.
[0085] In the prior art, since there is only one regression test file inputted into the workspace each time, there is only one corresponding simulation executable file generated. After the regression test files of other regression types are inputted, a new simulation executable file is generated. Therefore, in the workspace, there is only one simulation executable file running each time.
[0086] In the present application, since the regression test file input into the workspace includes all regression test cases, the generated simulation executable file is all files corresponding to each regression type. Therefore, in the workspace, at least one simulation executable file can be executed simultaneously according to the needs of actual operations, thereby improving the work efficiency of the verification personnel and being more selective.
[0087] In combination with the above embodiments, in one implementation, the present application further provides a test case regression method, in which the above step S104 specifically further includes the following contents:
[0088] A first regression test case belonging to the first regression type and a second regression test case belonging to the second regression type are run in parallel using a simulation executable file of the first regression type and a simulation executable file of the second regression type, so as to implement regression testing of the first regression test case and the second regression test case at the same time.
[0089] In the prior art, since regression test files are multiple files generated according to different regression types, when input into the workspace, all regression test cases included in the input belong to the same regression type.
[0090] In the present embodiment, as mentioned above, since the regression test file contains various regression test cases of this regression test, multiple simulation executable files can be obtained after the regression test file is input into the workspace. In the process of regression testing, since there are multiple different simulation executable files in the same workspace, different regression types of test cases can be selected for operation according to the needs of the verification personnel, and when the workspace conditions permit, different test cases can be simulated and tested at the same time. Therefore, the present application can achieve the technical effect that the prior art cannot achieve, that is, regression testing can be performed on test cases of different regression types at the same time.
[0091] For example, as shown in the above code, in the prior art, only the regression test case with the regression type of type1 can be run in one simulation test, and then the regression test case with the regression type of type2 can be run in the next simulation test; while in the present application, the test case No. 0 type1_testcase0 with the regression type of type1 and the test case No. 1 typeN_testcase1 with the regression type of typeN can be run simultaneously in one simulation test.
[0092] In combination with the above embodiments, in one implementation, the present application further provides a test case regression method, in which the above step S102 specifically further includes the following contents:
[0093] First, add descriptive text for each of the multiple regression types.
[0094] In the prior art, regression test files are usually managed by distinguishing them through simple file naming. A relatively clearer way is to choose to add a management table to describe the regression test files corresponding to each regression type.
[0095] In this application, through the regression test file in yaml format, personalized descriptions can be added to each regression type, which is convenient for verification personnel to understand and operate, and also makes file management clearer.
[0096] For example, in the above code, each regression type is described in detail through the description: command line. The verifier can know the specific content of the corresponding regression type by browsing the content described in the regression test file, which is clearer and easier to understand when checking.
[0097] Then, configure the compilation macros separately for each of the multiple regression types.
[0098] In the present application, for each regression test case set of each regression type, corresponding compilation macros are configured in the regression test file to distinguish the compilations, and simulation executable files corresponding to each regression type are generated according to the different defined compilation macros.
[0099] For example, in the above code, the compilation macros are distinguished for each regression type through the build_opts: command line. After the regression test file is input into the workspace, the corresponding simv.type1-simv.typeN simulation executable files can be generated according to the different compilation macros.
[0100] Finally, a regression test code line is configured for each regression type among the multiple regression types, and each regression test case belonging to the type is defined under the regression test code line configured for the type.
[0101] In the present application, since the regression test file contains multiple regression types, it is necessary to distinguish different regression types in the regression test file, and then place each regression test case under the code line belonging to the corresponding regression type based on the classification described in step S101, so as to complete the classification of each regression test case.
[0102] For example, in the above code, each regression type is distinguished by the command line of regression_type:, such as regression_type:typeN is a set of regression test cases with regression type typeN, and all regression test cases of this type are configured under this regression test code line.
[0103] In combination with the above embodiments, in one implementation, the present application further provides a test case regression method, in which the above step S102 specifically further includes the following contents:
[0104] First, a compilation macro configured for each regression type in the regression test file is identified.
[0105] In the present application, after the regression test file is input into the workspace, the regression test file needs to be compiled to obtain a simulation executable file for running. Since different regression types are configured with different compilation macros, it is necessary to identify the compilation macro corresponding to each regression type before compilation can be performed.
[0106] Then, when the compilation macro of the first regression test type is identified, a first simulation executable file with the first regression test type as the file name is generated, and when the compilation macro of the second regression test type is identified, a second simulation executable file with the second regression test type as the file name is generated.
[0107] In the prior art, since the regression test file only contains regression test cases of one regression type, only a compilation macro of one regression type is configured in each regression test file. In the present application, since the regression test file contains multiple different regression types, when the workspace recognizes the compilation macro of the first regression test type, the first simulation executable file of the first regression type corresponding to the compilation macro will be generated, and then when the workspace recognizes the compilation macro of the second regression test type, the second simulation executable file of the second regression type corresponding to the compilation macro will be generated. In this way, by traversing the regression test file, the compilation macros corresponding to all the regression types therein can be compiled to generate simulation executable files corresponding to each regression type.
[0108] In combination with the above embodiments, in one implementation, the present application further provides a test case regression method, in which the above step S102 specifically further includes the following contents:
[0109] For each regression test case of the same type, the personalized setting parameters of the regression test case are defined, and the personalized setting parameters include at least the following items: the number of times the regression test case is run, the simulation process options, the case description, and the post-processing options after the simulation is completed.
[0110] In the prior art, if a regression test file needs to be described, in addition to a simple distinction in the file name, it can only be described by attaching an additional description document. In the present application, by modifying the command lines in each classified test case through the regression test file, a personalized description of each regression test can be achieved.
[0111] Furthermore, during the running of regression testing, a certain regression test case requires special operation steps. In the prior art, the operation is usually performed on all regression test cases in the entire regression test file, or special instructions are given through additional scripts to test the regression test case alone. In the present application, additional tests can be performed in a targeted manner by personalizing the regression test cases.
[0112] For example, if some use cases in the test involve random variables, they need to be run multiple times to ensure that the test is sufficient, while some use cases do not involve random variables and can be run only once. In this application, the run_opts: command line can be used to specify the number of times each use case is run to save regression testing time.
[0113] It should be noted that the above personalized parameters are only used as examples in this embodiment, and the specific parameters should be based on actual conditions.
[0114] In combination with the above embodiments, in one implementation, the present application further provides a test case regression method, in which the above step S104 specifically further includes the following contents:
[0115] For each regression type of simulation executable file, regression testing is performed on the first regression test case according to the first personalized setting parameters of the first regression test case belonging to the type, and regression testing is performed on the second regression test case according to the second personalized setting parameters of the second regression test case belonging to the type.
[0116] As described in the above steps, in the present application, since different personalized parameters are set for each regression test case, during the regression test process, different regression test parameters should be selected for each regression test case to perform personalized testing.
[0117] Based on the same design concept, an embodiment of the present application provides a test case regression device. Figure 2 , Figure 2 1 is a structural block diagram of a test case regression device provided by an embodiment of the present application. Figure 2 As shown, the device comprises:
[0118] The classification module classifies regression test cases based on their compilation options;
[0119] The regression test file generation module adds regression test cases of multiple regression types to a regression list and generates a regression test file in yaml format;
[0120] A simulation executable file generation module, which generates simulation executable files of multiple regression types based on the regression test file when a compile operation is detected;
[0121] The regression testing module uses simulation executable files of various regression types to perform regression testing.
[0122] Optionally, the classification module includes:
[0123] The regression test file reading submodule reads the pre-stored regression test file to generate simulation executable files of multiple regression types when detecting that the state of the workspace is running;
[0124] The workspace running submodule uses multiple regression types of simulation executable files to perform regression testing, including: using multiple regression types of simulation executable files to perform regression testing in the workspace;
[0125] Optionally, the regression testing module includes:
[0126] The parallel regression test submodule uses the simulation executable file of the first regression type and the simulation executable file of the second regression type to run the first regression test case belonging to the first regression type and the second regression test case belonging to the second regression type in parallel, so as to achieve regression testing of the first regression test case and the second regression test case at the same time.
[0127] Optionally, the regression test file generation module includes:
[0128] A description text adding submodule is used to add description text to each regression type among multiple regression types;
[0129] A compilation macro configuration submodule configures compilation macros for each of the multiple regression types;
[0130] The code line configuration submodule configures a regression test code line for each regression type among the multiple regression types, and defines each regression test case belonging to the type under the regression test code line configured for the type.
[0131] Optionally, the simulation executable file generation module includes:
[0132] A compile macro identification submodule, identifying the compile macros respectively configured for each regression type in the regression test file;
[0133] The simulation executable file parallel generation submodule generates a first simulation executable file with the first regression test type as the file name when a compilation macro of a first regression test type is identified, and generates a second simulation executable file with the second regression test type as the file name when a compilation macro of a second regression test type is identified.
[0134] Optionally, the regression test file generation module further includes:
[0135] The personalized setting submodule defines personalized setting parameters of each regression test case belonging to the same type, and the personalized setting parameters include at least the following items: the number of times the regression test case is run, the simulation process options, the case description, and the post-processing options after the simulation is completed.
[0136] Optionally, the regression testing module further includes:
[0137] The personalized test submodule performs regression testing on the first regression test case according to the first personalized setting parameters of the first regression test case belonging to the type for the simulation executable file of each regression type, and performs regression testing on the second regression test case according to the second personalized setting parameters of the second regression test case belonging to the type.
[0138] Based on the same design concept, another embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps in the test case regression method described in any of the above embodiments of the present application are implemented.
[0139] Based on the same design concept, another embodiment of the present application provides an electronic device, such as Figure 3 shown. Figure 3 This is a schematic diagram of an electronic device shown in an embodiment of the present application. The electronic device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes, the steps in the test case regression method described in any of the above embodiments of the present application are implemented.
[0140] As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.
[0141] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.
[0142] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, devices, or computer program products. Therefore, the embodiments of the present application may adopt the form of complete hardware embodiments, complete software embodiments, or embodiments in combination with software and hardware. Moreover, the embodiments of the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.
[0143] The embodiments of the present application are described with reference to the flowcharts and / or block diagrams of the methods, terminal devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing terminal device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing terminal device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0144] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing terminal device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0145] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal device so that a series of operating steps are executed on the computer or other programmable terminal device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable terminal device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.
[0146] Although the preferred embodiments of the present application have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the embodiments of the present application.
[0147] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or terminal 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 terminal device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or terminal device including the elements.
[0148] The above is a detailed introduction to a test case regression method, device, equipment, medium and product provided by the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for general technical personnel in this field, according to the idea of the present application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.
Claims
1. A test case regression method, comprising: Classify regression test cases based on their compilation options; Add regression test cases of multiple regression types to a regression list and generate a regression test file in yaml format; When a compile operation is detected, generating multiple regression-type simulation executable files based on the regression test file; Perform regression testing using simulation executables of multiple regression types.
2. A test case regression method according to claim 1, characterized in that: The method further comprises: When it is detected that the state of the workspace is running, the pre-stored regression test file is read to generate simulation executable files of multiple regression types; Perform regression testing using simulation executables for multiple regression types, including: Regression testing is performed in the workspace using simulation executables of multiple regression types.
3. A test case regression method according to claim 1, characterized in that: Perform regression testing using simulation executables for multiple regression types, including: A first regression test case belonging to the first regression type and a second regression test case belonging to the second regression type are run in parallel using a simulation executable file of the first regression type and a simulation executable file of the second regression type, so as to implement regression testing of the first regression test case and the second regression test case at the same time.
4. A test case regression method according to claim 1, characterized in that: Add regression test cases of multiple regression types to a regression list and generate a regression test file in yaml format, including: Add descriptive text for each of the multiple regression types; Configure compilation macros for each of the multiple regression types separately; A regression test code line is configured for each regression type among the multiple regression types, and each regression test case belonging to the type is defined under the regression test code line configured for the type.
5. A test case regression method according to claim 4, characterized in that: When a compile operation is detected, multiple regression-type simulation executable files are generated based on the regression test file, including: identifying a compilation macro configured in the regression test file for each of the plurality of regression types; When a compilation macro of a first regression test type is identified, a first simulation executable file with the first regression test type as the file name is generated, and when a compilation macro of a second regression test type is identified, a second simulation executable file with the second regression test type as the file name is generated.
6. A test case regression method according to claim 4, characterized in that: Also includes: For each regression test case of the same type, define personalized setting parameters of the regression test case, wherein the personalized setting parameters include at least the following items: the number of times the regression test case is run, simulation process options, case description, and post-processing options after the simulation is completed; Perform regression testing using simulation executables for multiple regression types, including: For each regression type of simulation executable file, regression testing is performed on the first regression test case according to the first personalized setting parameters of the first regression test case belonging to the type, and regression testing is performed on the second regression test case according to the second personalized setting parameters of the second regression test case belonging to the type.
7. A test case regression device, characterized in that: The device comprises: The classification module classifies regression test cases based on their compilation options; The regression test file generation module adds regression test cases of multiple regression types to a regression list and generates a regression test file in yaml format; A simulation executable file generation module, which generates simulation executable files of multiple regression types based on the regression test file when a compile operation is detected; The regression testing module uses simulation executable files of various regression types to perform regression testing.
8. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the computer program is executed by the processor, the test case regression method according to any one of claims 1 to 6 is implemented.
9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the test case regression method according to any one of claims 1 to 6 is implemented.
10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the test case regression method according to any one of claims 1 to 6 is implemented.