CN115687140B - Test case writing method and system based on automatic test - Google Patents
Test case writing method and system based on automatic test Download PDFInfo
- Publication number
- CN115687140B CN115687140B CN202211405771.XA CN202211405771A CN115687140B CN 115687140 B CN115687140 B CN 115687140B CN 202211405771 A CN202211405771 A CN 202211405771A CN 115687140 B CN115687140 B CN 115687140B
- Authority
- CN
- China
- Prior art keywords
- variable
- tested
- pool
- automation
- writing
- 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
- 238000012360 testing method Methods 0.000 title claims abstract description 53
- 238000000034 method Methods 0.000 title claims abstract description 22
- 230000006870 function Effects 0.000 claims abstract description 11
- 230000008569 process Effects 0.000 abstract description 10
- 230000001419 dependent effect Effects 0.000 abstract description 4
- 235000014510 cooky Nutrition 0.000 description 6
- 238000013522 software testing Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 238000012356 Product development Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 239000002243 precursor Substances 0.000 description 1
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The invention provides a test case writing method and a system based on automatic test, comprising the following steps: writing an automatic step to be tested; reading an input variable from a variable pool based on the automation step to be tested; executing the automation step to be tested by using the input variable; judging whether the automatic step to be tested passes or not; if yes, writing the variable obtained after the execution into the variable pool, and taking the automation step to be tested as an automation step; writing the next automation step to be tested, and executing; if not, re-writing the automatic step to be tested and re-executing; when the automation steps to be tested corresponding to the functions are all executed and passed, storing a plurality of the automation steps which are executed and passed as test cases; the problem that dependent use cases or steps need to be repeatedly executed during debugging due to inter-step variable dependence in the process of writing the use cases is solved, and the efficiency of writing the use cases is remarkably improved.
Description
Technical Field
The invention relates to the technical field of software testing, in particular to a test case writing method and system based on automatic testing.
Background
Software testing is required before software is online so as to ensure stable operation after the software is online. However, as the pace of life increases, the demand for iterative cycles of software becomes faster and faster, leaving the customer in the market for the first time, the time left for product development is becoming more and more intense. Because there is not enough time to test the software, the deficiency of perfecting the software, the BUG often appears after the product is on line, resulting in user loss and even capital loss.
In view of this, the present specification proposes a test case writing method and system based on automated testing, so as to improve the efficiency and quality of software testing.
Disclosure of Invention
The invention aims to provide a test case writing method based on automatic test, which comprises the following steps: writing an automatic step to be tested; reading an input variable from a variable pool based on the automation step to be tested; one or more variables are stored in the variable pool; the one or more variables are obtained by performing a history automation step; executing the automation step to be tested by using the input variable; judging whether the automatic step to be tested passes or not; if yes, writing the variable obtained after the execution into the variable pool, and taking the automation step to be tested as an automation step; writing the next automation step to be tested, and executing; if not, re-writing the automatic step to be tested and re-executing; when all the automation steps to be tested corresponding to the functions pass, storing the multiple automation steps passing through as test cases.
Further, the reading the input variable from the variable pool includes: judging whether the automatic step to be tested uses a variable or not; if yes, judging whether the variable required by the automatic step to be tested exists in the variable pool or not; if so, extracting default values of required variables from the variable pool as the input variables.
Furthermore, the storage structure of the variable pool adopts a tree structure.
Further, the writing the variable obtained after the execution pass into the variable pool includes: judging whether variable output exists or not; if yes, judging whether other automatic steps output variables with the same variable name; if yes, the variable name is used as a father node, and the variable value and the variable source are added in a child node; if not, adding the variable name, the variable value and the variable source into the variable pool.
Further, the father node further comprises a default variable value, the variable name corresponds to the default variable value, and the default variable value is the value of the same-name variable added to the variable pool where the variable name is located for the last time.
The invention aims to provide a test case writing system based on automatic test, which comprises a writing module, an acquisition module, an execution module, a judgment module, a determination module and a storage module; the writing module is used for writing the automatic step to be tested; the compiling module is further used for re-compiling the automatic step to be tested when the automatic step to be tested is not passed; the acquisition module is used for reading an input variable from a variable pool based on the automatic step to be detected; one or more variables are stored in the variable pool; the one or more variables are obtained by performing a history automation step; the execution module is used for executing the automation step to be tested by using the input variable; the execution module is also used for executing again according to the rewritten automatic step to be tested when the automatic step to be tested is not executed; the judging module is used for judging whether the automatic step to be tested passes or not; the determining module is used for writing variables obtained after the execution of the automatic step to be tested into the variable pool when the automatic step to be tested is executed and passing, and taking the automatic step to be tested as an automatic step; writing the next automation step to be tested, and executing; and the storage module is used for storing a plurality of automation steps which are executed as test cases when all the automation steps to be tested corresponding to the functions are executed.
Further, the obtaining module is further configured to: judging whether the automatic step to be tested uses a variable or not; if yes, judging whether the variable required by the automatic step to be tested exists in the variable pool or not; if so, extracting default values of required variables from the variable pool as the input variables.
Furthermore, the storage structure of the variable pool adopts a tree structure.
Further, the determining module is further used for judging whether a variable is output or not; if yes, judging whether other automatic steps output variables with the same variable name; if yes, the variable name is used as a father node, and the variable value and the variable source are added in a child node; if not, adding the variable name, the variable value and the variable source into the variable pool.
Further, the father node further comprises a default variable value, the variable name corresponds to the default variable value, and the default variable value is the value of the same-name variable added to the variable pool where the variable name is located for the last time.
The technical scheme of the embodiment of the invention has at least the following advantages and beneficial effects:
some embodiments of the present disclosure enable the execution of an automated debug phase to be independent, eliminating the need for prior steps or dependent test cases to be performed for each execution of the dependent variable problem. After the steps are newly added or modified, the steps can be directly executed, and the variables in the variable pool are read for use, so that the purpose of debugging whether the steps are correct or not can be achieved. The problem that dependent use cases or steps need to be repeatedly executed during debugging due to inter-step variable dependence in the process of writing the use cases is solved, and the efficiency of writing the use cases is remarkably improved.
Drawings
FIG. 1 is an exemplary flow chart of a test case writing method based on automated testing provided by some embodiments of the present invention;
FIG. 2 is an exemplary flow chart for reading input variables from a variable pool provided by some embodiments of the present invention;
FIG. 3 is an exemplary flow chart for writing variables obtained after execution passes to a variable pool provided by some embodiments of the present invention;
FIG. 4 is an exemplary flow chart of use case authoring using the automated test-based test case authoring method provided by some embodiments of the present invention;
FIG. 5 is an exemplary block diagram of a test case writing system based on automated testing according to some embodiments of the present invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments of the present invention. The components of the embodiments of the present invention generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations.
FIG. 1 is an exemplary flow chart of a test case writing method based on automated testing provided by some embodiments of the present invention. In some embodiments, the process 100 may be performed by the system 500. As shown in fig. 1, the process 100 may include the steps of:
step 110, writing an automation step to be tested. In some embodiments, step 110 may be performed by the writing module 510.
An automated step may refer to a step for automated testing of software. The written automation step needs to be tested before it is used for the system automation test, so that an automation step that has not been tested can be regarded as an automation step to be tested.
Step 120, based on the automation step to be tested, reads the input variables from the variable pool. In some embodiments, step 120 may be performed by acquisition module 520.
A variable pool may refer to a database that stores variables. One or more variables are stored in the variable pool, wherein the one or more variables are obtained by performing a history automation step. The history automation step may refer to an automation step that has been performed historically. The input variables may refer to variables required to perform an automation step to be measured, by which the automation step to be measured is performed, and when the execution passes, the variables to perform the automation step may be obtained. The automated test steps and variables may be input into a variable pool, wherein when the next automated step to be tested of the automated step is performed, the automated step may be considered a historical automated step and the corresponding variable may be considered an input variable. In some embodiments, the variable name of the variable required to perform the automation step under test may be obtained, and the value of the variable is obtained from the variable pool by the variable name. For more on reading input variables from the variable pool, see FIG. 2 and its associated description.
Step 130, performing the automation step to be tested using the input variables. In some embodiments, step 130 may be performed by execution module 530. The automation step to be tested may be performed in various possible ways.
Step 140, determining whether the automation step to be tested is executed. In some embodiments, step 140 may be performed by decision module 540.
When the automatic step to be tested is executed, the expected function is realized, and the execution passing of the automatic step to be tested is determined; if the expected function is not realized, determining that the execution of the automation step to be tested is not passed. For example, the automatic step to be tested is a step of logging in the APP, the variables comprise a user name and a login password, and when the step of logging in the APP is executed by using the preset user name and the login password, the APP is successfully logged in, and the step of logging in the APP is confirmed to be executed; otherwise, not pass.
Step 150, if yes, writing the variable obtained after execution into a variable pool, and taking the automation step to be tested as an automation step; and writing the next automation step to be tested, and executing. In some embodiments, step 150 may be performed by determination module 550.
For example, after the step of executing the login APP passes, a cookie including a user name, login information may be generated, the cookie may be written as a variable into the variable pool, and the automation step to be tested to be executed as an automation step, indicating that the automation step is executed. In some embodiments, variables and their corresponding automation steps may be written to a variable pool for use in subsequent software testing. For more on the writing of variables into the variable pool that results from the execution pass, see FIG. 3 and its associated description.
Step 160, if not, re-writing the automation step to be tested and re-executing. In some embodiments, step 160 may be performed by the writing module 510.
And step 170, when all the automation steps to be tested corresponding to the functions pass, storing the multiple automation steps passing through as test cases. In some embodiments, step 170 may be performed by storage module 560.
A test case may refer to a collection of steps for testing software. For example, the functions of the on-shelf commodity may include a step of registering APP, a step of creating a commodity, a step of on-shelf commodity, and the like, and when the step of registering APP, the step of creating a commodity, and the step of on-shelf commodity are all executed, the step of registering APP, the step of creating a commodity, the step of on-shelf commodity, and the execution order thereof are saved as test cases.
FIG. 2 is an exemplary flow chart for reading input variables from a variable pool provided by some embodiments of the invention. In some embodiments, the process 200 may be performed by the acquisition module 520. As shown in fig. 2, the process 200 may include the steps of:
the steps are performed separately. That is, the automation step to be measured is separately performed without performing the preamble automation step.
And judging whether the automatic step to be tested uses the variable or not.
If not, directly executing the automatic step to be tested.
If yes, judging whether the variable required by the automatic step to be tested exists in the variable pool or not.
When the automated step under test uses variables, the variables used may be considered as the desired variables. In some embodiments, the variable names of the required variables may be obtained, and matching is performed based on the variable names and the variable names existing in the variable pool, if there is a variable with a consistent variable name, it is determined whether the source of the variable in the variable pool is consistent with the precursor automation step of the required variable, if yes, it is determined that the required variable exists in the variable pool. If not, the required variable is not stored in the variable pool. When the desired variable is not in the variable pool, the preamble step is performed to obtain the desired variable. For example, executing the automation step 1 to obtain a variable 1, executing the automation step 2 to obtain a variable 2, executing the automation step 3 to be tested now, wherein the execution of the automation step 3 to be tested requires the variable 2, so that whether the variable 2 exists can be searched in the variable pool, and if yes, the automation step 3 to be tested is directly executed based on the value of the variable 2; when the variable pool does not exist the variable 2, re-executing the automation step 2 to obtain the variable 2, when the automation step 2 is executed, searching whether the variable 1 exists in the variable pool, when the variable 1 exists, directly executing the automation step 2 by using the variable 1 in the variable pool, when the variable 1 does not exist, re-executing the automation step 1, and the like, until the variable 2 is obtained.
If so, extracting default values of the required variables from the variable pool as input variables.
In the software test process, multiple variable values may exist for the same variable name, and for the case of multiple variable values, a certain variable value may be designated as a default value of the variable.
FIG. 3 is an exemplary flow chart for writing variables obtained after execution passes to a variable pool provided by some embodiments of the present invention. In some embodiments, the process 300 may be performed by the determination module 550. In some embodiments, the storage structure of the variable pool may take the form of a tree structure. As shown in fig. 3, the process 300 may include the steps of:
use cases/steps are performed. Wherein, the use cases are test use cases, and the steps are automatic steps.
And judging whether a variable is output or not.
If yes, judging whether other automatic steps output the variables with the same variable names. Other steps may refer to other automated steps of the test case as well as to automated steps of other test cases.
If yes, the variable name is taken as a father node, and the variable value and the variable source are added in the child node. For example, for variable 1, the parent node is variable name 1, and the child nodes are variable value 1 [ variable source ], variable value 2 [ variable source ].
In some embodiments, the parent node further includes a default variable value, the variable name corresponding to the default variable value, the default variable value being the value of the same name variable that was last added to the variable pool in which the variable name was located. For example, for the variable good_id, the variable value 1 is included: GOOD01 and variable value 2: GOOD02, variable value 2 is the variable added last to the variable pool where the variable name is located, so GOOD02 can be taken as the value of variable goods_id. For example, for the variable goods_id, its parent node may be a goods_id: GOOD02 [ commodity management-commodity use case-commodity put-on-shelf ], its child nodes may include GOOD01 [ commodity management-commodity put-on-shelf use case-create commodity ] and GOOD02 [ commodity management-commodity put-on-shelf use case-commodity put-on-shelf ].
If not, adding the variable name, the variable value and the variable source into the variable pool. For example, for variable 2, variable name 2 [ variable value and variable source ]. Illustratively, for a variable cookie, its form in the variable pool is a cookie: EDNG10DFN3 [ Commodity management-Commodity put on shelf use case-user Login ].
In some embodiments, the variable pool also provides the function of editing variables to prune the variables in the variable pool to adapt to the scene under different requirements.
FIG. 4 is an exemplary flow chart for use in use case authoring using the automated test-based test case authoring method provided by some embodiments of the present invention. As shown in fig. 4, a process 400, which is a step of writing an on-shelf commodity test case, may include:
the test case is started to be created.
Writing a user login step, executing the user login step by using a user name and a password in a variable pool, and writing and creating a commodity when the user passes the user login step; and when the execution does not pass, the step of re-writing the user login.
Writing and creating commodities, and executing the step of creating commodities by using cookies in the variable pool; wherein the cookie includes a user and user information. A step of writing up the shelf commodity when the pass is executed; and when the execution does not pass, the step of creating the commodity is rewritten.
A step of compiling the on-shelf commodity, and a step of executing the commodity by using the goods_id in the variable pool; wherein, the good_id comprises the commodity and the information of the commodity. When the execution passes, the test case is saved, and the creation of the test case is completed; and when the program does not pass, the step of re-writing the shelf commodity.
FIG. 5 is an exemplary block diagram of a test case writing system based on automated testing according to some embodiments of the present invention. As shown in fig. 5, the system 500 includes a writing module 510, an acquisition module 520, an execution module 530, a judgment module 540, a determination module 550, and a storage module 560.
The writing module 510 is used for writing the automation step to be tested. The writing module 510 is further configured to re-write the automation step to be tested when the automation step to be tested is not executed. For more on the authoring module 510, see FIG. 1 and its associated description.
The obtaining module 520 is configured to read an input variable from the variable pool based on the automation step to be tested; one or more variables are stored in the variable pool; one or more variables are obtained by performing a history automation step. The acquisition module 520 is further configured to: judging whether the automatic step to be tested uses a variable or not; if yes, judging whether the variable required by the automatic step to be tested exists in a variable pool or not; if so, extracting default values of the required variables from the variable pool as input variables. For more details on the acquisition module 520, see FIG. 1 and its associated description.
The execution module 530 is configured to execute an automation step to be tested using the input variable; the execution module is also used for re-executing the automatic step to be tested according to the re-written automatic step to be tested when the automatic step to be tested is not executed. For more details on the execution module 530, see FIG. 1 and its associated description.
The judging module 540 is configured to judge whether the automation step to be tested is executed. For more details on the determination module 540, see FIG. 1 and its associated description.
The determining module 550 is configured to write, when the automation step to be tested passes, a variable obtained after the passing of the execution into the variable pool, and take the automation step to be tested as an automation step; and writing the next automation step to be tested, and executing. The determining module 550 is further configured to determine whether there is a variable output; if yes, judging whether other automatic steps output variables with the same variable name; if yes, the variable name is taken as a father node, and the variable value and the variable source are added in the child node; if not, adding the variable name, the variable value and the variable source into the variable pool. For more details on the determination module 550, see FIG. 1 and its associated description.
The storage module 560 is configured to store, as test cases, a plurality of automation steps that are executed when all the automation steps to be tested corresponding to the functions are executed. For more details on the memory module 560, see FIG. 1 and its associated description.
The above is only a preferred embodiment of the present invention, and is not intended to limit the present invention, but various modifications and variations can be made to the present invention by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (1)
1. The test case writing method based on the automatic test is characterized by comprising the following steps of:
writing an automatic step to be tested;
reading an input variable from a variable pool based on the automation step to be tested; one or more variables are stored in the variable pool; the one or more variables are obtained by performing a history automation step;
executing the automation step to be tested by using the input variable;
judging whether the automatic step to be tested passes or not;
if yes, writing the variable obtained after the execution into the variable pool, and taking the automation step to be tested as an automation step; writing the next automation step to be tested, and executing;
if not, re-writing the automatic step to be tested and re-executing;
when the automation steps to be tested corresponding to the functions are all executed and passed, storing a plurality of the automation steps which are executed and passed as test cases;
the reading of the input variables from the variable pool comprises:
judging whether the automatic step to be tested uses a variable or not;
if not, directly executing the automatic step to be tested;
if yes, judging whether the variable required by the automatic step to be tested exists in the variable pool or not;
when the automatic step to be tested uses the variable, the variable used is considered as the required variable; acquiring the variable names of the required variables, matching the variable names with the variable names existing in the variable pool, judging whether the source of the variable in the variable pool is consistent with the preamble automatic step of the required variable if the variable names are consistent with the variable names, and if the source of the variable in the variable pool is consistent with the preamble automatic step of the required variable, determining that the required variable exists in the variable pool; if not, the required variable does not exist in the variable pool; when the required variable does not exist in the variable pool, executing the preamble step to obtain the required variable;
if the variable exists, extracting a default value of a required variable from the variable pool as the input variable;
the storage structure of the variable pool adopts a tree structure;
the writing the variable obtained after the execution is passed into the variable pool comprises the following steps:
judging whether variable output exists or not;
if yes, judging whether other automatic steps output variables with the same variable name;
if yes, the variable name is used as a father node, and the variable value and the variable source are added in a child node;
if not, adding the variable name, the variable value and the variable source into the variable pool;
the father node also comprises a default variable value, the variable name corresponds to the default variable value, and the default variable value is the value of the homonymous variable added into the variable pool where the variable name is located for the last time;
the method is executed by a test case writing system based on automatic test, and the system comprises a writing module, an acquisition module, an execution module, a judgment module, a determination module and a storage module;
the writing module is used for writing the automatic step to be tested; the compiling module is further used for re-compiling the automatic step to be tested when the automatic step to be tested is not passed;
the acquisition module is used for reading an input variable from a variable pool based on the automatic step to be detected; one or more variables are stored in the variable pool; the one or more variables are obtained by performing a history automation step;
the execution module is used for executing the automation step to be tested by using the input variable; the execution module is also used for executing again according to the rewritten automatic step to be tested when the automatic step to be tested is not executed;
the judging module is used for judging whether the automatic step to be tested passes or not;
the determining module is used for writing variables obtained after the execution of the automatic step to be tested into the variable pool when the automatic step to be tested is executed and passing, and taking the automatic step to be tested as an automatic step; writing the next automation step to be tested, and executing;
the storage module is used for storing a plurality of automation steps which are executed as test cases when all the automation steps to be tested corresponding to the functions are executed;
the acquisition module is further configured to:
judging whether the automatic step to be tested uses a variable or not;
if yes, judging whether the variable required by the automatic step to be tested exists in the variable pool or not;
if the variable exists, extracting a default value of a required variable from the variable pool as the input variable;
the storage structure of the variable pool adopts a tree structure;
the determining module is also used for judging whether variable output exists or not;
if yes, judging whether other automatic steps output variables with the same variable name;
if yes, the variable name is used as a father node, and the variable value and the variable source are added in a child node;
if not, adding the variable name, the variable value and the variable source into the variable pool;
the father node also comprises a default variable value, the variable name corresponds to the default variable value, and the default variable value is the value of the same-name variable which is added into the variable pool where the variable name is located for the last time.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211405771.XA CN115687140B (en) | 2022-11-10 | 2022-11-10 | Test case writing method and system based on automatic test |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211405771.XA CN115687140B (en) | 2022-11-10 | 2022-11-10 | Test case writing method and system based on automatic test |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115687140A CN115687140A (en) | 2023-02-03 |
| CN115687140B true CN115687140B (en) | 2024-01-30 |
Family
ID=85052337
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211405771.XA Active CN115687140B (en) | 2022-11-10 | 2022-11-10 | Test case writing method and system based on automatic test |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115687140B (en) |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106528395A (en) * | 2015-09-09 | 2017-03-22 | 阿里巴巴集团控股有限公司 | Test case generation method and apparatus |
| CN107894952A (en) * | 2017-11-08 | 2018-04-10 | 中国平安人寿保险股份有限公司 | Generation method, device, equipment and the readable storage medium storing program for executing of interface testing use-case |
| CN108287788A (en) * | 2017-12-26 | 2018-07-17 | 广东睿江云计算股份有限公司 | A kind of use-case step matching method based on test case, system |
| CN108563539A (en) * | 2018-03-21 | 2018-09-21 | 广州视源电子科技股份有限公司 | Interface testing method, server, readable storage medium and system |
| CN109697167A (en) * | 2018-12-27 | 2019-04-30 | 江苏满运软件科技有限公司 | Management method, system, electronic equipment and the storage medium of test variable |
| CN110134612A (en) * | 2019-05-17 | 2019-08-16 | 深圳前海微众银行股份有限公司 | UI test data generating method, device, equipment and readable storage medium storing program for executing |
| CN110287121A (en) * | 2019-06-28 | 2019-09-27 | 深圳前海微众银行股份有限公司 | A kind of test method and device automating use-case |
| CN110968500A (en) * | 2018-09-30 | 2020-04-07 | 北京国双科技有限公司 | Test case execution method and device |
| CN112328226A (en) * | 2020-09-17 | 2021-02-05 | 北京中数科技术有限公司 | Embedded system automatic test code generation method and device |
| CN112579455A (en) * | 2020-12-23 | 2021-03-30 | 安徽航天信息有限公司 | Interface automatic testing method and device, electronic equipment and storage medium |
| US11436130B1 (en) * | 2020-07-28 | 2022-09-06 | Amdocs Development Limited | System, method, and computer program for automating manually written test cases |
-
2022
- 2022-11-10 CN CN202211405771.XA patent/CN115687140B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106528395A (en) * | 2015-09-09 | 2017-03-22 | 阿里巴巴集团控股有限公司 | Test case generation method and apparatus |
| CN107894952A (en) * | 2017-11-08 | 2018-04-10 | 中国平安人寿保险股份有限公司 | Generation method, device, equipment and the readable storage medium storing program for executing of interface testing use-case |
| CN108287788A (en) * | 2017-12-26 | 2018-07-17 | 广东睿江云计算股份有限公司 | A kind of use-case step matching method based on test case, system |
| CN108563539A (en) * | 2018-03-21 | 2018-09-21 | 广州视源电子科技股份有限公司 | Interface testing method, server, readable storage medium and system |
| CN110968500A (en) * | 2018-09-30 | 2020-04-07 | 北京国双科技有限公司 | Test case execution method and device |
| CN109697167A (en) * | 2018-12-27 | 2019-04-30 | 江苏满运软件科技有限公司 | Management method, system, electronic equipment and the storage medium of test variable |
| CN110134612A (en) * | 2019-05-17 | 2019-08-16 | 深圳前海微众银行股份有限公司 | UI test data generating method, device, equipment and readable storage medium storing program for executing |
| CN110287121A (en) * | 2019-06-28 | 2019-09-27 | 深圳前海微众银行股份有限公司 | A kind of test method and device automating use-case |
| US11436130B1 (en) * | 2020-07-28 | 2022-09-06 | Amdocs Development Limited | System, method, and computer program for automating manually written test cases |
| CN112328226A (en) * | 2020-09-17 | 2021-02-05 | 北京中数科技术有限公司 | Embedded system automatic test code generation method and device |
| CN112579455A (en) * | 2020-12-23 | 2021-03-30 | 安徽航天信息有限公司 | Interface automatic testing method and device, electronic equipment and storage medium |
Non-Patent Citations (3)
| Title |
|---|
| Testing pairs of continuous random variables for independence: A simple heuristic;Mahfuza Khatun et al.;Journal of Computational Mathematics and Data Science;第1卷;全文 * |
| 一种软件自动测试工具的研究与实现;王帅兵;《中国优秀硕士学位论文全文数据库信息科技辑》(第03期);全文 * |
| 基于上下文的错误定位方法研究;张旭;《中国优秀硕士学位论文全文数据库信息科技辑》(第01期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115687140A (en) | 2023-02-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112256581B (en) | Log playback test method and device for high-simulation securities trade trading system | |
| CN110188036A (en) | A kind of method for testing software and device | |
| CN111008154B (en) | Android application automatic test method and system based on reinforcement learning | |
| CN114139923A (en) | Task relevance analysis method and device and computer readable storage medium | |
| CN105279092A (en) | Software testing method and apparatus | |
| CN111651358B (en) | Method for generating test case, software test method, device and server | |
| CN112148614A (en) | Regression testing method and device | |
| CN115687140B (en) | Test case writing method and system based on automatic test | |
| CN112486811A (en) | Interface test method, device, equipment and medium | |
| CN112035308A (en) | Method and device for generating system interface test table | |
| CN115629996B (en) | Automatic testing method for embedded software | |
| CN112540970B (en) | Metadata blood margin analysis method and system based on version management | |
| CN116185706A (en) | Data backup method and device, computing and storage medium and electronic equipment | |
| CN111177014B (en) | Software automatic test method, system and storage medium | |
| CN115563008A (en) | Code coverage rate detection system, method, device and storage medium | |
| CN112905438A (en) | Automatic testing method and device | |
| CN111309598A (en) | Test case execution environment recovery method, system, terminal and storage medium | |
| CN110554947A (en) | method and system for testing stability of hard disk based on capacity adjustment | |
| CN117792821B (en) | Vehicle information recording and playback method and device, computer equipment and storage medium | |
| CN118689762A (en) | Code quality test automatic configuration method and related equipment | |
| CN118550836A (en) | Black box testing method and system without expected result injection | |
| JPH0363837A (en) | Software program inspection system | |
| CN115617684A (en) | Function test method of equipment | |
| CN117234927A (en) | Automatic testing method, system, equipment and medium for information communication equipment | |
| CN116244197A (en) | Automatic expected verification system based on full-system full-data-volume comparison |
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 |