CN110825645A - Assembly line type full-process automatic testing method - Google Patents
Assembly line type full-process automatic testing method Download PDFInfo
- Publication number
- CN110825645A CN110825645A CN201911097063.2A CN201911097063A CN110825645A CN 110825645 A CN110825645 A CN 110825645A CN 201911097063 A CN201911097063 A CN 201911097063A CN 110825645 A CN110825645 A CN 110825645A
- Authority
- CN
- China
- Prior art keywords
- test
- tested
- testing
- environment
- detected
- 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.)
- Pending
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 166
- 238000000034 method Methods 0.000 title claims abstract description 29
- 238000004801 process automation Methods 0.000 claims abstract description 9
- 238000004140 cleaning Methods 0.000 claims abstract description 8
- 238000012795 verification Methods 0.000 claims abstract description 6
- 238000004519 manufacturing process Methods 0.000 claims abstract description 5
- 238000010998 test method Methods 0.000 claims abstract description 4
- 238000007726 management method Methods 0.000 claims description 7
- 230000009191 jumping Effects 0.000 claims description 6
- 238000002360 preparation method Methods 0.000 claims description 6
- 238000004364 calculation method Methods 0.000 claims description 5
- 230000010354 integration Effects 0.000 claims description 3
- 238000003860 storage Methods 0.000 claims description 3
- 230000000694 effects Effects 0.000 abstract description 16
- 238000013522 software testing Methods 0.000 description 3
- BUGBHKTXTAQXES-UHFFFAOYSA-N Selenium Chemical compound [Se] BUGBHKTXTAQXES-UHFFFAOYSA-N 0.000 description 2
- 235000002597 Solanum melongena Nutrition 0.000 description 2
- 244000061458 Solanum melongena Species 0.000 description 2
- 229910052711 selenium Inorganic materials 0.000 description 2
- 239000011669 selenium Substances 0.000 description 2
- 238000004891 communication Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000011056 performance test Methods 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 238000013024 troubleshooting Methods 0.000 description 1
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/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
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3664—Environments for testing or debugging software
-
- 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
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)
- Debugging And Monitoring (AREA)
Abstract
A production line type full-process automatic test method comprises the following steps: acquiring an object to be detected, and performing hash value verification on the object to be detected; step two: deploying a test environment of an object to be tested; step three: testing the object to be tested by using a testing tool and obtaining a testing result; step four: cleaning the test environment, recovering to the state before deploying the test environment of the object to be tested, detecting whether a new test task exists, if so, skipping to the first step, and if not, ending the test flow. The assembly line type test activity full-process automation method disclosed by the invention can realize test full-process automation, all links are automatically connected, personnel participation is not required in the whole test activity, the test activity automation coverage rate is greatly improved, the test efficiency and the execution speed are improved, and the test risk caused by manual misoperation is effectively avoided.
Description
Technical Field
The invention relates to the technical field of software testing, in particular to a test flow management and test execution method.
Background
The software testing activity not only comprises the execution of testing on released software, but also comprises the steps of initiating a testing task, acquiring a tested object, checking the tested object, building a testing environment, deploying the tested software, collecting a testing result, recovering the testing environment, notifying the testing result and the like. However, at present, many papers, articles, and ideas related to test automation are focused on how to automate test execution, such as automation of performance test, and realization of function test, white box test, and the like by means of tools (pendy software test automation method research, electronic quality, 2018(11):45-46.), and insufficient attention on how to automate other links of test activities to improve efficiency.
However, in the overall testing activity, not only the testing execution is time-consuming, but also the building of the testing environment and the deployment of the tested software occupy valuable time for the testing personnel. Moreover, because the acquisition and verification of the tested object in the conventional test process are performed manually by the tester, if manual operation fails or is neglected (for example, when the tested object is acquired by operating the ClearCase configuration library, resources are forgotten to be refreshed), the later-stage error troubleshooting and rework can also consume a lot of time and energy of the tester.
The prior art discloses a software testing system and method (application number 201410757945.8), the system includes one or more array servers for storing virtual image files corresponding to different testing environments, the testing environments include an operating system and corresponding application programs; one or more test servers; the central server is used for receiving and storing the software to be tested and the testing environment information to be tested, and loading and operating the corresponding virtual mirror image files stored in the array server in one or more testing servers according to the testing environment information; and the communication module is used for loading along with the virtual mirror image file, running in the corresponding test server, communicating with the central server, downloading the software to be tested from the central server, and running the software to be tested in the test server. The invention does not need continuous participation of testing personnel in the whole testing process, avoids partial manual operation, simultaneously does not need one-to-one correspondence between the testing machine and the testing environment, and is more flexible to realize. But still require personnel to be on duty and perform critical manual operations. That is, the phenomena of large time consumption and low test efficiency due to the fact that the existing test automation concern is mostly performed in the test, the rest stages of the test activity are basically performed manually, and the automation degree is low still exist.
Disclosure of Invention
Aiming at the defects in the technology, the invention provides the production line type full-flow automatic testing method, which automatically covers all stages of testing activities, realizes full-flow automatic connection and unattended operation, improves the testing efficiency, saves the execution time, and avoids the testing risk caused by artificial misoperation.
To achieve the above object, the present invention is realized by:
a production line type full-process automatic test method is characterized by comprising the following steps:
the method comprises the following steps: acquiring an object to be detected, and performing hash value verification on the object to be detected;
step two: deploying a test environment of an object to be tested;
step three: testing the object to be tested by using a testing tool and obtaining a testing result;
step four: cleaning the test environment, recovering to the state before deploying the test environment of the object to be tested, detecting whether a new test task exists, if so, skipping to the first step, and if not, ending the test flow.
Further, the first step specifically includes:
step 100: a tester inputs a test task release order number on a task flow release platform, and the order number is transmitted into a Jenkins continuous integration platform;
step 101, after a test task release order number enters a system, a task flow release platform acquires XML format information of a release document;
102, analyzing data of a released document in an XML format, and extracting version information of an object to be detected released this time; the version information of the object to be tested comprises a software name, a type, a release version at this time, a label in a configuration library, a feature code, a required operation environment and the like.
103, after analyzing the relevant information of the object to be tested, Jenkins calls a clearase or git configuration library tool, connects the configuration library and downloads the corresponding object to be tested;
104, after the object to be detected is obtained, calling a hash value calculation tool to calculate the obtained characteristic value of the object to be detected;
step 105, comparing the calculated characteristic value of the object to be detected with the characteristic value of the object to be detected recorded in the corresponding release sheet by the program, and skipping to step 106 if the comparison result is inconsistent; if the comparison result is consistent, the program considers that the object to be detected is successfully obtained, and then the step 107 is carried out;
step 106, Jenkins considers that the file is in storage error or the network has error in the acquisition process, reports the error and exits, and ends the whole test flow;
and 107, Jenkins considers that the object to be tested is successfully obtained, starts an environment preparation module in the laboratory environment, ends unnecessary programs running on an industrial personal computer in the laboratory environment, and vacates hardware resources for deployment and testing of the object to be tested. The invention automatically calls a file hash value calculation tool through a program, calculates and downloads the data to be tested and software, compares the data to be tested and the software with the feature codes extracted from the test task release list, and replaces manual work to judge whether the file is correctly obtained.
Further, the second step specifically comprises:
and step 108, after the environment preparation module is operated, starting the automatic deployment tool, and deploying the software and data of the object to be tested on the prepared laboratory environment.
Further, the third step specifically comprises:
step 109, after deployment is completed, Jenkins starts an automatic test tool; the automatic testing tool includes, but is not limited to, software such as Eggplant, Selenium, and the like.
Step 110, Jenkins controls an automatic test tool to execute a pre-compiled test case, and tests an object to be tested;
step 111, Jenkins monitors the test process and judges whether the test case is executed completely; if the test cases are not completely executed, jumping to step 110; and if the test cases are completely executed, skipping to the fourth step.
Further, the fourth step specifically includes:
step 112, after the test is finished, the environment cleaning tool is started, the tested software is closed, the automatic test tool is quitted, and the operation of the surrounding environment is finished;
step 113, the task management platform detects whether a next test task exists in the system, and if so, the first step is skipped; if all the test tasks are completed and the next test task does not exist in the task management platform, jumping to step 114;
step 114, all the testing tasks are completed, the program ends the process and waits for a new testing command to be issued.
In the invention, whether the automatic test is finished or not is judged by monitoring the automatic test link, and after the test is finished, a mailbox interface is called to send a test report to a tester for verification according to the actual situation requirement. And by calling the environment cleaning module, the deployed and tested object to be tested is clarified, and the testing environment is recovered to an initial state to prepare for the next pipeline flow.
In a specific application scenario, other options may be added in the embodiment, such as adding options of manually confirming whether a test task is to be started, whether only deployment is to be performed without testing, whether to call a mail interface to notify related personnel after deployment is completed, and the like, so as to enhance the usability and compatibility of the method.
The method has the advantages that the method for the full-process automation of the assembly line type test activities can realize the full-process automation of the tests, all links are automatically connected, and the whole test activities do not need personnel to participate. According to the invention, automation of the previous testing links which need to be manually carried out is realized, and all the automation links are connected in series through assembly line operation, so that the whole automation of the testing activity is realized, the automation coverage rate of the testing activity is greatly improved, the testing efficiency and the execution speed are improved, and the testing risk caused by manual misoperation is effectively avoided.
Drawings
FIG. 1 is a block diagram of the architecture composition, module invocation relationship and staging of the present invention.
Fig. 2 is a flow chart of an example of an implementation of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
Reference is made to fig. 1-2.
A production line type full-process automatic test method is characterized by comprising the following steps:
the method comprises the following steps: acquiring an object to be detected, and performing hash value verification on the object to be detected;
step two: deploying a test environment of an object to be tested;
step three: testing the object to be tested by using a testing tool and obtaining a testing result;
step four: cleaning the test environment, recovering to the state before deploying the test environment of the object to be tested, detecting whether a new test task exists, if so, skipping to the first step, and if not, ending the test flow.
In this embodiment, the first step specifically includes:
step 100: a tester inputs a test task release order number on a task flow release platform, and the order number is transmitted into a Jenkins continuous integration platform;
step 101, after a test task release order number enters a system, a task flow release platform acquires XML format information of a release document;
102, analyzing data of a released document in an XML format, and extracting version information of an object to be detected released this time; the version information of the object to be tested comprises a software name, a type, a release version at this time, a label in a configuration library, a feature code, a required operation environment and the like.
103, after analyzing the relevant information of the object to be tested, Jenkins calls a clearase or git configuration library tool, connects the configuration library and downloads the corresponding object to be tested;
104, after the object to be detected is obtained, calling a hash value calculation tool to calculate the obtained characteristic value of the object to be detected;
step 105, comparing the calculated characteristic value of the object to be detected with the characteristic value of the object to be detected recorded in the corresponding release sheet by the program, and skipping to step 106 if the comparison result is inconsistent; if the comparison result is consistent, the program considers that the object to be detected is successfully obtained, and then the step 107 is carried out;
step 106, Jenkins considers that the file is in storage error or the network has error in the acquisition process, reports the error and exits, and ends the whole test flow;
and 107, Jenkins considers that the object to be tested is successfully obtained, starts an environment preparation module in the laboratory environment, ends unnecessary programs running on an industrial personal computer in the laboratory environment, and vacates hardware resources for deployment and testing of the object to be tested. The invention automatically calls a file hash value calculation tool through a program, calculates and downloads the data to be tested and software, compares the data to be tested and the software with the feature codes extracted from the test task release list, and replaces manual work to judge whether the file is correctly obtained.
In this embodiment, the second step specifically includes:
and step 108, after the environment preparation module is operated, starting the automatic deployment tool, and deploying the software and data of the object to be tested on the prepared laboratory environment.
In this embodiment, the third step specifically includes:
step 109, after deployment is completed, Jenkins starts an automatic test tool; the automatic testing tool includes, but is not limited to, software such as Eggplant, Selenium, and the like.
Step 110, Jenkins controls an automatic test tool to execute a pre-compiled test case, and tests an object to be tested;
step 111, Jenkins monitors the test process and judges whether the test case is executed completely; if the test cases are not completely executed, jumping to step 110; and if the test cases are completely executed, skipping to the fourth step.
In this embodiment, the fourth step specifically includes:
step 112, after the test is finished, the environment cleaning tool is started, the tested software is closed, the automatic test tool is quitted, and the operation of the surrounding environment is finished;
step 113, the task management platform detects whether a next test task exists in the system, and if so, the first step is skipped; if all the test tasks are completed and the next test task does not exist in the task management platform, jumping to step 114;
step 114, all the testing tasks are completed, the program ends the process and waits for a new testing command to be issued.
The method has the advantages that the method for the full-process automation of the assembly line type test activities can realize the full-process automation of the tests, all links are automatically connected, and the whole test activities do not need personnel to participate. According to the invention, automation of the previous testing links which need to be manually carried out is realized, and all the automation links are connected in series through assembly line operation, so that the whole automation of the testing activity is realized, the automation coverage rate of the testing activity is greatly improved, the testing efficiency and the execution speed are improved, and the testing risk caused by manual misoperation is effectively avoided.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents and improvements made within the spirit and principle of the present invention are intended to be included within the scope of the present invention.
Claims (5)
1. A production line type full-process automatic test method is characterized by comprising the following steps:
the method comprises the following steps: acquiring an object to be detected, and performing hash value verification on the object to be detected;
step two: deploying a test environment of an object to be tested;
step three: testing the object to be tested by using a testing tool and obtaining a testing result;
step four: cleaning the test environment, recovering to the state before deploying the test environment of the object to be tested, detecting whether a new test task exists, if so, skipping to the first step, and if not, ending the test flow.
2. The pipelined full-flow automation testing method of claim 1, the first step specifically comprising:
step 100: a tester inputs a test task release order number on a task flow release platform, and the order number is transmitted into a Jenkins continuous integration platform;
step 101, after a test task release order number enters a system, a task flow release platform acquires XML format information of a release document;
102, analyzing data of a released document in an XML format, and extracting version information of an object to be detected released this time;
103, after analyzing the relevant information of the object to be tested, Jenkins calls a clearase or git configuration library tool, connects the configuration library and downloads the corresponding object to be tested;
104, after the object to be detected is obtained, calling a hash value calculation tool to calculate the obtained characteristic value of the object to be detected;
step 105, comparing the calculated characteristic value of the object to be detected with the characteristic value of the object to be detected recorded in the corresponding release sheet by the program, and skipping to step 106 if the comparison result is inconsistent; if the comparison result is consistent, the program considers that the object to be detected is successfully obtained, and then the step 107 is carried out;
step 106, Jenkins considers that the file is in storage error or the network has error in the acquisition process, reports the error and exits, and ends the whole test flow;
and 107, Jenkins considers that the object to be tested is successfully obtained, starts an environment preparation module in the laboratory environment, ends unnecessary programs running on an industrial personal computer in the laboratory environment, and vacates hardware resources for deployment and testing of the object to be tested.
3. The pipelined full-process automation testing method of claim 1, step two specifically comprising:
and step 108, after the environment preparation module is operated, starting the automatic deployment tool, and deploying the software and data of the object to be tested on the prepared laboratory environment.
4. The pipelined full-process automation testing method of claim 1, step three specifically comprising:
step 109, after deployment is completed, Jenkins starts an automatic test tool;
step 110, Jenkins controls an automatic test tool to execute a pre-compiled test case, and tests an object to be tested;
step 111, Jenkins monitors the test process and judges whether the test case is executed completely; if the test cases are not completely executed, jumping to step 110; and if the test cases are completely executed, skipping to the fourth step.
5. The pipelined full-process automation testing method of claim 1, the fourth step specifically comprising:
step 112, after the test is finished, the environment cleaning tool is started, the tested software is closed, the automatic test tool is quitted, and the operation of the surrounding environment is finished;
step 113, the task management platform detects whether a next test task exists in the system, and if so, the first step is skipped; if all the test tasks are completed and the next test task does not exist in the task management platform, jumping to step 114;
step 114, all the testing tasks are completed, the program ends the process and waits for a new testing command to be issued.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911097063.2A CN110825645A (en) | 2019-11-11 | 2019-11-11 | Assembly line type full-process automatic testing method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911097063.2A CN110825645A (en) | 2019-11-11 | 2019-11-11 | Assembly line type full-process automatic testing method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110825645A true CN110825645A (en) | 2020-02-21 |
Family
ID=69554026
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911097063.2A Pending CN110825645A (en) | 2019-11-11 | 2019-11-11 | Assembly line type full-process automatic testing method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110825645A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111797018A (en) * | 2020-07-01 | 2020-10-20 | 卡斯柯信号(北京)有限公司 | STP test environment deployment method and device |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030182652A1 (en) * | 2001-12-21 | 2003-09-25 | Custodio Gabriel T. | Software building and deployment system and method |
| CN102420714A (en) * | 2011-08-29 | 2012-04-18 | 展讯通信（上海）有限公司 | Test managing method, test managing system master control center and test managing system |
| CN104360952A (en) * | 2012-03-02 | 2015-02-18 | 北京奇虎科技有限公司 | Software test system and software test method |
| CN105446878A (en) * | 2015-11-09 | 2016-03-30 | 上海爱数信息技术股份有限公司 | Continuous program automated testing method |
| CN106547688A (en) * | 2016-10-19 | 2017-03-29 | 厦门市美亚柏科信息股份有限公司 | Product automation method of testing and its system based on Windows |
| CN108334437A (en) * | 2018-03-02 | 2018-07-27 | 江苏电力信息技术有限公司 | It is a kind of that acceptance method is delivered based on the software continuous of continuous integrating and automatic test |
| CN108874650A (en) * | 2017-05-09 | 2018-11-23 | 上海秦苍信息科技有限公司 | A kind of continuous integrating automated testing method |
| CN109634855A (en) * | 2018-12-04 | 2019-04-16 | 郑州云海信息技术有限公司 | A kind of automatic test ambient intelligence matching process based on cloud computing |
| CN110096425A (en) * | 2018-12-10 | 2019-08-06 | 厦门市美亚柏科信息股份有限公司 | A kind of automated testing method based on QT development mode, device and storage medium |
-
2019
- 2019-11-11 CN CN201911097063.2A patent/CN110825645A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030182652A1 (en) * | 2001-12-21 | 2003-09-25 | Custodio Gabriel T. | Software building and deployment system and method |
| CN102420714A (en) * | 2011-08-29 | 2012-04-18 | 展讯通信（上海）有限公司 | Test managing method, test managing system master control center and test managing system |
| CN104360952A (en) * | 2012-03-02 | 2015-02-18 | 北京奇虎科技有限公司 | Software test system and software test method |
| CN105446878A (en) * | 2015-11-09 | 2016-03-30 | 上海爱数信息技术股份有限公司 | Continuous program automated testing method |
| CN106547688A (en) * | 2016-10-19 | 2017-03-29 | 厦门市美亚柏科信息股份有限公司 | Product automation method of testing and its system based on Windows |
| CN108874650A (en) * | 2017-05-09 | 2018-11-23 | 上海秦苍信息科技有限公司 | A kind of continuous integrating automated testing method |
| CN108334437A (en) * | 2018-03-02 | 2018-07-27 | 江苏电力信息技术有限公司 | It is a kind of that acceptance method is delivered based on the software continuous of continuous integrating and automatic test |
| CN109634855A (en) * | 2018-12-04 | 2019-04-16 | 郑州云海信息技术有限公司 | A kind of automatic test ambient intelligence matching process based on cloud computing |
| CN110096425A (en) * | 2018-12-10 | 2019-08-06 | 厦门市美亚柏科信息股份有限公司 | A kind of automated testing method based on QT development mode, device and storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111797018A (en) * | 2020-07-01 | 2020-10-20 | 卡斯柯信号(北京)有限公司 | STP test environment deployment method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107302476B (en) | Automatic testing method and system for testing asynchronous interactive system | |
| CN110008123B (en) | Method for automatically deploying test software and corresponding device | |
| EP1179776A1 (en) | Test automation framework | |
| CN112765028A (en) | Android application program testing method and system based on group control mechanism | |
| CN110990289B (en) | Method and device for automatically submitting bug, electronic equipment and storage medium | |
| CN110825645A (en) | Assembly line type full-process automatic testing method | |
| CN111193638A (en) | Linux platform based network card automatic testing method and device | |
| CN110198222B (en) | Plug-and-play test method and test master station for power distribution automation terminal | |
| CN116431522A (en) | Automatic test method and system for low-code object storage gateway | |
| CN110795341A (en) | Automatic testing method, system and device for server | |
| CN112596750B (en) | Application testing method and device, electronic equipment and computer readable storage medium | |
| JP2007140954A (en) | Operator simulation system and operator simulation method | |
| CN115576816A (en) | Linux operating system-based android application function automatic testing method and device | |
| CN115269443A (en) | Software defect automatic positioning test method and system | |
| CN111581081B (en) | Automatic test system and method | |
| CN110838951A (en) | Network equipment testing method and system | |
| CN110765011B (en) | Automatic acquisition and verification device and method for test operation and maintenance data in configuration library | |
| CN117492869B (en) | Visual automatic deployment service system and method | |
| CN114253867B (en) | Automatic testing method, device and system based on neural network model | |
| CN114610329B (en) | Solid state disk deployment method and device, readable storage medium and electronic equipment | |
| CN112579455B (en) | Automatic interface testing method and device, electronic equipment and storage medium | |
| CN114064508B (en) | Mobile terminal software testing method and system based on group control technology | |
| CN116303067B (en) | Testing method, device, equipment and medium based on cloud testing platform | |
| CN116932413B (en) | Defect processing method, defect processing device and storage medium for test task | |
| CN116820975A (en) | Interface software testing method and system based on script and electronic equipment |
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 | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20200221 |
|
| WD01 | Invention patent application deemed withdrawn after publication |