CN111240981A - Interface testing method, system and platform - Google Patents
Interface testing method, system and platform Download PDFInfo
- Publication number
- CN111240981A CN111240981A CN202010034757.8A CN202010034757A CN111240981A CN 111240981 A CN111240981 A CN 111240981A CN 202010034757 A CN202010034757 A CN 202010034757A CN 111240981 A CN111240981 A CN 111240981A
- Authority
- CN
- China
- Prior art keywords
- interface
- tested
- test
- result
- test 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
- 238000012360 testing method Methods 0.000 title claims abstract description 300
- 238000000034 method Methods 0.000 claims abstract description 21
- 238000012795 verification Methods 0.000 claims description 19
- 238000010998 test method Methods 0.000 abstract description 5
- 230000006870 function Effects 0.000 description 7
- 238000011161 development Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- XSQUKJJJFZCRTK-NJFSPNSNSA-N UREA C 14 Chemical compound N[14C](N)=O XSQUKJJJFZCRTK-NJFSPNSNSA-N 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
- 230000003245 working effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Prevention of errors by analysis, debugging or testing of software
- G06F11/3668—Testing of software
- 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—Prevention of errors by analysis, debugging or testing of software
- G06F11/3668—Testing of software
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application discloses an interface test method, a system and a platform, wherein the method comprises the steps of receiving a call request of an interface to be tested; acquiring an interface test case of the interface to be tested; receiving an interface return result, wherein the interface return result is obtained by dynamically calling the interface to be tested by an interface test execution framework according to the interface test case data; if the interface return result contains the input expected result, determining that the test result of the interface to be tested is qualified; and if the interface return result does not contain the input expected result, determining that the test result of the interface to be tested is unqualified. According to the interface testing method and device, the interface testing case is automatically obtained, the interface is automatically tested, whether the interface is qualified or not is automatically judged, and then the interface testing efficiency is improved.
Description
Technical Field
The present disclosure relates to the field of interface testing technologies, and in particular, to a method, a system, and a platform for testing an interface.
Background
With the development of software technology, more and more software provides services for users through platforms, and a third party can customize required services according to platform provided interfaces, so that the software often relates to interface testing nowadays. Interfaces are predefined functions that are intended to provide applications and developers the ability to access a set of routines based on certain software or hardware without having to access source code or understand the details of the internal workings. The interface test is a test of submitting input data to an interface, obtaining a return result and analyzing whether the result meets expectations. Various system commands, test tools, and even programming techniques may be involved in the interface testing.
At present, most of software development processes manually compile various types of interface use cases, and then manually run the use cases by using some existing tools in the market after the use cases are compiled, so that a series of problems of low efficiency, influence on project progress and the like are caused.
Disclosure of Invention
The application aims to provide an interface testing method, system and platform so as to solve the problems that the interface testing efficiency is low, the project progress is influenced and the like.
In a first aspect, an embodiment of the present application provides an interface testing method, including:
receiving a calling request of an interface to be tested;
acquiring an interface test case of the interface to be tested;
receiving an interface return result, wherein the interface return result is obtained by dynamically calling the interface to be tested by an interface test execution framework according to the interface test case data;
if the interface return result contains the input expected result, determining that the test result of the interface to be tested is qualified;
and if the interface return result does not contain the input expected result, determining that the test result of the interface to be tested is unqualified.
With reference to the first aspect, in a first implementable manner of the first aspect, the step of obtaining the interface test case of the interface to be tested includes:
acquiring an interface test case compiled by a webpage, and storing the interface test case to a database;
or,
and acquiring an interface test case of the interface to be tested in the database.
With reference to the first aspect, in a second implementable manner of the first aspect, the step of obtaining the interface test case of the interface to be tested includes:
acquiring test case set data set to be executed by a user;
and matching through a test case list in a database according to the test case set data to assemble the interface test case of the tested interface.
With reference to the first aspect, in a third implementable manner of the first aspect, the method further includes:
obtaining a return value of the interface call request to be tested in a database;
comparing the return value with the expected value of the interface test case;
if the return value is the same as the expected value, determining that the verification is successful;
and if the return value is not the same as the expected value, determining that the verification fails.
With reference to the first aspect, in a fourth implementable manner of the first aspect, the method further includes:
classifying the interface test cases according to the type of the interface to be tested;
and counting the test result executed by the test case of each type of interface.
In a second aspect, an embodiment of the present application provides an interface test system, including:
the request receiving unit is used for receiving a calling request of the interface to be tested;
the first acquisition unit is used for acquiring an interface test case of the interface to be tested;
the return result receiving unit is used for receiving an interface return result, and the interface return result is obtained by dynamically calling the interface to be tested by the interface test execution frame according to the interface test case data;
the test result determining unit is used for determining that the test result of the interface to be tested is qualified if the interface return result contains the input expected result;
and if the interface return result does not contain the input expected result, determining that the test result of the interface to be tested is unqualified.
With reference to the second aspect, in a first implementable manner of the first aspect, the first obtaining unit includes:
the first acquiring subunit is used for acquiring an interface test case compiled by a webpage;
the storage unit is used for storing the interface test case to a database;
or,
and the second obtaining subunit is used for obtaining the interface test case of the interface to be tested in the database.
With reference to the second aspect, in a second implementable manner of the first aspect, the first obtaining unit includes:
the third acquisition subunit is used for acquiring the test case set data set by the user for execution;
and the assembling unit is used for matching through a test case list in a database according to the test case set data to assemble the interface test case of the tested interface.
With reference to the second aspect, in a third implementable manner of the first aspect, the system further includes:
the second acquisition unit is used for acquiring a return value of the interface call request to be tested in the database;
the comparison unit is used for comparing the return value with the expected value of the interface test case;
the verification determining unit is used for determining that verification is successful if the return value is the same as the expected value;
and if the return value is not the same as the expected value, determining that the verification fails.
With reference to the second aspect, in a fourth implementable manner of the first aspect, the system further includes:
the classification unit is used for classifying the interface test cases according to the type of the interface to be tested;
and the statistical unit is used for counting the test result executed by each type of interface test case.
In a third aspect, an embodiment of the present application provides an interface test platform, including a web application system, an interface test execution framework and a database;
the web application system is connected with the interface test execution framework, the interface test execution framework is connected with the database, and the web application system is connected with the database;
the web application system is used for receiving a calling request of an interface to be tested; acquiring an interface test case of the interface to be tested; receiving an interface return result, wherein the interface return result is obtained by dynamically calling the interface to be tested by an interface test execution framework according to the interface test case data; if the interface return result contains the input expected result, determining that the test result of the interface to be tested is qualified; if the interface return result does not contain the input expected result, determining that the test result of the interface to be tested is unqualified;
the interface test execution framework is used for dynamically calling the interface to be tested according to the interface test case data to obtain an interface return result;
the database is used for storing interface test cases, test data and test results executed by the interface test cases.
According to the technical scheme, after the call request of the interface to be tested is received; acquiring an interface test case of the interface to be tested; dynamically calling the interface to be tested according to the interface test case data to obtain an interface return result; if the interface return result contains the input expected result, determining that the test result of the interface to be tested is qualified; and if the interface return result does not contain the input expected result, determining that the test result of the interface to be tested is unqualified. According to the interface testing method and device, the interface testing case is automatically obtained, the interface is automatically tested, whether the interface is qualified or not is automatically judged, and then the interface testing efficiency is improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.
Fig. 1 is a flowchart illustrating a first embodiment of an interface testing method according to an embodiment of the present application;
FIG. 2 is a block diagram illustrating an interface test system according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of an interface test platform 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 and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application. The technical solutions provided by the embodiments of the present application are described in detail below with reference to the accompanying drawings.
Referring to fig. 1, a flowchart of a first embodiment of an interface testing method is provided for the embodiment of the present application, including:
step 101, receiving a call request of an interface to be tested;
the call request of the interface to be tested is initiated by a user.
102, acquiring an interface test case of the interface to be tested;
the interface test case of the interface to be tested can be written by a user, the existing interface test case can be called from a database, and the required interface test case can be assembled according to the test case set data.
103, receiving an interface return result, wherein the interface return result is obtained by dynamically calling the interface to be tested by an interface test execution framework according to the interface test case data;
the interface test execution framework can intelligently identify the interface to be tested according to the data transmitted by the page, execute the interface to be tested and store the test result in the database.
104, if the interface return result contains an input expected result, determining that the test result of the interface to be tested is qualified;
and 105, if the interface return result does not contain the input expected result, determining that the test result of the interface to be tested is unqualified.
For example, after receiving a call request of the interface to be tested, the call request of the interface to be tested initiated by the user returns a return result of the interface according to the request. Specifically, a user initiates an interface calling request for calling a display picture, returns a test result to the electronic device after receiving the request, and if the request is successful, the frame layer returns a success label to indicate that the test interface is qualified. If the request fails, the framework layer returns that the failure indicates that the test interface is unqualified.
It should be noted that, the interface is often packaged as a function for testing, and then the function is called to automate the interface function test. The user writes an interface test case through the platform, and then executes the interface test case through the interface case execution system. According to the embodiment of the application, the interface test is carried out by adopting the B/S mode platform, business personnel uniformly enter the operation, and the environment and data do not need to be built and prepared by self.
As can be seen from the above embodiments, in the first embodiment of the interface testing method of the present application, a call request of an interface to be tested is received; acquiring an interface test case of the interface to be tested; receiving an interface return result, wherein the interface return result is obtained by dynamically calling the interface to be tested by an interface test execution framework according to the interface test case data; if the interface return result contains the input expected result, determining that the test result of the interface to be tested is qualified; and if the interface return result does not contain the input expected result, determining that the test result of the interface to be tested is unqualified. According to the interface testing method and device, the interface testing case is automatically obtained, the interface is automatically tested, whether the interface is qualified or not is automatically judged, and then the interface testing efficiency is improved.
On the basis of the first embodiment, an embodiment of the present application provides a second embodiment of an interface test method, where the step of obtaining an interface test case of the interface to be tested includes:
and acquiring an interface test case compiled by a webpage, and storing the interface test case to a database.
The embodiment of the application can also utilize the webpage page to manage the interface test cases, wherein the management of the interface test cases specifically refers to modification or deletion of the interface test cases. According to the method and the device, the webpage is used for compiling and managing the interface test cases, and the method and the device have the advantages of being visual, easy to operate and intelligent.
According to the second embodiment of the interface test method, the interface test case written by the webpage is obtained, and the interface test case is stored to the database. The user edits the use case in a webpage operation mode, and the platform stores the use case input by the user into the database, so that the data can be persisted, and the data can be conveniently reused.
On the basis of the first embodiment, an embodiment of the present application provides a third embodiment of an interface test method, where the step of obtaining an interface test case of the interface to be tested includes:
and acquiring an interface test case of the interface to be tested in the database.
The database stores all interface test cases written by users.
If the interface test case of the interface to be tested is not found in the database, the user needs to write the interface test case by using the webpage. If the interface test case of the interface to be tested can be found in the database, the interface test case of the interface to be tested in the database can be directly obtained.
As can be seen from the above embodiments, in the third embodiment of the interface testing method according to the present application, the interface test case of the interface to be tested in the database is obtained. The interface test cases in the database are directly called, and a user does not need to compile the cases in a webpage operation mode, so that the compiling time of the interface test cases is saved, and the interface test efficiency is improved.
On the basis of the first embodiment, an embodiment of the present application provides a fourth embodiment of an interface test method, where the step of obtaining an interface test case of the interface to be tested includes:
acquiring test case set data set to be executed by a user;
and matching through a test case list in a database according to the test case set data to assemble the interface test case of the tested interface.
According to the method and the device, all test cases required to be executed by a user can be combined and sequentially executed according to the sequence.
According to the fourth embodiment of the interface testing method, the test case set data required to be executed by the user is obtained; and matching through a test case list in a database according to the test case set data to assemble the test case of the tested interface. The embodiment of the application can meet the requirement that a user assembles the required interface test case for testing, and improves the interface test efficiency.
On the basis of the first embodiment, an embodiment of the present application provides a fifth embodiment of an interface testing method, where the method further includes:
obtaining a return value of the interface call request to be tested in a database;
comparing the return value with the expected value of the interface test case;
if the return value is the same as the expected value, determining that the verification is successful;
and if the return value is not the same as the expected value, determining that the verification fails.
And judging whether the interface test case is complete or not according to the verification result. If the interface test case is successfully verified, the interface test case can be continuously used. If the interface test case is verified to be failed, the interface test case is not suitable for the interface to be tested, and the interface test case can be changed or replaced.
As can be seen from the foregoing embodiments, in the fifth embodiment of the interface testing method according to the present application, a return value of the interface call request to be tested in the database is obtained; comparing the return value with the expected value of the interface test case; if the return value is the same as the expected value, determining that the verification is successful; and if the return value is not the same as the expected value, determining that the verification fails. The embodiment of the application can verify the test result of the interface test case, and the accuracy of the interface test case is ensured.
On the basis of the first embodiment, an embodiment of the present application provides a sixth embodiment of an interface testing method, where the method further includes:
classifying the interface test cases according to the type of the interface to be tested;
and counting the test result executed by the test case of each type of interface.
After the interface test cases are classified according to the types of the interfaces to be tested, the same type of interface test cases are used for testing the interfaces to be tested corresponding to the type of interface test cases. And according to the test results of the test cases of the same type of interface, carrying out classified statistics on the execution results of the test cases of the interface by a report statistical tool. Specifically, the coverage rate, success rate and the like of each type of tested interface can be counted.
As can be seen from the above embodiments, in the sixth embodiment of the interface testing method according to the present application, interface test cases are classified according to the type of the interface to be tested; and counting the test result executed by the test case of each type of interface. The method and the device can test the interfaces to be tested of the same type by using the interface test cases of the same type, can calculate the coverage rate, the success rate and the like of each type of tested interface according to the test result, and display the statistical result to the service personnel, so that the service personnel can conveniently adjust the interface test cases.
Referring to fig. 2, a block diagram of an interface test system is provided in the present application, and an interface test system provided in the embodiment of the present application includes:
a request receiving unit 201, configured to receive a call request of an interface to be tested;
a first obtaining unit 202, configured to obtain an interface test case of the interface to be tested;
a returned result receiving unit 203, configured to receive an interface returned result, where the interface returned result is obtained by dynamically calling, by an interface test execution framework, the interface to be tested according to the interface test case data;
a test result determining unit 204, configured to determine that the test result of the interface to be tested is qualified if the interface return result includes an input expected result;
and if the interface return result does not contain the input expected result, determining that the test result of the interface to be tested is unqualified.
In another embodiment of an interface testing system provided by the present application, the first obtaining unit includes:
the first acquiring subunit is used for acquiring an interface test case compiled by a webpage;
the storage unit is used for storing the interface test case to a database;
or,
and the second obtaining subunit is used for obtaining the interface test case of the interface to be tested in the database.
In another embodiment of an interface testing system provided by the present application, the first obtaining unit includes:
the third acquisition subunit is used for acquiring the test case set data set by the user for execution;
and the assembling unit is used for matching through a test case list in a database according to the test case set data to assemble the interface test case of the tested interface.
In another embodiment of an interface testing system provided by the present application, the system further includes:
the second acquisition unit is used for acquiring a return value of the interface call request to be tested in the database;
the comparison unit is used for comparing the return value with the expected value of the interface test case;
the verification determining unit is used for determining that verification is successful if the return value is the same as the expected value;
and if the return value is not the same as the expected value, determining that the verification fails.
In another embodiment of an interface testing system provided by the present application, the system further includes:
the classification unit is used for classifying the interface test cases according to the type of the interface to be tested:
and the statistical unit is used for counting the test result executed by each type of interface test case.
Referring to fig. 3, a schematic structural diagram of an interface test platform is provided for the present application, and an embodiment of the present application provides an interface test platform, including a web application system 301, an interface test execution framework 302, and a database 303;
the web application system 301 is connected with the interface test execution framework 302, the interface test execution framework 302 is connected with the database 303, and the web application system 301 is connected with the database 303;
the web application system 301 is configured to receive a call request of an interface to be tested; acquiring an interface test case of the interface to be tested; receiving an interface return result, wherein the interface return result is obtained by dynamically calling the interface to be tested by an interface test execution framework according to the interface test case data; if the interface return result contains the input expected result, determining that the test result of the interface to be tested is qualified; if the interface return result does not contain the input expected result, determining that the test result of the interface to be tested is unqualified;
the interface test execution framework 302 is configured to dynamically call the interface to be tested according to the interface test case data to obtain an interface return result;
the database 303 is configured to store an interface test case, test data, and a test result executed by the interface test case.
It should be noted that the interface test platform includes 3 components, specifically, a web application system 301 developed based on Django + VUE, an interface test execution framework 302, and a database 303; the web application development framework of the python technology stack is simple to enter and easy to develop; the VUE is an open-source front-end web development scaffold, and the open-source front-end components are rich in resources and high in development efficiency. The web application system is used as a unique entrance of the interface automatic test, and provides a newly added interface test case, test case management, interface test case database, interface test service verification supporting multiple test environments, online display of test reports, an online combination test set and a Restful API (application program interface) providing for a third party; the interface test execution framework comprises interface definitions packaged by service personnel according to specifications, interface definition database, test data configuration, logic judgment, execution of interface test case main functions, interface calling unified processing logic, a same log management system and the like; the database not only stores and manages the test cases and the test data in the web application system, but also needs to archive the service interface.
In addition, the general flow of executing the interface test is as follows:
1. logging in a unified interface test platform, selecting a test environment, entering a test case management module, selecting an interface test case to be executed, and realizing a customized interface test sequence;
2. clicking a construction button to trigger the automatic test execution of the interface;
3. after receiving the execution request, the back end transmits the relevant parameters to the main function of the execution framework in a mode of executing the py file by a command line;
4. after the execution frame main function takes the relevant parameters, executing a pytest frame command, and uniformly executing the automatic test of the interface;
5. and after the execution is finished, the user views the automatic test report of the interface on the platform.
According to the technical scheme, after the call request of the interface to be tested is received; acquiring an interface test case of the interface to be tested; dynamically calling the interface to be tested according to the interface test case data to obtain an interface return result; if the interface return result contains the input expected result, determining that the test result of the interface to be tested is qualified; and if the interface return result does not contain the input expected result, determining that the test result of the interface to be tested is unqualified. According to the interface testing method and device, the interface testing case is automatically obtained, the interface is automatically tested, whether the interface is qualified or not is automatically judged, and then the interface testing efficiency is improved.
In specific implementation, the present application further provides a computer storage medium, where the computer storage medium may store a program, and the program may include some or all of the steps in the embodiments of the method for improving asset security provided by the present invention when executed. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM) or a Random Access Memory (RAM).
Those skilled in the art will readily appreciate that the techniques of the embodiments of the present invention may be implemented as software plus a required general purpose hardware platform. Based on such understanding, the technical solutions in the embodiments of the present invention may be essentially or partially implemented in the form of a software product, which may be stored in a storage medium, such as ROM/RAM, magnetic disk, optical disk, etc., and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method according to the embodiments or some parts of the embodiments.
The same and similar parts in the various embodiments in this specification may be referred to each other. In particular, for the system and platform embodiments for interface testing, since they are substantially similar to the method embodiments, the description is simple, and the relevant points can be referred to the description in the method embodiments.
The above-described embodiments of the present application do not limit the scope of the present application.
Claims (11)
1. An interface testing method, comprising:
receiving a calling request of an interface to be tested;
acquiring an interface test case of the interface to be tested;
receiving an interface return result, wherein the interface return result is obtained by dynamically calling the interface to be tested by an interface test execution framework according to the interface test case data;
if the interface return result contains the input expected result, determining that the test result of the interface to be tested is qualified;
and if the interface return result does not contain the input expected result, determining that the test result of the interface to be tested is unqualified.
2. The method according to claim 1, wherein the step of obtaining the interface test case of the interface to be tested comprises:
acquiring an interface test case compiled by a webpage, and storing the interface test case to a database;
or,
and acquiring an interface test case of the interface to be tested in the database.
3. The method according to claim 1, wherein the step of obtaining the interface test case of the interface to be tested comprises:
acquiring test case set data set to be executed by a user;
and matching through a test case list in a database according to the test case set data to assemble the interface test case of the tested interface.
4. The method of claim 1, further comprising:
obtaining a return value of the interface call request to be tested in a database;
comparing the return value with the expected value of the interface test case;
if the return value is the same as the expected value, determining that the verification is successful;
and if the return value is not the same as the expected value, determining that the verification fails.
5. The method of claim 1, further comprising:
classifying the interface test cases according to the type of the interface to be tested:
and counting the test result executed by the test case of each type of interface.
6. An interface test system, comprising:
the request receiving unit is used for receiving a calling request of the interface to be tested;
the first acquisition unit is used for acquiring an interface test case of the interface to be tested;
the return result receiving unit is used for receiving an interface return result, and the interface return result is obtained by dynamically calling the interface to be tested by the interface test execution frame according to the interface test case data;
the test result determining unit is used for determining that the test result of the interface to be tested is qualified if the interface return result contains the input expected result;
and if the interface return result does not contain the input expected result, determining that the test result of the interface to be tested is unqualified.
7. The system of claim 6, wherein the first obtaining unit comprises:
the first acquiring subunit is used for acquiring an interface test case compiled by a webpage;
the storage unit is used for storing the interface test case to a database;
or,
and the second obtaining subunit is used for obtaining the interface test case of the interface to be tested in the database.
8. The system of claim 6, wherein the first obtaining unit comprises:
the third acquisition subunit is used for acquiring the test case set data set by the user for execution;
and the assembling unit is used for matching through a test case list in a database according to the test case set data to assemble the interface test case of the tested interface.
9. The system of claim 6, further comprising:
the second acquisition unit is used for acquiring a return value of the interface call request to be tested in the database;
the comparison unit is used for comparing the return value with the expected value of the interface test case;
the verification determining unit is used for determining that verification is successful if the return value is the same as the expected value;
and if the return value is not the same as the expected value, determining that the verification fails.
10. The system of claim 6, further comprising:
the classification unit is used for classifying the interface test cases according to the type of the interface to be tested;
and the statistical unit is used for counting the test result executed by each type of interface test case.
11. An interface test platform is characterized by comprising a web application system, an interface test execution framework and a database;
the web application system is connected with the interface test execution framework, the interface test execution framework is connected with the database, and the web application system is connected with the database;
the web application system is used for receiving a calling request of an interface to be tested; acquiring an interface test case of the interface to be tested; receiving an interface return result, wherein the interface return result is obtained by dynamically calling the interface to be tested by an interface test execution framework according to the interface test case data; if the interface return result contains the input expected result, determining that the test result of the interface to be tested is qualified; if the interface return result does not contain the input expected result, determining that the test result of the interface to be tested is unqualified;
the interface test execution framework is used for dynamically calling the interface to be tested according to the interface test case data to obtain an interface return result;
the database is used for storing interface test cases, test data and test results executed by the interface test cases.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010034757.8A CN111240981A (en) | 2020-01-14 | 2020-01-14 | Interface testing method, system and platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010034757.8A CN111240981A (en) | 2020-01-14 | 2020-01-14 | Interface testing method, system and platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111240981A true CN111240981A (en) | 2020-06-05 |
Family
ID=70874500
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010034757.8A Pending CN111240981A (en) | 2020-01-14 | 2020-01-14 | Interface testing method, system and platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111240981A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112052161A (en) * | 2020-08-06 | 2020-12-08 | 中信银行股份有限公司 | Interface testing method and device, electronic equipment and medium |
| CN112559346A (en) * | 2020-12-14 | 2021-03-26 | 北京三快在线科技有限公司 | Service testing method and device |
| CN114153747A (en) * | 2021-12-21 | 2022-03-08 | 优刻得科技股份有限公司 | Interface testing method, electronic equipment and computer readable storage medium |
| CN117171056A (en) * | 2023-11-02 | 2023-12-05 | 绿城科技产业服务集团有限公司 | Test method and device based on automatic interface |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108549606A (en) * | 2018-04-16 | 2018-09-18 | 成都医云科技有限公司 | interface test method and device |
-
2020
- 2020-01-14 CN CN202010034757.8A patent/CN111240981A/en active Pending
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108549606A (en) * | 2018-04-16 | 2018-09-18 | 成都医云科技有限公司 | interface test method and device |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112052161A (en) * | 2020-08-06 | 2020-12-08 | 中信银行股份有限公司 | Interface testing method and device, electronic equipment and medium |
| CN112052161B (en) * | 2020-08-06 | 2024-05-28 | 中信银行股份有限公司 | Interface testing method and device, electronic equipment and medium |
| CN112559346A (en) * | 2020-12-14 | 2021-03-26 | 北京三快在线科技有限公司 | Service testing method and device |
| CN114153747A (en) * | 2021-12-21 | 2022-03-08 | 优刻得科技股份有限公司 | Interface testing method, electronic equipment and computer readable storage medium |
| CN117171056A (en) * | 2023-11-02 | 2023-12-05 | 绿城科技产业服务集团有限公司 | Test method and device based on automatic interface |
| CN117171056B (en) * | 2023-11-02 | 2024-01-09 | 绿城科技产业服务集团有限公司 | Test method and device based on automatic interface |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10872029B1 (en) | System, apparatus and method for deploying infrastructure to the cloud | |
| US11233708B1 (en) | System, apparatus and method for deploying infrastructure to the cloud | |
| US8954930B2 (en) | System and method for reducing test effort by object risk analysis | |
| Cojocaru et al. | Attributes assessing the quality of microservices automatically decomposed from monolithic applications | |
| US8984489B2 (en) | Quality on submit process | |
| CN111240981A (en) | Interface testing method, system and platform | |
| US10990370B1 (en) | System, apparatus and method for deploying infrastructure to the cloud | |
| CN108492005B (en) | Project data processing method and device, computer equipment and storage medium | |
| CN108108297A (en) | The method and apparatus of automatic test | |
| CN114546738B (en) | Universal test method, system, terminal and storage medium for server | |
| CN102571403A (en) | Realization method and device for general data quality control adapter | |
| GB2604007A (en) | Software upgrade stability recommendations | |
| US9823999B2 (en) | Program lifecycle testing | |
| CN111984882A (en) | Data processing method, system and equipment | |
| CN113778878A (en) | Interface testing method and device, electronic equipment and storage medium | |
| EP2199905A1 (en) | Lifecycle management and consistency checking of object models using application platform tools | |
| EP2913757A1 (en) | Method, system, and computer software product for test automation | |
| CN112527564A (en) | Database data recovery drilling method and device and storage medium | |
| CN115576817A (en) | Automatic test system, method, electronic equipment and storage medium | |
| CN109992614B (en) | Data acquisition method, device and server | |
| CN115292418B (en) | Cross-system business process automatic processing method and system | |
| US8868424B1 (en) | Interactive voice response data collection object framework, vertical benchmarking, and bootstrapping engine | |
| US20160180262A1 (en) | System and method for testing enterprise transactions | |
| Fu et al. | Runtime recovery actions selection for sporadic operations on public cloud | |
| US11366642B1 (en) | Change migration: processes for ensuring successful deployment of design changes |
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 | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: Floor 1, No.81 Xinle Road, high tech Zone, Chengdu, Sichuan 610041 Applicant after: Chengdu Cooper Innovation Technology Co.,Ltd. Address before: 610041 floor 1, No. 81, Xinle Road, Chengdu hi tech Zone, Chengdu, Sichuan Applicant before: Chengdu Cooper blockchain Technology Co.,Ltd. |
|
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200605 |