CN106951364B - Test method and device - Google Patents
Test method and device Download PDFInfo
- Publication number
- CN106951364B CN106951364B CN201710068554.9A CN201710068554A CN106951364B CN 106951364 B CN106951364 B CN 106951364B CN 201710068554 A CN201710068554 A CN 201710068554A CN 106951364 B CN106951364 B CN 106951364B
- Authority
- CN
- China
- Prior art keywords
- interface
- tested
- result data
- test
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/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 invention is applicable to the field of software testing and provides a testing method and a testing device. The test method comprises the following steps: acquiring the serial number and the parameters of the interface to be tested; calling a pre-established test case library based on the serial number of the interface to be tested to obtain a corresponding test case configuration file, wherein the test case library comprises the test case configuration file and expected result data; starting an interface calling tool, calling an interface corresponding to the serial number of the interface to be tested to run the test case configuration file based on the parameter of the interface to be tested, and acquiring return result data; and outputting and displaying a test result based on the expected result data and the return result data. By the method, the testing efficiency and the testing accuracy can be improved.
Description
Technical Field
The embodiment of the invention belongs to the field of software testing, and particularly relates to a testing method and a testing device.
Background
At present, data extraction interfaces are needed for testing of a plurality of terminal products, the interfaces involved in different projects are different, and the calling modes of different interfaces are also different. In the prior art, a project group developer compiles an interface to call a test tool, runs the test tool, and stores data returned by the interface in a file for the analysis of the tester. The tester analyzes and compares the received data in the file with an expected result, and judges whether the data are in accordance with the expectation.
In the prior art, on one hand, a test tool does not have a unified design specification and a unified framework, and the test tool is developed by different project groups, so that the reliability problem exists in the tool, and the test cost is additionally increased. On the other hand, automatic testing is not realized, and a manual testing method is adopted, so that the period is long, the coverage rate of testing data is low, and the testing efficiency and the accuracy rate of testing results are low.
Therefore, a new technical solution is needed to solve the above technical problems.
Disclosure of Invention
In view of this, the embodiments of the present invention provide a testing method and apparatus, which aim to solve the problem that the existing testing tools are not unified and do not implement automated testing, so that the testing efficiency and the accuracy of the testing result are low.
The embodiment of the invention is realized in such a way that a test method comprises the following steps:
starting an interface calling tool to obtain the serial number and the parameters of the interface to be tested;
calling a pre-established test case library based on the serial number of the interface to be tested to obtain a corresponding test case configuration file, wherein the test case library comprises the test case configuration file and expected result data;
calling an interface corresponding to the interface number to be tested to run the test case configuration file based on the interface parameter to be tested, and acquiring return result data;
and outputting and displaying a test result based on the expected result data and the return result data.
Another object of an embodiment of the present invention is to provide a testing apparatus, including:
the device comprises a to-be-tested interface information acquisition unit, a to-be-tested interface calling tool and a to-be-tested interface calling module, wherein the to-be-tested interface information acquisition unit is used for starting the interface calling tool and acquiring the serial number and the parameters of the to-be-tested interface of the to-be-;
a test case configuration file obtaining unit, configured to call a pre-established test case library based on the serial number of the interface to be tested, and obtain a corresponding test case configuration file, where the test case library includes the test case configuration file and expected result data;
a returned result data obtaining unit, configured to call, based on the parameter of the interface to be tested, an interface corresponding to the serial number of the interface to be tested to run the test case configuration file, and obtain returned result data;
and the result display unit is used for outputting and displaying the test result based on the expected result data and the return result data.
In the embodiment of the invention, the interface test integration and automatic test are realized by acquiring the interface number and the interface parameter of the interface to be tested, calling the pre-established test case library based on the interface number to be tested to acquire the corresponding test case configuration file, wherein the test case library comprises the test case configuration file and the expected result data, starting an interface calling tool, calling the interface corresponding to the interface number to be tested to operate the test case configuration file based on the interface parameter to be tested, acquiring the return result data, and outputting and displaying the test result based on the expected result data and the return result data, thereby improving the test efficiency and accuracy.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.
FIG. 1 is a flow chart of a testing method according to a first embodiment of the present invention;
fig. 2 is a structural diagram of a testing apparatus according to a second embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is also to be understood that the terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the specification of the present invention and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should be further understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when", "upon" or "in response to a determination" or "in response to a detection". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted contextually to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".
In order to explain the technical means of the present invention, the following description will be given by way of specific examples.
The first embodiment is as follows:
fig. 1 shows a flowchart of a testing method provided in a first embodiment of the present invention, which is detailed as follows:
and step S11, acquiring the serial number and the parameters of the interface to be tested.
The interface to be tested is an interface to be tested.
Optionally, before the step S11, to improve the test efficiency and the test accuracy, the method includes:
a1, obtaining the interface type of the appointed interface, wherein the appointed interface comprises the interface to be tested. Wherein the interface types include, but are not limited to, c/c + + dynamic libraries and webAPIs.
A2, numbering the appointed interface based on the interface type, and generating the interface number. And the interface number comprises the number of the interface to be tested.
And A3, acquiring the interface parameters of the specified interface. And the interface parameters comprise the interface parameters to be tested.
And A4, acquiring the test environment information of the specified interface. And the test environment information comprises the test environment information of the interface to be tested.
And A5, acquiring an expected test result rule of the specified interface. Wherein the expected test result rule comprises an expected test result rule of the interface to be tested.
A6, setting a test case configuration file based on the interface number, the interface parameters and the test environment information.
And A7, generating expected test result data based on the expected test result rule and the test case configuration file.
And A8, establishing a test case library based on the test case configuration file and the expected test result data.
Specifically, the interface type of the designated interface is obtained, where the designated interface may include all interfaces, may only include the interface to be tested, and may also include the interface to be tested and some interfaces in all interfaces. And numbering the designated interface according to the interface type to generate an interface number, wherein the interface number comprises the serial number of the interface to be tested. And setting a test case configuration file based on the interface number, the interface parameters and the test environment information. That is, test case configuration files of different types of interfaces are preset, and the interface numbers correspond to the test case configuration files one to one. And generating and storing expected test result data based on the expected test result rule and the test case configuration file, wherein the expected test result data also corresponds to the interface numbers one by one. And finally, establishing a test case library based on the test case configuration file and the expected test result data. Therefore, the corresponding test case configuration file can be searched and called through the interface number, and the test efficiency is improved.
The test case configuration file is set based on the interface number, the interface parameters and the test environment information, expected test result data are generated based on the expected test result rule and the test case configuration file, and finally a test case library is established based on the test case configuration file and the expected test result data, so that a tester can call the test case configuration file according to the interface number and obtain the expected test result data conveniently, and the test efficiency is improved.
Optionally, before the step S11, to improve the testing efficiency, the method includes:
and B1, acquiring the calling mode of the interface to be tested.
And B2, modifying an interface calling tool based on the calling mode, the serial number of the interface to be tested and the parameters of the interface to be tested.
Specifically, before a calling tool is started, the serial number of the interface to be tested and the parameters of the interface to be tested are input into the calling tool. Meanwhile, the calling modes of different types of interfaces are different, so that the calling mode is added into the interface calling tool by acquiring the calling mode of the interface to be tested. Optionally, the calling mode of the interface to be tested may use the serial number of the interface to be tested as an identifier.
And step S12, calling a pre-established test case library based on the serial number of the interface to be tested to obtain a corresponding test case configuration file, wherein the test case library comprises the test case configuration file and expected result data.
Specifically, based on the serial number of the interface to be tested, a pre-established test case library is called, and a test case configuration file corresponding to the serial number of the interface to be tested is obtained, so that the operation is simple, and the test efficiency is high.
Step S13, starting an interface calling tool, calling an interface corresponding to the interface number to be tested to run the test case configuration file based on the interface parameter to be tested, and acquiring return result data.
Optionally, in order to refine the test result, after the step S13, the method further includes:
c1, acquiring a format setting command;
c2, generating a test report based on the expected result data, the return result data and the format setting command.
Specifically, after a format setting command is obtained, the format of a test report is set according to the format setting command, and a test report is generated and output for a tester to refer to based on the expected result number and the returned result data.
And step S14, outputting and displaying the test result based on the expected result data and the return result data.
Optionally, the step S14 specifically includes:
d1, comparing the expected result data with the return result data.
D2, if the expected result data is consistent with the return result data, outputting a pass.
D3, if the expected result data is not consistent with the return result data, the output is failed.
Optionally, in order to make the testing personnel more clearly understand the testing result, if the expected result data is inconsistent with the returned result data, the step S14 further includes:
d4, marking the part of the expected result data inconsistent with the returned result data. The marking method includes common marking methods such as color marking and underline marking, which are not limited herein.
Optionally, in order to record the test process for the reference of the tester, in the embodiment of the present invention, the test operation process may be recorded by a log.
In the first embodiment of the present invention, an interface number is generated by obtaining an interface type of a designated interface, numbering the designated interface based on the interface type, wherein the interface number includes an interface number to be tested, obtaining an interface parameter, test environment information, and an expected test result rule of the designated interface, setting a test case configuration file based on the interface number, the interface parameter, and the test environment information, generating expected test result data based on the expected test result rule and the test case configuration file, pre-establishing a test case library based on the test case configuration file and the expected test result data, and calling the pre-established test case library to obtain a corresponding test case configuration file based on the interface number to be tested by obtaining the interface number and the interface parameter of the interface to be tested, the test case library comprises a test case configuration file and expected result data, an interface calling tool is started, an interface corresponding to the serial number of the interface to be tested is called to operate the test case configuration file based on the parameters of the interface to be tested, return result data is obtained, and finally a test result is output and displayed based on the expected result data and the return result data, so that the integration and automatic test of interface test are realized, and the test efficiency and accuracy are improved.
It should be understood that, in the embodiment of the present invention, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiment of the present invention.
Example two:
fig. 2 is a block diagram of a test apparatus according to a second embodiment of the present invention, in which only the parts related to the embodiment of the present invention are shown for convenience of explanation.
The test device includes: the device comprises an interface information acquisition unit to be tested 21, a test case configuration file acquisition unit 22, a return result data acquisition unit 23 and a result display unit 24, wherein:
the interface information acquiring unit to be tested 21 is configured to start an interface calling tool, and acquire the serial number of the interface to be tested and the parameters of the interface to be tested.
Optionally, in order to improve the testing efficiency and the testing accuracy, the testing apparatus further includes:
and the appointed interface type acquisition unit is used for acquiring the interface type of the appointed interface, and the appointed interface comprises the interface to be tested. Wherein the interface types include, but are not limited to, c/c + + dynamic libraries and webAPIs.
And the specified interface number acquisition unit is used for generating an interface number for the specified interface number based on the interface type. And the interface number comprises the number of the interface to be tested.
And the appointed interface parameter acquisition unit is used for acquiring the interface parameters of the appointed interface. And the interface parameters comprise the interface parameters to be tested.
And the appointed interface environment information acquisition unit is used for acquiring the test environment information of the appointed interface, wherein the test environment information comprises the test environment information of the interface to be tested.
And the specified interface rule obtaining unit is used for obtaining the expected test result rule of the specified interface. Wherein the expected test result rule comprises an expected test result rule of the interface to be tested.
And the setting unit is used for setting a test case configuration file based on the interface number, the interface parameters and the test environment information.
And the result generating unit is used for generating expected test result data based on the expected test result rule and the test case configuration file.
And the case base establishing unit is used for establishing a test case base based on the test case configuration file and the expected test result data.
Specifically, the interface type of the designated interface is obtained, where the designated interface may include all interfaces, may only include the interface to be tested, and may also include the interface to be tested and some interfaces in all interfaces. And numbering the designated interface according to the interface type to generate an interface number, wherein the interface number comprises the serial number of the interface to be tested. And setting a test case configuration file based on the interface number, the interface parameters and the test environment information. That is, test case configuration files of different types of interfaces are preset, and the interface numbers correspond to the test case configuration files one to one. And generating and storing expected test result data based on the expected test result rule and the test case configuration file, wherein the expected test result data also corresponds to the interface numbers one by one. And finally, establishing a test case library based on the test case configuration file and the expected test result data. Therefore, the corresponding test case configuration file can be searched and called through the interface number, and the test efficiency is improved.
The test case configuration file is set based on the interface number, the interface parameters and the test environment information, expected test result data are generated based on the expected test result rule and the test case configuration file, and finally a test case library is established based on the test case configuration file and the expected test result data, so that a tester can call the test case configuration file according to the interface number and obtain the expected test result data conveniently, and the test efficiency is improved.
Optionally, in order to improve the testing efficiency, the testing apparatus further includes:
and the calling mode acquiring unit is used for acquiring the calling mode of the interface to be tested.
And the modifying unit is used for modifying the interface calling tool based on the calling mode, the serial number of the interface to be tested and the parameter of the interface to be tested.
Specifically, before a calling tool is started, the serial number of the interface to be tested and the parameters of the interface to be tested are input into the calling tool. Meanwhile, the calling modes of different types of interfaces are different, so that the calling mode is added into the interface calling tool by acquiring the calling mode of the interface to be tested. Optionally, the calling mode of the interface to be tested may use the serial number of the interface to be tested as an identifier.
The test case configuration file obtaining unit 22 is configured to call a pre-established test case library based on the serial number of the interface to be tested, and obtain a corresponding test case configuration file, where the test case library includes the test case configuration file and expected result data.
Specifically, based on the serial number of the interface to be tested, a pre-established test case library is called, and a test case configuration file corresponding to the serial number of the interface to be tested is obtained, so that the operation is simple, and the test efficiency is high.
And the return result data obtaining unit 23 is configured to call an interface corresponding to the interface number to be tested to run the test case configuration file based on the interface parameter to be tested, and obtain return result data.
And a result display unit 24 for outputting and displaying the test result based on the expected result data and the return result data.
Optionally, the result display unit 24 specifically includes:
a comparison module for comparing the expected result data with the returned result data.
And the pass output module is used for outputting pass if the expected result data is consistent with the returned result data.
And the failure output module is used for outputting failure if the expected result data is inconsistent with the returned result data.
Optionally, in order to make the testing personnel more clearly understand the testing result, if the expected result data is inconsistent with the returned result data, the result displaying unit 24 further includes:
and the marking unit is used for marking the part of the expected result data inconsistent with the returned result data. The marking method includes common marking methods such as color marking and underline marking, which are not limited herein.
Optionally, in order to refine the test result, the apparatus further comprises:
and the format acquisition unit is used for acquiring the format setting command.
And the report generating unit is used for generating a test report based on the expected result data, the return result data and the format setting command.
Specifically, after a format setting command is obtained, the format of a test report is set according to the format setting command, and a test report is generated and output for a tester to refer to based on the expected result number and the returned result data.
Optionally, in order to record the testing process for the reference of the tester, the testing apparatus further includes:
and the recording unit is used for recording the test operation process through the log.
In the second embodiment of the present invention, an interface number is generated by obtaining an interface type of a designated interface, numbering the designated interface based on the interface type, wherein the interface number includes a serial number of an interface to be tested, obtaining interface parameters, test environment information, and expected test result rules of the designated interface, setting a test case configuration file based on the interface number, the interface parameters, and the test environment information, generating expected test result data based on the expected test result rules and the test case configuration file, pre-establishing a test case library based on the test case configuration file and the expected test result data, and calling the pre-established test case library to obtain a corresponding test case configuration file based on the serial number of the interface to be tested by obtaining the interface number and the interface parameters of the interface to be tested, the test case library comprises a test case configuration file and expected result data, an interface calling tool is started, an interface corresponding to the serial number of the interface to be tested is called to operate the test case configuration file based on the parameters of the interface to be tested, return result data is obtained, and finally a test result is output and displayed based on the expected result data and the return result data, so that the integration and automatic test of interface test are realized, and the test efficiency and accuracy are improved.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (10)
1. A method of testing, the method comprising:
acquiring the serial number and the parameters of the interface to be tested;
calling a pre-established test case library based on the serial number of the interface to be tested to obtain a corresponding test case configuration file, wherein the test case library comprises the test case configuration file and expected result data;
before starting an interface calling tool, inputting the serial number of the interface to be tested and the parameters of the interface to be tested into the interface calling tool, acquiring the calling mode of the interface to be tested, adding the calling mode into the interface calling tool, starting the interface calling tool by using the serial number of the interface to be tested as an identifier, calling the interface corresponding to the serial number of the interface to be tested to run the test case configuration file based on the parameters of the interface to be tested, and acquiring return result data, wherein the test running process is recorded by logs;
and outputting and displaying a test result based on the expected result data and the return result data.
2. The method according to claim 1, wherein before the obtaining of the serial number of the interface to be tested and the parameters of the interface to be tested, the method comprises:
acquiring an interface type of a designated interface, wherein the designated interface comprises the interface to be tested;
numbering the specified interface based on the interface type to generate an interface number;
acquiring interface parameters of the specified interface;
acquiring test environment information of the specified interface;
acquiring an expected test result rule of the specified interface;
setting a test case configuration file based on the interface number, the interface parameters and the test environment information;
generating expected test result data based on the expected test result rule and the test case configuration file;
and establishing a test case library based on the test case configuration file and the expected test result data.
3. The method according to claim 1, wherein before the obtaining of the serial number of the interface to be tested and the parameters of the interface to be tested, the method comprises:
acquiring a calling mode of an interface to be tested;
and modifying an interface calling tool based on the calling mode, the serial number of the interface to be tested and the parameters of the interface to be tested.
4. The method according to claim 1, wherein outputting and displaying test results based on the expected result data and the returned result data comprises:
comparing the expected result data with the returned result data;
if the expected result data is consistent with the returned result data, outputting the result data to pass;
and if the expected result data is inconsistent with the returned result data, outputting failure.
5. The method according to any one of claims 1 to 4, wherein after the invoking an interface corresponding to the interface number to be tested to run the test case configuration file based on the interface parameter to be tested and acquiring return result data, the method further comprises:
acquiring a format setting command;
generating a test report based on the expected result data, the returned result data, and a format setting command.
6. A test apparatus, characterized in that the test apparatus comprises:
the device comprises a to-be-tested interface information acquisition unit, a to-be-tested interface information acquisition unit and a to-be-tested interface information acquisition unit, wherein the to-be-tested interface information acquisition unit is used for acquiring the serial number and the parameters of the to-be-tested interface of the to-be;
a test case configuration file obtaining unit, configured to call a pre-established test case library based on the serial number of the interface to be tested, and obtain a corresponding test case configuration file, where the test case library includes the test case configuration file and expected result data;
a return result data obtaining unit, configured to, before starting an interface calling tool, input the serial number of the interface to be tested and the parameter of the interface to be tested into the interface calling tool, obtain a calling mode of the interface to be tested, add the calling mode into the interface calling tool, start the interface calling tool by using the serial number of the interface to be tested as an identifier for the calling mode of the interface to be tested, call an interface corresponding to the serial number of the interface to be tested to run the test case configuration file based on the parameter of the interface to be tested, and obtain return result data, where a test running process is recorded by a log;
and the result display unit is used for outputting and displaying the test result based on the expected result data and the return result data.
7. The apparatus of claim 6, wherein the testing apparatus further comprises:
the specified interface type obtaining unit is used for obtaining the interface type of a specified interface, and the specified interface comprises the interface to be tested;
the specified interface number acquisition unit is used for numbering the specified interface based on the interface type and generating an interface number;
a designated interface parameter obtaining unit, configured to obtain an interface parameter of the designated interface;
the system comprises an appointed interface environment information acquisition unit, a test environment information acquisition unit and a test environment information acquisition unit, wherein the appointed interface environment information acquisition unit is used for acquiring the test environment information of an appointed interface;
the specified interface rule obtaining unit is used for obtaining an expected test result rule of the specified interface;
the setting unit is used for setting a test case configuration file based on the interface number, the interface parameters and the test environment information;
a result generating unit, configured to generate expected test result data based on the expected test result rule and the test case configuration file;
and the case base establishing unit is used for establishing a test case base based on the test case configuration file and the expected test result data.
8. The apparatus of claim 6, wherein the testing apparatus further comprises:
the calling mode acquiring unit is used for acquiring the calling mode of the interface to be tested;
and the modifying unit is used for modifying the interface calling tool based on the calling mode, the serial number of the interface to be tested and the parameter of the interface to be tested.
9. The apparatus according to claim 6, wherein the result display unit specifically comprises:
a comparison module for comparing the expected result data with the returned result data;
the pass output module is used for outputting pass if the expected result data is consistent with the returned result data;
and the failure output module is used for outputting failure if the expected result data is inconsistent with the returned result data.
10. The apparatus of any one of claims 6 to 9, further comprising:
a format acquisition unit for acquiring a format setting command;
and the report generating unit is used for generating a test report based on the expected result data, the return result data and the format setting command.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710068554.9A CN106951364B (en) | 2017-02-08 | 2017-02-08 | Test method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710068554.9A CN106951364B (en) | 2017-02-08 | 2017-02-08 | Test method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106951364A CN106951364A (en) | 2017-07-14 |
| CN106951364B true CN106951364B (en) | 2020-05-12 |
Family
ID=59465454
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710068554.9A Active CN106951364B (en) | 2017-02-08 | 2017-02-08 | Test method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106951364B (en) |
Families Citing this family (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107908540B (en) * | 2017-07-26 | 2021-04-06 | 平安壹钱包电子商务有限公司 | Test case creating method and device, computer equipment and medium |
| CN107592238B (en) * | 2017-08-07 | 2021-05-28 | 千寻位置网络有限公司 | Automatic test method and system of interface, service terminal and memory |
| CN107807869A (en) * | 2017-10-16 | 2018-03-16 | 微梦创科网络科技（中国）有限公司 | A kind of test system and method for testing |
| CN107766190B (en) * | 2017-10-31 | 2020-06-12 | 平安科技（深圳）有限公司 | Interface testing method and device, computer equipment and storage medium |
| CN109871312B (en) * | 2017-12-05 | 2022-08-12 | 航天信息股份有限公司 | Interface testing method, device, equipment and readable storage medium |
| CN107977317A (en) * | 2017-12-22 | 2018-05-01 | 上海庆科信息技术有限公司 | A kind of test method of data network, system and relevant apparatus |
| CN109117368A (en) * | 2018-07-27 | 2019-01-01 | 平安科技（深圳）有限公司 | A kind of interface test method, electronic equipment and storage medium |
| CN109032956B (en) * | 2018-09-11 | 2022-03-22 | 郑州云海信息技术有限公司 | Interface testing method and device |
| CN109408370A (en) * | 2018-09-18 | 2019-03-01 | 深圳壹账通智能科技有限公司 | Interface testing document generating method, device, computer equipment and storage medium |
| CN111198810A (en) * | 2018-11-16 | 2020-05-26 | 鸿合科技股份有限公司 | Software testing method and device and electronic equipment |
| CN109828904A (en) * | 2018-12-14 | 2019-05-31 | 深圳壹账通智能科技有限公司 | System Authentication method, device, electronic equipment and storage medium |
| CN109766231A (en) * | 2019-01-11 | 2019-05-17 | 未来电视有限公司 | Interface test method and device |
| CN110162979A (en) * | 2019-05-27 | 2019-08-23 | 北京百度网讯科技有限公司 | A kind of safety detecting method, device, electronic equipment and the storage medium of Web API |
| CN110287113A (en) * | 2019-06-25 | 2019-09-27 | 四川长虹电器股份有限公司 | Automation interface test method |
| CN110928777B (en) * | 2019-11-15 | 2023-04-07 | 深圳前海微众银行股份有限公司 | Test case processing method, device, equipment and storage medium |
| CN110941519B (en) * | 2019-12-17 | 2022-12-13 | 锐捷网络股份有限公司 | Chip testing method and device of network equipment |
| CN111401955A (en) * | 2020-03-16 | 2020-07-10 | 畅捷通信息技术股份有限公司 | Price and amount algorithm verification system, method, device and storage medium |
| CN113806209A (en) * | 2020-06-16 | 2021-12-17 | 腾讯科技（深圳）有限公司 | Interface testing method, frame, computer device and storage medium |
| CN112362360B (en) * | 2020-11-10 | 2023-03-31 | 广州小鹏汽车科技有限公司 | Vehicle component testing method, device and system, test board card and storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101212357A (en) * | 2006-12-31 | 2008-07-02 | 亿阳信通股份有限公司 | Interface testing method and device |
| CN105897497A (en) * | 2015-07-20 | 2016-08-24 | 广州华多网络科技有限公司 | Interface test method, application device and service device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9424167B2 (en) * | 2014-05-21 | 2016-08-23 | Cgi Technologies And Solutions Inc. | Automated testing of an application system |
-
2017
- 2017-02-08 CN CN201710068554.9A patent/CN106951364B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101212357A (en) * | 2006-12-31 | 2008-07-02 | 亿阳信通股份有限公司 | Interface testing method and device |
| CN105897497A (en) * | 2015-07-20 | 2016-08-24 | 广州华多网络科技有限公司 | Interface test method, application device and service device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106951364A (en) | 2017-07-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106951364B (en) | Test method and device | |
| CN105787364B (en) | Automatic testing method, device and system for tasks | |
| CN111181805B (en) | Micro-service test baffle generation method and system based on test case | |
| WO2018195795A1 (en) | Test method, test server, and system | |
| CN114546738A (en) | Server general test method, system, terminal and storage medium | |
| CN106557308A (en) | A kind of software continuous integrated approach and device | |
| CN105630656A (en) | Log model based system robustness analysis method and apparatus | |
| CN114141302A (en) | Test method of solid state disk and electronic equipment | |
| CN108595332B (en) | Software testing method and device | |
| CN106294109B (en) | Method and device for acquiring defect code | |
| CN112416735A (en) | Application program detection method and device, terminal equipment and storage medium | |
| CN113590498B (en) | Method and system for testing application starting time of desktop operating system | |
| CN110866492B (en) | Baseline branch identification method and device and computer system | |
| CN114661586A (en) | Embedded computer software testing method | |
| CN113821389A (en) | Method, device and equipment for testing performance of solid state disk and readable storage medium | |
| CN113591147A (en) | Data extraction method and device, computer equipment and storage medium | |
| CN111722886A (en) | Tool starting method and device, computer equipment and computer readable storage medium | |
| CN114860549B (en) | Buried data verification method, buried data verification device, buried data verification equipment and storage medium | |
| CN112115046B (en) | Software fault positioning method, device and terminal | |
| CN111309598A (en) | Test case execution environment recovery method, system, terminal and storage medium | |
| CN110109809B (en) | Method and equipment for testing log auditing function according to syslog | |
| CN117370203B (en) | Automatic test method, system, electronic equipment and storage medium | |
| CN114816876B (en) | Automatic test system for server Redfish interface specifications | |
| CN117453567A (en) | Chaos testing method, device and equipment | |
| CN114138635A (en) | Automatic test script generation method and device |
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: 518000 12th Floor, Building A4, Nanshan Zhiyuan, 1001 Xueyuan Avenue, Nanshan District, Shenzhen City, Guangdong Province Applicant after: Shenzhen Guotaian Educational Technology Co., Ltd. Address before: 518000 Checkpoint, Nantou, Shenzhen, Guangdong Province, 30 Building 3, Zhiheng Industrial Park, Gate 2, Nanshan District, Shenzhen Applicant before: GTA INFORMATION TECHNOLOGY CO., LTD. (GTA) |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20211221 Address after: 518000 Room 201, building A, No. 1, Qian Wan Road, Qianhai Shenzhen Hong Kong cooperation zone, Shenzhen, Guangdong (Shenzhen Qianhai business secretary Co., Ltd.) Patentee after: Shenzhen guotengan Vocational Education Technology Co.,Ltd. Address before: 518000 12th Floor, Building A4, Nanshan Zhiyuan, 1001 Xueyuan Avenue, Nanshan District, Shenzhen City, Guangdong Province Patentee before: SHENZHEN GTA EDUCATION TECH Ltd. |