A method for performing simulation testing based on Excel tables

Abstract

The invention discloses a method for performing simulation testing based on an Excel table, and relates to the technical field of computer application. The method includes using an Excel table to carry test cases, analyzing columns in the Excel table through a PERL script, automatically extracting parameters and generating test cases; automatically performing phased inspections through the screening function of the Excel table to check the test status of the test cases; creating basic test cases in the Excel table and creating derivative test cases; specifying specific simulation parameters and conditions for each derivative test case, and allocating an identifier and a parameter set for each derivative test case; the invention adopts an automation method combining an Excel table with a Perl script to solve the complexity of test case management under a traditional Linux system, and realizes efficient organization of test cases, automatic extraction of key parameters, rapid monitoring of test status, and accurate quantification of test case differences.

Description

Technical Field

[0001] The invention relates to the technical field of computer application, and in particular to a method for performing simulation testing based on an Excel table. Background Art

[0002] In traditional verification tests, test cases are an important part of verification platforms such as UVM / OVM, which are used to complete tests for different system characteristics. As the system scale expands and the number of characteristics increases, more test cases need to be created to cover the testing requirements of the entire system. However, due to the inconvenience of document management in the Linux system, it is difficult to achieve effective document management when the number of test cases is large, which further aggravates the difficulty of test case management and maintenance. Summary of the invention

[0003] The purpose of the present invention is to provide a method for executing simulation test based on Excel table, which adopts the automation method of Excel table combined with Perl script to solve the complexity of test case management under traditional Linux system.

[0004] The purpose of the present invention can be achieved through the following technical solutions:

[0005] The present application provides a method for performing simulation testing based on an Excel spreadsheet, comprising the following steps:

[0006] Use Excel tables to carry test cases, analyze columns in Excel tables through PERL scripts, and automatically extract key parameters;

[0007] Among them, the key parameters include hardware macros, software macros, simulation parameters and whether to perform regression testing; according to the extracted key parameters, the corresponding test modules are automatically selected and corresponding test cases are generated for writing into Excel tables and performing reading and classification processing;

[0008] Through the filtering function of the Excel table, you can automatically perform periodic checks to view the test status of specific test cases, and filter the modified features of the current project based on whether the test case is a modification point;

[0009] By creating basic test cases in Excel tables, derivative test cases are created for the test cases of the same feature to optimize the test process; the basic test cases serve as templates and contain common test logic and initialization settings;

[0010] The method comprises creating a basic test case in an Excel spreadsheet, wherein the basic test case includes common test logic and initialization settings, and creating a Sheet to create a derivative test case for the test case of the same feature, wherein the derivative test case inherits the common logic and initialization settings of the basic test case, and then introduces new simulation parameters and conditions according to specific test requirements;

[0011] By specifying specific simulation parameters and conditions for each derived test case in Excel, and assigning a unique identifier and parameter set to each derived test case.

[0012] Furthermore, before the extracted key parameters automatically select the corresponding test modules, the method further includes: importing the Excel table into a perl script program, and calling the perl script program to parse the data structure of the Excel table.

[0013] Furthermore, the extracted key parameters automatically select corresponding test modules, specifically including: according to the hardware macro in the key parameters, determining the hardware module corresponding to the hardware macro from multiple hardware modules; according to the software macro in the key parameters, determining the software module corresponding to the software macro from multiple software modules; according to the simulation parameters in the key parameters, determining the simulation model corresponding to the simulation parameters from multiple simulation models; according to whether regression testing is performed in the key parameters, determining the regression test template corresponding to the regression testing from multiple regression test templates; and combining the determined hardware modules, software modules, simulation models and regression test templates to obtain a complete test module.

[0014] Furthermore, corresponding test cases are generated for writing into Excel tables and performing reading and classification processing, including:

[0015] Write multiple test cases into an Excel table; read the Excel table to obtain multiple cells in the Excel table, each cell corresponding to a test case; judge each row of data in the Excel table, if it is detected that the data in the row is a title, skip the row and continue to judge the next row; if it is detected that the row is a blank row, skip the row and continue to judge the next row; if it is detected that the row is not a title and is not a blank row, read the content of the i-th cell of the row from left to right, and determine the type of the row, wherein, when the i-th cell belongs to any type of test module, use the content of the i-1th cell as the file name, and use the content of the i-th cell as the search string; if there is no unprocessed cell in the Excel table, end this loop.

[0016] Furthermore, the modified features of the current project are filtered according to whether the test case is a modification point, including saving the data in the Excel table to a local folder, and using the use case description in the Excel table to identify and obtain the differences between different test cases through the test case description.

[0017] Furthermore, the string similarity measurement method of Levenshtein distance is used to calculate the differences between different test cases, including:

[0018] Set the strings of the two test cases to and , Levenshtein distance is the minimum number of operations to transform s into t by inserting, deleting, or replacing operations;

[0019] create The matrix D, where express arrive Levenshtein distance, initialize the first row and first column as:

[0020]

[0021] For i from 1 to n and j from 1 to m, update the matrix according to the following rules:

[0022]

[0023] in represents the minimum number of edits required to convert the substring of string s from index i-1 to index i into the first j characters of string t, followed by a deletion operation; represents the minimum number of edits required to convert the first i characters of string s into a substring of string t from index j-1 to index j, followed by an insertion operation; represents the minimum number of edits required to convert the string s from index i-1 to the substring at index i into the string t from index j-1 to the substring at index j, when ,but , no replacement operation is required, when ,but , needs to be replaced once;

[0024] According to the calculated , is the minimum number of edits required to convert the entire string s to t, which is the Levenshtein distance.

[0025] Furthermore, new simulation parameters and conditions are introduced according to specific test requirements, including:

[0026] A unique case ID is assigned to each derived test case, and the new simulation parameters and conditions are bound to a specific test case through the case ID; wherein the derived test case is used to refine the test conditions and expected results for a specific test point, and the case ID includes a prefix and an incremental number.

[0027] Furthermore, the steps also include: reducing the compilation scale according to the hardware macro selection, and integrating the empty shell module into the test environment for simulation testing.

[0028] The beneficial effects of the present invention are:

[0029] (1) The automation method of combining Excel tables with Perl scripts solves the complexity of test case management in traditional Linux systems, realizes efficient organization of test cases, automatic extraction of key parameters, rapid monitoring of test status, and accurate quantification of test case differences. By creating basic and derivative test cases, the test process is optimized and duplication of work is reduced. At the same time, the Levenshtein distance algorithm is used to measure the similarity between test cases, further improving the efficiency of test case maintenance.

[0030] (2) By optimizing the simulation environment design and reducing the coupling between test cases through hardware macro selection and shell module integration, the compilation scale is reduced and the simulation test speed is accelerated. This method ensures that the test cases can run independently, solves the problem of inconsistent test results and unreliability caused by high coupling between test cases, ensures that each test case can run independently and provide accurate test results, improves test accuracy, and provides reliable test results under various conditions, while reducing the risk of test failure. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] For better understanding and implementation, the technical solution of the present application is described in detail below with reference to the accompanying drawings.

[0032] Figure 1 A flowchart of a method for performing simulation testing based on an Excel spreadsheet provided in Example 1 of the present application;

[0033] Figure 2 A flowchart of automatically selecting corresponding test modules for extracting key parameters according to a method for performing simulation tests based on an Excel spreadsheet provided in Example 1 of the present application;

[0034] Figure 3A flowchart of writing an Excel spreadsheet and performing reading and classification processing for a method for performing simulation testing based on an Excel spreadsheet provided in Example 1 of the present application. DETAILED DESCRIPTION

[0035] In order to further explain the technical means and effects taken by the present invention to achieve the predetermined invention purpose, exemplary embodiments will be described in detail here, and examples thereof are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are only examples of methods and systems consistent with some aspects of the present application as detailed in the attached claims.

[0036] The terms used in this application are for the purpose of describing specific embodiments only and are not intended to limit this application. The singular forms of "a", "said" and "the" used in this application and the appended claims are also intended to include plural forms unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0037] The specific implementation methods, features and effects of the present invention are described in detail below in conjunction with the accompanying drawings and preferred embodiments.

[0038] Example 1

[0039] See also Figure 1-Figure 3 This embodiment provides a method for performing simulation testing based on Excel tables, which uses an automated method combining Excel tables with Perl scripts to solve the complexity of test case management under traditional Linux systems.

[0040] The present invention provides a method for performing simulation testing based on an Excel spreadsheet, comprising the following steps:

[0041] S1. Use Excel tables to carry test cases, analyze columns in the Excel tables through PERL scripts, and automatically extract key parameters, where the key parameters include hardware macros, software macros, simulation parameters, and whether regression testing is performed, etc.; automatically select corresponding test modules (tb.f) according to the extracted key parameters and generate corresponding test cases for writing into Excel tables and performing reading and classification processing;

[0042] Specifically, the Excel table is parsed using a Perl script: the Excel table is imported into the PERL script program, and the script extracts and processes key parameters by parsing the data structure.

[0043] By using Excel spreadsheets to carry test cases, you can quickly build a test framework, reduce errors caused by human factors, and improve test efficiency and accuracy; at the same time, by reading and classifying Excel spreadsheets, the test process is more flexible and more scalable.

[0044] S2. Through the filtering function of Excel tables, automatic periodic checks are performed to view the test status of specific test cases, and the modified features of the current project are filtered based on whether the test case is a modification point, which facilitates key coverage and review.

[0045] Specifically, the filtering function of Excel spreadsheets is used to automatically perform periodic checks to view the current status of specific test cases. This process pays special attention to test cases marked as modification points, which represent features that have been updated or changed in the project and need to be covered and reviewed first. Through this method, the team can focus resources and attention on the most critical test areas, ensure that the modified features are thoroughly verified, and improve the efficiency and effectiveness of the overall testing process.

[0046] S3. By creating basic test cases in Excel tables, derivative test cases are created for the test cases of the same feature to optimize the test process, such as memory control register, which can reduce the number of test cases and simplify the inheritance and modification work between projects.

[0047] Among them, the basic test case serves as a template, which contains common test logic and initialization settings.

[0048] S4. By specifying specific simulation parameters and conditions for each derived test case in Excel and assigning a unique identifier and parameter set to each derived test case, the coupling between test cases is reduced, the targeting and efficiency of the test are improved, and each test case is ensured to run independently and provide accurate test results.

[0049] Among them, the derived test cases target specific test points and refine the test conditions and expected results.

[0050] S5. Reduce the compilation scale according to the hardware macro selection, integrate the empty shell module into the test environment for simulation testing, reduce the risk of the simulation environment, reduce the test time, and improve the overall efficiency of the test process.

[0051] Among them, empty shell modules are an important part of simplifying the test environment and accelerating the development process in simulation testing and hardware design. These modules simulate the interface and behavior of the actual hardware module, but do not perform the full function of the module. By integrating the empty shell modules into the test environment for simulation testing, the empty shell modules simulate the behavior of the real hardware modules and allow testing without actual hardware, which can reduce the complexity and potential risks of the test environment and speed up the testing process.

[0052] Specifically, the simulation test process includes: first, select appropriate test modules according to the hardware macro settings, and simplify the integration environment by introducing empty shell modules (modules with no functions but occupying interfaces), thereby reducing the compilation scale. Then, integrate these modules into the simulation test environment and use simulation tools to run test cases. In this way, the complexity and risk of the simulation environment can be effectively reduced, while reducing the test time, and ultimately improving the efficiency of the entire test process;

[0053] Among them, hardware macros allow certain modules to be compiled selectively according to specific needs, which can avoid compiling unnecessary modules and thus reduce the final compilation scale. In this way, resource consumption during compilation and simulation is significantly reduced, especially in complex hardware environments, where compilation time and simulation time are greatly shortened. In addition, the use of empty shell modules further optimizes the test environment. These modules simulate the interface and behavior of actual hardware modules but do not perform specific functions, thereby avoiding the introduction of potential risks and errors. This approach not only reduces variables in testing, but also ensures the stability and predictability of the test environment, allowing test engineers to focus more on the verification of core functions without having to worry about interference caused by the complexity of the environment. Ultimately, the combination of these measures significantly improves the efficiency of the test process, shortens the development cycle, and ensures the reliability of test results.

[0054] Compared with the prior art, the present invention has the following advantages: convenient and unified management of test cases, conducive to periodic inspection of the current verification status, clear identification of differences between different test cases, improved regression testing efficiency, conducive to the migration of test cases between projects, simplified adaptability modifications, and effectively reduced simulation environment risks.

[0055] Furthermore, before the extracted key parameters automatically select the corresponding test module (tb.f), it also includes: importing the Excel table into a perl script program, and calling the perl script program to parse the data structure of the Excel table.

[0056] Furthermore, the extracted key parameters automatically select the corresponding test modules (tb.f), including:

[0057] S11, according to the hardware macro in the key parameter, determining a hardware module corresponding to the hardware macro from a plurality of hardware modules;

[0058] S12, according to the software macro in the key parameter, determining a software module corresponding to the software macro from a plurality of software modules;

[0059] S13, according to the simulation parameters in the key parameters, determining a simulation model corresponding to the simulation parameters from a plurality of simulation models;

[0060] S14, according to whether regression test is performed in the key parameter, determining a regression test template corresponding to whether regression test is performed from multiple regression test templates;

[0061] S15. Combining the determined hardware modules, software modules, simulation models and regression test templates to obtain a complete test module.

[0062] Furthermore, corresponding test cases are generated for writing into Excel tables and performing reading and classification processing, including:

[0063] S21, writing multiple test cases into an Excel table, and reading the Excel table to obtain multiple cells in the Excel table, each cell corresponding to a test case;

[0064] S22, judging each row of data in the Excel table, if it is detected that the data in the row is a title, skipping the row and continuing to judge the next row;

[0065] S23, if it is detected that the line is a blank line, skip the line and continue to judge the next line;

[0066] S24. If it is detected that the row is not a header and is not a blank row, the contents of the i-th cell of the row are read from left to right, and the type of the row is determined.

[0067] When the i-th cell belongs to any type of test module, the content of the i-1-th cell is used as the file name, and the content of the i-th cell is used as the search string;

[0068] S25. If there are no unprocessed cells in the Excel table, then this cycle ends.

[0069] Furthermore, the modified features of the current project are filtered according to whether the test case is a modification point, including saving the data in the Excel table to a local folder, and using the use case description in the Excel table to identify and obtain the differences between different test cases through the test case description.

[0070] Specifically, the string similarity measurement method of Levenshtein distance is used to calculate the differences between different test cases, including:

[0071] Set the strings of the two test cases to and , Levenshtein distance is the minimum number of operations to transform s into t by inserting, deleting, or replacing operations;

[0072] create The matrix D, where express arrive Levenshtein distance, initialize the first row and first column as:

[0073]

[0074] For i from 1 to n and j from 1 to m, update the matrix according to the following rules:

[0075]

[0076] in represents the minimum number of edits required to convert the substring of string s from index i-1 to index i into the first j characters of string t, followed by a deletion operation; represents the minimum number of edits required to convert the first i characters of string s into the substring of string t from index j-1 to index j, followed by an insertion operation; represents the minimum number of edits required to convert the string s from index i-1 to the substring at index i into the string t from index j-1 to the substring at index j, when ,but , no replacement operation is required, when ,but , needs to be replaced once;

[0077] According to the calculated , is the minimum number of edits required to convert the entire string s to t, which is the Levenshtein distance.

[0078] Specifically, when parsing the data in the Excel table, the data type of each cell is detected. According to the data parsing library in the Perl script, the data type is automatically identified when the test case contains a complex non-string data structure (such as an array, object, or nested structure), which can be converted into a string format using serialization technology and stored in the Excel table.

[0079] The effect of using Levenshtein distance is to quantify the similarity between different test cases, help identify and optimize redundant or similar test scenarios. This method can significantly improve the efficiency of test case maintenance, reduce duplication of work, and ensure that test resources are focused on unique and valuable test scenarios. In addition, Levenshtein distance can also assist in the merging and streamlining of automated test cases, improve the overall quality of the test suite, and support data-driven test decision-making processes through precise similarity analysis.

[0080] Furthermore, by creating basic test cases in Excel, specifically creating a Sheet that contains common test logic and initialization settings,

[0081] Create derivative test cases for the same feature test case, where the derivative test cases inherit the common logic and initialization settings of the base test case, and then introduce new simulation parameters and conditions based on specific test requirements.

[0082] Specifically, for a feature (such as Memory Control Register), you only need to define the basic test logic once, and you can cover multiple test scenarios by adjusting the simulation parameters, which greatly reduces the number of test cases; when you need to change the test logic or initialization settings, you only need to modify the basic test case template, and the derived test cases will automatically inherit these changes without having to modify them one by one, thus simplifying the inheritance and modification work between projects.

[0083] Furthermore, new simulation parameters and conditions are introduced according to specific test requirements, including:

[0084] Assign a unique case ID to each derived test case. This case ID consists of a prefix (e.g., DER_TC) and an incremental number (e.g., 001, 002) to ensure that each test case is unique and traceable throughout the testing process.

[0085] New simulation parameters and conditions are bound to specific test cases through the use case ID, ensuring the independence of each test case. Different use cases have different parameter sets and test conditions, so they will not affect each other during the test process, avoiding coupling.

[0086] Specifically, in Excel, specific simulation parameters and conditions are specified for each derived test case, and a unique identifier and parameter set are assigned. The principle is to ensure that each test case is unique and traceable throughout the entire testing process by assigning a unique case ID to each test case. This case ID is not only an identifier of the test case, but also serves as an index to bind specific simulation parameters and test conditions to it. Through this binding mechanism, each test case has unique simulation parameters and condition settings, such as the type of input signal, register settings, and initialization conditions before testing. Each test case will read and use the parameters and conditions associated with the ID when executed, thereby ensuring its independence and accuracy. Specifically, this method can effectively reduce the coupling between test cases and avoid them affecting each other during the test process, thereby improving the pertinence and efficiency of the test. In this way, different test cases can run independently in any order, and their results will not be affected by other test cases. At the same time, this method simplifies the management and maintenance of test cases. Test engineers can easily find and modify specific test cases and their corresponding parameters and conditions without worrying about affecting the settings of other test cases, thereby greatly reducing the maintenance workload and the possibility of errors. Ultimately, this method ensures that test cases can provide accurate and reliable test results under various conditions, and improves the efficiency and manageability of the entire testing process.

[0087] The Excel-based simulation test method achieves efficient and reliable test process management through automated Perl script processing, sophisticated case management, test case independence assurance, and optimized simulation environment. The advantages of this method are that it facilitates unified management of test cases, improves regression test efficiency, simplifies adaptability modifications, and reduces simulation environment risks, greatly improving project development efficiency and test reliability.

[0088] The present invention realizes the automatic management and execution of test cases through the collaborative work of Excel tables and Perl scripts, optimizes the entire process from test case generation to simulation testing, improves test efficiency and accuracy, and realizes the precise quantification of test case differences and intelligent optimization of test coverage through advanced technical means such as Levenshtein distance.

[0089] The above description is only a preferred embodiment of the present invention and does not limit the present invention in any form. Although the present invention has been disclosed as a preferred embodiment as above, it is not used to limit the present invention. Any technical personnel in this field can make some changes or modify the technical contents disclosed above into equivalent embodiments without departing from the scope of the technical solution of the present invention. However, any brief modifications, equivalent changes and modifications made to the above embodiments based on the technical essence of the present invention without departing from the content of the technical solution of the present invention are still within the scope of the technical solution of the present invention.

Claims

1. A method for performing simulation testing based on an Excel spreadsheet, characterized in that: Use Excel tables to carry test cases, analyze columns in Excel tables through PERL scripts, and automatically extract key parameters; Among them, the key parameters include hardware macros, software macros, simulation parameters and whether to perform regression testing; according to the extracted key parameters, the corresponding test modules are automatically selected and corresponding test cases are generated for writing into Excel tables and performing reading and classification processing; Through the filtering function of Excel tables, automatic phased checks are performed to view the test status of specific test cases, and the modified features of the current project are filtered based on whether the test case is a modification point; By creating basic test cases in Excel tables, derivative test cases are created for the test cases of the same feature to optimize the test process; the basic test cases serve as templates and contain common test logic and initialization settings; The method comprises creating a basic test case in an Excel spreadsheet, wherein the basic test case includes common test logic and initialization settings, and creating a Sheet to create a derivative test case for the test case of the same feature, wherein the derivative test case inherits the common logic and initialization settings of the basic test case, and then introduces new simulation parameters and conditions according to specific test requirements; By specifying specific simulation parameters and conditions for each derived test case in Excel and assigning a unique identifier and parameter set to each derived test case; Then, the compilation scale is reduced according to the hardware macro selection, and the empty shell module is integrated into the test environment for simulation testing.

2. A method for performing simulation testing based on an Excel spreadsheet according to claim 1, characterized in that: Before the extracted key parameters automatically select the corresponding test modules, the method further includes: importing the Excel table into a perl script program, and calling the perl script program to parse the data structure of the Excel table.

3. The method for performing simulation testing based on an Excel spreadsheet according to claim 1, characterized in that: The extracted key parameters automatically select corresponding test modules, specifically including: according to the hardware macro in the key parameters, determining the hardware module corresponding to the hardware macro from multiple hardware modules; according to the software macro in the key parameters, determining the software module corresponding to the software macro from multiple software modules; according to the simulation parameters in the key parameters, determining the simulation model corresponding to the simulation parameters from multiple simulation models; according to whether regression test is performed in the key parameters, determining the regression test template corresponding to the regression test from multiple regression test templates; and combining the determined hardware modules, software modules, simulation models and regression test templates to obtain a complete test module.

4. The method for performing simulation testing based on an Excel spreadsheet according to claim 1, characterized in that: Generate corresponding test cases for writing into Excel tables and performing reading and classification processing, including: Write multiple test cases into Excel spreadsheet; The Excel table is read to obtain a plurality of cells in the Excel table, each cell corresponding to a test case; each row of data in the Excel table is judged, and when it is detected that the data in the row is a title, the row is skipped and the judgment of the next row is continued; when it is detected that the row is a blank row, the row is skipped and the judgment of the next row is continued; when it is detected that the row is not a title and is not a blank row, the content of the i-th cell of the row is read from left to right in sequence, and the type of the row is determined, wherein, when the i-th cell belongs to any type of test module, the content of the i-1th cell is used as the file name, and the content of the i-th cell is used as the search string; When there are no unprocessed cells in the Excel table, this loop ends.

5. The method for performing simulation testing based on an Excel spreadsheet according to claim 1, characterized in that: The modified features of the current project are filtered according to whether the test case is a modification point, including saving the data in the Excel table to a local folder, and using the use case description in the Excel table to identify and obtain the differences between different test cases through the test case description.

6. The method for performing simulation testing based on an Excel spreadsheet according to claim 5, characterized in that: The string similarity metric method using Levenshtein distance calculates the differences between different test cases, including: Set the strings of the two test cases to and , Levenshtein distance is the minimum number of operations to transform s into t by inserting, deleting, or replacing operations; create The matrix D, where express arrive Levenshtein distance, initialize the first row and first column as: ; For i from 1 to n and j from 1 to m, update the matrix according to the following rules: ； in represents the minimum number of edits required to convert the substring of string s from index i-1 to index i into the first j characters of string t, followed by a delete operation; represents the minimum number of edits required to convert the first i characters of string s into the substring of string t from index j-1 to index j, followed by an insertion operation; represents the minimum number of edits required to convert the string s from index i-1 to the substring at index i into the string t from index j-1 to the substring at index j, when ,but , no replacement operation is required, when ,but , needs to be replaced once; in is the minimum number of edits required to transform the entire string s into t, and is the Levenshtein distance.

7. The method for performing simulation testing based on an Excel spreadsheet according to claim 1, characterized in that: Introduce new simulation parameters and conditions based on specific test requirements, including: A unique case ID is assigned to each derived test case, and the new simulation parameters and conditions are bound to a specific test case through the case ID; wherein the derived test case is used to refine the test conditions and expected results for a specific test point, and the case ID includes a prefix and an incremental number.

Images