CN111694734A - Software interface checking method and device and computer equipment - Google Patents
Software interface checking method and device and computer equipment Download PDFInfo
- Publication number
- CN111694734A CN111694734A CN202010452879.9A CN202010452879A CN111694734A CN 111694734 A CN111694734 A CN 111694734A CN 202010452879 A CN202010452879 A CN 202010452879A CN 111694734 A CN111694734 A CN 111694734A
- Authority
- CN
- China
- Prior art keywords
- test
- interface
- tested
- verification
- test result
- 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 75
- 238000012795 verification Methods 0.000 claims abstract description 128
- 238000004519 manufacturing process Methods 0.000 claims abstract description 25
- 238000012360 testing method Methods 0.000 claims description 282
- 244000035744 Hura crepitans Species 0.000 claims description 20
- 238000006243 chemical reaction Methods 0.000 claims description 6
- 238000004590 computer program Methods 0.000 claims description 4
- 230000002349 favourable effect Effects 0.000 abstract description 3
- 238000012423 maintenance Methods 0.000 abstract description 3
- 238000010586 diagram Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 238000012937 correction Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000011990 functional testing Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000003672 processing method Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
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)
- Stored Programmes (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application discloses a software interface checking method, a software interface checking device, computer equipment and a storage medium. By using the return data of the existing production environment of the version before the online as the verification data of the tested version interface, the complex verification method for each interface case does not need to be compiled again, and the interface is executed according to the verification method to obtain a specific verification result, so that the time cost for compiling the verification method and running the verification method to obtain the verification result is greatly saved. In addition, when the interface is checked, the method and the device can also send early warning to the interface which does not pass the check, analyze and check the problem of the interface, and are favorable for maintenance personnel to quickly carry out interface debugging work.
Description
Technical Field
The present invention relates to the technical field of interface function verification, and in particular, to a software interface verification method, apparatus, computer device, and storage medium.
Background
Before a new version of the software is online every time, the new version needs to be deployed in a sandbox environment for an overall function test once, and the software can be used online formally after the function test is passed. Since a lot of test time is consumed for performing the overall function test on the software, the overall function test on the software is usually performed in an interface test manner.
When the software is subjected to functional test in an interface test mode, interface cases of each interface need to be collected uniformly, corresponding verification methods are compiled according to the interfaces respectively, and then the interfaces are tested by using the verification methods.
However, since the version of the software is updated continuously, a corresponding verification method needs to be written for the interface use case continuously along with the updating of the version of the software, and when the number of interfaces is large, time cost is high when a thinner verification method is written.
Disclosure of Invention
The invention aims to provide a software interface checking method, a software interface checking device, computer equipment and a storage medium, and aims to solve the problems of long time consumption and low efficiency of checking in the prior art.
In a first aspect, the present application provides a software interface verification method, including:
receiving a verification request, wherein the verification request comprises a test case of a tested interface;
testing the tested interface of the online version of the tested software by using the test case in a production environment to generate a first test result;
converting the first test result into verification data;
testing the tested interface of the tested version of the tested software by using the test case in a sandbox environment to generate a second test result;
and comparing the second test result with the verification data to generate a test result.
Optionally, the step of comparing the second test result with the verification data to generate a test result includes:
if the data type of the second test result is different from the data type indicated by the verification data, generating a test result for indicating that the tested interface fails the test case test;
if the data type of the second test result is the same as the data type indicated by the verification data, but the numerical value of the second test result is different from the numerical value indicated by the verification data, generating a test result for indicating that the tested interface fails the test case test;
the method further comprises the following steps:
and if the test result indicates that the tested interface fails to pass the test of the test case, sending reminding information.
Optionally, the method further includes:
and if the second test result is the same as the data type and the numerical value indicated by the verification data, generating a test result for indicating that the tested interface passes the test case test.
Optionally, the method further includes:
and when all tested interfaces in the tested version of the tested software generate test results for indicating the tested interfaces to pass the test case test, sending an online instruction to a terminal.
In a second aspect, the present application provides a software interface checking apparatus, including:
the device comprises a receiving request unit, a verification request unit and a verification unit, wherein the receiving request unit is used for receiving a verification request which comprises a test case of a tested interface;
the first test unit is used for testing the tested interface of the online version of the tested software by using the test case in a production environment to generate a first test result;
the data conversion unit is used for converting the first test result into verification data;
the second testing unit is used for testing the tested interface of the tested version of the tested software by using the test case in a sandbox environment to generate a second testing result;
and the comparison unit is used for comparing the second test result with the verification data to generate a test result.
Optionally, the comparing unit includes:
the data type checking subunit is used for comparing the checking data with the data type of a second test result, and if the data type of the second test result is different from the data type indicated by the checking data, generating a test result for indicating that the tested interface fails the test case test;
a numerical value checking subunit, configured to compare, when the data type of the second test result is the same as the data type indicated by the check data, a numerical value of the check data with a numerical value of the second test result, and if the numerical value of the second test result is different from the numerical value indicated by the check data, generate a test result indicating that the tested interface fails the test case test;
the device further comprises:
and the information feedback unit is used for sending reminding information when the test result indicates that the tested interface fails the test of the test case.
Optionally, the numerical value verification subunit is further configured to generate a test result for indicating that the interface under test passes the test case test when the second test result is the same as the data type and the numerical value indicated by the verification data.
Optionally, the apparatus further comprises:
and the summarizing unit is used for sending an online instruction to a terminal when all tested interfaces in the tested version of the tested software generate test results for indicating that the tested interfaces pass the test case test.
In a third aspect, the present application provides a computer device for performing the above method, comprising:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the methods described above.
In a fourth aspect, the present application also provides a computer-readable storage medium having a computer program stored thereon, the program being executable by a processor to implement the method described above.
When the tool provided by the application carries out function test on the software online service version, a first test result is obtained by firstly requesting a production environment for each interface, the first test result is converted into verification data for verification, then a sandbox environment is requested for the same interface, sandbox data is obtained, and whether the interface passes the verification or not is determined according to the comparison result of the verification data and the sandbox data. According to the method and the device, the return data of the existing production environment of the version before online are used as the verification data of the tested version interface, and therefore a complex verification method does not need to be compiled for each interface case again, and the interface is executed according to the verification method to obtain a specific verification result, so that the time cost for compiling the verification method and running the verification method to obtain the verification result is greatly saved. In addition, when the interface is checked, the method and the device can also send early warning to the interface which does not pass the check, analyze and check the problem of the interface, and are favorable for maintenance personnel to quickly carry out interface debugging work.
Drawings
In order to more clearly explain the technical solution of the present application, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious to those skilled in the art that other drawings can be obtained according to the drawings without any creative effort.
FIG. 1 is a flowchart of a software interface verification method according to the present application;
FIG. 2 is an exploded view of the process of step S80 of the method of FIG. 1;
FIG. 3 is a block diagram of a software interface verification apparatus according to the present application;
FIG. 4 is a diagram showing the structure of a comparison unit in the apparatus shown in FIG. 3.
Detailed Description
The technical solutions in the embodiments of the present invention will be described clearly and completely with reference to the accompanying drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, 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 invention.
The invention provides a software interface checking method, wherein online refers to a service which can be accessed by a full-network user, namely, the service passes a test in a production environment, and the service in the production environment can be called an online service. In addition, in the method provided by the application, a sandbox environment is needed for verification, the sandbox environment is a production environment which can only be accessed by internal personnel, and interface problems can be found in time before the version is on line and operations such as correction and the like are carried out.
Referring to fig. 1, a flowchart of a software interface verification method according to the present application is shown;
as can be seen from fig. 1, when the method is applied to the server, the method provided by the present application includes:
s40: receiving a verification request, wherein the verification request comprises a test case of a tested interface;
in this embodiment, when checking the tested interface of the tested version of the tested software, it is necessary to perform a checking process on each tested interface, step S40 is an operation step when a certain interface is selected as the tested interface, and since one interface may correspond to a plurality of test cases, a test case corresponding to the interface should be indicated in the checking request; for the selection of the test case, the following description of the steps in the terminal application can be referred to.
S50: testing the tested interface of the online version of the tested software by using the test case in a production environment to generate a first test result; the first test result comprises a test result generated by loading the test case in a production environment;
in this embodiment, for the test case specified in the verification request, the production environment is first adopted to load and run once, and since the production environment is the application environment of the current online version, the verification method of the interface is known and is easy to call, so that the first test result is obtained without writing a new interface verification method.
Furthermore, when the tested interface in the verification request changes, as long as the interface is the interface of the current online version software, the corresponding first test result can be obtained by loading and running the test case corresponding to the interface in the production environment.
In general, since the returned data received in the production environment (online) and the sandbox environment (offline) are inconsistent, if the returned data is verified by directly using the first test result obtained after the operation in the production environment, a large amount of data is easily inconsistent, and an effective verification result cannot be obtained, so that the following data conversion step is required.
S60: converting the first test result into verification data;
in this embodiment, the data in json format is mainly used for checking the returned data in sandbox environment (offline), specifically, the first test result is converted into json chema format according to json, which may be expressed as:
if "status": true, the correspondingly generated jsonschme format is: "status": { "type": "borolen" };
therefore, the jsonschme format data can be used for checking the value or the type of the field of the status during checking, and the checking of the tested interface can be completed only by judging whether the type or the value of the field of the returned value meets the set requirement.
S70: testing the tested interface of the tested version of the tested software by using the test case in a sandbox environment to generate a second test result; the second test result comprises a test result generated by loading the test case in a sandbox environment;
before executing the step, whether the production environment passes through and the first test result is obtained or not needs to be considered while the verification request is carried out, if the first test result is obtained, the step can be executed after the first test result is converted into the verification data, and the step can also be executed while the first test result is converted into the verification data, so that the system processing efficiency is increased.
S80: and comparing the second test result with the verification data to generate a test result.
In this embodiment, the test results include a pass test and a fail test, and each interface of the tested version of the software under test can obtain its corresponding test result, and the test results for all interfaces can be collectively represented in a list or other form. For example:
| interface numbering | Test results |
| Interface A | Pass the test |
| Interface B | Pass the test |
| Interface C | Failed test |
| … | … |
| Interface N | Pass/fail test |
Further, the criterion for determining whether the interface passes the test may be a data type or a numerical value, and correspondingly, as shown in fig. 2, step S80 can be decomposed as:
s81: if the data type of the second test result is different from the data type indicated by the verification data, generating a test result for indicating that the tested interface fails the test case test;
for example, the first test result obtained by the request production environment is string type data, at this time, it is required to check whether the data in the second test result is the same as the string type data, and if the types are not the same, a test result for indicating that the tested interface fails the test case test can be directly generated, so that a subsequent judgment process can be avoided, and computational resources can be saved.
S82: and if the data type of the second test result is the same as the data type indicated by the verification data, but the numerical value of the second test result is different from the numerical value indicated by the verification data, generating a test result for indicating that the tested interface fails the test case test.
And on the premise that the data types of the two are the same, whether the data with the same numerical value exists in the second test result can be further judged, if the numerical values are different, the test result used for indicating that the tested interface fails the test case test can be directly generated, so that the subsequent judgment process can be avoided, and the operation resources are saved.
S83: and if the second test result is the same as the data type and the numerical value indicated by the verification data, generating a test result for indicating that the tested interface passes the test case test.
In this embodiment, the cause of the failed test is not limited to data comparison, and the failed test may result in failed verification due to data failure, data loss, and the like, so that the interface problem is checked and analyzed in time, and a responsible person can implement the processing scheme correctly.
S90: and if the test result indicates that the tested interface fails to pass the test of the test case, sending reminding information.
In order to enable the test result to be more intuitively and timely known, if the situation of failing to pass the test occurs, it is indicated that one or more interfaces failing the test exist in all tested interfaces in the tested version of the tested software, at this moment, early warning information is timely sent to the terminal, so that a related responsible person can know the situation at the first time through the query of the terminal, and therefore, the content of the early warning information at least comprises information such as the interface number, the interface position, the failure reason and the like of failing to pass the test.
In addition, in this embodiment, the time for sending the warning information may be set to two times: the first method can be carried out in the process of checking, namely, the interfaces to be tested are checked one by one, and once one interface fails to pass the test, early warning information is sent to a terminal immediately, so that the method has instantaneity and is convenient for related responsible persons to quickly master the position information of the interfaces; the second type can be after all interfaces accomplish the check-up, and the unified early warning information that sends is to the terminal, makes things convenient for relevant responsible person once only to collect the check-up result like this, avoids reminding many times and brings the inconvenience for relevant responsible person.
Further, the method further comprises:
s100: and when all tested interfaces in the tested version of the tested software generate test results for indicating the tested interfaces to pass the test case test, sending an online instruction to a terminal.
The above steps S40-S90 are a process of verifying an interface of the online version of the software, and for the tested version of the software to be tested, the software can be online only when all the interfaces pass the interface test, so in this embodiment, the verification operation is sequentially performed on each interface until all the interfaces are verified, and if all the interfaces generate the test result indicating that the tested interface passes the test case test, the verification of the tested version of the software is completed, and at this time, the verification process of the whole tested version can be completed.
Correspondingly, when the verification request is applied to the terminal, the terminal needs to execute the following method to generate the verification request:
s10: and acquiring an interface list of the tested version of the tested software.
S20: and establishing a set of test cases corresponding to each interface in the interface list.
Each time the software has a new version online, the interfaces providing the online service of the software usually have a plurality of interfaces, and each interface can correspond to a plurality of interface use cases, before the overall interface verification is performed, all the interfaces need to uniformly collect the result into a set containing the interface use cases by using a packet capturing tool, and in this embodiment, the interface use cases corresponding to each interface are collected and added into the set in the form of an interface list. Specifically, the interface and the terminal (for example, a mobile phone end) may be connected, data interaction is performed between the interface and the terminal by triggering an operation of the terminal (for example, the mobile phone end), a value returned by the interface providing the service is a required result, similarly, the other interfaces may also obtain the first test result respectively, and finally, all the test results are collected into the interface case set. In this embodiment, the packet capturing tool used should be considered as an agent tool for recording all operation data in the terminal and online service process, and its main function is to record and store the online service result, and the specific representation form of the tool is not limited in this application.
It should be noted that, in the present application, the main purpose of data interaction between the tested interface and the terminal is to obtain an interface list, that is, the number and type of interfaces, and corresponding interface use cases, etc.; the method for acquiring the interface list is not limited to one, and other methods may also be adopted for acquiring, such as development and provision, automatic generation of code scanning, and the like, and details of the specific method are not described herein again.
S30: selecting a test case from the set of test cases, generating a verification request of a corresponding interface and sending the verification request to a server; the generation of the verification request can be to randomly extract any one interface or randomly designate one interface, or to sequence the interfaces according to the interface list obtained in the previous step and then sequentially generate the verification request for the interfaces according to the set sequence; the verification request comprises a test case of a tested interface of a tested version of the tested software, so that the server can load the corresponding test case to a production environment or a sandbox environment according to the received verification request.
In this embodiment, the generated verification request further includes a sequence for specifying a verification process performed on a certain interface, that is, a production environment is requested first, and when the verification data in the production environment is obtained, a sandbox environment is requested.
After the server end completes the verification process according to the verification request, the terminal also needs to execute the steps of receiving, analyzing or other operations on the verification result:
s110: and receiving a test result and reminding information sent by the server.
In this step, a user (e.g., a relevant person in charge) may check the test result after the verification process is performed by the server at the terminal, for example, when the test results of all the interfaces to be tested pass the test, the user may perform an operation of confirming the online of the software to be tested or sending a relevant instruction at the terminal; if the test result of some tested interfaces is the failed test, the user can inquire the interface information, the interface problem and the like of the failed test through the terminal position so as to conveniently carry out debugging, repairing and other operations on the interfaces which fail to pass the test.
According to the technical scheme, when the method provided by the application is used for carrying out the function test on the online service version, each interface firstly requests a production environment to obtain a first test result, the first test result is converted into verification data for verification, then the same interface requests a sandbox environment to obtain sandbox data, and whether the interface passes the verification or not is determined according to the comparison result of the verification data and the sandbox data. According to the method and the device, the return data of the existing production environment of the version before online are used as the verification data of the tested version interface, and therefore a complex verification method does not need to be compiled for each interface case again, and the interface is executed according to the verification method to obtain a specific verification result, so that the time cost for compiling the verification method and running the verification method to obtain the verification result is greatly saved. In addition, when the interface is checked, the method and the device can also send early warning to the interface which does not pass the check, analyze and check the problem of the interface, and are favorable for maintenance personnel to quickly carry out interface debugging work.
Referring to fig. 3, a configuration diagram of a software interface verification apparatus provided in the present application is shown;
as can be seen from fig. 3, corresponding to the above method, the present application further provides a software interface verification apparatus, including:
the device comprises a receiving request unit 1, a verification request unit and a verification unit, wherein the receiving request unit is used for receiving a verification request which comprises a test case of a tested interface;
the first test unit 2 is used for testing the tested interface of the online version of the tested software by using the test case in a production environment to generate a first test result;
and the data conversion unit 3 is used for converting the first test result into verification data.
The second testing unit 4 is used for testing the tested interface of the tested version of the tested software by using the test case in a sandbox environment to generate a second testing result; it should be noted that the condition for starting the execution of the second testing unit 4 may be started after the first testing unit 2 obtains the first testing result (solid line in the figure), or may be started when the data conversion unit 3 completes the conversion of the verification data (dotted line in the figure).
The comparison unit 5 is used for comparing the second test result with the verification data to generate a test result;
further, the apparatus further comprises:
and the sending early warning unit 6 is used for sending reminding information when the test result indicates that the tested interface fails the test of the test case.
The interface problem analysis unit 7 is used for checking the problem of the tested interface when the tested interface fails the test; the problem of the tested interface comprises that a valid signal is not tested, or the verification data is not in accordance with the second test result;
and the information feedback unit 8 is used for sending the test result and the problem of the tested interface to the terminal.
Further, as can be seen from fig. 4, the comparing unit 5 includes:
a data type verification subunit 51, configured to compare verification data with a data type of a second test result, and if the data type of the second test result is different from the data type indicated by the verification data, generate a test result indicating that the tested interface fails the test case test;
a numerical value checking subunit 52, configured to, when the data type of the second test result is the same as the data type indicated by the check data, compare the check data with a numerical value of the second test result, and if the numerical value of the second test result is different from the numerical value indicated by the check data, generate a test result indicating that the tested interface fails the test case test; and when the second test result is the same as the data type and value indicated by the verification data, generating a test result for indicating that the tested interface passes the test case test.
Further, the apparatus further comprises:
and the summarizing unit 9 is used for sending an online instruction to the terminal when all tested interfaces in the tested version of the tested software generate test results for indicating that the tested interfaces pass the test case test.
Corresponding to the method, the application also provides a corresponding terminal of the software interface checking device, which comprises:
the list acquiring unit 10 is configured to acquire an interface list of a tested version of the software to be tested;
the integration unit 11 is configured to establish a set of test cases corresponding to each interface in the interface list;
the request sending unit 12 is configured to select a test case from the set of test cases, generate a verification request for a corresponding interface, and send the verification request to the server;
and the receiving unit 13 is used for receiving the test result and the reminding information sent by the server.
The functional role of each structural unit in the embodiment when executing the method is described in the embodiment of the method, and is not described herein again.
The present application further provides a computer device, comprising:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement a method as described.
For the computer device provided in this embodiment, the implementation effect and the function thereof may be explained with reference to other embodiments, and are not described herein again.
The application also provides a computer readable storage medium, wherein computer program instructions are stored in the computer readable storage medium and used for executing the channel package automatic batch processing method shown in the figure. The functions and effects achieved when the computer program instructions are executed can be explained with reference to other embodiments, and are not described in detail herein.
Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the invention and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.
It will be understood that the invention is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the invention is limited only by the appended claims.
Claims (10)
1. A software interface verification method, comprising:
receiving a verification request, wherein the verification request comprises a test case of a tested interface;
testing the tested interface of the online version of the tested software by using the test case in a production environment to generate a first test result;
converting the first test result into verification data;
testing the tested interface of the tested version of the tested software by using the test case in a sandbox environment to generate a second test result;
and comparing the second test result with the verification data to generate a test result.
2. The method according to claim 1, wherein the step of comparing the second test result with the verification data to generate a test result comprises:
if the data type of the second test result is different from the data type indicated by the verification data, generating a test result for indicating that the tested interface fails the test case test;
if the data type of the second test result is the same as the data type indicated by the verification data, but the numerical value of the second test result is different from the numerical value indicated by the verification data, generating a test result for indicating that the tested interface fails the test case test;
the method further comprises the following steps:
and if the test result indicates that the tested interface fails to pass the test of the test case, sending reminding information.
3. A software interface verification method according to claim 2, said method further comprising:
and if the second test result is the same as the data type and the numerical value indicated by the verification data, generating a test result for indicating that the tested interface passes the test case test.
4. A software interface verification method according to claim 3, said method further comprising:
and when all tested interfaces in the tested version of the tested software generate test results for indicating the tested interfaces to pass the test case test, sending an online instruction to a terminal.
5. A software interface verification apparatus, comprising:
the device comprises a receiving request unit, a verification request unit and a verification unit, wherein the receiving request unit is used for receiving a verification request which comprises a test case of a tested interface;
the first test unit is used for testing the tested interface of the online version of the tested software by using the test case in a production environment to generate a first test result;
the data conversion unit is used for converting the first test result into verification data;
the second testing unit is used for testing the tested interface of the tested version of the tested software by using the test case in a sandbox environment to generate a second testing result;
and the comparison unit is used for comparing the second test result with the verification data to generate a test result.
6. The apparatus according to claim 5, wherein the comparing unit comprises:
the data type checking subunit is used for comparing the checking data with the data type of a second test result, and if the data type of the second test result is different from the data type indicated by the checking data, generating a test result for indicating that the tested interface fails the test case test;
a numerical value checking subunit, configured to compare, when the data type of the second test result is the same as the data type indicated by the check data, a numerical value of the check data with a numerical value of the second test result, and if the numerical value of the second test result is different from the numerical value indicated by the check data, generate a test result indicating that the tested interface fails the test case test;
the device further comprises:
and the information feedback unit is used for sending reminding information when the test result indicates that the tested interface fails the test of the test case.
7. The software interface verification apparatus of claim 6,
the numerical value verification subunit is further configured to generate a test result for indicating that the interface under test passes the test case test when the second test result is the same as the data type and the numerical value indicated by the verification data.
8. The apparatus according to claim 7, wherein the apparatus further comprises:
and the summarizing unit is used for sending an online instruction to a terminal when all tested interfaces in the tested version of the tested software generate test results for indicating that the tested interfaces pass the test case test.
9. A computer device, characterized in that the computer device comprises:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-4.
10. A computer-readable storage medium, on which a computer program is stored, characterized in that the program is executed by a processor to implement the method according to any of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010452879.9A CN111694734A (en) | 2020-05-26 | 2020-05-26 | Software interface checking method and device and computer equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010452879.9A CN111694734A (en) | 2020-05-26 | 2020-05-26 | Software interface checking method and device and computer equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111694734A true CN111694734A (en) | 2020-09-22 |
Family
ID=72478240
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010452879.9A Pending CN111694734A (en) | 2020-05-26 | 2020-05-26 | Software interface checking method and device and computer equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111694734A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112965910A (en) * | 2021-03-19 | 2021-06-15 | 携程旅游信息技术（上海）有限公司 | Automatic regression testing method and device, electronic equipment and storage medium |
| CN113760315A (en) * | 2020-09-27 | 2021-12-07 | 北京沃东天骏信息技术有限公司 | Method and device for testing system |
| CN114417323A (en) * | 2022-01-21 | 2022-04-29 | 北京飞书科技有限公司 | Data reference method, device, equipment and medium |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120304157A1 (en) * | 2011-05-23 | 2012-11-29 | International Business Machines Corporation | Method for testing operation of software |
| CN104111885A (en) * | 2013-04-22 | 2014-10-22 | 腾讯科技（深圳）有限公司 | Method and device for verifying interface test results |
| CN106897217A (en) * | 2017-02-13 | 2017-06-27 | 北京趣拿软件科技有限公司 | Method of testing and test device |
| CN107220121A (en) * | 2017-05-25 | 2017-09-29 | 深信服科技股份有限公司 | Sandbox environment method of testing and its system under a kind of NUMA architecture |
| CN108549606A (en) * | 2018-04-16 | 2018-09-18 | 成都医云科技有限公司 | interface test method and device |
| CN110347605A (en) * | 2019-07-12 | 2019-10-18 | 北京百度网讯科技有限公司 | Method, apparatus, equipment and the storage medium for preventing software from degenerating |
| CN110633217A (en) * | 2019-09-19 | 2019-12-31 | 中国银行股份有限公司 | Interface checking method and device |
| CN110798544A (en) * | 2019-11-05 | 2020-02-14 | Oppo（重庆）智能科技有限公司 | Method and device for verifying validity of mobile terminal, terminal and storage medium |
| CN110908888A (en) * | 2018-09-17 | 2020-03-24 | 百度在线网络技术（北京）有限公司 | Server testing method and device |
-
2020
- 2020-05-26 CN CN202010452879.9A patent/CN111694734A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120304157A1 (en) * | 2011-05-23 | 2012-11-29 | International Business Machines Corporation | Method for testing operation of software |
| CN104111885A (en) * | 2013-04-22 | 2014-10-22 | 腾讯科技（深圳）有限公司 | Method and device for verifying interface test results |
| CN106897217A (en) * | 2017-02-13 | 2017-06-27 | 北京趣拿软件科技有限公司 | Method of testing and test device |
| CN107220121A (en) * | 2017-05-25 | 2017-09-29 | 深信服科技股份有限公司 | Sandbox environment method of testing and its system under a kind of NUMA architecture |
| CN108549606A (en) * | 2018-04-16 | 2018-09-18 | 成都医云科技有限公司 | interface test method and device |
| CN110908888A (en) * | 2018-09-17 | 2020-03-24 | 百度在线网络技术（北京）有限公司 | Server testing method and device |
| CN110347605A (en) * | 2019-07-12 | 2019-10-18 | 北京百度网讯科技有限公司 | Method, apparatus, equipment and the storage medium for preventing software from degenerating |
| CN110633217A (en) * | 2019-09-19 | 2019-12-31 | 中国银行股份有限公司 | Interface checking method and device |
| CN110798544A (en) * | 2019-11-05 | 2020-02-14 | Oppo（重庆）智能科技有限公司 | Method and device for verifying validity of mobile terminal, terminal and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 张善文等: "《软件测试及其案例分析》", 西安电子科技大学出版社, pages: 177 - 178 * |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113760315A (en) * | 2020-09-27 | 2021-12-07 | 北京沃东天骏信息技术有限公司 | Method and device for testing system |
| CN112965910A (en) * | 2021-03-19 | 2021-06-15 | 携程旅游信息技术（上海）有限公司 | Automatic regression testing method and device, electronic equipment and storage medium |
| CN114417323A (en) * | 2022-01-21 | 2022-04-29 | 北京飞书科技有限公司 | Data reference method, device, equipment and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107341098B (en) | Software performance testing method, platform, equipment and storage medium | |
| CN110069572B (en) | HIVE task scheduling method, device, equipment and storage medium based on big data platform | |
| CN111694734A (en) | Software interface checking method and device and computer equipment | |
| CN108521353B (en) | Processing method and device for positioning performance bottleneck and readable storage medium | |
| CN107451040B (en) | Method and device for positioning fault reason and computer readable storage medium | |
| CN111897724B (en) | Automatic testing method and device suitable for cloud platform | |
| CN112241360B (en) | Test case generation method, device, equipment and storage medium | |
| US7913233B2 (en) | Performance analyzer | |
| CN108446223B (en) | Business scene automatic testing method based on dynamic compilation | |
| CN110764998B (en) | Data comparison method, device, equipment and storage medium based on Django framework | |
| CN109885496B (en) | Test log management method and system | |
| CN112052169A (en) | Test management method, system, device and computer readable storage medium | |
| CN112395202B (en) | Interface automation test method and device, computer equipment and storage medium | |
| CN112286806A (en) | Automatic testing method and device, storage medium and electronic equipment | |
| CN111309609A (en) | Software processing system | |
| CN112269697B (en) | Equipment storage performance testing method, system and related device | |
| CN110231921B (en) | Log printing method, device, equipment and computer readable storage medium | |
| CN110928787A (en) | Automatic test script recording and playback method, device, equipment and storage medium | |
| CN111694724A (en) | Testing method and device of distributed table system, electronic equipment and storage medium | |
| CN111654553B (en) | Middleware-based management and control operation method and device, computer equipment and medium | |
| CN115525392A (en) | Container monitoring method and device, electronic equipment and storage medium | |
| CN114327981A (en) | Safety verification system, method and device of function safety mechanism | |
| CN113360389A (en) | Performance test method, device, equipment and storage medium | |
| CN108845932B (en) | Unit testing method and device of network library, storage medium and terminal | |
| CN112631929A (en) | Test case generation method and device, storage medium and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |