CN112527680B - Project API level full-link automatic test method and system based on Fitnesse framework - Google Patents
Project API level full-link automatic test method and system based on Fitnesse framework Download PDFInfo
- Publication number
- CN112527680B CN112527680B CN202011545830.4A CN202011545830A CN112527680B CN 112527680 B CN112527680 B CN 112527680B CN 202011545830 A CN202011545830 A CN 202011545830A CN 112527680 B CN112527680 B CN 112527680B
- Authority
- CN
- China
- Prior art keywords
- link
- level full
- full
- project api
- project
- 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.)
- Active
Links
- 238000010998 test method Methods 0.000 title claims abstract description 7
- 238000012360 testing method Methods 0.000 claims abstract description 122
- 238000013515 script Methods 0.000 claims abstract description 43
- 238000011161 development Methods 0.000 claims abstract description 32
- 238000009960 carding Methods 0.000 claims abstract description 20
- 238000000034 method Methods 0.000 claims description 20
- 230000008569 process Effects 0.000 claims description 11
- 238000004806 packaging method and process Methods 0.000 claims description 10
- 239000008186 active pharmaceutical agent Substances 0.000 description 41
- 230000010354 integration Effects 0.000 description 5
- 238000012986 modification Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 2
- 230000008676 import Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000005538 encapsulation Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 239000000779 smoke Substances 0.000 description 1
- 238000013522 software testing Methods 0.000 description 1
- 239000012085 test solution Substances 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
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/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Test And Diagnosis Of Digital Computers (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention provides a project API level full-link automatic test method and system based on a Fitnesse framework, comprising the following steps: step M1: constructing a jar package of secondary development engineering, and generalizing operation types used for project API level full-link testing into tool types; step M2: based on jar package of secondary development engineering, realizing a general control class through Cglib reverse proxy; step M3: carding project API level full-link test operation steps to obtain corresponding step description; step M4: according to project API level full-link test operation steps, carding into Wiki Comment according to the sequence; step M5: and according to the project API level full-link test operation step, calling an interface of the secondary development engineering general control class according to the Wiki Comment, and completing the full-link automatic test script. The invention solves the wiki separator problem of Fitnesse framework native through secondary development of replacing the pipeline character with other special characters.
Description
Technical Field
The invention relates to the technical field of blockchains, in particular to a project API-level full-link automatic test method and system based on a Fitnesse frame, and more particularly relates to a project API-level full-link automatic test solution based on the Fitnesse frame.
Background
In the software testing process, especially in the internet technology, the time from the requirement standpoint to the version on-line is short, the iteration of the version is very fast, and a large number of repeated regression tests are needed by testers to ensure the on-line quality. In these regression tests, the interface class is the dominant one. In the field of testing, interface testing belongs to a complex test, and because no interface exists, the interface is required to be manually called, and the result is compared, so that the testing efficiency is low and the testing time is long.
Patent document CN108334449a (application number 201810076537.4) discloses a method and a device for automatic testing of interfaces, and relates to the technical field of computers. One embodiment of the method comprises the following steps: building an interface test framework and a continuous integration tool in a test environment; creating a test task through a continuous integration tool, and configuring configuration information of the test task; based on the configuration information of the test task, the test class is called by running the test task to execute the test case, so that a test result is obtained. The embodiment can solve the problem that continuous automatic test cannot be realized. One embodiment of the patent includes: building an interface test framework and a continuous integration tool in a test environment; creating a test task through a continuous integration tool, and configuring configuration information of the test task; based on the configuration information of the test task, the test class is called by running the test task to execute the test case, so that a test result is obtained. The implementation mode can solve the problem that continuous integrated test cannot be realized. The invention aims to solve the problem of full-link automatic test, and is different from the access point of the patent. The patent cut-in point is continuous integration, the secondary development of the packaging content is mainly based on the test result, and the packaging of the generalized calling tool in the full-link automatic test process is not mentioned. The invention uses the operation type generalization tool API in the project full-link automation process to enable the team by a secondary development method based on the Fitnesse framework, reduces the technical threshold and strings the project full-link automation.
Disclosure of Invention
Aiming at the defects in the prior art, the invention aims to provide a project API-level full-link automatic test method and system based on a Fitnesse framework.
The project API level full-link automatic testing method based on the Fitnesse framework provided by the invention comprises the following steps:
step M1: constructing a jar package of secondary development engineering, and generalizing operation types used for project API level full-link testing into tool types;
step M2: based on jar package of secondary development engineering, realizing a general control class through Cglib reverse proxy;
step M3: carding project API level full-link test operation steps to obtain corresponding step description;
step M4: according to project API level full-link test operation steps, carding into Wiki Comment according to the sequence;
step M5: and according to the project API level full-link test operation step, calling an interface of the secondary development engineering general control class according to the Wiki Comment, and completing the full-link automatic test script.
Preferably, generalizing the operation type used for the project API-level full link test into the tool class in the step M1 includes: http & Hppts, dubbo, redis, nacos configuration & registry, kafka, mysql, minio, zookeeper, eureka, random content generation, date class, encryption and decryption library packaging, and/or Linux command execution.
Preferably, the step M1 further includes replacing the pipeline symbol with a preset special character in the process of generalizing the operation type used for the project API level full-link test into the tool class.
Preferably, the step M3 includes: and (3) a step of carding the project API level full-link test operation, wherein a step description comprising the called interface name, the Kafka Topic and the message body is acquired through a packet capturing mode.
Preferably, the step M5 includes: each row of script of Wiki Comment sequentially calls the total control class in the Jar package; calling a specific interface of a specific tool class through the master control class so as to execute script specific operation; and generating a test report after the script in the preset range is executed.
The project API-level full-link automatic test system based on the Fitnesse framework provided by the invention comprises:
module M1: constructing a jar package of secondary development engineering, and generalizing operation types used for project API level full-link testing into tool types;
module M2: based on jar package of secondary development engineering, realizing a general control class through Cglib reverse proxy;
module M3: carding project API level full-link test operation steps to obtain corresponding step description;
module M4: according to project API level full-link test operation steps, carding into Wiki Comment according to the sequence;
module M5: and according to the project API level full-link test operation step, calling an interface of the secondary development engineering general control class according to the Wiki Comment, and completing the full-link automatic test script.
Preferably, generalizing the operation types used for the project API-level full link test into tool classes in the module M1 includes: http & Hppts, dubbo, redis, nacos configuration & registry, kafka, mysql, minio, zookeeper, eureka, random content generation, date class, encryption and decryption library packaging, and/or Linux command execution.
Preferably, the module M1 further includes replacing the pipeline symbol with a preset special character in the process of generalizing the operation type used for the project API level full-link test into the tool class.
Preferably, the module M3 comprises: and (3) a step of carding the project API level full-link test operation, wherein a step description comprising the called interface name, the Kafka Topic and the message body is acquired through a packet capturing mode.
Preferably, the module M5 comprises: each row of script of Wiki Comment sequentially calls the total control class in the Jar package; calling a specific interface of a specific tool class through the master control class so as to execute script specific operation; and generating a test report after the script in the preset range is executed.
Compared with the prior art, the invention has the following beneficial effects:
1. in the service full-link test, the operations of message middleware Kafka, cache middleware Redis, database middleware mysql, linux command execution, nacos configuration center, json analysis, encryption and decryption, job execution and the like are used.
2. Automated testing often requires programming experience and middleware usage experience. The accurate familiarity project whole-process business of the new colleague consumes a long time. For each iteration, the test environment availability verification, smoke test, manual regression test require a significant amount of time. Therefore, based on the Fitnesse framework, various types of operations which can be involved in the testing process are packaged into tool types through secondary development, and through the Cglib reverse proxy of JAVA, the project full-link automatic testing threshold is reduced, the writing convenience of testing scripts is improved, and team enabling is realized.
3. The invention solves the wiki separator problem of Fitnesse framework native through secondary development of replacing the pipeline character with other special characters.
Drawings
Other features, objects and advantages of the present invention will become more apparent upon reading of the detailed description of non-limiting embodiments, given with reference to the accompanying drawings in which:
FIG. 1 is an execution flow of a single full link automation test script;
FIG. 2 is a schematic diagram of a project API-level full-link automated test system architecture based on the Fitnesse framework;
fig. 3 is a logic diagram of a project API-level full-link automated test system based on the Fitnesse framework.
Detailed Description
The present invention will be described in detail with reference to specific examples. The following examples will assist those skilled in the art in further understanding the present invention, but are not intended to limit the invention in any way. It should be noted that variations and modifications could be made by those skilled in the art without departing from the inventive concept. These are all within the scope of the present invention.
Example 1
According to the project API level full-link automatic test method based on the Fitnesse framework, as shown in FIG. 1, the method comprises the following steps:
step M1: constructing a jar package of secondary development engineering, and generalizing operation types used for project API level full-link testing into tool types;
step M2: based on jar package of secondary development engineering, realizing a general control class through Cglib reverse proxy;
step M3: carding project API level full-link test operation steps to obtain corresponding step description;
step M4: according to project API level full-link test operation steps, carding into Wiki Comment according to the sequence;
step M5: and according to the project API level full-link test operation step, calling an interface of the secondary development engineering general control class according to the Wiki Comment, and completing the full-link automatic test script.
Specifically, generalizing the operation types used for the project API-level full-link test into tool classes in the step M1 includes: http & Hppts, dubbo, redis, nacos configuration & registry, kafka, mysql, minio, zookeeper, eureka, random content generation, date class, encryption and decryption library packaging, and/or Linux command execution.
Specifically, the step M1 further includes replacing the pipeline symbol with a preset special character in the process of generalizing the operation type used for the project API level full-link test into the tool class.
Specifically, the step M3 includes: and (3) a step of carding the project API level full-link test operation, wherein a step description comprising the called interface name, the Kafka Topic and the message body is acquired through a packet capturing mode.
Specifically, the step M5 includes: each row of script of Wiki Comment sequentially calls the total control class in the Jar package; calling a specific interface of a specific tool class through the master control class so as to execute script specific operation; and generating a test report after the script in the preset range is executed.
According to the project API-level full-link automatic test system based on Fitnesse framework provided by the invention, as shown in fig. 2, the project API-level full-link automatic test system comprises:
module M1: constructing a jar package of secondary development engineering, and generalizing operation types used for project API level full-link testing into tool types;
module M2: based on jar package of secondary development engineering, realizing a general control class through Cglib reverse proxy;
module M3: carding project API level full-link test operation steps to obtain corresponding step description;
module M4: according to project API level full-link test operation steps, carding into Wiki Comment according to the sequence;
module M5: and according to the project API level full-link test operation step, calling an interface of the secondary development engineering general control class according to the Wiki Comment, and completing the full-link automatic test script.
Specifically, generalizing the operation types used for the project API-level full-link test into tool classes in the module M1 includes: http & Hppts, dubbo, redis, nacos configuration & registry, kafka, mysql, minio, zookeeper, eureka, random content generation, date class, encryption and decryption library packaging, and/or Linux command execution.
Specifically, the module M1 further includes replacing the pipeline symbol with a preset special character in the process of generalizing the operation type used for the project API level full-link test into the tool class.
Specifically, the module M3 includes: and (3) a step of carding the project API level full-link test operation, wherein a step description comprising the called interface name, the Kafka Topic and the message body is acquired through a packet capturing mode.
Specifically, the module M5 includes: each row of script of Wiki Comment sequentially calls the total control class in the Jar package; calling a specific interface of a specific tool class through the master control class so as to execute script specific operation; and generating a test report after the script in the preset range is executed.
Example 2
Example 2 is a modification of example 1
The invention relates to the technical fields of secondary development based on the use aspect of commonly used technical middleware, encryption and decryption technology, fitnesse automatic test framework, reverse proxy technology, full-link automatic test technology and the like. Through various operation types in the packaging function test process, an energy team is enabled, an automatic test threshold is reduced, and programming experience requirements are avoided. The user can easily complete the automatic test script by being familiar with the measured object service and knowing the operation flow.
Step 1: and constructing a secondary development project, and generalizing the operation types used for the project full-link test into tool types.
Step 2: and realizing a total control class through the Cglib reverse proxy, participating in tool class constructors as the participating of the total control class constructors, and packaging tool APIs to be exposed to the test script.
Step 3: the secondary development engineering is made into jar package and is introduced as plug-in of Fitnesse
Step 4: and calling an interface of a secondary development engineering general control class according to the project full-link operation step to complete the full-link automatic test script.
The step 1 comprises the following sub-steps:
step 1.1: only the tool class of the generalization call is provided and is not related to any business so as to provide a generalized service;
step 1.2: the functionality of the tool class is covered.
Support for, but not limited to, http & Hppts, dubbo, redis, nacos configuration & registry, kafka, mysql, minio, zookeeper, eureka, random content generation, date class, encryption and decryption library encapsulation, linux command execution, etc.
Step 1.3: and (5) processing the pipeline symbols.
Since the Finesse front-end script is a wiki grammar, and the pipeline symbol is present as a separator of the script table, for example, a scene of using the pipeline symbol in a Linux command needs to be replaced by other special characters, for example, if ps-ef|grep java is to be executed in the wiki script, the script is written into ps-ef|grep java, and the pipeline symbol problem of the wiki grammar can be solved by automatically converting the pipeline symbol into ps-ef|grep java when the tool class executes the command.
The step 2 has the advantages that: the interface in the secondary development engineering can be accessed only by one class of the report master control class in the automation script, so that the efficiency is high.
The step 3 comprises the following sub-steps:
step 3.1: wiki script-! Path-designated jar packet path
Step 3.2: upper-level testStuiste, import generic control class
After the steps are completed, a tool interface provided by secondary development engineering can be called in the automatic test script, and the subtest suite and each testCase do not need to additionally import a total control class.
Example 3
Example 3 is a modification of example 1 and/or example 2
As shown in fig. 3, a flowchart of the use case execution is shown, and the steps are as follows:
step 1: entering a TestSuite;
step 2: executing TearUp of the Testsuite dimension to prepare the current TestCase script before execution;
step 3: executing a first script TestCase1 in TestSuite;
step 4: according to the script line of the TestCase1, the generalized call of the total control class interface appointed in the script is executed successively; if the generalization calling interface exists, calling a specific generalization interface of a specific tool class through the general control class, and executing specific operation; the execution is successful or failed, and the next script TestCase2 is continuously executed;
step 5: after the step 4 is executed, if the interface called by generalization does not exist, the current Case fails to execute, and the next script TestCase2 is continuously executed;
step 6: after all the TestCases in the Testsuite are executed, the TearDown is executed to restore configuration/data/files and the like, so that the influence on the next script execution is avoided;
step 7: a test report is generated.
Those skilled in the art will appreciate that the systems, apparatus, and their respective modules provided herein may be implemented entirely by logic programming of method steps such that the systems, apparatus, and their respective modules are implemented as logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers, etc., in addition to the systems, apparatus, and their respective modules being implemented as pure computer readable program code. Therefore, the system, the apparatus, and the respective modules thereof provided by the present invention may be regarded as one hardware component, and the modules included therein for implementing various programs may also be regarded as structures within the hardware component; modules for implementing various functions may also be regarded as being either software programs for implementing the methods or structures within hardware components.
The foregoing describes specific embodiments of the present invention. It is to be understood that the invention is not limited to the particular embodiments described above, and that various changes or modifications may be made by those skilled in the art within the scope of the appended claims without affecting the spirit of the invention. The embodiments of the present application and features in the embodiments may be combined with each other arbitrarily without conflict.
Claims (8)
1. The project API level full-link automatic testing method based on the Fitnesse framework is characterized by comprising the following steps of:
step M1: constructing a jar package of secondary development engineering, and generalizing operation types used for project API level full-link testing into tool types;
step M2: based on jar package of secondary development engineering, realizing a general control class through Cglib reverse proxy;
step M3: carding project API level full-link test operation steps to obtain corresponding step description;
step M4: according to project API level full-link test operation steps, carding into Wiki Comment according to the sequence;
step M5: according to the project API level full-link test operation step, calling an interface of a secondary development engineering general control class according to Wiki Comment to complete a full-link automatic test script;
the step M5 includes: each row of script of Wiki Comment sequentially calls the total control class in the Jar package; calling a specific interface of a specific tool class through the master control class so as to execute script specific operation; and generating a test report after the script in the preset range is executed.
2. The method for automatically testing the project API full link based on Fitnesse framework according to claim 1, wherein the step M1 generalizes the operation types used for the project API full link test into tool classes, and the functional coverage of the tool classes includes: http & Https, dubbo, redis, nacos configuration & registry, kafka, mysql, minio, zookeeper, eureka, random content generation, date class, encryption and decryption library packaging, and/or Linux command execution.
3. The method for automatically testing the project API full link based on the Fitnesse framework according to claim 1, wherein said step M1 further comprises replacing the pipeline symbol with a preset special character in the process of generalizing the operation type used for the project API full link test into the tool class.
4. The Fitnesse framework-based project API-level full-link automation test method of claim 1, wherein said step M3 comprises: and (3) a step of carding the project API level full-link test operation, wherein a step description comprising the called interface name, the Kafka Topic and the message body is acquired through a packet capturing mode.
5. A project API-level full-link automated testing system based on a Fitnesse framework, comprising:
module M1: constructing a jar package of secondary development engineering, and generalizing operation types used for project API level full-link testing into tool types;
module M2: based on jar package of secondary development engineering, realizing a general control class through Cglib reverse proxy;
module M3: carding project API level full-link test operation steps to obtain corresponding step description;
module M4: according to project API level full-link test operation steps, carding into Wiki Comment according to the sequence;
module M5: according to the project API level full-link test operation step, calling an interface of a secondary development engineering general control class according to Wiki Comment to complete a full-link automatic test script;
the module M5 includes: each row of script of Wiki Comment sequentially calls the total control class in the Jar package; calling a specific interface of a specific tool class through the master control class so as to execute script specific operation; and generating a test report after the script in the preset range is executed.
6. The Fitnesse framework-based project API-level full-link automated testing system of claim 5, wherein said module M1 generalizes operation types used for project API-level full-link testing into tool classes, and functional coverage of the tool classes comprises: http & Https, dubbo, redis, nacos configuration & registry, kafka, mysql, minio, zookeeper, eureka, random content generation, date class, encryption and decryption library packaging, and/or Linux command execution.
7. The Fitnesse-framework-based project API-level full-link automatic test system of claim 5, wherein said module M1 further comprises replacing a pipe character with a predetermined special character in a process of generalizing an operation type used for project API-level full-link test into a tool class.
8. The Fitnesse framework-based project API-level full-link automated test system of claim 5, wherein said module M3 comprises: and (3) a step of carding the project API level full-link test operation, wherein a step description comprising the called interface name, the Kafka Topic and the message body is acquired through a packet capturing mode.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011545830.4A CN112527680B (en) | 2020-12-23 | 2020-12-23 | Project API level full-link automatic test method and system based on Fitnesse framework |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011545830.4A CN112527680B (en) | 2020-12-23 | 2020-12-23 | Project API level full-link automatic test method and system based on Fitnesse framework |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112527680A CN112527680A (en) | 2021-03-19 |
| CN112527680B true CN112527680B (en) | 2024-04-02 |
Family
ID=74976109
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011545830.4A Active CN112527680B (en) | 2020-12-23 | 2020-12-23 | Project API level full-link automatic test method and system based on Fitnesse framework |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112527680B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7685472B1 (en) * | 2007-01-30 | 2010-03-23 | Intuit, Inc. | Method and apparatus for testing object-oriented-programming methods |
| KR20100080044A (en) * | 2008-12-31 | 2010-07-08 | 엔에이치엔(주) | Method for generating api test case, and method for performing test case using the same |
| CN102063300A (en) * | 2010-12-21 | 2011-05-18 | 深圳市金蝶中间件有限公司 | Help documentation generating device and method |
| CN106326111A (en) * | 2016-08-11 | 2017-01-11 | 浪潮电子信息产业股份有限公司 | Fitnesse-based automatic testing framework for webpage and interface |
| CN107562626A (en) * | 2017-08-31 | 2018-01-09 | 国家电网公司 | A kind of method that encapsulation Selenium and Sikuli realizes Web automatic tests |
| CN109977020A (en) * | 2019-04-01 | 2019-07-05 | 山东威尔数据股份有限公司 | A kind of automated testing method |
| CN110321281A (en) * | 2019-05-24 | 2019-10-11 | 中国工程物理研究院计算机应用研究所 | Web test platform and test method based on mixing automated test frame |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR101728170B1 (en) * | 2011-03-21 | 2017-04-19 | 네이버 주식회사 | System and method for executing test with respect to web service automatically based on keyword |
| US10613966B2 (en) * | 2017-02-09 | 2020-04-07 | Wipro Limited | Method of controlling automation of testing applications and a system therefor |
| US10776253B2 (en) * | 2018-05-02 | 2020-09-15 | Dell Products L.P. | Test manager to coordinate testing across multiple test tools |
-
2020
- 2020-12-23 CN CN202011545830.4A patent/CN112527680B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7685472B1 (en) * | 2007-01-30 | 2010-03-23 | Intuit, Inc. | Method and apparatus for testing object-oriented-programming methods |
| KR20100080044A (en) * | 2008-12-31 | 2010-07-08 | 엔에이치엔(주) | Method for generating api test case, and method for performing test case using the same |
| CN102063300A (en) * | 2010-12-21 | 2011-05-18 | 深圳市金蝶中间件有限公司 | Help documentation generating device and method |
| CN106326111A (en) * | 2016-08-11 | 2017-01-11 | 浪潮电子信息产业股份有限公司 | Fitnesse-based automatic testing framework for webpage and interface |
| CN107562626A (en) * | 2017-08-31 | 2018-01-09 | 国家电网公司 | A kind of method that encapsulation Selenium and Sikuli realizes Web automatic tests |
| CN109977020A (en) * | 2019-04-01 | 2019-07-05 | 山东威尔数据股份有限公司 | A kind of automated testing method |
| CN110321281A (en) * | 2019-05-24 | 2019-10-11 | 中国工程物理研究院计算机应用研究所 | Web test platform and test method based on mixing automated test frame |
Non-Patent Citations (1)
| Title |
|---|
| 基于FitNesse的验收测试驱动开发;杨卫明;张聪;;计算机应用(第S1期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112527680A (en) | 2021-03-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Amalfitano et al. | A gui crawling-based technique for android mobile application testing | |
| CN110716870B (en) | Automatic service testing method and device | |
| US8352907B2 (en) | Software application recreation | |
| CN112084113B (en) | Configurable automatic test method and system based on embedded simulation verification software | |
| CN106909498B (en) | Method and system for injecting fault into Java program | |
| US10592703B1 (en) | Method and system for processing verification tests for testing a design under test | |
| Wen et al. | Pats: A parallel gui testing framework for android applications | |
| CN113254054B (en) | Intelligent contract one-stop development system and method | |
| CN112631919A (en) | Comparison test method and device, computer equipment and storage medium | |
| CN112650676A (en) | Software testing method, device, equipment and storage medium | |
| CN111679977B (en) | Method, equipment and storage medium for testing exact project unit based on Jest | |
| CN107622017B (en) | Analysis method for universal automation software test | |
| CN110688313B (en) | Fault injection method for software testing under VxWorks operating system | |
| Barbosa et al. | Verification and validation of (real time) COTS products using fault injection techniques | |
| CN112527680B (en) | Project API level full-link automatic test method and system based on Fitnesse framework | |
| Kranzlmüller et al. | NOPE: A nondeterministic program evaluator | |
| CN111274144A (en) | Unit testing method and system based on network file system operation word interface | |
| CN115934559A (en) | Testing method of intelligent form testing system | |
| CN115470141A (en) | Fault simulation method, device and related equipment | |
| CN115577673A (en) | Efficient verification method for 5G baseband chip system pin | |
| US20140047410A1 (en) | Method and system for semiconductor host simulation automation | |
| CN113641575A (en) | Test method, device, equipment and storage medium | |
| CN112241268A (en) | Keil engineering compiling method, system and equipment | |
| CN111881025A (en) | Automatic test task scheduling method, device and system | |
| Bathla et al. | Innovative approaches of automated tools in software testing and current technology as compared to manual testing |
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 |