CN112882931A - Automatic testing method and device based on DDT - Google Patents
Automatic testing method and device based on DDT Download PDFInfo
- Publication number
- CN112882931A CN112882931A CN202110165550.9A CN202110165550A CN112882931A CN 112882931 A CN112882931 A CN 112882931A CN 202110165550 A CN202110165550 A CN 202110165550A CN 112882931 A CN112882931 A CN 112882931A
- Authority
- CN
- China
- Prior art keywords
- execution
- data
- list
- test
- parameter
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3604—Software analysis for verifying properties of programs
- G06F11/3612—Software analysis for verifying properties of programs by runtime analysis
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention relates to the technical field of testing, in particular to a DDT-based automatic testing method and a device, and the method comprises the following steps: reading a data file according to the path annotation in the test method, adding an execution method in a preset method execution list when the test data exists in the data file, adding corresponding test data in a preset parameter execution list, and automatically creating a data list when the test data does not exist in the data file; after the addition of the test data and the execution method corresponding to all the test methods is completed in sequence, when elements exist in both the method execution list and the parameter execution list, a first element in the method execution list and the parameter execution list is extracted for execution, the execution result is recorded until the elements do not exist in the method execution list and the parameter execution list, and all the execution results are stored. By adopting the scheme, the coding workload of data reading can be reduced, and the execution efficiency is improved.
Description
Technical Field
The invention relates to the technical field of testing, in particular to an automatic testing method and device based on DDT.
Background
The DDT, called Data Drive Test entirely, is translated into a Data Drive Test, which mainly refers to a Test performed on the same Test case by using different Test Data. When the data input test device is used specifically, a business function is designed according to business requirements, the input of the business function relates to various data, and the business function is tested through the combination of different data, so that whether the output of the business function can meet the business requirements under the condition of different data input is verified.
The main principle of the conventional test frame based on Junit is that a test method is arranged in a Java test class, test data is read from an external data source through the test method, and when multiple test methods exist in the test class, if one test method needs to be called to read the test data, all test methods in the test class need to be read, and the adoption of the methods has the following defects:
1. the introduction of test data requires data reading codes, if the test method is called each time, the test method under the test class needs to be read, and when the number of the test classes is large, the code workload of data reading is greatly increased;
2. when the test method required by the test data is called, all test methods in the test class need to be read, so that other test methods except the required test method can be executed, unnecessary repeated execution is caused, and the execution efficiency is reduced.
Disclosure of Invention
One objective of the present invention is to provide an automated testing method based on DDT, which can reduce the encoding workload of data reading and improve the execution efficiency.
The invention provides a basic scheme I:
the automatic testing method based on the DDT comprises the following steps:
s1: acquiring a test method in a test class, wherein a path annotation corresponding to a data file is marked in the test method;
s2: reading a data file of the specified path according to the path annotation, and judging whether test data exist in the data file or not;
s3: when test data exist in the data file, generating an execution method according to the test data and a corresponding test method, adding the execution method in a preset method execution list, and adding the corresponding test data in a preset parameter execution list;
s4: repeating the steps S1-S3 until the addition of test data and execution methods corresponding to all test methods is completed;
s5: after the addition of the test data and the execution method corresponding to all the test methods is finished, judging whether elements exist in a method execution list and a parameter execution list or not;
s6: when the element exists, extracting a first element in the method execution list and the parameter execution list, and executing the extracted first element; after the execution of the first element is finished, recording an execution result, and deleting the first element in the method execution list and the parameter execution list;
s7: steps S5-S6 are repeated until no elements exist, saving all execution results.
Description of the nouns: a test class refers to a collection of test methods. The test method refers to the written code for testing the specific service function interface, and the test purpose is achieved by calling the test method. The path annotation is a designated path of a data file storing test data annotated in the test method. Test data refers to the values of parameters under execution.
The beneficial effects of the first basic scheme are as follows: the path annotation is Java annotation, and test data is introduced in a Java annotation mode, so that compared with a coding mode, the path annotation is more convenient to use, the usability of the system is improved, and the coding workload of data reading is reduced.
The execution method and the test data are correspondingly added into the method execution list and the data execution list and are executed according to the list sequence, all executions are in one test class, the execution is optimized, the execution needs to be executed corresponding to one test class when one test data is executed in the prior art, and the optimization is carried out when one test data corresponds to each test method, so that the execution of other test methods except the needed test method is avoided, the unnecessary repeated execution is avoided, and the execution efficiency is improved.
Further, S3 further includes the steps of: and when the test data does not exist in the data file, automatically creating a data list according to the path annotation, and exiting the program after the creation is finished.
Has the advantages that: based on the technical idea of refilling data with the test logic of the prior component, the data list is automatically created for the testers to fill the test data under the condition of no test data, so that the test data and the test logic are prevented from being adjusted repeatedly, the code compiling efficiency is improved, and the test efficiency is improved.
Further, S3 further includes the steps of: and when the program exits, sending out a data addition reminder.
Has the advantages that: and the data addition reminding is set to remind the testers, so that the test data is filled.
Further, in S3, adding an execution method in a preset method execution list, and adding corresponding test data in a preset parameter execution list, includes the following steps: adding the execution method to the end of the element in the preset method execution list, and adding the test data to the end of the element in the preset parameter execution list.
Has the advantages that: and adding the execution method to be executed into the method execution list and adding the corresponding test data into the parameter execution list in sequence, wherein when the method is added, the method is added to the tail end of the elements in the list, namely the sequence of the elements in the list is the adding sequence, so that the method is convenient to execute in sequence, and the accuracy of the test is ensured.
Further, in S3, automatically creating a data list according to the path annotation includes the following steps: the testing method comprises the steps of testing parameter names of data to be tested, creating a data list under a specified path according to path annotations, wherein the data list comprises the data names, and updating the data names in the data list according to the parameter names.
Has the advantages that: data names in the data list are updated according to the needed parameter names, so that the data names can be conveniently checked by a tester, and when the tester fills the test data, the tester can quickly fill the test data according to the data names, and the test efficiency is improved.
Further, the step of determining whether the method execution list and the parameter execution list have elements in S5 includes the following steps: and generating a judgment result according to the method execution list and the parameter execution list, wherein the judgment result comprises an existing element and an nonexistent element, when the execution method exists in the method execution list and the test data exists in the parameter execution list, the judgment result of the existing element is generated, otherwise, the judgment result of the nonexistent element is generated.
Has the advantages that: the existing element represents that the parameter execution list has test data, the method execution list has an execution method, otherwise, the element does not exist, namely, the parameter execution list does not have test data, the method execution list has no execution method, and when the element exists in both the method execution list and the parameter execution list, the first element is executed. By means of strong judgment, the method execution list and the parameter execution list are prevented from being executed under the condition that elements are lacked, accordingly waste of execution time is avoided, and testing efficiency is improved.
Further, the execution result is recorded in S6, including the following steps: and outputting the execution result to a preset detail file for recording.
Has the advantages that: setting a detail file, and realizing the storage of an execution result.
The invention also aims to provide an automatic testing device based on DDT.
The invention provides a second basic scheme: the automatic testing device based on the DDT uses the automatic testing method based on the DDT.
The second basic scheme has the beneficial effects that: test data are introduced in a Java annotation mode, and compared with a coding mode, the method is more convenient to use, improves the usability of the system, and reduces the coding workload of data reading. The execution method and the test data are correspondingly added into the method execution list and the data execution list and are executed according to the list sequence, and one test data is executed corresponding to each test method, so that the execution of other test methods except for the required test method is avoided, unnecessary repeated execution is avoided, and the execution efficiency is improved.
Drawings
FIG. 1 is a flowchart of a first embodiment of an automated testing method based on DDT according to the present invention.
Detailed Description
The following is further detailed by way of specific embodiments:
example one
An automated testing method based on DDT, as shown in FIG. 1, comprises the following steps:
s1: and acquiring a test method in the test class, wherein the test method is marked with a path annotation corresponding to the data file. A test class refers to a collection of test methods. The test method refers to the written code for testing the specific service function interface, and the test purpose is achieved by calling the test method. The path annotation is a designated path of a data file storing test data annotated in the test method, and is Java annotation written in the test method.
S2: and reading the data file of the specified path according to the path annotation, and judging whether the test data exists in the data file. And searching a data file under the specified path according to the information recorded in the path annotation, wherein the data file is used for storing a data list, and parameter values of parameters required by the test method are recorded in the data list, and the parameter values are the test data.
S3: when test data exist in the data file, generating an execution method according to the test data and a corresponding test method, adding the execution method in a preset method execution list, and adding the corresponding test data in a preset parameter execution list; and when no test data exists in the data file, automatically creating a data list according to the path annotation, exiting the program after the creation is finished, and sending a data addition prompt when exiting the program. The method specifically comprises the following steps:
and when the test data exists in the data file, namely the test data exists in the data list in the data file, generating an execution method according to the test data and the corresponding test method. And adding the generated execution method to the tail end of the element in the preset method execution list, and adding the test data to the tail end of the element in the preset parameter execution list. The method execution list is used for storing the execution methods in sequence, the parameter execution list is used for storing the test data in sequence, and the execution methods and the test data are in one-to-one correspondence.
When the test data does not exist in the data file, the data list does not exist in the data file or the test data does not exist in the data list. In this embodiment, the data list is present by default, i.e. test data is present, so that when no data list is present in the data file, i.e. no test data is considered to be present, the data list is present, i.e. test data is present. The test method comprises the steps of establishing a data list under an appointed path according to a parameter name corresponding to data to be tested, wherein the data list comprises the data name, updating the data name in the data list according to the parameter name, and completing the establishment of the data list after the updating is finished. And after the creation of the data list is finished, exiting the program, and sending out a data addition reminder when exiting the program.
Based on the technical idea of refilling data with the test logic of the prior component, the data list is automatically created for the testers to fill the test data under the condition of no test data, so that the test data and the test logic are prevented from being adjusted repeatedly, the code compiling efficiency is improved, and the test efficiency is improved.
In other embodiments, when an update of the test data is detected, i.e., the test data is filled and modified by the tester, the application is automatically re-executed, i.e., step S1 is executed.
S4: steps S1-S3 are repeated until the addition of test data and execution methods corresponding to all test methods is completed. The test class comprises a plurality of test methods, and the addition of the corresponding test data and the execution method is completed in sequence according to the path annotation in the test methods, so that a method execution list and a parameter execution category corresponding to the current test class are obtained.
S5: and after the addition of the test data and the execution method corresponding to all the test methods is finished, judging whether the method execution list and the parameter execution list have elements or not. The method specifically comprises the following steps:
and when the execution method exists in the method execution list and the test data exists in the parameter execution list, generating a judgment result of the existing element, otherwise, generating a judgment result of the nonexistence element. In other embodiments, the determination result may be generated only from the parameter execution list.
S6: when the element exists, extracting a first element in the method execution list and the parameter execution list, and executing the extracted first element; and after the execution of the first element is finished, recording the execution result, and deleting the first element in the method execution list and the parameter execution list. When no element is present, the program exits. The method specifically comprises the following steps:
when elements exist in both the method execution list and the parameter execution list, namely, an execution method exists in the method execution list and test data exists in the parameter execution list, first elements in the method execution list and the parameter execution list are extracted, and the extracted first elements are executed through a reflection function of Java. And after the execution of the first element is finished, recording an execution result, and specifically, outputting the execution result to a preset detail file for recording. When recording the execution result, deleting the first item element in the method execution list and the parameter execution list. The next element which is not executed is located at the head of the method execution list and the parameter execution list, and the first element is still extracted when the next element is executed, so that the searching and reading work of the unexecuted element is reduced, and the execution efficiency is improved.
Otherwise, when the element does not exist, namely the method execution list does not exist the execution method and/or the parameter execution list does not exist the test data, the program is exited.
S7: steps S5-S6 are repeated until no elements exist, saving all execution results. After all elements in the method execution list and the parameter execution list are executed in sequence, the execution result is saved, and specifically, the DETAIL file is saved.
For example, two test methods A, B are written under the test class, test data corresponding to test method a includes a, B, and c, and test data corresponding to test method B includes d and e, and then the data list corresponding to test method a is as shown in table one:
watch 1
Name of data | Parameter value |
a | X1 |
b | X2 |
c | X3 |
The parameter values X1, X2 and X3 in Table I are corresponding values of the test data a, b and c, respectively. And if the method execution list generated according to the test method A, B is [ A, A, A, B, B ], the corresponding parameter execution list is [ a, B, c, d, e ], the extracted first element is A-a, the subsequent sequential combinations are A-B, A-c, B-d, B-e, the execution results are sequentially executed according to the combinations, the execution results are recorded when the execution of each combination is finished, and the execution results are stored after the execution of all the combinations is finished.
The automatic testing device based on the DDT uses the automatic testing method based on the DDT.
The method and the device adopt a Java annotation mode to introduce test data, and compared with a coding mode, the method and the device are more convenient to use, increase the usability of a system, and reduce the coding workload of data reading. The execution method and the test data are correspondingly added into the method execution list and the data execution list and are executed according to the list sequence, all executions are in a test class, the execution of the data lines in a data file is optimized, the original execution of each row of data needs to call the test class for optimization into the execution of one test class, the execution of all data lines is completed, only one test method is called corresponding to each row of data, and therefore the execution of other test methods except the required test method is avoided, unnecessary repeated execution is avoided, and the execution efficiency is improved.
The foregoing is merely an example of the present invention, and common general knowledge in the field of known specific structures and characteristics is not described herein in any greater extent than that known in the art at the filing date or prior to the priority date of the application, so that those skilled in the art can now appreciate that all of the above-described techniques in this field and have the ability to apply routine experimentation before this date can be combined with one or more of the present teachings to complete and implement the present invention, and that certain typical known structures or known methods do not pose any impediments to the implementation of the present invention by those skilled in the art. It should be noted that, for those skilled in the art, without departing from the structure of the present invention, several changes and modifications can be made, which should also be regarded as the protection scope of the present invention, and these will not affect the effect of the implementation of the present invention and the practicability of the patent. The scope of the claims of the present application shall be determined by the contents of the claims, and the description of the embodiments and the like in the specification shall be used to explain the contents of the claims.
Claims (8)
1. The automatic testing method based on the DDT is characterized by comprising the following steps: the method comprises the following steps:
s1: acquiring a test method in a test class, wherein a path annotation corresponding to a data file is marked in the test method;
s2: reading a data file of the specified path according to the path annotation, and judging whether test data exist in the data file or not;
s3: when test data exist in the data file, generating an execution method according to the test data and a corresponding test method, adding the execution method in a preset method execution list, and adding the corresponding test data in a preset parameter execution list;
s4: repeating the steps S1-S3 until the addition of test data and execution methods corresponding to all test methods is completed;
s5: after the addition of the test data and the execution method corresponding to all the test methods is finished, judging whether elements exist in a method execution list and a parameter execution list or not;
s6: when the element exists, extracting a first element in the method execution list and the parameter execution list, and executing the extracted first element; after the execution of the first element is finished, recording an execution result, and deleting the first element in the method execution list and the parameter execution list;
s7: steps S5-S6 are repeated until no elements exist, saving all execution results.
2. A DDT based automated testing method according to claim 1, characterized in that: s3 further includes the steps of:
and when the test data does not exist in the data file, automatically creating a data list according to the path annotation, and exiting the program after the creation is finished.
3. A DDT based automated testing method according to claim 2, characterized in that: s3 further includes the steps of:
and when the program exits, sending out a data addition reminder.
4. A DDT based automated testing method according to claim 1, characterized in that: in S3, adding an execution method in a preset method execution list, and adding corresponding test data in a preset parameter execution list, including the following steps:
adding the execution method to the end of the element in the preset method execution list, and adding the test data to the end of the element in the preset parameter execution list.
5. A DDT based automated testing method according to claim 2, characterized in that: automatically creating a data list from the path annotation in S3, comprising the steps of:
the testing method comprises the steps of testing parameter names of data to be tested, creating a data list under a specified path according to path annotations, wherein the data list comprises the data names, and updating the data names in the data list according to the parameter names.
6. A DDT based automated testing method according to claim 1, characterized in that: the step of judging whether the method execution list and the parameter execution list have elements in S5 includes the following steps:
and generating a judgment result according to the method execution list and the parameter execution list, wherein the judgment result comprises an existing element and an nonexistent element, when the execution method exists in the method execution list and the test data exists in the parameter execution list, the judgment result of the existing element is generated, otherwise, the judgment result of the nonexistent element is generated.
7. A DDT based automated testing method according to claim 1, characterized in that: the execution result is recorded in S6, and the method includes the following steps:
and outputting the execution result to a preset detail file for recording.
8. Automatic testing arrangement based on DDT, its characterized in that: use of the automated DDT-based testing method of any of claims 1-7.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202110165550.9A CN112882931B (en) | 2021-02-06 | 2021-02-06 | Automatic test method and device based on DDT |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202110165550.9A CN112882931B (en) | 2021-02-06 | 2021-02-06 | Automatic test method and device based on DDT |
Publications (2)
Publication Number | Publication Date |
---|---|
CN112882931A true CN112882931A (en) | 2021-06-01 |
CN112882931B CN112882931B (en) | 2023-05-09 |
Family
ID=76055956
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202110165550.9A Active CN112882931B (en) | 2021-02-06 | 2021-02-06 | Automatic test method and device based on DDT |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN112882931B (en) |
Citations (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE19650293C1 (en) * | 1996-12-04 | 1998-04-09 | Siemens Ag | System component testing method for object-orientated program |
WO2001093043A1 (en) * | 2000-03-27 | 2001-12-06 | Accenture Llp | System, method, and article of manufacture for an automated scripting solution for enterprise testing |
US20030056150A1 (en) * | 2001-09-14 | 2003-03-20 | David Dubovsky | Environment based data driven automated test engine for GUI applications |
CN101158919A (en) * | 2007-11-07 | 2008-04-09 | 中兴通讯股份有限公司 | Unit test method driven by data |
CN102486749A (en) * | 2010-12-03 | 2012-06-06 | 中兴通讯股份有限公司 | Method and system for data driving test |
CN104407973A (en) * | 2014-11-25 | 2015-03-11 | 珠海格力电器股份有限公司 | Method and device for realizing automatic unit test |
CN104598376A (en) * | 2014-12-30 | 2015-05-06 | 中国科学院计算机网络信息中心 | Data driving layered automation test system and method |
CN107832220A (en) * | 2017-11-15 | 2018-03-23 | 中国银行股份有限公司 | A kind of method and system for generating test script |
CN108536593A (en) * | 2018-04-02 | 2018-09-14 | 泰华智慧产业集团股份有限公司 | CS Framework Softwares automated testing method based on UI and system |
CN108595342A (en) * | 2018-05-14 | 2018-09-28 | 杭州有赞科技有限公司 | Unit test method and device |
CN108897687A (en) * | 2018-06-29 | 2018-11-27 | 泰华智慧产业集团股份有限公司 | A kind of API automated testing method and system based on data-driven |
CN109800154A (en) * | 2018-12-15 | 2019-05-24 | 深圳壹账通智能科技有限公司 | Loading method, device, computer equipment and the storage medium of test data |
CN111159049A (en) * | 2019-12-31 | 2020-05-15 | 中国银行股份有限公司 | Automatic interface testing method and system |
CN111459821A (en) * | 2020-04-01 | 2020-07-28 | 汇通达网络股份有限公司 | Software automation unit testing method based on TestNG |
CN111625445A (en) * | 2020-04-23 | 2020-09-04 | 平安国际智慧城市科技股份有限公司 | Java-based test framework construction method and device and storage medium |
CN111752834A (en) * | 2020-06-24 | 2020-10-09 | 京东数字科技控股有限公司 | Automatic testing method and device |
CN111858386A (en) * | 2020-08-05 | 2020-10-30 | 深圳壹账通智能科技有限公司 | Data testing method and device, computer equipment and storage medium |
-
2021
- 2021-02-06 CN CN202110165550.9A patent/CN112882931B/en active Active
Patent Citations (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE19650293C1 (en) * | 1996-12-04 | 1998-04-09 | Siemens Ag | System component testing method for object-orientated program |
WO2001093043A1 (en) * | 2000-03-27 | 2001-12-06 | Accenture Llp | System, method, and article of manufacture for an automated scripting solution for enterprise testing |
US20030056150A1 (en) * | 2001-09-14 | 2003-03-20 | David Dubovsky | Environment based data driven automated test engine for GUI applications |
CN101158919A (en) * | 2007-11-07 | 2008-04-09 | 中兴通讯股份有限公司 | Unit test method driven by data |
CN102486749A (en) * | 2010-12-03 | 2012-06-06 | 中兴通讯股份有限公司 | Method and system for data driving test |
CN104407973A (en) * | 2014-11-25 | 2015-03-11 | 珠海格力电器股份有限公司 | Method and device for realizing automatic unit test |
CN104598376A (en) * | 2014-12-30 | 2015-05-06 | 中国科学院计算机网络信息中心 | Data driving layered automation test system and method |
CN107832220A (en) * | 2017-11-15 | 2018-03-23 | 中国银行股份有限公司 | A kind of method and system for generating test script |
CN108536593A (en) * | 2018-04-02 | 2018-09-14 | 泰华智慧产业集团股份有限公司 | CS Framework Softwares automated testing method based on UI and system |
CN108595342A (en) * | 2018-05-14 | 2018-09-28 | 杭州有赞科技有限公司 | Unit test method and device |
CN108897687A (en) * | 2018-06-29 | 2018-11-27 | 泰华智慧产业集团股份有限公司 | A kind of API automated testing method and system based on data-driven |
CN109800154A (en) * | 2018-12-15 | 2019-05-24 | 深圳壹账通智能科技有限公司 | Loading method, device, computer equipment and the storage medium of test data |
CN111159049A (en) * | 2019-12-31 | 2020-05-15 | 中国银行股份有限公司 | Automatic interface testing method and system |
CN111459821A (en) * | 2020-04-01 | 2020-07-28 | 汇通达网络股份有限公司 | Software automation unit testing method based on TestNG |
CN111625445A (en) * | 2020-04-23 | 2020-09-04 | 平安国际智慧城市科技股份有限公司 | Java-based test framework construction method and device and storage medium |
CN111752834A (en) * | 2020-06-24 | 2020-10-09 | 京东数字科技控股有限公司 | Automatic testing method and device |
CN111858386A (en) * | 2020-08-05 | 2020-10-30 | 深圳壹账通智能科技有限公司 | Data testing method and device, computer equipment and storage medium |
Non-Patent Citations (2)
Title |
---|
刘跃光: "浅谈数据驱动测试(DDT)在银行系统中的应用", 《中国金融电脑》 * |
江屿: "基于Junit的接口测试框架的设计与实现", 中国优秀硕士学位论文全文数据库 信息科技辑 * |
Also Published As
Publication number | Publication date |
---|---|
CN112882931B (en) | 2023-05-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP2783641B2 (en) | Design evaluation method and design evaluation tool | |
CN100401265C (en) | Keyword-driven automatic testing system and method | |
CN110716870B (en) | Automatic service testing method and device | |
US8555234B2 (en) | Verification of soft error resilience | |
US20070094541A1 (en) | Method and apparatus for generating test execution sequences automatically for a software testing process | |
CN109189479B (en) | Parallel automatic verification method for processor instruction set | |
CN108763091B (en) | Method, device and system for regression testing | |
US7895575B2 (en) | Apparatus and method for generating test driver | |
US20090019427A1 (en) | Method and Apparatus for Providing Requirement Driven Static Analysis of Test Coverage for Web-Based, Distributed Processes | |
CN111538659B (en) | Interface testing method, system, electronic equipment and storage medium of business scene | |
CN106776334A (en) | Based on annotation generation method of test example and device | |
CN112181854A (en) | Method, device, equipment and storage medium for generating flow automation script | |
CN103678116A (en) | Method and system for facilitating automated program testing | |
US9274933B2 (en) | Pretest setup planning | |
US6546526B2 (en) | Active trace debugging for hardware description languages | |
CN112882931A (en) | Automatic testing method and device based on DDT | |
CN111880803B (en) | Software construction method and device applied to multiple platforms | |
CN113485919A (en) | Test method, test device and computer readable storage medium | |
CN111651360B (en) | Test method, test device, electronic equipment and medium | |
CN117573564B (en) | Method for automatically identifying differences based on gitlab code submitted log | |
US8751870B2 (en) | Method and system for providing a random sequence coverage | |
CN110765020B (en) | Test case generation method based on domain knowledge | |
CN111708572B (en) | Automatic control flow chart generation method based on Clang program structure | |
JP5140691B2 (en) | Integration test system, integration test method, and integration test program | |
CN115525577A (en) | Method for testing and managing based on automation data and process |
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 |