CN112559356A - Automatic software testing method and system - Google Patents
Automatic software testing method and system Download PDFInfo
- Publication number
- CN112559356A CN112559356A CN202011510560.3A CN202011510560A CN112559356A CN 112559356 A CN112559356 A CN 112559356A CN 202011510560 A CN202011510560 A CN 202011510560A CN 112559356 A CN112559356 A CN 112559356A
- Authority
- CN
- China
- Prior art keywords
- interface
- case
- unit
- setting
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 60
- 238000013522 software testing Methods 0.000 title claims description 14
- 238000012360 testing method Methods 0.000 claims abstract description 31
- 230000004044 response Effects 0.000 claims description 31
- 238000012795 verification Methods 0.000 claims description 18
- 238000007781 pre-processing Methods 0.000 claims description 17
- 238000012805 post-processing Methods 0.000 claims description 15
- 238000000605 extraction Methods 0.000 claims description 11
- 238000012545 processing Methods 0.000 claims description 6
- 125000004122 cyclic group Chemical group 0.000 claims description 3
- 238000010998 test method Methods 0.000 abstract 2
- 230000006870 function Effects 0.000 description 5
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000002349 favourable effect Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
-
- 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
An automatic test method and system for software, the test method includes the following steps: setting one or more groups of use case groups, wherein the use case groups comprise use case group names; one or more use cases are set under each group of use cases, and each use case comprises a use case name; each use case is provided with one or more corresponding interfaces; generating an interface list by using the corresponding interface; and executing the set use case or use case group. The method for executing the set use case or use case group comprises the following steps: the single-case execution method comprises the following steps: selecting a required test case, inquiring an interface list under the selected case, and sequentially executing interfaces under the interface list; or, the case group execution method comprises the following steps: selecting a case group to be tested, inquiring a case list under the case group, and executing the case under the case list according to a single case execution method. The invention realizes an automatic test platform, and the software application test can be realized by setting cases and case group data on the test platform; the automatic case compiling efficiency is high, and the threshold is low.
Description
Technical Field
The invention relates to a computer software technology, in particular to a software testing technology, and specifically relates to an automatic software testing technology.
Background
The technical field of software testing has a certain operation threshold, software testing technicians need to master a certain programming technology to independently realize a testing process, and when the testing functions are multiple and are updated frequently, the technicians need to frequently modify testing codes to realize corresponding operation. For inexperienced technicians, the threshold for entry is high, which is not favorable for the application.
Disclosure of Invention
Aiming at the defects in the prior art, the invention provides a system and an execution method capable of rapidly mastering a test flow.
In order to solve the technical problem, the invention is solved by the following technical scheme:
an automatic software testing method comprises the following steps:
setting one or more groups of use case groups, wherein the use case groups comprise use case group names;
one or more use cases are set under each group of use cases, and each use case comprises a use case name;
each use case is provided with one or more corresponding interfaces; the interface data comprises an interface address and parameters;
generating an interface list by using the corresponding interface;
and executing the set use case or use case group.
Optionally, the method for executing the set use case or use case group includes:
the single-case execution method comprises the following steps: selecting a required test case, inquiring an interface list under the selected case, and sequentially executing interfaces under the interface list;
or, the case group execution method comprises the following steps: selecting a case group to be tested, inquiring a case list under the case group, and executing the case under the case list according to a single case execution method.
Optionally, the single-case execution method includes:
according to the selected use case, inquiring an interface list under the use case of mysql, and sequentially operating the interfaces in the interface list;
the operation method of the interface comprises the following steps:
before calling an interface, inquiring a preprocessing parameter of the interface, and clearing data and waiting time before executing the interface;
inquiring a request address and request content, calling the interface, acquiring a response value, extracting the response value and storing a redis cache;
inquiring parameters of the verification unit and executing verification;
and inquiring parameters of the post-processing unit, and clearing data and waiting time after the interface operates.
Optionally, selecting a case group to be tested, querying a case list under the case group,
executing the use cases in the use case list according to the single use case execution method in sequence;
or executing the use cases in the use case list in a multi-thread mode.
Optionally, the multi-thread execution method of the use case:
setting the concurrency number n of the use cases, creating a java thread pool with n threads according to the concurrency number n, submitting the use cases in the use case list to the thread pool for execution, and executing each use case according to a single use case execution method.
Optionally, the request content parameter includes a body parameter, a response value extraction parameter, a loop processing parameter, a concurrency setting parameter, and an independent user parameter;
the request address body parameter comprises a key-value format and a json format;
acquiring the response value includes: acquiring response data of the interface, wherein the response data comprises json path acquisition and regular matching acquisition, and the acquired response value is stored in redis and used for verifying or transmitting parameters of the next interface;
and (3) circulating treatment: executing polling aiming at the asynchronous interface, confirming that the interface does not respond to a certain specific value, and then executing the next process; setting an actual value, an expected value, the maximum circulation times and the waiting time of each circulation by a user;
setting concurrent parameters: and setting the concurrency number for the interfaces needing concurrent execution.
The invention also provides a software automatic test system, which comprises one or more groups of case groups and an operation unit;
the set of use cases comprises one or more use cases;
the use case comprises an interface unit;
the interface unit is used for setting an interface address;
the operation unit is used for inquiring the case interface unit and executing all interface unit data under the case group.
Optionally, the use case includes:
the interface name unit is used for setting an interface id and butting a corresponding test interface;
the request address unit is used for setting an interface address, acquiring the interface address when executing the interface address and butting a corresponding test interface;
the request content unit comprises an interface request body parameter, a response value extraction parameter, a cyclic management request parameter and a concurrency number;
the pre-processing unit is used for setting pre-processing parameters, executing the pre-processing parameters before calling the interface and clearing data and waiting time before executing the interface;
the post-processing unit is used for setting post-processing parameters, is used for the last step after the interface is executed, and clears data and waiting time after the interface is operated;
and the checking unit is used for setting checking parameters and judging the interface execution condition.
Optionally, the requesting content unit includes:
a request body unit for setting a request body parameter;
a response value extraction unit for setting a response value extraction parameter;
a loop processing unit for setting an actual value and an expected value, the maximum number of loops and each loop waiting time;
the concurrent setting unit is used for setting the concurrent number when the interface needs concurrent testing;
and the independent user unit is used for setting other available users of the application case interface.
Alternatively to this, the first and second parts may,
the verification unit includes a verification unit for verifying whether the verification unit includes,
a response value checking unit: the system is used for setting verification parameters including actual values, conditions, expected values and descriptions;
mysql check unit: the method comprises the steps of setting mysql check parameters including sql, fields, expected values and descriptions;
and a concurrent checking unit: the method is used for setting response texts, and comprises fields and quantity;
the pre-processing unit and the post-processing unit both comprise,
msql addition unit: the system is used for setting the sql statement and can perform checking, modifying and deleting of the sql;
redis addition unit: keys and values for setting the redis can realize the clearing and updating of the redis cache;
a fixed latency setting unit: wait before executing the interface.
The invention has the beneficial effects that:
1. the automatic software testing method and the automatic software testing method system disclosed by the invention realize an automatic testing platform, and technicians can realize software application testing by setting cases and case group data on the testing platform; the automatic case compiling efficiency is high, the threshold is low, and codes do not need to be compiled. The use case data and the operation data are all stored in the database, and the maintenance is convenient; the method is convenient to integrate to an operation and maintenance release platform and realizes CI/CD conveniently.
2. The interface automation test disclosed by the invention is mainly aimed at back-end services, and when some systems are changed, a user only needs to run a corresponding case group and does not need to run all interface automation cases. The use cases contained in the use case group are usually a certain service or several services in the same business scene, and in some fields such as advertisement, the service content is frequently modified, and then the technical scheme simplifies the traditional testing process.
Specifically, each use case group is operated independently, each use case group comprises a plurality of interface automation use cases of a certain scene, and the use cases below the use case group can be sequentially operated when the use case group is operated. The operation logic of the case group is to inquire all the cases in the case group in the database, the cases can be executed serially or in multiple threads (the speed is higher) during execution, and the function of retrying the failed cases can be realized after the execution is finished.
Drawings
(none)
Detailed Description
The present invention will be described in further detail with reference to examples, which are illustrative of the present invention and are not to be construed as being limited thereto.
The automatic software testing system comprises one or more groups of use cases and a running unit, wherein the use cases comprise one or more use cases; the use case comprises an interface unit; the interface unit is used for setting an interface address and parameters;
the operation unit is used for inquiring the case interface unit and executing all interface unit data under the case group;
wherein each use case is provided with a use case id, and each use case group is provided with a use case group id.
Wherein the use case comprises:
the interface name unit is used for setting an interface id and butting a corresponding test interface;
the request address unit is used for setting an interface address, acquiring the interface address when executing the interface address and butting a corresponding test interface;
the request content unit comprises an interface request body parameter, a response value extraction parameter, a cyclic management request parameter and a concurrency number;
the pre-processing unit is used for setting pre-processing parameters, executing the pre-processing parameters before calling the interface and clearing data and waiting time before executing the interface;
the post-processing unit is used for setting post-processing parameters, is used for the last step after the interface is executed, and clears data and waiting time after the interface is operated;
and the checking unit is used for setting checking parameters and judging the interface execution condition.
The above configurations all correspond to the same interface id, a plurality of interface ids correspond to one use case id, and a plurality of use case ids correspond to the same use case group id. During execution, according to the case group id, inquiring the corresponding case id, and then according to the case id, inquiring the interface id, and executing the interface, wherein the interface execution content is as follows: pre-processing, requesting an interface, checking and post-processing.
Wherein the request content unit includes:
the request body unit is used for setting request body parameters including a key-value format and a json format, and can be parameterized, wherein a specific value is obtained from a return value of a previous interface or is directly assigned in case setting, and a variable is automatically assigned when a case runs;
a response value extraction unit for setting a response value extraction parameter;
a loop processing unit for setting an actual value and an expected value, the maximum number of loops and each loop waiting time;
the concurrent setting unit is used for setting the concurrent number when the interface needs concurrent testing;
and the independent user unit is used for setting other available users of the application case interface.
Wherein the verification unit comprises a verification unit and a verification unit,
a response value checking unit: the system is used for setting verification parameters including actual values, conditions, expected values and descriptions;
mysql check unit: the method comprises the steps of setting mysql check parameters including sql, fields, expected values and descriptions;
and a concurrent checking unit: the method is used for setting response texts, and comprises fields and quantity;
the preprocessing unit includes:
msql addition unit: the system is used for filling out the sql statement and can perform the addition, the modification and the deletion of the sql;
redis addition unit: keys and values for filling the redis can realize the clearing and updating of the redis cache;
a fixed latency setting unit: wait before executing the interface.
The post-processing unit includes:
msql addition unit: the system is used for filling out the sql statement and can perform the addition, the modification and the deletion of the sql;
redis addition unit: keys and values for filling the redis can realize the clearing and updating of the redis cache;
a fixed latency setting unit: wait before executing the interface.
Example 2:
an automatic software testing method comprises the following steps:
setting one or more groups of use case groups, wherein the use case groups comprise use case group names;
one or more use cases are set under each group of use cases, and each use case comprises a use case name;
each use case is provided with one or more corresponding interfaces;
generating an interface list by using the corresponding interface;
and executing the set use case or use case group.
The method for executing the set use case or use case group comprises the following steps:
the single-case execution method comprises the following steps: selecting a required test case, inquiring an interface list under the selected case, and sequentially executing interfaces under the interface list;
or, the case group execution method comprises the following steps: selecting a case group to be tested, inquiring a case list under the case group, and executing the case under the case list according to a single case execution method.
The single-case execution method comprises the following steps:
according to the selected use case, inquiring an interface list under the use case of mysql, and sequentially operating the interfaces in the interface list;
in detail, the single-use-case execution method described herein is executed concurrently or independently and sequentially for each use case, and may select one use case or multiple use cases to execute.
The operation method of the interface comprises the following steps:
before calling an interface, inquiring a preprocessing parameter of the interface, and clearing data and waiting time before executing the interface;
inquiring a request address and request content, calling the interface, acquiring a response value, extracting the response value and storing a redis cache;
inquiring parameters of the verification unit and executing verification;
and inquiring parameters of the post-processing unit, and clearing data and waiting time after the interface operates.
After the operation is finished, if a failed case exists and the user sets the failure retry, the failed case is operated again, and finally a test report is generated.
The case group execution method comprises the following steps: selecting a case group to be tested, inquiring a case list under the case group,
executing the use cases in the use case list according to the single use case execution method in sequence;
or executing the use cases in the use case list in a multi-thread mode.
The multithreading execution method of the use case comprises the following steps: setting the concurrency number n of the use cases, creating a java thread pool with n threads according to the concurrency number n, submitting the use cases in the use case list to the thread pool for execution, and executing each use case according to a single use case execution method.
Specifically, a use case group needing to be executed is selected, the use case group is clicked to operate, a use case list under the use case group in a database is queried according to a use case group id, a use case under the use case group is obtained and is placed into an execution list, a thread pool with n thread numbers is created according to the set concurrency number n, then the use case of the use case list is submitted to the thread pool to be executed, and each thread can execute one use case.
The logic executed by each thread of the thread pool is: according to the id of the use case, all interfaces under the use case are queried, the interfaces are put into list1, the list1 is sorted, and then each interface executing list1 is circularly traversed.
The execution logic of each interface is: inquiring according to the interface id, inquiring the pre-processing, operating the corresponding operation, inquiring the interface address and the parameters, calling the interface, inquiring the checking configuration according to the interface id, executing the checking, inquiring the post-processing configuration according to the interface id, and executing the post-processing.
Example 3:
the embodiment discloses an automatic test platform based on embodiments 1 and 2, which is used for testing functions of software commodities, wherein a software product is divided into three classes, the software product is a first class group and comprises a plurality of second class groups, the second class groups are the use case groups, each second class group comprises a plurality of third class groups, and specific use case names and configurations are set in the third class groups; each use case group comprises a certain service or several services of the same business scenario.
The method specifically comprises the following steps: an operation configuration unit: the unit for configuring the embodiments 1 and 2 includes setting a use case name, a use case group, a use case and use case group sequence, runtime, executor, progress, editing module, and the like.
And the editing unit is used for editing the functions described in the embodiment 1 and the embodiment 2, and comprises functions of deleting, modifying, controlling running/stopping, setting concurrency number, the number of failed retries, timing trigger events and the like.
A test report unit: and the record is used for recording the operation process and the result after the operation is finished, and comprises the name of the case group, the executor, the time, the total number of the cases, the failure number and the success rate. The test report unit is also provided with the operation details of the use case, and the corresponding use case can be clicked and skipped, so that the failed use case can be conveniently debugged.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described device embodiments are merely illustrative, and for example, the division of the modules or units is only one logical functional division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another device, or some features may be omitted, or not executed.
The units may or may not be physically separate, and components displayed as units may be one physical unit or a plurality of physical units, that is, may be located in one place, or may be distributed in a plurality of different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a readable storage medium. Based on such understanding, the technical solution of the embodiments of the present invention may be essentially or partially contributed to by the prior art, or all or part of the technical solution may be embodied in the form of a software product, where the software product is stored in a storage medium and includes several instructions to enable a device (which may be a single chip, a chip, or the like) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The above description is only an embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions within the technical scope of the present invention are intended to be covered by the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the appended claims.
Claims (10)
1. An automatic software testing method is characterized by comprising the following steps:
setting one or more groups of use case groups, wherein the use case groups comprise use case group names;
one or more use cases are set under each group of use cases, and each use case comprises a use case name;
each use case is provided with one or more corresponding interfaces; the interface data comprises an interface address and parameters;
generating an interface list by using the corresponding interface;
and executing the set use case or use case group.
2. The method according to claim 1, wherein the method for executing the set use case or use case group comprises:
the single-case execution method comprises the following steps: selecting a required test case, inquiring an interface list under the selected case, and sequentially executing interfaces under the interface list;
or, the case group execution method comprises the following steps: selecting a case group to be tested, inquiring a case list under the case group, and executing the case under the case list according to a single case execution method.
3. The system of claim 1, wherein the single-case execution method comprises:
according to the selected use case, inquiring an interface list under the use case of mysql, and sequentially operating the interfaces in the interface list;
the operation method of the interface comprises the following steps:
before calling an interface, inquiring a preprocessing parameter of the interface, and clearing data and waiting time before executing the interface;
inquiring a request address and request content, calling the interface, acquiring a response value, extracting the response value and storing a redis cache;
inquiring parameters of the verification unit and executing verification;
and inquiring parameters of the post-processing unit, and clearing data and waiting time after the interface operates.
4. The method according to claim 1, wherein a group of cases to be tested is selected, a list of cases under the group of cases is queried,
executing the use cases in the use case list according to the single use case execution method in sequence;
or executing the use cases in the use case list in a multi-thread mode.
5. The method according to claim 4, wherein the multi-thread execution method of the use case comprises:
setting the concurrency number n of the use cases, creating a java thread pool with n threads according to the concurrency number n, submitting the use cases in the use case list to the thread pool for execution, and executing each use case according to a single use case execution method.
6. The method according to claim 8,
the request content parameters comprise body parameters, response value extraction parameters, circulation processing parameters, concurrency setting parameters and independent user parameters;
the request address body parameter comprises a key-value format and a json format;
acquiring the response value includes: acquiring response data of the interface, wherein the response data comprises json path acquisition and regular matching acquisition, and the acquired response value is stored in redis and used for verifying or transmitting parameters of the next interface;
and (3) circulating treatment: executing polling aiming at the asynchronous interface, confirming that the interface does not respond to a certain specific value, and then executing the next process; setting an actual value, an expected value, the maximum circulation times and the waiting time of each circulation by a user;
setting concurrent parameters: and setting the concurrency number for the interfaces needing concurrent execution.
7. An automatic software testing system is characterized in that,
the system comprises one or more use case groups and an operation unit;
the set of use cases comprises one or more use cases;
the use case comprises an interface unit;
the interface unit is used for setting an interface address;
the operation unit is used for inquiring the case interface unit and executing all interface unit data under the case group.
8. The system according to claim 7, wherein the use case comprises:
the interface name unit is used for setting an interface id and butting a corresponding test interface;
the request address unit is used for setting an interface address, acquiring the interface address when executing the interface address and butting a corresponding test interface;
the request content unit comprises an interface request body parameter, a response value extraction parameter, a cyclic management request parameter and a concurrency number;
the pre-processing unit is used for setting pre-processing parameters, executing the pre-processing parameters before calling the interface and clearing data and waiting time before executing the interface;
the post-processing unit is used for setting post-processing parameters, is used for the last step after the interface is executed, and clears data and waiting time after the interface is operated;
and the checking unit is used for setting checking parameters and judging the interface execution condition.
9. The system of claim 7, wherein the requesting unit comprises:
a request body unit for setting a request body parameter;
a response value extraction unit for setting a response value extraction parameter;
a loop processing unit for setting an actual value and an expected value, the maximum number of loops and each loop waiting time;
the concurrent setting unit is used for setting the concurrent number when the interface needs concurrent testing;
and the independent user unit is used for setting other available users of the application case interface.
10. The automatic software testing system according to claim 8,
the verification unit includes a verification unit for verifying whether the verification unit includes,
a response value checking unit: the system is used for setting verification parameters including actual values, conditions, expected values and descriptions;
mysql check unit: the method comprises the steps of setting mysql check parameters including sql, fields, expected values and descriptions;
and a concurrent checking unit: the method is used for setting response texts, and comprises fields and quantity;
the pre-processing unit and the post-processing unit both comprise,
msql addition unit: the system is used for setting the sql statement and can perform checking, modifying and deleting of the sql;
redis addition unit: keys and values for setting the redis can realize the clearing and updating of the redis cache;
a fixed latency setting unit: wait before executing the interface.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011510560.3A CN112559356A (en) | 2020-12-18 | 2020-12-18 | Automatic software testing method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011510560.3A CN112559356A (en) | 2020-12-18 | 2020-12-18 | Automatic software testing method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112559356A true CN112559356A (en) | 2021-03-26 |
Family
ID=75030477
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011510560.3A Pending CN112559356A (en) | 2020-12-18 | 2020-12-18 | Automatic software testing method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112559356A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113220566A (en) * | 2021-04-26 | 2021-08-06 | 深圳市云网万店科技有限公司 | Interface performance test script generation method and device and computer equipment |
| CN113282476A (en) * | 2021-06-24 | 2021-08-20 | 深圳市商汤科技有限公司 | Interface performance testing method and device and electronic equipment |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030131290A1 (en) * | 1998-06-22 | 2003-07-10 | Amir Weinberg | Software system and methods for testing transactional servers |
| US20130042222A1 (en) * | 2011-08-08 | 2013-02-14 | Computer Associates Think, Inc. | Automating functionality test cases |
| CN105138461A (en) * | 2015-09-23 | 2015-12-09 | 网易（杭州）网络有限公司 | Interface testing method and device for application program |
| CN105373469A (en) * | 2014-08-25 | 2016-03-02 | 广东金赋信息科技有限公司 | Interface based software automation test method |
| CN107577599A (en) * | 2017-08-21 | 2018-01-12 | 同程网络科技股份有限公司 | A kind of automatic interface testing method and platform based on custom script |
| CN107844421A (en) * | 2017-10-31 | 2018-03-27 | 平安科技（深圳）有限公司 | Interface test method, device, computer equipment and storage medium |
| CN109992509A (en) * | 2019-03-22 | 2019-07-09 | 恒生电子股份有限公司 | The automated execution method, apparatus of test case, electronic equipment |
| CN110704328A (en) * | 2019-10-15 | 2020-01-17 | 北京城市网邻信息技术有限公司 | Interface testing method and device, electronic equipment and readable storage medium |
| US20200233793A1 (en) * | 2019-01-17 | 2020-07-23 | Jpmorgan Chase Bank, N.A. | Behavior driven development test framework for application programming interfaces and webservices |
| WO2020155778A1 (en) * | 2019-02-03 | 2020-08-06 | 苏州市龙测智能科技有限公司 | Interface automation test method, test apparatus, test device and storage medium |
| CN111752844A (en) * | 2020-06-30 | 2020-10-09 | 北京来也网络科技有限公司 | Interface testing method and device, computing equipment and storage medium |
-
2020
- 2020-12-18 CN CN202011510560.3A patent/CN112559356A/en active Pending
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030131290A1 (en) * | 1998-06-22 | 2003-07-10 | Amir Weinberg | Software system and methods for testing transactional servers |
| US20130042222A1 (en) * | 2011-08-08 | 2013-02-14 | Computer Associates Think, Inc. | Automating functionality test cases |
| CN105373469A (en) * | 2014-08-25 | 2016-03-02 | 广东金赋信息科技有限公司 | Interface based software automation test method |
| CN105138461A (en) * | 2015-09-23 | 2015-12-09 | 网易（杭州）网络有限公司 | Interface testing method and device for application program |
| CN107577599A (en) * | 2017-08-21 | 2018-01-12 | 同程网络科技股份有限公司 | A kind of automatic interface testing method and platform based on custom script |
| CN107844421A (en) * | 2017-10-31 | 2018-03-27 | 平安科技（深圳）有限公司 | Interface test method, device, computer equipment and storage medium |
| US20200233793A1 (en) * | 2019-01-17 | 2020-07-23 | Jpmorgan Chase Bank, N.A. | Behavior driven development test framework for application programming interfaces and webservices |
| WO2020155778A1 (en) * | 2019-02-03 | 2020-08-06 | 苏州市龙测智能科技有限公司 | Interface automation test method, test apparatus, test device and storage medium |
| CN109992509A (en) * | 2019-03-22 | 2019-07-09 | 恒生电子股份有限公司 | The automated execution method, apparatus of test case, electronic equipment |
| CN110704328A (en) * | 2019-10-15 | 2020-01-17 | 北京城市网邻信息技术有限公司 | Interface testing method and device, electronic equipment and readable storage medium |
| CN111752844A (en) * | 2020-06-30 | 2020-10-09 | 北京来也网络科技有限公司 | Interface testing method and device, computing equipment and storage medium |
Non-Patent Citations (7)
| Title |
|---|
| ISHA等: "Automated API Testing", 《2018 3RD INTERNATIONAL CONFERENCE ON INVENTIVE COMPUTATION TECHNOLOGIES(ICICT)》, 12 March 2020 (2020-03-12), pages 788 - 791 * |
| MARJAN VENEMA等: "Testing every implementer of an interface with the same tests using MSTest", Retrieved from the Internet <URL:https://softwareonastring.com/502/testing-every-implementer-of-an-interface-with-the-same-tests-using-mstest> * |
| 一个椰子: "pytest接口自动化用例详解T011", Retrieved from the Internet <URL:https://zhuanlan.zhihu.com/p/305646269> * |
| 于敞: "基于微服务架构的接口自动化测试服务与测试报告的设计与实现", 《中国优秀硕士学位论文全文数据库 信息科技辑》, no. 2019, 15 September 2019 (2019-09-15), pages 138 - 231 * |
| 李璇: "服务端接口自动化测试的设计与实现", 《中国优秀硕士论文全文数据库 信息科技辑》, no. 2019, 15 June 2019 (2019-06-15), pages 138 - 161 * |
| 程序员-小枫: "软件测试的那些事之接口自动化测试（九）：测试用例管理", Retrieved from the Internet <URL:https://blog.csdn.net/weixin_49346599/article/details/108474688> * |
| 蒋灵仙: "基于Tesng的Web接口测试的自动化框架设计与实现", 《中国优秀硕士论文全文数据库 信息科技辑》, no. 2017, 15 June 2017 (2017-06-15), pages 138 - 807 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113220566A (en) * | 2021-04-26 | 2021-08-06 | 深圳市云网万店科技有限公司 | Interface performance test script generation method and device and computer equipment |
| CN113282476A (en) * | 2021-06-24 | 2021-08-20 | 深圳市商汤科技有限公司 | Interface performance testing method and device and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8091075B2 (en) | Method and apparatus for breakpoint analysis of computer programming code using unexpected code path conditions | |
| US8892953B2 (en) | Method and system for test suite control | |
| US7644394B2 (en) | Object-oriented creation breakpoints | |
| US10613964B2 (en) | Conditional debugging of server-side production code | |
| US20090287729A1 (en) | Source code coverage testing | |
| CN112559356A (en) | Automatic software testing method and system | |
| US20130318504A1 (en) | Execution Breakpoints in an Integrated Development Environment for Debugging Dataflow Progrrams | |
| US20150143179A1 (en) | System and Method for Progressive Fault Injection Testing | |
| CN112988782B (en) | Hive-supported interactive query method and device and storage medium | |
| CN105989059A (en) | Data record checking method and device | |
| US20150106348A1 (en) | Monitoring business transaction failures involving database procedure calls | |
| CN111767227A (en) | Recording playback test method and device | |
| CN108319711A (en) | Transaction consistency test method, device, storage medium and the equipment of database | |
| CN102981946B (en) | ETL smoke test method | |
| CN101034402B (en) | Method and apparatus for handling a user-defined event that is generated during test of a device | |
| US20050144596A1 (en) | Method and apparatus for parallel action processing | |
| CN112286534A (en) | Automatic compiling method for software package | |
| JP2007249949A (en) | Device for storing variable value to provide context for test result to be formatted | |
| CN111984241B (en) | Method, device, equipment and medium for dynamically taking effect of online codes | |
| CN114691496A (en) | Unit testing method, unit testing device, computing equipment and medium | |
| CN108804311B (en) | Method and device for executing test file | |
| CN112965798A (en) | Big data processing method and system based on distributed multithreading | |
| CN112732367A (en) | Event flow processing method, device and equipment and readable storage medium | |
| CN111552608A (en) | Drive memory monitoring method and system | |
| CN111723104A (en) | Method, device and system for syntax analysis in data processing system |
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 |