CN117075891A - Method and device for associating configuration files for test cases - Google Patents
Method and device for associating configuration files for test cases Download PDFInfo
- Publication number
- CN117075891A CN117075891A CN202311333957.3A CN202311333957A CN117075891A CN 117075891 A CN117075891 A CN 117075891A CN 202311333957 A CN202311333957 A CN 202311333957A CN 117075891 A CN117075891 A CN 117075891A
- Authority
- CN
- China
- Prior art keywords
- configuration file
- parameter
- test case
- test
- value
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 121
- 238000000034 method Methods 0.000 title claims abstract description 31
- 238000004088 simulation Methods 0.000 claims abstract description 23
- 238000012795 verification Methods 0.000 claims abstract description 18
- 238000012545 processing Methods 0.000 claims description 4
- 230000005284 excitation Effects 0.000 abstract description 10
- 230000002159 abnormal effect Effects 0.000 description 5
- 238000010276 construction Methods 0.000 description 2
- 230000003247 decreasing effect Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 238000013142 basic testing Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000007796 conventional method Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/36—Software reuse
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
- G06F9/4451—User profiles; Roaming
Abstract
The invention discloses a method and a device for associating configuration files for test cases, which belong to the technical field of chip verification and comprise the steps of preparing the test cases and the configuration files associated with the test cases; during simulation, a simulation operation instruction is input through a command line, and the name of a configuration file is designated; the simulation tool refers to the configuration file in a mode of adding simulation options, and the content of the configuration file is imported into a command line; after compiling is finished, simulating, and after simulating is started, analyzing the related test cases according to the names of the configuration files; analyzing the value of each parameter in the configuration file from the command line parameters; and executing code logic corresponding to the test case according to the analyzed parameter value, and testing the tested unit. The method and the device for associating the configuration file for the test case do not reload the excitation class, do not need to recompile the environment when the configuration file is operated after being modified, improve the simulation efficiency and improve the multiplexing rate of the environment codes.
Description
Technical Field
The present invention relates to the field of chip verification technologies, and in particular, to a method and apparatus for associating configuration files for test cases.
Background
When verifying a chip based on a general verification methodology, various scenes of a tested unit in actual use need to be simulated, which means that various stimuli, including stimuli in normal scenes and stimuli in abnormal scenes, are sent to the tested unit in simulation. These different stimuli correspond to different test cases (test cases), respectively. When the verification environment platform is built, generally, each time a test scene is constructed, the basic test cases are inherited to create new test cases. This conventional method has the following disadvantages: firstly, in order to construct the excitation content required by the test case, the excitation class needs to be reloaded, and the reloading has a plurality of constraint conditions, so that the use is more complicated. In order to construct the stimulus conforming to the test scene, the stimulus content and the stimulus construction mode are generally required to be controlled, and then if the control content is modified, the environment code is required to be changed, so that the environment is required to be recompiled, the simulation efficiency is low, and the environment code multiplexing rate is low.
Disclosure of Invention
In order to solve the above problems, the present invention provides a method and an apparatus for associating configuration files for test cases, based on the feature that parameters are transferred through command lines in the process of compiling Verilog simulator (VCS) simulation, the running simulation of test cases associated with the configuration files is realized by running different configuration files.
In order to achieve the above purpose, the technical scheme of the invention is as follows:
a method for associating a configuration file for a test case, comprising,
step S1, preparing a test case and a configuration file associated with the test case;
step S2, during simulation, a simulation operation instruction is input through a command line, and the name of a configuration file is specified, wherein a parameter tc is used for storing the name of the specified configuration file;
s3, enabling a simulation tool to refer to the configuration file in a mode of adding simulation options, and importing the content of the configuration file into a command line;
s4, after the compiling is finished, simulating, analyzing the related test cases according to the names of the configuration files, and processing the parameters tc in the automatic compiling script to obtain the names of the test cases related to the configuration files;
the step S4 includes the steps of,
step S41, replacing the character string "_tc_" in the parameter tc with ";
step S42, the former character string of the character string obtained in the step S41 is taken out, and the name of the test case related to the configuration file is obtained;
s5, analyzing the value of each parameter in the configuration file from the command line parameters;
and S6, executing code logic corresponding to the test case according to the analyzed parameter value, and testing the tested unit.
Further, the configuration files correspond to the test cases, and parameter values required by the test cases associated with the configuration files are specified in each configuration file.
Further, in the step S3, the configuration file is referenced by the custom command dut_sim_opt, specifically, dut_sim_opt= -f./ $ (ptc_dir)/$ (PTC). Cfg, where ptc_dir represents the path of the configuration file, PTC represents the file name of the configuration file, and dut_sim_opt= -f./ $ (ptc_dir)/$ (PTC). Cfg represents the configuration file with the file name PTC under the reference path ptc_dir.
Further, the step S5 includes,
step S51, obtaining the current value of the parameter in the configuration file through a get_arg_value function provided by UVM _cmdline_processor class built in a universal verification methodology (Universal Verification Methodology, UVM);
step S52, storing the content on the right of the parameter equal sign as a character string type;
step S53, processing the obtained character string and converting the character string into an integer type;
step S54, judging whether the integer obtained in step S53 is a determined value, if yes, proceeding to step S55, if no, indicating that the parameter value is a range, proceeding to step S56;
step S55, obtaining the value of the parameter;
step S56, randomly selecting a value from the range of parameter values as the value of the parameter.
Further, a test case includes one or more test scenarios, and a test case associates one or more configuration files.
The invention also provides a device for associating the configuration file for the test case, and the method for associating the configuration file for the test case comprises a test case module, a custom parameter class module, a configuration file module and an analysis module, wherein the configuration file module is connected with the test case module, the custom parameter module and the analysis module.
The test case module comprises a test case.
The custom parameter class module custom defines parameters needed by the verification environment, and realizes the macro setting of the parameters through the custom parameters, including setting parameter names, parameter default values and parameter types.
The function of the profile module is to name the profile and set parameter values of parameters therein.
The function of the analysis module is to analyze the name of the related test case according to the name of the configuration file, and analyze the value of each parameter in the configuration file from the command line parameters.
The method and the device for associating the configuration file for the test case have the beneficial effects that the method and the device do not reload the excitation class, the upper hand is simple and direct, the constraint branches of the excitation contents required under different test scenes are directly realized when excitation is generated and stored in the test case, and then the specific selection of the constraint branches is controlled through the parameter values in the configuration file during the test; the simulation efficiency is improved, the general verification methodology supports the transmission of command line parameters during simulation, and parameters in the configuration file are actually transmitted as command line parameters and are independent of the verification environment, so that the verification environment is not required to be recompiled by modifying the content of the configuration file; the method improves the multiplexing rate of the environment codes, and can directly restrict the interface value in the excitation to be equal to the value of the parameter in the configuration file or restrict the random range of the interface value to the value of the parameter in the configuration file when constructing the excitation, and only the parameter value in the configuration file related to the test case needs to be modified when changing the interface value subsequently.
In order to make the above features and advantages of the present invention more comprehensible, embodiments accompanied with figures are described in detail below.
Drawings
FIG. 1 is a flow chart of a method for associating configuration files for test cases according to the present invention.
Fig. 2 is a specific flowchart of step S4 in fig. 1.
Fig. 3 is a specific flowchart of step S5 in fig. 1.
FIG. 4 is a schematic diagram of an apparatus for associating configuration files with test cases according to the present invention.
Detailed Description
In order to make the purpose and technical solutions of the embodiments of the present invention more clear, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. It will be apparent that the described embodiments are some, but not all, embodiments of the invention. All other embodiments, which can be made by a person skilled in the art without creative efforts, based on the described embodiments of the present invention fall within the protection scope of the present invention.
FIG. 1 is a flow chart of a method for associating configuration files for test cases according to the present invention. As shown in FIG. 1, a method for associating a configuration file for a test case according to the present invention includes the following steps.
Step S1, preparing a test case and a configuration file associated with the test case.
The test case is a description composed of test input, execution conditions and expected results. The configuration file corresponds to the test case, and the content of the configuration file is mainly related parameter information of the corresponding test case.
In a specific embodiment, it is assumed that it is necessary to test whether the unit under test can correctly process the input message, and the following scenarios are included:
scene a): the length of the input message is increased;
scene b): the length of the input message is decreased;
scene c): the input message data is all 0;
scene d): the input message data is all 1;
scene e): interleaving the input message data 0 and 1;
in practice, for all the above test scenarios, one test case is written, and the test case is named as tc_base, and the pseudo code of the content is as follows:
if(pktlen_inc === 1)begin
constructing message length increment;
//……
end
if(pktlen_dec === 1) begin
constructing message length decrementing;
//……
end
if(pktdata_all_0 === 1) begin
constructing message data as all 0;
//……
end
if(pktdata_all_1 === 1) begin
constructing message data as all 1;
//……
end
if(pktdata_alt=== 1) begin
the data of the constructing message is alternated 0 and 1;
//……
End
wherein, the parameter pktlen_inc is 1, which indicates that the length of the constructed message is increased; the parameter pktlen_dec is 1, which indicates that the length of the constructed message is decreased; the parameter pktdata_all_0 is 1, which indicates that the constructed message data is all 0; the parameter pktdata_all_1 is 1, which indicates that the constructed message data is all 1; the parameter pktdata_alt is 1, which indicates that the data content of the construction message alternates between 0 and 1.
Further, a plurality of configuration files corresponding to the test scene based on the test case tc_base are created. The test scene and the configuration file based on the test case corresponding to the test scene are shown in the following table:
in particular embodiments, the configuration files may be named according to actual test functions, test points, or scenarios.
Alternatively, a test case may include one or more test scenarios, and a test case may be associated with one or more configuration files.
In each configuration file, parameter values required by the test cases associated with the configuration files are specified, so that the test cases meet the requirements of test scenes.
For example, the contents of the configuration file tc_base_tc_pktlen_inc_test are:
+pktlen_inc = 1，
+pktlen_dec = 0，
+pktdata_all_0 = 0，
+pktdata_all_1 = 0，
+pktdata_alt =1。
step S2, during simulation, a simulation operation instruction is input through a command line, and the name of a configuration file is specified, wherein a parameter tc is used for storing the name of the specified configuration file.
In a specific embodiment, the parameter tc=tc_base_tc_pktlen_inc_test represents that the name of the configuration file corresponding to the test case is tc_base_tc_pktlen_inc_test, and the parameter tc is a string.
And step S3, enabling the simulation tool to refer to the configuration file by adding the simulation option, and importing the content of the configuration file into the command line.
In a specific embodiment, the configuration file is referenced by a command dut_sim_opt, which is a custom command, specifically dut_sim_opt= -f./ $ (ptc_dir)/$ (PTC). Cfg, where ptc_dir represents the path of the configuration file, PTC represents the file name of the configuration file, dut_sim_opt= -f./ $ (ptc_dir)/$ (PTC). Cfg represents the configuration file with the file name PTC under ptc_dir referencing the path, and this custom command dut_sim_opt is appended after the VCS tool emulation run command in an auto-compiled script.
And S4, after compiling is finished, simulating, and after the simulating is started, analyzing the related test cases according to the names of the configuration files. More specifically, the parameter tc is processed in the automated compiling script to obtain the name of the test case associated with the configuration file.
In one embodiment, the parameter tc=tc_base_tc_pktlen_inc_test is taken as an example.
As shown in fig. 2, step S4 further includes step S41, in which the string "_tc_" in the parameter tc is replaced with "," and the string tc_base_tc_pktlen_inc_test becomes the string tc_base.
Step S4 further includes step S42 of extracting the preceding string, i.e., string tc_base, of strings tc_base, pktlen_inc_test, and obtaining the name tc_base of the test case associated with the configuration file tc_base_tc_pktlen_inc_test.
And S5, analyzing the value of each parameter in the configuration file from the command line parameters.
The step S5 further includes the following steps, as shown in fig. 3.
Step S51, obtaining the current value of the parameter in the configuration file through a get_arg_value function provided by UVM _cmdline_processor class built in a universal verification methodology (Universal Verification Methodology, UVM);
step S52, storing the content on the right of the parameter equal sign as a character string type;
step S53, the obtained character string is processed and converted into an integer type;
step S54, judging whether the integer obtained in step S53 is a determined value, if yes, proceeding to step S55, if no, indicating that the parameter value is a range, proceeding to step S56;
step S55, obtaining the value of the parameter;
step S56, randomly selecting a value from the range of parameter values as the value of the parameter.
In one embodiment, when the parameter port_en=1 in the configuration file, the value of the parameter port_en is 1 after step S5; when the parameter port_en= [1,2,3], after step S5, a value is randomly selected from 1,2,3 as the value of the parameter port_en.
And S6, executing code logic corresponding to the test case according to the analyzed parameter value, and testing the tested unit.
In one embodiment, the configuration file includes a parameter aa, and when the verification platform constructed based on the Universal Verification Methodology (UVM) is simulated, different motivational content is constructed according to the value of the parameter aa.
When the parameter aa is 0, constructing normal motivational content; when the parameter aa is 1, constructing abnormal excitation content; when the parameter aa is 2, the excitation content of normal and abnormal mixing is constructed.
Examples of pseudocode are as follows:
if(aa === 0)begin
constructing normal motivational content;
//……
end
else if(aa === 1) begin
constructing abnormal motivational content;
//……
end
else if(aa === 2) begin
constructing normal and abnormal mixed motivational content;
//……
end
the invention also provides a device for associating the configuration file for the test case, and the method for associating the configuration file for the test case is implemented.
Fig. 4 is a schematic structural diagram of an apparatus for associating configuration files with test cases according to the present invention, and as shown in fig. 4, the apparatus for associating configuration files with test cases according to the present invention includes a test case module 11, a custom parameter class module 12, a configuration file module 13 and an analysis module 14, where the configuration file module 13 connects the test case module 11, the custom parameter module 12 and the analysis module 14.
The test case module 11 includes a test case, where the test case is a description composed of test input, execution conditions, and expected results. The configuration file corresponds to the test case, and the content of the configuration file is mainly related parameter information of the corresponding test case.
In a specific embodiment, the test cases may be written manually or may be generated automatically.
The custom parameter class module 12 custom-defines parameters needed by the verification environment, and more specifically, custom-defines parameters needed by the verification environment, and sets parameters by implementing macros through the custom-defined parameters, including setting parameter names, parameter default values, parameter types, and the like.
The function of the profile module 13 is to name the profile and set parameter values for the parameters therein. The naming rules of the configuration file are as follows: [ tc_name ] _tc_ [ cfg_name ]. Cfg, wherein tc_name represents the name of the corresponding test case, cfg_name represents the identification of the configuration file, which can be defined by itself, in a specific embodiment, the name of the configuration file is tc_base_tc_pktlen_inc_test.
Further, the naming rules of the transfer parameters are: + [ variable name ] = [ variable constraint ]. In one embodiment, the transfer parameter port_en is defined as follows: +port_en=1 or +port_en= [1,2,3], +port_en=1 represents that the value of port_en is 1, and +port_en= [1,2,3] represents that the value of port_en is randomly selected from among three values of 1,2, 3.
The parsing module 14 is configured to parse the name of the associated test case according to the name of the configuration file, and parse the value of each parameter in the configuration file from the command line parameters.
Although the present invention has been described with reference to the above embodiments, it should be understood that the invention is not limited thereto, but rather is capable of modification and variation without departing from the spirit and scope of the present invention.
Claims (10)
1. A method for associating a configuration file for a test case, comprising,
step S1, preparing a test case and a configuration file associated with the test case;
step S2, during simulation, a simulation operation instruction is input through a command line, and the name of a configuration file is specified, wherein a parameter tc is used for storing the name of the specified configuration file;
s3, enabling a simulation tool to refer to the configuration file in a mode of adding simulation options, and importing the content of the configuration file into a command line;
s4, after the compiling is finished, simulating, analyzing the related test cases according to the names of the configuration files, and processing the parameters tc in the automatic compiling script to obtain the names of the test cases related to the configuration files;
the step S4 includes the steps of,
step S41, replacing the character string "_tc_" in the parameter tc with ";
step S42, the former character string of the character string obtained in the step S41 is taken out, and the name of the test case related to the configuration file is obtained;
s5, analyzing the value of each parameter in the configuration file from the command line parameters;
and S6, executing code logic corresponding to the test case according to the analyzed parameter value, and testing the tested unit.
2. The method of claim 1, wherein the configuration files correspond to test cases, and wherein parameter values required for the test cases associated therewith are specified in each configuration file.
3. The method according to claim 2, wherein in the step S3, the configuration file, specifically dut_sim_opt= -f./$ (ptc_dir)/$ (PTC). Cfg, is referred to by a custom command dut_sim_opt, wherein ptc_dir represents a path of the configuration file, PTC represents a file name of the configuration file, and dut_sim_opt= -f./$ (ptc_dir)/$ (PTC). Cfg represents a configuration file with a file name PTC under the reference path ptc_dir.
4. The method of claim 3, wherein step S5 comprises,
step S51, obtaining the current value of the parameter in the configuration file through a get_arg_value function provided by a uvm _cmdline_processor class built in the general verification methodology;
step S52, storing the content on the right of the parameter equal sign as a character string type;
step S53, processing the obtained character string and converting the character string into an integer type;
step S54, judging whether the integer obtained in step S53 is a determined value, if yes, proceeding to step S55, if no, indicating that the parameter value is a range, proceeding to step S56;
step S55, obtaining the value of the parameter;
step S56, randomly selecting a value from the range of parameter values as the value of the parameter.
5. The method of claim 1, wherein a test case includes one or more test scenarios and wherein a test case associates one or more configuration files.
6. A device for associating a configuration file for a test case, wherein a method for associating a configuration file for a test case according to any one of claims 1 to 5 is performed, and the device comprises a test case module, a custom parameter class module, a configuration file module and an analysis module, wherein the configuration file module is connected with the test case module, the custom parameter module and the analysis module.
7. The apparatus for associating a configuration file for a test case as recited in claim 6, wherein the test case module includes a test case.
8. The apparatus of claim 7, wherein the custom parameter class module custom defines parameters needed by the verification environment, and implements macro setting of parameters by custom parameters, including setting parameter names, parameter default values, and parameter types.
9. The apparatus of claim 8, wherein the profile module functions to name the profile and set parameter values for parameters therein.
10. The apparatus of claim 9, wherein the parsing module is configured to parse the name of the associated test case according to the name of the configuration file, and parse the value of each parameter in the configuration file from the command line parameters.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311333957.3A CN117075891B (en) | 2023-10-16 | 2023-10-16 | Method and device for associating configuration files for test cases |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311333957.3A CN117075891B (en) | 2023-10-16 | 2023-10-16 | Method and device for associating configuration files for test cases |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN117075891A true CN117075891A (en) | 2023-11-17 |
| CN117075891B CN117075891B (en) | 2024-02-02 |
Family
ID=88708385
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311333957.3A Active CN117075891B (en) | 2023-10-16 | 2023-10-16 | Method and device for associating configuration files for test cases |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117075891B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20090078696A (en) * | 2008-01-15 | 2009-07-20 | 포항공과대학교 산학협력단 | Method of simulation supporting software testing based on user environment profiling |
| CN112084113A (en) * | 2020-09-16 | 2020-12-15 | 上海创景信息科技有限公司 | Configurable automatic test method and system based on embedded simulation verification software |
| CN113204939A (en) * | 2021-04-29 | 2021-08-03 | 山东华芯半导体有限公司 | Full-chip simulation verification method |
| CN113709003A (en) * | 2021-09-02 | 2021-11-26 | 上海天旦网络科技发展有限公司 | System, method and medium for automatically generating test case through network flow data |
| CN113986263A (en) * | 2021-10-25 | 2022-01-28 | 展讯半导体(南京)有限公司 | Code automation test method, device, electronic equipment and storage medium |
| CN115221035A (en) * | 2021-04-19 | 2022-10-21 | 深圳开立生物医疗科技股份有限公司 | Software testing method and device and related equipment |
-
2023
- 2023-10-16 CN CN202311333957.3A patent/CN117075891B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20090078696A (en) * | 2008-01-15 | 2009-07-20 | 포항공과대학교 산학협력단 | Method of simulation supporting software testing based on user environment profiling |
| CN112084113A (en) * | 2020-09-16 | 2020-12-15 | 上海创景信息科技有限公司 | Configurable automatic test method and system based on embedded simulation verification software |
| CN115221035A (en) * | 2021-04-19 | 2022-10-21 | 深圳开立生物医疗科技股份有限公司 | Software testing method and device and related equipment |
| CN113204939A (en) * | 2021-04-29 | 2021-08-03 | 山东华芯半导体有限公司 | Full-chip simulation verification method |
| CN113709003A (en) * | 2021-09-02 | 2021-11-26 | 上海天旦网络科技发展有限公司 | System, method and medium for automatically generating test case through network flow data |
| CN113986263A (en) * | 2021-10-25 | 2022-01-28 | 展讯半导体(南京)有限公司 | Code automation test method, device, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN117075891B (en) | 2024-02-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8392884B2 (en) | Test case automatic generation method for testing proactive GSM application on SIM cards | |
| CN112270149B (en) | Verification platform automatic integration method and system, electronic equipment and storage medium | |
| CN110334021B (en) | Interface test case generation method, device, equipment and storage medium | |
| US7895575B2 (en) | Apparatus and method for generating test driver | |
| CN107341102B (en) | Test case file generation method and device | |
| CN107239392A (en) | A kind of method of testing, device and terminal | |
| US7680668B2 (en) | Method for generating a language-independent regression test script | |
| CN109933521A (en) | Automated testing method, device, computer equipment and storage medium based on BDD | |
| CN110532182B (en) | Automatic testing method and device for virtualization platform | |
| CN111913889A (en) | Test system building method and test system | |
| CN110515755A (en) | Interface function verification method, device, equipment and computer readable storage medium | |
| CN112506785A (en) | Automatic testing method, device, equipment and medium for login of Html5 game page | |
| CN112181749A (en) | Hardware testing method and device, electronic equipment and storage medium | |
| CN111897742A (en) | Method and device for generating intelligent contract test case | |
| CN103176894A (en) | Test data automatic derivative method and automatic derivative device facing database | |
| CN108021503A (en) | The method, apparatus and computer-readable storage medium of automated function test | |
| CN117075891B (en) | Method and device for associating configuration files for test cases | |
| CN113138937A (en) | Test method and device | |
| CN111143228B (en) | Test code generation method and device based on decision table method | |
| CN112561690A (en) | Method, system, equipment and storage medium for testing credit card staging service interface | |
| CN109684205B (en) | System testing method, device, electronic equipment and storage medium | |
| US6978216B2 (en) | Testing of integrated circuits from design documentation | |
| US20050177773A1 (en) | Software method for exhaustive variation of parameters, independent of type | |
| US6976188B2 (en) | System and method for creating a customized power on self test (POST) program for use in a computing system | |
| CN113986263A (en) | Code automation test method, device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |