CN110704322B - Software testing method and system - Google Patents
Software testing method and system Download PDFInfo
- Publication number
- CN110704322B CN110704322B CN201910938815.7A CN201910938815A CN110704322B CN 110704322 B CN110704322 B CN 110704322B CN 201910938815 A CN201910938815 A CN 201910938815A CN 110704322 B CN110704322 B CN 110704322B
- Authority
- CN
- China
- Prior art keywords
- iteration
- case
- case set
- software
- use case
- 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
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/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Abstract
The application relates to a software testing method and a system, which belong to the technical field of software testing, and the software testing method comprises the following steps: creating an iteration case set for storing a current iteration case, a core case set for storing a test case aiming at a main flow of a product and a mirror case set for storing a historical iteration case in advance; carrying out configuration maintenance on the iteration use case set, the core use case set and the mirror image use case set; in the functional test, calling an iteration case set and a mirror image case set to carry out software functional test and defect verification; and after the software is released, calling the core case set to perform an online smoking test. By carrying out classification management on the cases in the software test and calling different case combinations at different testing stages, the reuse rate of the test cases is improved, and the efficiency of the software test is integrally improved.
Description
Technical Field
The application belongs to the technical field of software testing, and particularly relates to a software testing method and system.
Background
Computer systems are comprised of software, which is a program and corresponding documentation that runs on a computer, and hardware. Software generally exists to provide functionality to solve specific problems. After the computer software is developed, the computer software needs to be tested, whether the functions of the software meet the specification or not is tested, whether the performance of the software meets the requirements or not is tested, whether the software has safety problems or not is tested, and the like. The tests are carried out by depending on the design of the test cases, and the good test case design can cover enough scenes.
In the process of using the software, new functions and performance requirements are generated, or software functions which are not applicable any more are abandoned, and the test needs to be modified for many times. A large number of test cases are generated at this time. In the prior art, software testing of a software company writes test cases for iteration contents, after a plurality of iterations, no complete case can reflect the latest function of software, and the learning cost of a new person is high, so that the testing efficiency is influenced.
Disclosure of Invention
In order to overcome the problems in the related art at least to a certain extent, the application provides a software testing method and system, which are beneficial to improving the testing efficiency.
In order to achieve the purpose, the following technical scheme is adopted in the application:
in a first aspect,
the application provides a software testing method, which comprises the following steps:
creating an iteration case set for storing a current iteration case, a core case set for storing a test case aiming at a main flow of a product and a mirror case set for storing a historical iteration case in advance;
configuring and maintaining the iteration use case set, the core use case set and the mirror image use case set;
in the functional test, calling the iteration case set and the mirror image case set to perform software functional test and defect verification;
and after the software is released, calling the core case set to perform online smoke test.
Optionally, the configuring and maintaining the iteration use case set, the core use case set, and the mirror use case set includes:
in the first iteration of the process,
designing an iteration case aiming at the function of the iteration to be on-line and storing the iteration case into an iteration case set;
taking out the use cases aiming at the main flow in the iteration use case set and storing the use cases into the core use case set;
after the first iteration is finished, copying the use cases in the iteration use case set into the mirror image use case set, and emptying the iteration use case set;
in the following iteration(s) of the process,
and based on the function development condition of the current iteration, carrying out configuration maintenance on one or more of the iteration use case set, the core use case set and the mirror use case set.
Optionally, the function development condition of the current iteration includes adding a function on the basis of the last iteration, modifying a function on the basis of the last iteration, and deleting a function on the basis of the last iteration.
Optionally, when the current iteration is to add a function on the basis of the last iteration, performing configuration maintenance on the iteration use case set and the mirror use case set as follows:
designing an iteration case aiming at the newly added function and storing the iteration case into an iteration case set;
after the iteration is finished, copying the use cases in the iteration use case set into a mirror image use case set, and emptying the iteration use case set.
Optionally, when the current iteration is to modify the function on the basis of the last iteration, the following configuration maintenance is performed on the mirror use case set:
and modifying the corresponding function use case in the mirror image use case set aiming at the modified function.
Optionally, when the current iteration is to delete the function on the basis of the last iteration, the following configuration maintenance is performed on the mirror use case set:
and deleting the corresponding function use case in the mirror image use case set aiming at the function to be deleted.
Optionally, the method further includes checking and updating the core use case set, so that use cases in the core use case set always aim at the current main flow of the software.
Optionally, the method further comprises creating a regression case set for storing regression test cases in advance;
carrying out configuration maintenance on the regression case set;
and calling the mirror image case set and the regression case set for testing during regression testing.
Optionally, the configuring and maintaining the regression case set includes:
analyzing the defects found in the functional test, and finding typical defects of the software;
analyzing the use problems reported by the user after the software is released, and finding out the online defects of the software;
and storing the use cases designed for discovering the typical defects of the software and the defects on the software line into the regression use case set.
In a second aspect of the present invention,
the present application provides a software testing system, comprising:
the iteration use case module is used for storing a current iteration use case;
the core case module is used for storing a test case aiming at the main flow of the product;
the mirror image use case module is used for storing a historical iteration use case;
the regression case module is used for storing regression test cases;
the processing module is used for adding, deleting and modifying the iteration case module, the core case module, the mirror image case module and the regression case module;
and the test module is used for calling the cases in the iteration case module, the core case module, the mirror image case module and the regression case module to perform software test.
This application adopts above technical scheme, possesses following beneficial effect at least:
by carrying out classification management on the cases in the software test and calling different case combinations at different stages of the test, the reuse rate of the test cases is improved, the learning cost of the shift of testers and the replacement of the testers is reduced, and the efficiency of the software test is integrally improved.
Additional advantages, objects, and features of the invention will be set forth in part in the description which follows and in part will become apparent to those having ordinary skill in the art upon examination of the following or may be learned from practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
Drawings
The accompanying drawings are included to provide a further understanding of the technology or prior art of the present application and are incorporated in and constitute a part of this specification. The drawings expressing the embodiments of the present application are used for explaining the technical solutions of the present application, and should not be construed as limiting the technical solutions of the present application.
FIG. 1 is a schematic flow chart of a software testing method according to an embodiment of the present application;
fig. 2 is a schematic diagram illustrating use case configuration maintenance of a software testing method according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail below. It is to be understood that the embodiments described are only a few embodiments of the present application and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the examples given herein without making any creative effort, shall fall within the protection scope of the present application.
In order to facilitate understanding of the technical solutions of the present invention, a description will first be given of several concepts related to the present application.
On-line defects (on-line Bug): the problem is found when the real user uses the software after the software is released.
Typical defects (typical Bug): a problem occurring in a certain function of software may also occur in other modules or software.
Iteration: the method refers to that a product has a plurality of functions to be realized, a plan is realized according to a plurality of cycles, what contents are realized in each cycle are planned, and the fixed cycle is called iteration.
In software testing, test cases are necessarily involved. In the existing software test, cases are designed aiming at new functions of software, the classification mode of the cases is greatly related to the habits or styles of personnel designing the cases, and the cases are uploaded to a test case storage tool of a company after being designed. And when the function changes, a test case is designed aiming at the new function and is uploaded to a case storage tool. After several iterations, the test case corresponding to the latest function of the software needs to browse historical test cases, possibly in a case document uploaded for the first time, possibly in a case document uploaded for the second time, and possibly no corresponding case at all. When the software is regressed before online, a new function is tested according to the test case, the previous function can only be supplemented back to the test case, or the test is performed by experience or exploratory test, and the probability of test omission is very high. In other words, in the existing software testing method, effective management on test cases is lacked, and the software testing efficiency is low due to low reuse rate.
To this end, the present application proposes a software testing method, as shown in fig. 1, in which the following steps are included:
step S110, an iteration case set used for storing a current iteration case, a core case set used for storing a test case aiming at a main flow of a product and a mirror case set used for storing a historical iteration case are created in advance.
And step S120, carrying out configuration maintenance on the iteration use case set, the core use case set and the mirror use case set. The configuration maintenance includes operations such as adding, modifying, and deleting use cases to each use case set, so that each use case set includes a corresponding test use case, and a specific configuration maintenance process will be further described later.
Step S130, calling the iteration case set and the mirror image case set to perform software function test and defect verification in the function test;
and step S140, after the software is released, calling the core case set to perform on-line smoke test. The online smoking test refers to a function use test which is performed on the released software quickly once in the first time after the software is released.
According to the method and the device, cases in the software test are classified, hierarchical organization and management are carried out, different case combinations are called at different stages of the test, the reusability of the test cases is improved, the learning cost of the test personnel on duty and replacement of the test personnel is reduced, and the efficiency of the software test is integrally improved.
The technical solution of the present invention is specifically described below with a specific example.
Aiming at a certain software product for development and test, an iteration case set for storing a current iteration case, a core case set for storing a test case aiming at a main flow of the product and a mirror case set for storing a historical iteration case are created in advance.
In this embodiment, configuration and maintenance are performed on the iteration use case set, the core use case set, and the mirror use case set, which specifically include two scenarios, that is, the first iteration and the iteration after the first iteration, which are described below.
First iteration
The first iteration here refers to the iterative testing of the software to be developed from scratch, with the online function to be performed for the first iteration. In the first iteration, an iteration case is designed according to the function of the iteration to be on-line and is stored into an iteration case set, and cases aiming at the main flow in the iteration case set are taken out and stored into a core case set;
in the function test of the first iteration, calling the use cases in the iteration use case set and the mirror image use case set (empty at the moment) to perform software function test and defect verification;
after the first iteration is finished, copying the use cases in the iteration use case set into the mirror image use case set, and emptying the iteration use case set. And certainly, after the first iteration is finished, the software product can be released for the first time, and after the software is released for the first time, the core case set is called to carry out the online smoking test.
Subsequent iteration
The subsequent iteration pointer is used for performing secondary iteration on the software product and performing iteration after the second iteration. In the subsequent iteration, based on the function development condition of the current iteration, one or more of the iteration use case set, the core use case set and the mirror use case set are configured and maintained.
Specifically, the function development situation of the current iteration includes adding functions on the basis of the last iteration, modifying functions on the basis of the last iteration, and deleting functions on the basis of the last iteration.
For example, the current iteration is the second iteration, and the functional development conditions of the second iteration of the software product are not three conditions: adding new functions on the basis of the last (first) iteration; finding that the last (first) function does not meet the requirement of the user, and modifying the function; it is found that the function of the last (first) iteration is not used at all, and it is deleted.
For these three cases, configuration maintenance is performed on one or more of the use case sets. In particular, the method comprises the following steps of,
(1) When the current iteration is to add functions on the basis of the last iteration, the following configuration maintenance is carried out on the iteration use case set and the mirror image use case set:
designing an iteration case aiming at the newly added function and storing the iteration case into an iteration case set;
after the iteration is finished, copying the use cases in the iteration use case set into the mirror image use case set, and emptying the iteration use case set.
(2) When the current iteration is to modify the function on the basis of the last iteration, the following configuration maintenance is carried out on the mirror image case set:
and modifying the corresponding function case in the mirror image case set according to the modified function without rewriting a test case.
(3) When the current iteration is to delete the function on the basis of the last iteration, the mirror image case set is configured and maintained as follows:
and deleting the corresponding function use case in the mirror image use case set aiming at the function to be deleted.
In addition, in this embodiment, in all of the three cases, the method further includes checking and updating the core case set, so that the use cases in the core case set always aim at the configuration maintenance process of the current main flow of the software. For example, a main process case with a newly added function is designed, and is placed into the core case set, for example, when the main process case is modified and deleted in the iteration, corresponding modification and deletion are performed in the core case set. It should be noted that, in the foregoing iteration and the issuance after the iteration, a process similar to the process of testing the call case set combination in the first iteration is also included.
On the basis of the above embodiment, in another embodiment, the software testing method in the present invention further includes creating a regression case set in advance for storing regression test cases;
configuring and maintaining the regression case set;
during regression testing (for example, regression testing before the software is finally online), the mirror case set and the regression case set are called for testing.
Specifically, the configuring and maintaining of the regression case set includes,
in each iteration, analyzing the defects found in the functional test to find typical software defects; after each iteration, analyzing the use problems reported by the user after the software is released, and finding out the online defects of the software; and storing the use cases designed for finding the typical defects of the software and the defects on the software line into a regression use case set.
In this embodiment, the example configuration maintenance in the software testing method of the present application is shown in fig. 2. In order to further understand the technical solution of the present application with reference to fig. 2, differences and uses of the core use case (core use case set), the mirror use case (mirror use case set), the iteration use case (iteration use case set), and the regression use case (regression use case set) in the embodiment technical solution of the present application are further described below:
core use case versus mirror use case: the core use case reflects the main flow (core flow) of the product, and the mirror use case reflects all the functional points of the current product.
Iterative use case versus mirror use case: the iteration use case is a function check point for a specific iteration, and the mirror use case is a result of the iteration accumulating to the current state.
Regression case: the iteration process finds the extracted typical defects and converts the typical defects into regression cases, and the defects (typical defects) which occur on the line are converted into regression cases.
The core case can be used to understand the product, besides testing, it can be used by any interested person; the regression case is used for supplementing a test coverage scene, and the iteration case is used for checking a corresponding iteration function and is used by a tester; the mirror case is used for inheritance and is used for testing the old man/new entry of the group.
In addition, according to the human cost which can be input in the test, the configuration maintenance of the regression case set can be omitted, and the cases in the mirror case set are directly used for testing during the regression test.
An embodiment of the present application further provides a software testing system, including:
the iteration use case module is used for storing the current iteration use case;
the core case module is used for storing a test case aiming at the main flow of the product;
the mirror image use case module is used for storing a historical iteration use case;
the regression case module is used for storing regression test cases;
the processing module is used for adding, deleting and modifying the iteration case module, the core case module, the mirror image case module and the regression case module;
and the test module is used for calling cases in the iteration case module, the core case module, the mirror image case module and the regression case module to perform software test.
The specific implementation of the processing module and the testing module in the software testing system has been described in detail in relation to the embodiment of the method, and will not be elaborated here.
While the invention has been described with reference to specific preferred embodiments, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention as defined in the following claims. Therefore, the protection scope of the present invention should be subject to the protection scope of the claims.
Claims (8)
1. A software testing method, comprising:
creating an iteration case set for storing a current iteration case, a core case set for storing a test case aiming at a main flow of a product and a mirror case set for storing a historical iteration case in advance;
configuring and maintaining the iteration use case set, the core use case set and the mirror image use case set;
in the functional test, calling the iteration case set and the mirror image case set to perform software functional test and defect verification;
after the software is released, calling a core case centralized case to perform an online smoking test;
the configuration and maintenance of the iteration use case set, the core use case set and the mirror use case set includes:
in the first iteration of the process,
designing an iteration case aiming at the function of the iteration to be on-line and storing the iteration case into an iteration case set;
taking out the use cases aiming at the main flow in the iteration use case set and storing the use cases into the core use case set;
after the first iteration is finished, copying the use cases in the iteration use case set into the mirror image use case set, and emptying the iteration use case set;
in the following iteration(s) of the process,
based on the function development condition of the current iteration, carrying out configuration maintenance on one or more of the iteration use case set, the core use case set and the mirror image use case set;
the function development condition of the current iteration comprises the steps of adding functions on the basis of the last iteration, modifying the functions on the basis of the last iteration and deleting the functions on the basis of the last iteration.
2. The software testing method according to claim 1, wherein when the current iteration is to add functions on the basis of the last iteration, the following configuration maintenance is performed on the iteration case set and the mirror case set:
designing an iteration case aiming at the newly added function and storing the iteration case into an iteration case set;
after the iteration is finished, copying the use cases in the iteration use case set into a mirror image use case set, and emptying the iteration use case set.
3. The software testing method of claim 1, wherein when the current iteration is to modify the function on the basis of the last iteration, the mirror image case set is configured and maintained as follows:
and modifying the corresponding function use case in the mirror image use case set aiming at the modified function.
4. The software testing method according to claim 1, wherein when the current iteration is to delete functions on the basis of the last iteration, the following configuration maintenance is performed on the mirror image case set:
and deleting the corresponding function use case in the mirror image use case set aiming at the function to be deleted.
5. The software testing method according to any one of claims 2 to 4, further comprising checking and updating the core case set, so that the use cases in the core case set always aim at the current main flow of the software.
6. The software testing method according to claim 1, further comprising creating a regression case set for storing regression test cases in advance;
carrying out configuration maintenance on the regression case set;
and calling the mirror image case set and the regression case set for testing during regression testing.
7. The software testing method of claim 6, wherein the configuring and maintaining the regression case set comprises:
analyzing the defects found in the functional test, and finding typical defects of the software;
analyzing the use problems reported by users after the software is released, and finding out the online defects of the software;
and storing the use cases designed for finding the typical defects of the software and the defects on the software line into the regression use case set.
8. A software testing system, comprising:
the iteration use case module is used for storing the current iteration use case;
the core case module is used for storing a test case aiming at the main flow of the product;
the mirror image use case module is used for storing a historical iteration use case;
the regression case module is used for storing regression test cases;
the processing module is used for adding, deleting and modifying the iteration case module, the core case module, the mirror image case module and the regression case module;
the test module is used for calling the cases in the iteration case module, the core case module, the mirror image case module and the regression case module to perform software test;
the processing module configured to:
in the first iteration of the process,
designing an iteration case aiming at the function of the iteration to be on-line and storing the iteration case into the iteration case module;
taking out the use cases aiming at the main flow in the iteration use case module and storing the use cases into the core use case module;
after the first iteration is finished, copying the use case in the iteration use case module into the mirror image use case module, and emptying the iteration use case module;
in the following iteration(s) of the process,
based on the function development condition of the current iteration, one or more of the iteration use case module, the core use case module and the mirror use case module are configured and maintained;
the function development condition of the current iteration comprises the steps of adding functions on the basis of the last iteration, modifying the functions on the basis of the last iteration and deleting the functions on the basis of the last iteration.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910938815.7A CN110704322B (en) | 2019-09-30 | 2019-09-30 | Software testing method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910938815.7A CN110704322B (en) | 2019-09-30 | 2019-09-30 | Software testing method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110704322A CN110704322A (en) | 2020-01-17 |
| CN110704322B true CN110704322B (en) | 2023-03-10 |
Family
ID=69197720
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910938815.7A Active CN110704322B (en) | 2019-09-30 | 2019-09-30 | Software testing method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110704322B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102521376A (en) * | 2011-12-20 | 2012-06-27 | 上海电机学院 | Method for simplifying software test case suite |
| US8881095B1 (en) * | 2012-03-30 | 2014-11-04 | Sprint Communications Company L.P. | Software defect prediction |
| CN107391376A (en) * | 2017-07-26 | 2017-11-24 | 成都科来软件有限公司 | A kind of regression testing method |
| CN109446097A (en) * | 2018-11-07 | 2019-03-08 | 郑州云海信息技术有限公司 | A kind of regression test case selection method, device, terminal and storage medium |
| CN109918271A (en) * | 2019-03-28 | 2019-06-21 | 上海中通吉网络技术有限公司 | Data quality monitoring method, system and storage medium |
| CN110134588A (en) * | 2019-04-16 | 2019-08-16 | 江苏大学 | A kind of priorities of test cases sort method and test macro based on code and combined covering |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1680741B1 (en) * | 2003-11-04 | 2012-09-05 | Kimberly-Clark Worldwide, Inc. | Testing tool for complex component based software systems |
| US20090307763A1 (en) * | 2008-06-05 | 2009-12-10 | Fiberlink Communications Corporation | Automated Test Management System and Method |
-
2019
- 2019-09-30 CN CN201910938815.7A patent/CN110704322B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102521376A (en) * | 2011-12-20 | 2012-06-27 | 上海电机学院 | Method for simplifying software test case suite |
| US8881095B1 (en) * | 2012-03-30 | 2014-11-04 | Sprint Communications Company L.P. | Software defect prediction |
| CN107391376A (en) * | 2017-07-26 | 2017-11-24 | 成都科来软件有限公司 | A kind of regression testing method |
| CN109446097A (en) * | 2018-11-07 | 2019-03-08 | 郑州云海信息技术有限公司 | A kind of regression test case selection method, device, terminal and storage medium |
| CN109918271A (en) * | 2019-03-28 | 2019-06-21 | 上海中通吉网络技术有限公司 | Data quality monitoring method, system and storage medium |
| CN110134588A (en) * | 2019-04-16 | 2019-08-16 | 江苏大学 | A kind of priorities of test cases sort method and test macro based on code and combined covering |
Non-Patent Citations (5)
| Title |
|---|
| Adaptive Random Testing by Static Partitioning;Korosh Koochekian Sabor;《IEEE Xplore》;20150727;全文 * |
| 基于历史信息的自适应测试用例优先级技术;常龙辉等;《计算机科学》;20150915(第09期);全文 * |
| 基于持续集成的冒烟测试;姜文等;《计算机技术与发展》;20180428(第08期);全文 * |
| 基于程序切片的测试用例集约简方法;吴洁等;《重庆交通大学学报(自然科学版)》;20100415(第02期);全文 * |
| 应用软件项目的迭代开发与测试;姜文等;《计算机技术与发展》;20181220(第04期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110704322A (en) | 2020-01-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105487980B (en) | The method and device that repairing applications are operating abnormally | |
| CN106708719B (en) | Service function testing method and device | |
| CN111680008B (en) | Log processing method and system, readable storage medium and intelligent device | |
| CN103646104A (en) | Hard real-time fault diagnosis method and system | |
| US20050091026A1 (en) | Modelling and simulation method | |
| CN115048254B (en) | Simulation test method, system, equipment and readable medium for data distribution strategy | |
| CN110543427A (en) | Test case storage method and device, electronic equipment and storage medium | |
| WO2022095847A1 (en) | System upgrading method and apparatus, device, and storage medium | |
| CN107621963A (en) | A kind of software deployment method, software deployment system and electronic equipment | |
| CN107368330A (en) | Client patch restorative procedure, device and system | |
| CN111382198A (en) | Data recovery method, device, equipment and storage medium | |
| CN109992476A (en) | A kind of analysis method of log, server and storage medium | |
| CN109254791A (en) | Develop management method, computer readable storage medium and the terminal device of data | |
| CN110704322B (en) | Software testing method and system | |
| CN108664255B (en) | Software upgrading method and device | |
| US11663113B2 (en) | Real time fault localization using combinatorial test design techniques and test case priority selection | |
| CN112000321A (en) | Method and device for realizing undo and/or redo of three-dimensional detection software | |
| CN115454860A (en) | Automatic testing method and device, storage medium and electronic equipment | |
| CN111694724A (en) | Testing method and device of distributed table system, electronic equipment and storage medium | |
| CN112463596B (en) | Test case data processing method, device and equipment and processing equipment | |
| CN112395199B (en) | Distributed software instance testing method based on cloud computing and software development platform | |
| CN107861739A (en) | ReactNative applications method of adjustment, client and system | |
| CN110738384B (en) | Event sequence checking method and system | |
| CN112596750A (en) | Application testing method and device, electronic equipment and computer readable storage medium | |
| CN109992475A (en) | A kind of processing method of log, server and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |