CN107844421B - Interface testing method and device, computer equipment and storage medium - Google Patents
Interface testing method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN107844421B CN107844421B CN201711044187.5A CN201711044187A CN107844421B CN 107844421 B CN107844421 B CN 107844421B CN 201711044187 A CN201711044187 A CN 201711044187A CN 107844421 B CN107844421 B CN 107844421B
- Authority
- CN
- China
- Prior art keywords
- interface
- test
- tested
- case
- 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/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)
- Debugging And Monitoring (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention relates to an interface testing method, an interface testing device, computer equipment and a storage medium, wherein the method comprises the following steps: acquiring an interface test instruction; inquiring precondition information associated with a test case identifier in the interface test instruction; acquiring to-be-tested case parameter information corresponding to the test case identification according to the precondition information; acquiring a to-be-tested case template and to-be-tested interface communication parameters corresponding to the test case identification from a test case library; generating a test case of the interface to be tested according to the parameter information of the case to be tested and the template of the case to be tested; and testing the interface to be tested corresponding to the address of the interface to be tested in the test case of the interface to be tested according to the test case of the interface to be tested and the communication parameters of the interface to be tested. Only the test case identification is associated with the precondition information, so that the test efficiency of automatically testing the interface to be tested according to the test case is improved.
Description
Technical Field
The present invention relates to the field of test technologies, and in particular, to an interface test method and apparatus, a computer device, and a storage medium.
Background
At present, with the development of computer technology and the enrichment of services in different fields (such as financial transaction field), the demand for automated testing of complex systems is increasing. The general test method is mainly realized by developing a test tool, and the existing test tool is mainly divided into a commercial test tool, an open source test framework and a lightweight test script compiled by a tester from the technical architecture; from the functional point of view, the test system is mainly divided into a function test tool, a performance test tool, a safety test tool and the like; from the viewpoint of an operation platform, the operation platform is mainly divided into a Windows-based operation system, a Unix/Linux-based operation system and the like; from the perspective of the system under test, for example, the system under test is classified into a Web test tool, a message test tool, and the like.
However, in the test process, sometimes when a certain interface is tested, parameters of the associated interface need to be acquired, and the interface can be tested according to the acquired parameters, so when a test case of the interface is programmed, the test case content of the associated interface needs to be written into the test case content of the interface. Therefore, the content of some test cases is easily repeatedly absorbed into different test cases, so that more time is consumed for writing the test cases, and the interface test efficiency is reduced.
Disclosure of Invention
In view of the above, it is necessary to provide an interface testing method, an interface testing apparatus, a computer device, and a storage medium, for solving the problem of inefficient interface testing.
An interface testing method, the method comprising:
acquiring an interface test instruction;
inquiring precondition information associated with a test case identifier in the interface test instruction;
acquiring to-be-tested case parameter information corresponding to the test case identification according to the precondition information;
acquiring a to-be-tested case template and to-be-tested interface communication parameters corresponding to the test case identification from a test case library;
generating a test case of the interface to be tested according to the parameter information of the case to be tested and the template of the case to be tested;
and testing the interface to be tested corresponding to the address of the interface to be tested in the interface test case to be tested according to the interface test case to be tested and the communication parameters of the interface to be tested.
An interface testing apparatus, the apparatus comprising:
the test instruction acquisition module is used for acquiring an interface test instruction;
the prepositive condition query module is used for querying prepositive condition information associated with the test case identification in the interface test instruction;
the parameter information acquisition module is used for acquiring the parameter information of the to-be-tested case corresponding to the test case identifier according to the precondition information;
the case module acquisition module is used for acquiring a case template to be tested and communication parameters of an interface to be tested, which correspond to the test case identification, from a test case library;
the test case generation module is used for generating a test case of the interface to be tested according to the parameter information of the case to be tested and the case template to be tested;
and the interface test module to be tested is used for testing the interface to be tested corresponding to the address of the interface to be tested in the interface test case to be tested according to the interface test case to be tested and the communication parameters of the interface to be tested.
A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the interface testing method provided in any embodiment of the invention when executing the computer program.
A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the interface testing method provided in any of the embodiments of the present invention.
According to the interface testing method, the interface testing device, the computer equipment and the storage medium, in the interface testing process, before the test case corresponding to the test case identification is executed, the parameter information of the case to be tested is obtained according to the precondition information, the test case of the interface to be tested is generated according to the obtained parameter information of the case to be tested and the case template to be tested, and the interface to be tested is tested according to the test case of the interface to be tested and the communication parameters of the interface to be tested. Test case contents of other interfaces associated with the interface to be tested are not required to be written into the test case of the interface to be tested, and only the test case identification is associated with the precondition information, so that time consumed by repeatedly compiling the test case contents is saved, and the test efficiency of automatically testing the interface to be tested according to the test case is improved.
Drawings
FIG. 1 is a diagram of an application environment of a method for interface testing in one embodiment;
FIG. 2 is a flow chart illustrating a method for testing an interface according to an embodiment;
FIG. 3 is a flowchart illustrating steps in generating interface test instructions according to one embodiment;
FIG. 4 is a flowchart illustrating steps for executing pre-test cases in one embodiment;
FIG. 5 is a flowchart illustrating steps of obtaining parameter information of a case to be tested in one embodiment;
FIG. 6 is a flowchart illustrating steps for testing an interface under test in one embodiment;
FIG. 7 is a block diagram showing the structure of an interface test apparatus according to an embodiment;
FIG. 8 is a block diagram showing the structure of an interface test apparatus according to an embodiment;
FIG. 9 is a block diagram of a parameter information obtaining module according to an embodiment;
FIG. 10 is a block diagram of a server in the interface test system in one embodiment.
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.
FIG. 1 is a diagram of an exemplary implementation of a method for testing an interface. Referring to fig. 1, the interface test method is applied to an interface test system. The interface test system includes a terminal 110 and a server 120, wherein the terminal 110 is connected to the server 120 through a network. The terminal 110 may be a fixed terminal, which may specifically be at least one of a printer, a scanner, and a monitor, or a mobile terminal, which may specifically be at least one of a tablet, a smartphone, a personal data assistant, and a digital camera.
As shown in fig. 2, in an embodiment, an interface testing method is provided, which is exemplified by applying the method to the server 120 in fig. 1, and the method specifically includes the following steps:
s202, obtaining an interface test instruction.
Specifically, an interface test configuration page is displayed in the terminal 110, a user can input test case configuration information in the interface test configuration page, and the user clicks a configuration completion button in the interface test configuration page through an input device of the terminal 110. When detecting that the configuration completion button in the interface test configuration page is clicked, the terminal 110 acquires the test case configuration information input in the interface test configuration page, and generates an interface test instruction according to the test case configuration information. The test case configuration information includes test case identifiers, and the extracted test case identifiers may be one or more. The terminal 110 transmits the generated interface test instruction to the server 120.
S204, inquiring precondition information associated with the test case identification in the interface test instruction.
The server 120 is provided with a test case library, and the test case library stores a test case template, interface communication parameters, and precondition information. The test case template is a template for generating a test case; the communication parameters corresponding to the interface to be tested of the interface communication parameters may specifically include at least one of an interface communication protocol type, an interface communication mode and a data transmission format; the precondition information is information or parameters required before executing the current test case. The user may configure the associated preconditions information for the test case identification in the interface test configuration page via an input device of terminal 110. The server 120 may store the precondition identifiers of the precondition information associated with the test case identifiers in the test cases.
Specifically, after obtaining the interface test instruction, the server 120 analyzes the interface test instruction, extracts a test case identifier in the interface test instruction through analysis, and queries whether associated preconditioned information exists in the test case library according to the extracted test case identifier.
In an embodiment, the server 120 queries whether a precondition identifier corresponding to the extracted test case identifier exists, and if the precondition identifier corresponding to the extracted test case identifier is queried, it indicates that associated precondition information exists; and if the precondition identifier corresponding to the extracted test case identifier is not inquired, indicating that no associated precondition information exists.
And S206, acquiring the parameter information of the to-be-tested case corresponding to the test case identifier according to the precondition information.
Specifically, the precondition information includes parameter information of the to-be-tested case corresponding to the extracted test case identifier. When the server 120 queries the precondition information corresponding to the extracted test case identifier, the precondition is analyzed, and the case parameter information to be tested, which is drunk by the test case identifier, is extracted.
In one embodiment, the server 120 queries the preconditioned information according to the queried preconditioned identifier when querying the preconditioned identifier corresponding to the extracted test case identifier, and extracts the data query condition in the preconditioned information. The data query condition comprises a data identifier and a database address. The server 120 establishes database connection according to the database address in the data query condition, queries data corresponding to the data identifier from the database according to the database connection, and takes the queried data as the parameter information of the to-be-tested case corresponding to the test case identifier.
And S208, acquiring the to-be-tested case template and the to-be-tested interface communication parameters corresponding to the test case identification from the test case library.
Specifically, after extracting the test case identifier from the interface test instruction, the server 120 queries, in the test case library, the to-be-tested case template and the to-be-tested interface communication parameter corresponding to the extracted test case identifier.
In one embodiment, the server 120 queries a to-be-tested case template corresponding to the extracted test case identifier in the test case library, extracts the communication parameter identifier from the to-be-tested case template, and queries the interface communication parameter in the test case according to the extracted communication parameter identifier.
S210, generating a test case of the interface to be tested according to the parameter information of the case to be tested and the template of the case to be tested.
Specifically, the test case of the interface to be tested is a test case for testing the interface to be tested. The case parameter information to be tested comprises request parameter information, return parameter information and an expected test result, and the case template to be tested is test scene information. And the server 120 merges the parameter information of the case to be tested and the template of the case to be tested, and obtains the test case corresponding to the test case identifier through merging.
In an embodiment, when there are multiple extracted test case identifiers, the server 120 obtains parameter information of a to-be-tested case according to the precondition information associated with each test case identifier, obtains a to-be-tested case template corresponding to each test case identifier from the test case library, and generates to-be-tested interface test cases respectively corresponding to each test case identifier according to the to-be-tested case parameter corresponding to each test case identifier and the to-be-tested case template.
S212, testing the interface to be tested corresponding to the address of the interface to be tested in the test case of the interface to be tested according to the test case of the interface to be tested and the communication parameters of the interface to be tested.
Specifically, the server 120 extracts test information and an address of the interface to be tested in the test case of the interface to be tested, encapsulates the extracted test information according to the communication parameters of the interface to be tested, and sends the encapsulated test information to the interface to be tested corresponding to the extracted address of the interface to be tested, so as to test the interface to be tested according to the encapsulated test information.
In an embodiment, the server 120 extracts the test information and the address of the interface to be tested in the test case of the interface to be tested, generates a test request of the interface to be tested according to the communication parameters of the interface to be tested and the extracted test information, and sends the test request of the interface to be tested to the interface to be tested corresponding to the extracted address of the interface to be tested to test the interface to be tested.
In this embodiment, in the interface test process, before executing the test case corresponding to the test case identifier, obtaining parameter information of the case to be tested according to the precondition information, generating the test case of the interface to be tested according to the obtained parameter information of the case to be tested and the case template to be tested, and testing the interface to be tested according to the test case of the interface to be tested and the communication parameters of the interface to be tested. Test case contents of other interfaces associated with the interface to be tested are not required to be written into the test case of the interface to be tested, and only the test case identification is associated with the precondition information, so that time consumed by repeatedly compiling the test case contents is saved, and the test efficiency of automatically testing the interface to be tested according to the test case is improved.
As shown in fig. 3, in an embodiment, before S202, a step of generating an interface test instruction is specifically included, where the step specifically includes the following steps:
s302, the test starting time in the test plan information is monitored.
The test plan information is input test plan information in an interface test configuration page displayed by the terminal 110 through an input device of the terminal 110. The terminal 110 transmits the input test plan information to the server 120. The server 120 may store the test plan information transmitted by the terminal 110 in a test case library. The test plan information comprises test execution time and a test case identification set, wherein the test execution time comprises test starting time and test ending time; the test case identification set comprises at least one test case identification.
Specifically, the test case library of the server 120 stores test plan information, where the test plan information includes test execution time, test cycle number, and a test case identifier set. The server 120 obtains the test execution time in the test plan information, extracts the test start time from the test execution time, and monitors whether the current time is equal to the test start time.
In one embodiment, the test case library includes a plurality of test plan information. The server 120 periodically acquires the current time, and compares the acquired current time with the test start time in each piece of test plan information to monitor whether the current time is the same as the test start time.
S304, when the current time is the same as the test starting time, extracting the test case identification corresponding to the test starting time from the test plan information.
Specifically, when monitoring that the current time is the same as the test start time, the server 120 reads the test case identifier set from the test plan information corresponding to the test start time, and extracts the test case identifiers in the test case identifier set.
And S306, generating a test instruction of the interface to be tested according to the extracted test case identification.
Specifically, after the server 120 extracts the test case identifier, the extracted test case identifier is packaged, and the test instruction of the interface to be tested is generated through the packaging.
In the embodiment, by monitoring the test starting time in each piece of test plan information, when the current time is monitored to be equal to the test starting time, the interface test instruction is generated according to the test plan information corresponding to the test starting time, the interface test instruction does not need to be triggered manually, and the intervention of manual operation is reduced. And the corresponding interface test instruction can be generated according to the test plan information, so that the convenience of generating the interface test instruction is improved.
As shown in fig. 4, in an embodiment, the S206 specifically includes a step of executing a pre-test case, where the step specifically includes the following steps:
s402, acquiring preposed case generation information, a preposed case template and a preposed interface communication parameter corresponding to the preposed condition information from the test case library.
Specifically, the preposed use case generation information, the preposed use case template, the preposed interface communication parameter and the preposed condition information are correspondingly stored in the test use case library. After querying the precondition information corresponding to the extracted test case identifier, the server 120 queries the precondition generation information, the precondition template, and the precondition communication parameters corresponding to the precondition information from the test case library.
In one embodiment, the server 120 extracts the preamble generation information and the preamble template identifier from the preamble information, queries a preamble template corresponding to the extracted preamble template identifier in the test case library, extracts the interface parameter identifier from the preamble template, and queries a preamble communication parameter corresponding to the interface parameter identifier in the test case library.
S404, generating a preposed test case according to the preposed case generating information and the preposed case template.
Specifically, the pre-case generation information includes pre-request parameter information, pre-return parameter information, and a pre-expected test result, and the pre-case template is pre-scenario information. The server 120 merges the pre-case generating information and the pre-case template, and obtains the pre-test case through merging.
S406, executing the preposed test case according to the communication parameters of the preposed interface to obtain the parameter information of the case to be tested corresponding to the test case identification.
Specifically, the server 120 extracts a pre-interface address in the pre-test case, packages the pre-test case according to the communication parameters of the pre-interface, sends the packaged pre-test case to the pre-interface according to the pre-interface address, enables the pre-interface to execute the pre-test case, and generates the parameter information of the case to be tested corresponding to the test case identifier according to the pre-test case. And the server 120 interface is used for returning the parameter information of the use case to be tested.
In the embodiment, when the associated precondition information is queried, the precondition test case is generated according to the precondition information, the pre-interface is tested according to the generated precondition test case, the test case parameter information corresponding to the test case identifier returned by the precondition test case by the pre-interface is obtained, and the accuracy of the case parameters to be tested is ensured.
As shown in fig. 5, in an embodiment, the step S406 specifically includes a step of obtaining parameter information of a use case to be tested, and the step specifically includes the following steps:
s502, testing the front interface corresponding to the front interface address in the front test case according to the front test case and the communication parameters of the front interface, and acquiring the parameter information returned by the front interface.
Specifically, the server 120 extracts a pre-interface address in the pre-test case, extracts an interface communication protocol type, an interface communication mode and an interface data transmission format in the pre-interface communication parameters, and encapsulates the pre-test case according to the extracted interface communication protocol type, interface communication mode and interface data transmission format to obtain a pre-interface test request. The server 120 sends the pre-interface test request to the pre-interface address, and the interface pre-interface returns the parameter information according to the pre-interface test request.
S504, whether the precondition information has the data query condition is detected.
Specifically, the data query condition includes a database address, a data identification, and a data query statement. The precondition information may also include a data query condition. The server 120 determines whether a data query condition exists through the data query identification in the precondition information.
S506, if the data query condition is detected to exist in the precondition information, querying data from the database according to the data query condition.
Specifically, the server 120 extracts the data query condition from the precondition information when detecting that the data query condition exists in the precondition information. The server 120 establishes a connection with the database according to the database address in the data query condition, and queries data corresponding to the data identifier from the database through the connection according to the data query statement.
And S508, taking the acquired parameter information and the inquired data as the parameter information of the to-be-tested case corresponding to the test case identifier.
Specifically, after the server 120 obtains the parameter information returned by the front interface and the data queried from the database, the obtained parameter information and the queried data are merged into the to-be-tested case parameter information corresponding to the test case identifier.
In this embodiment, after the parameter informatics returned by the front interface is acquired, data can be queried from the database according to the data query condition in the front condition information, and the to-be-tested case parameter information corresponding to the test case identifier is generated according to the acquired parameter information and the queried data, so that the acquisition efficiency of the to-be-tested case parameter information is improved.
As shown in fig. 6, in an embodiment, the step S212 specifically includes a step of testing the interface to be tested, where the step specifically includes the following steps:
s602, extracting the interface communication protocol type, the interface communication mode and the interface data transmission format in the interface communication parameters to be detected.
The interface communication parameters to be tested comprise an interface communication protocol type, an interface communication mode and an interface data transmission format. The interface communication protocol type is a communication protocol supported by the interface to be tested; the interface communication mode is a communication protocol supported by the interface to be tested; the interface data transmission format is a data transmission format which can be analyzed and supported by the interface to be tested.
Specifically, the server 120 parses the interface communication parameters to be tested, and extracts the interface communication protocol type, the interface communication mode, and the interface data transmission format from the interface communication parameters through parsing.
S604, generating a test request of the interface to be tested according to the interface communication protocol type, the interface communication mode, the interface data transmission format and the test case of the interface to be tested.
Specifically, the server 120 encapsulates the test case of the interface to be tested according to the extracted interface communication protocol type, interface communication mode and interface data transmission format, and encapsulates the test case to obtain the test request of the interface to be tested supported by the interface to be tested.
S606, testing the interface to be tested corresponding to the interface address to be tested in the interface to be tested test case according to the interface to be tested test request.
Specifically, the test case of the interface to be tested includes an address of the interface to be tested, and the address of the interface to be tested is the unique identifier of the interface to be tested. The server 120 extracts the address of the interface to be tested from the test case of the interface to be tested, and sends the test request of the interface to be tested to the interface to be tested according to the address of the interface to be tested, so as to test the interface to be tested.
In the embodiment, the compiling of the test case of the interface to be tested according to the interface type of the interface to be tested is not required to be considered, the test case of the interface to be tested is directly packaged according to the interface communication protocol type, the interface communication mode and the interface data transmission format in the communication parameters of the interface to be tested, the test request of the interface to be tested supported by the interface to be tested is generated, and the success rate of testing the interface to be tested according to the test request of the interface to be tested is ensured.
As shown in fig. 7, in one embodiment, an interface testing apparatus 700 is provided, which specifically includes the following: a test instruction obtaining module 702, a precondition query module 704, a parameter information obtaining module 706, a case module obtaining module 708, a test case generating module 710, and an interface to be tested testing module 712.
A test instruction obtaining module 702, configured to obtain an interface test instruction.
The precondition query module 704 is configured to query precondition information associated with a test case identifier in the interface test instruction.
The parameter information obtaining module 706 is configured to obtain parameter information of the to-be-tested case corresponding to the test case identifier according to the precondition information.
The case module obtaining module 708 is configured to obtain, from the test case library, a case template to be tested and communication parameters of the interface to be tested, where the case template to be tested corresponds to the test case identifier.
And the test case generating module 710 is configured to generate a test case of the interface to be tested according to the parameter information of the case to be tested and the case template to be tested.
The interface to be tested test module 712 is configured to test an interface to be tested corresponding to an interface address to be tested in the interface to be tested test case according to the interface to be tested test case and the communication parameters of the interface to be tested.
In this embodiment, in the interface test process, before executing the test case corresponding to the test case identifier, obtaining parameter information of the case to be tested according to the precondition information, generating the test case of the interface to be tested according to the obtained parameter information of the case to be tested and the case template to be tested, and testing the interface to be tested according to the test case of the interface to be tested and the communication parameters of the interface to be tested. Test case contents of other interfaces associated with the interface to be tested are not required to be written into the test case of the interface to be tested, and only the test case identification is associated with the precondition information, so that time consumed by repeatedly compiling the test case contents is saved, and the test efficiency of automatically testing the interface to be tested according to the test case is improved.
As shown in fig. 8, in an embodiment, the test case library includes a plurality of pieces of test plan information, and the test instruction obtaining module 702 specifically includes the following contents: a test plan monitoring module 714, a use case identification extraction module 716 and a test instruction generation module 718.
And a test plan monitoring module 714 for monitoring the test start time in the test plan information.
A case identifier extracting module 716, configured to extract a test case identifier corresponding to the test start time from the test plan information when it is monitored that the current time is the same as the test start time.
The test instruction generating module 718 is configured to generate a test instruction of the interface to be tested according to the extracted test case identifier.
In the embodiment, by monitoring the test starting time in each piece of test plan information, when the current time is monitored to be equal to the test starting time, the interface test instruction is generated according to the test plan information corresponding to the test starting time, the interface test instruction does not need to be triggered manually, and the intervention of manual operation is reduced. And the corresponding interface test instruction can be generated according to the test plan information, so that the convenience of generating the interface test instruction is improved.
As shown in fig. 9, in an embodiment, the parameter information obtaining module 706 specifically includes the following contents: a preposition information query module 706a, a preposition use case generation module 706b and a use case parameter obtaining module 706 c.
The preposition information query module 706a is used for acquiring preposition case generation information, a preposition case template and a preposition interface communication parameter corresponding to the preposition condition information from the test case library.
And the preposed use case generating module 706b is used for generating a preposed test case according to the preposed use case generating information and the preposed use case template.
The case parameter obtaining module 706c is configured to execute the pre-test case according to the communication parameter of the pre-interface, so as to obtain parameter information of the case to be tested corresponding to the test case identifier.
In the embodiment, when the associated precondition information is queried, the precondition test case is generated according to the precondition information, the pre-interface is tested according to the generated precondition test case, the test case parameter information corresponding to the test case identifier returned by the precondition test case by the pre-interface is obtained, and the accuracy of the case parameters to be tested is ensured.
In an embodiment, the use case parameter obtaining module 706c is further configured to test a pre-interface corresponding to a pre-interface address in the pre-test case according to the pre-test case and the communication parameters of the pre-interface, and obtain parameter information returned by the pre-interface; detecting whether a data query condition exists in the precondition information; if the precondition information is detected to have a data query condition, querying data from a database according to the data query condition; and taking the obtained parameter information and the inquired data as the parameter information of the to-be-tested case corresponding to the test case identification.
In this embodiment, after the parameter informatics returned by the front interface is acquired, data can be queried from the database according to the data query condition in the front condition information, and the to-be-tested case parameter information corresponding to the test case identifier is generated according to the acquired parameter information and the queried data, so that the acquisition efficiency of the to-be-tested case parameter information is improved.
In one embodiment, the interface-to-be-tested test module 712 is further configured to extract an interface communication protocol type, an interface communication mode, and an interface data transmission format from the interface communication parameters to be tested; generating a test request of the interface to be tested according to the type of the interface communication protocol, the interface communication mode, the interface data transmission format and the test case of the interface to be tested; and testing the interface to be tested corresponding to the address of the interface to be tested in the test case of the interface to be tested according to the test request of the interface to be tested.
In the embodiment, the compiling of the test case of the interface to be tested according to the interface type of the interface to be tested is not required to be considered, the test case of the interface to be tested is directly packaged according to the interface communication protocol type, the interface communication mode and the interface data transmission format in the communication parameters of the interface to be tested, the test request of the interface to be tested supported by the interface to be tested is generated, and the success rate of testing the interface to be tested according to the test request of the interface to be tested is ensured.
Fig. 10 is a schematic diagram illustrating an internal structure of the server 120 in the interface test system of fig. 1 according to an embodiment. As shown in fig. 10, the server 120 includes a processor, a memory, and a network interface connected by a system bus. The processor of the server 120 is used to provide computing and control capabilities, to support the operation of the entire server 120, the memory is used to store data, code instructions, etc., and the network interface is used to communicate with the terminal 110 over a network. The memory has at least one computer program stored thereon, which can be executed by the processor to implement the interface testing method provided in the embodiment of the present application and applied to the server 120. The Memory may include non-volatile storage media such as magnetic disks, optical disks, Read-Only memories (ROMs), and the like. For example, in one embodiment, the memory includes a non-volatile storage medium and an internal memory; the nonvolatile storage medium stores an operating system, a database and a computer program, wherein the database is provided with a test case library, and the computer program can be executed by a processor to realize the interface test method; the internal memory provides a cached execution environment for the operating system and computer-executable instructions in the non-volatile storage medium.
Embodiments of the present invention provide a computer device, which includes a series of computer programs stored in a memory, and when the computer programs are executed by a processor, the interface testing method provided in the embodiments of the present invention can be implemented. In some embodiments, based on the particular operations implemented by the various parts of the computer program.
In one embodiment, a computer device includes a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program: acquiring an interface test instruction; inquiring precondition information associated with a test case identifier in the interface test instruction; acquiring to-be-tested case parameter information corresponding to the test case identification according to the precondition information; acquiring a to-be-tested case template and to-be-tested interface communication parameters corresponding to the test case identification from a test case library; generating a test case of the interface to be tested according to the parameter information of the case to be tested and the template of the case to be tested; and testing the interface to be tested corresponding to the address of the interface to be tested in the test case of the interface to be tested according to the test case of the interface to be tested and the communication parameters of the interface to be tested.
In one embodiment, the test case library includes a plurality of test plan information, and before the interface test instruction is obtained, the processor executes the computer program to implement the following steps: monitoring the test starting time in the test plan information; when the current time is the same as the test starting time, extracting a test case identifier corresponding to the test starting time from the test plan information; and generating a test instruction of the interface to be tested according to the extracted test case identifier.
In one embodiment, obtaining the parameter information of the to-be-tested case corresponding to the test case identifier according to the precondition information includes: acquiring preposed case generation information, a preposed case template and a preposed interface communication parameter corresponding to the preposed condition information from a test case library; generating a preposed test case according to the preposed case generating information and the preposed case template; and executing the preposed test case according to the communication parameters of the preposed interface to obtain the parameter information of the case to be tested corresponding to the test case identification.
In one embodiment, executing the pre-test case according to the communication parameters of the pre-interface to obtain parameter information of the case to be tested corresponding to the test case identifier, including: testing a front interface corresponding to a front interface address in the front test case according to the front test case and the front interface communication parameters to acquire parameter information returned by the front interface; detecting whether a data query condition exists in the precondition information; if the precondition information is detected to have a data query condition, querying data from a database according to the data query condition; and taking the obtained parameter information and the inquired data as the parameter information of the to-be-tested case corresponding to the test case identification.
In one embodiment, the testing an interface to be tested corresponding to an address of an interface to be tested in an interface test case according to the interface test case to be tested and communication parameters of the interface to be tested includes: extracting an interface communication protocol type, an interface communication mode and an interface data transmission format in the communication parameters of the interface to be detected; generating a test request of the interface to be tested according to the type of the interface communication protocol, the interface communication mode, the interface data transmission format and the test case of the interface to be tested; and testing the interface to be tested corresponding to the address of the interface to be tested in the test case of the interface to be tested according to the test request of the interface to be tested.
In this embodiment, in the interface test process, before executing the test case corresponding to the test case identifier, obtaining parameter information of the case to be tested according to the precondition information, generating the test case of the interface to be tested according to the obtained parameter information of the case to be tested and the case template to be tested, and testing the interface to be tested according to the test case of the interface to be tested and the communication parameters of the interface to be tested. Test case contents of other interfaces associated with the interface to be tested are not required to be written into the test case of the interface to be tested, and only the test case identification is associated with the precondition information, so that time consumed by repeatedly compiling the test case contents is saved, and the test efficiency of automatically testing the interface to be tested according to the test case is improved.
A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of: acquiring an interface test instruction; inquiring precondition information associated with a test case identifier in the interface test instruction; acquiring to-be-tested case parameter information corresponding to the test case identification according to the precondition information; acquiring a to-be-tested case template and to-be-tested interface communication parameters corresponding to the test case identification from a test case library; generating a test case of the interface to be tested according to the parameter information of the case to be tested and the template of the case to be tested; and testing the interface to be tested corresponding to the address of the interface to be tested in the test case of the interface to be tested according to the test case of the interface to be tested and the communication parameters of the interface to be tested.
In one embodiment, the test case library includes a plurality of test plan information, and before the interface test instruction is obtained, the processor further performs the following steps: monitoring the test starting time in the test plan information; when the current time is the same as the test starting time, extracting a test case identifier corresponding to the test starting time from the test plan information; and generating a test instruction of the interface to be tested according to the extracted test case identifier.
In one embodiment, obtaining the parameter information of the to-be-tested case corresponding to the test case identifier according to the precondition information includes: acquiring preposed case generation information, a preposed case template and a preposed interface communication parameter corresponding to the preposed condition information from a test case library; generating a preposed test case according to the preposed case generating information and the preposed case template; and executing the preposed test case according to the communication parameters of the preposed interface to obtain the parameter information of the case to be tested corresponding to the test case identification.
In one embodiment, executing the pre-test case according to the communication parameters of the pre-interface to obtain parameter information of the case to be tested corresponding to the test case identifier, including: testing a front interface corresponding to a front interface address in the front test case according to the front test case and the front interface communication parameters to acquire parameter information returned by the front interface; detecting whether a data query condition exists in the precondition information; if the precondition information is detected to have a data query condition, querying data from a database according to the data query condition; and taking the obtained parameter information and the inquired data as the parameter information of the to-be-tested case corresponding to the test case identification.
In one embodiment, the testing an interface to be tested corresponding to an address of an interface to be tested in an interface test case according to the interface test case to be tested and communication parameters of the interface to be tested includes: extracting an interface communication protocol type, an interface communication mode and an interface data transmission format in the communication parameters of the interface to be detected; generating a test request of the interface to be tested according to the type of the interface communication protocol, the interface communication mode, the interface data transmission format and the test case of the interface to be tested; and testing the interface to be tested corresponding to the address of the interface to be tested in the test case of the interface to be tested according to the test request of the interface to be tested.
In this embodiment, in the interface test process, before executing the test case corresponding to the test case identifier, obtaining parameter information of the case to be tested according to the precondition information, generating the test case of the interface to be tested according to the obtained parameter information of the case to be tested and the case template to be tested, and testing the interface to be tested according to the test case of the interface to be tested and the communication parameters of the interface to be tested. Test case contents of other interfaces associated with the interface to be tested are not required to be written into the test case of the interface to be tested, and only the test case identification is associated with the precondition information, so that time consumed by repeatedly compiling the test case contents is saved, and the test efficiency of automatically testing the interface to be tested according to the test case is improved.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium, and can include the processes of the embodiments of the methods described above when the computer program is executed. The storage medium may be a non-volatile storage medium such as a magnetic disk, an optical disk, or a Read-Only Memory (ROM).
The technical features of the embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present invention, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. An interface testing method, the method comprising:
inputting test case configuration information in an interface test configuration page, and acquiring an interface test instruction generated according to the test case configuration information;
inquiring precondition information associated with a test case identifier in the interface test instruction; configuring associated precondition information for the test case identification in the interface test configuration page;
acquiring to-be-tested case parameter information corresponding to the test case identification according to the precondition information;
acquiring a to-be-tested case template and to-be-tested interface communication parameters corresponding to the test case identification from a test case library;
generating a test case of the interface to be tested according to the parameter information of the case to be tested and the template of the case to be tested;
testing the interface to be tested corresponding to the address of the interface to be tested in the interface to be tested test case according to the interface to be tested test case and the communication parameters of the interface to be tested;
the acquiring of the parameter information of the to-be-tested case corresponding to the test case identifier according to the precondition information includes:
acquiring preposed case generation information, a preposed case template and a preposed interface communication parameter corresponding to the preposed condition information from a test case library; the preposed case generation information, the preposed case template, the preposed interface communication parameter and the preposed condition information are correspondingly stored in a test case library;
generating a preposed test case according to the preposed case generation information and the preposed case template;
and executing the preposed test case according to the communication parameters of the preposed interface to obtain the parameter information of the case to be tested corresponding to the test case identification.
2. The method of claim 1, wherein the test case library includes a plurality of test plan information;
before the obtaining of the interface test instruction generated according to the test case configuration information, the method includes:
monitoring the test starting time in the test plan information;
when the current time is monitored to be the same as the test starting time, extracting a test case identifier corresponding to the test starting time from the test plan information;
and generating a test instruction of the interface to be tested according to the extracted test case identifier.
3. The method according to claim 1, wherein the executing the pre-test case according to the pre-interface communication parameters to obtain parameter information of a case to be tested corresponding to the test case identifier comprises:
testing a front interface corresponding to a front interface address in the front test case according to the front test case and the front interface communication parameters to acquire parameter information returned by the front interface;
detecting whether a data query condition exists in the precondition information;
if the precondition information is detected to have a data query condition, querying data from a database according to the data query condition;
and taking the obtained parameter information and the inquired data as the parameter information of the to-be-tested case corresponding to the test case identification.
4. The method according to claim 1, wherein the testing the interface to be tested corresponding to the address of the interface to be tested in the test case of the interface to be tested according to the test case of the interface to be tested and the communication parameters of the interface to be tested comprises:
extracting an interface communication protocol type, an interface communication mode and an interface data transmission format in the communication parameters of the interface to be detected;
generating a test request of the interface to be tested according to the interface communication protocol type, the interface communication mode, the interface data transmission format and the test case of the interface to be tested;
and testing the interface to be tested corresponding to the address of the interface to be tested in the test case of the interface to be tested according to the test request of the interface to be tested.
5. An interface testing apparatus, the apparatus comprising:
the test instruction acquisition module is used for inputting test case configuration information in the interface test configuration page and acquiring an interface test instruction generated according to the test case configuration information;
the prepositive condition query module is used for querying prepositive condition information associated with the test case identification in the interface test instruction; configuring associated precondition information for the test case identification in the interface test configuration page;
the parameter information acquisition module is used for acquiring the parameter information of the to-be-tested case corresponding to the test case identifier according to the precondition information;
the case module acquisition module is used for acquiring a case template to be tested and communication parameters of an interface to be tested, which correspond to the test case identification, from a test case library;
the test case generation module is used for generating a test case of the interface to be tested according to the parameter information of the case to be tested and the case template to be tested;
the interface test module to be tested is used for testing the interface to be tested corresponding to the interface address to be tested in the interface test case to be tested according to the interface test case to be tested and the communication parameters of the interface to be tested;
the parameter information acquisition module comprises:
the preposed information query module is used for acquiring preposed case generation information, a preposed case template and a preposed interface communication parameter corresponding to the preposed condition information from the test case library when the associated preposed condition information is queried;
the preposed case generating module is used for generating a preposed test case according to the preposed case generating information and the preposed case template;
and the case parameter obtaining module is used for executing the preposed test case according to the communication parameters of the preposed interface to obtain the parameter information of the case to be tested corresponding to the test case identification.
6. The apparatus according to claim 5, wherein the case parameter obtaining module is further configured to test a pre-interface corresponding to a pre-interface address in the pre-test case according to the pre-test case and the pre-interface communication parameters, and obtain parameter information returned by the pre-interface; detecting whether a data query condition exists in the precondition information; if the precondition information is detected to have a data query condition, querying data from a database according to the data query condition; and taking the obtained parameter information and the inquired data as the parameter information of the to-be-tested case corresponding to the test case identification.
7. The apparatus of claim 5, wherein the test case library includes a plurality of test plan information; the test instruction acquisition module further comprises:
the test plan monitoring module is used for monitoring the test starting time in the test plan information;
a case identifier extraction module, configured to extract a test case identifier corresponding to the test start time from the test plan information when it is monitored that the current time is the same as the test start time;
and the test instruction generating module is used for generating a test instruction of the interface to be tested according to the extracted test case identifier.
8. The apparatus of claim 5,
the interface test module to be tested is also used for extracting the interface communication protocol type, the interface communication mode and the interface data transmission format in the communication parameters of the interface to be tested; generating a test request of the interface to be tested according to the interface communication protocol type, the interface communication mode, the interface data transmission format and the test case of the interface to be tested; and testing the interface to be tested corresponding to the address of the interface to be tested in the test case of the interface to be tested according to the test request of the interface to be tested.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the method of any one of claims 1 to 4 when executing the computer program.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 4.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201711044187.5A CN107844421B (en) | 2017-10-31 | 2017-10-31 | Interface testing method and device, computer equipment and storage medium |
PCT/CN2017/112618 WO2019085079A1 (en) | 2017-10-31 | 2017-11-23 | Interface test method and apparatus, computer device and storage medium |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201711044187.5A CN107844421B (en) | 2017-10-31 | 2017-10-31 | Interface testing method and device, computer equipment and storage medium |
Publications (2)
Publication Number | Publication Date |
---|---|
CN107844421A CN107844421A (en) | 2018-03-27 |
CN107844421B true CN107844421B (en) | 2020-08-14 |
Family
ID=61681160
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201711044187.5A Active CN107844421B (en) | 2017-10-31 | 2017-10-31 | Interface testing method and device, computer equipment and storage medium |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN107844421B (en) |
WO (1) | WO2019085079A1 (en) |
Families Citing this family (32)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109726105B (en) * | 2018-05-15 | 2023-11-28 | 深圳市易行网数字科技有限公司 | Test data construction method, device, equipment and storage medium |
CN108984387A (en) * | 2018-05-30 | 2018-12-11 | 湖南鑫蜀山网络科技有限公司 | Interface test device applied to computer |
CN108733573A (en) * | 2018-05-30 | 2018-11-02 | 湖南鑫蜀山网络科技有限公司 | The interface testing equipment that application interface test method is tested |
CN109086199B (en) * | 2018-06-22 | 2022-06-07 | 网宿科技股份有限公司 | Method, terminal and storage medium for automatically generating test script |
CN109254920A (en) * | 2018-09-06 | 2019-01-22 | 上海精数信息科技有限公司 | Interface testing case generation method, device, electronic equipment, storage medium |
CN109446068B (en) * | 2018-09-26 | 2024-04-05 | 平安健康保险股份有限公司 | Interface test method, device, computer equipment and storage medium |
CN109446071A (en) * | 2018-09-26 | 2019-03-08 | 深圳壹账通智能科技有限公司 | Interface test method, interface test device, electronic equipment and storage medium |
CN109522218A (en) * | 2018-10-19 | 2019-03-26 | 平安科技(深圳)有限公司 | Interface test method, device, computer equipment and storage medium |
CN111090575B (en) * | 2018-10-23 | 2021-07-30 | 亿度慧达教育科技(北京)有限公司 | Test method |
CN109474488B (en) * | 2018-10-31 | 2020-10-27 | 中国银行股份有限公司 | Interface testing method and device and computer equipment |
CN109710532A (en) * | 2018-12-28 | 2019-05-03 | 北京金山安全软件有限公司 | Test case management method and device and electronic equipment |
CN109871314A (en) * | 2019-01-02 | 2019-06-11 | 石化盈科信息技术有限责任公司 | The automatic generation method of test script |
CN109815144A (en) * | 2019-01-16 | 2019-05-28 | 深圳壹账通智能科技有限公司 | Service application test method, device, computer equipment and storage medium |
CN109947646A (en) * | 2019-03-13 | 2019-06-28 | 平安信托有限责任公司 | Interface test method, device, computer equipment and storage medium |
CN109992508A (en) * | 2019-03-22 | 2019-07-09 | 恒生电子股份有限公司 | Test exemple automation generation method, device and electronic equipment |
CN110134583B (en) * | 2019-04-11 | 2023-06-16 | 口碑(上海)信息技术有限公司 | Software testing and data processing method and device |
CN110147319B (en) * | 2019-04-19 | 2022-09-20 | 平安普惠企业管理有限公司 | Database testing method and device and computer equipment |
CN110569198A (en) * | 2019-09-18 | 2019-12-13 | 北京搜狐新媒体信息技术有限公司 | Method and device for automatically testing service function |
CN112988555B (en) * | 2019-12-13 | 2024-05-24 | 中移信息技术有限公司 | Interface testing method, device, equipment and storage medium |
CN113297056A (en) * | 2020-02-24 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Test data setting method, test data application method, device and related equipment |
CN111459794B (en) * | 2020-02-25 | 2024-03-15 | 西安广和通无线软件有限公司 | Communication network testing method, device, computer equipment and storage medium |
CN111427790A (en) * | 2020-03-26 | 2020-07-17 | 中国建设银行股份有限公司 | Test method, test device, terminal equipment and storage medium |
CN111538659B (en) * | 2020-04-21 | 2024-03-01 | 上海携程商务有限公司 | Interface testing method, system, electronic equipment and storage medium of business scene |
CN111611174B (en) * | 2020-05-28 | 2023-08-11 | 北京火山引擎科技有限公司 | Method and device for constructing test data, computer equipment and storage medium |
CN114077540A (en) * | 2020-08-21 | 2022-02-22 | 北京金山云网络技术有限公司 | Interface test system and interface test method |
CN114205273B (en) * | 2020-08-26 | 2023-09-15 | 腾讯科技(深圳)有限公司 | System test method, device and equipment and computer storage medium |
CN112162915B (en) * | 2020-08-27 | 2024-06-25 | 杭州大搜车汽车服务有限公司 | Test data generation method, device, equipment and storage medium |
CN112231209B (en) * | 2020-10-10 | 2024-09-06 | 金医慧通科技有限公司 | Parameter acquisition method, device, computer equipment and storage medium |
CN112256571A (en) * | 2020-10-20 | 2021-01-22 | 苏州市软件评测中心有限公司 | Test case generation method and device and storage medium |
CN112699020A (en) * | 2020-12-11 | 2021-04-23 | 浙江中控技术股份有限公司 | Industrial real-time database API (application program interface) interface testing method |
CN112559356B (en) * | 2020-12-18 | 2024-07-12 | 杭州兑吧网络科技有限公司 | Automatic software testing method and system |
CN113220595B (en) * | 2021-06-11 | 2023-10-03 | 中国农业银行股份有限公司 | Test method and test equipment |
Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102831052A (en) * | 2011-06-16 | 2012-12-19 | 中国银联股份有限公司 | Automatic generating device and method for test case |
CN104331366A (en) * | 2014-10-30 | 2015-02-04 | 北京思特奇信息技术股份有限公司 | Test case design efficiency promotion method and system |
CN105183633A (en) * | 2015-07-21 | 2015-12-23 | 浪潮电子信息产业股份有限公司 | Method and system for generating test case |
CN105224461A (en) * | 2015-10-23 | 2016-01-06 | 网易(杭州)网络有限公司 | A kind of generation method and apparatus of integration testing use-case |
CN105630667A (en) * | 2014-11-28 | 2016-06-01 | 阿里巴巴集团控股有限公司 | Test method and terminal equipment |
US9501389B1 (en) * | 2015-08-20 | 2016-11-22 | International Business Machines Corporation | Test machine management |
CN106227667A (en) * | 2016-07-28 | 2016-12-14 | 南京大学 | A kind of method for generating test case of the Mobile solution of IFML based on extension |
CN106294162A (en) * | 2016-08-12 | 2017-01-04 | 江苏大学 | A kind of third party's component method for testing security based on data mining |
CN106708739A (en) * | 2016-12-30 | 2017-05-24 | 桂林电子科技大学 | Extended finite state machine (EFSM) model-based Web service case generation method and system |
CN106997322A (en) * | 2017-02-15 | 2017-08-01 | 网易宝有限公司 | Method and apparatus for automatic test |
Family Cites Families (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5390325A (en) * | 1992-12-23 | 1995-02-14 | Taligent, Inc. | Automated testing system |
US5881219A (en) * | 1996-12-26 | 1999-03-09 | International Business Machines Corporation | Random reliability engine for testing distributed environments |
US6823507B1 (en) * | 2000-06-06 | 2004-11-23 | International Business Machines Corporation | Detection of memory-related errors in computer programs |
US7844951B2 (en) * | 2005-12-30 | 2010-11-30 | Microsoft Corporation | Specification generation from implementations |
US8683446B2 (en) * | 2007-07-09 | 2014-03-25 | International Business Machines Corporation | Generation of test cases for functional testing of applications |
CN102096631B (en) * | 2009-12-11 | 2013-09-25 | 华为技术有限公司 | Interface testing method and device |
CN103617114B (en) * | 2013-10-23 | 2016-03-02 | 江苏大学 | Based on third party's component vulnerability test method of condition and parameter variation |
IN2015DE01395A (en) * | 2015-05-18 | 2015-06-26 | Hcl Technologies Ltd | |
CN105005532B (en) * | 2015-08-05 | 2017-11-24 | 广东欧珀移动通信有限公司 | A kind of system and method for automatic test application programming interfaces stability |
CN105630685A (en) * | 2016-01-29 | 2016-06-01 | 广州酷狗计算机科技有限公司 | Method and device for testing program interface |
CN106250310B (en) * | 2016-07-25 | 2019-01-29 | 微梦创科网络科技(中国)有限公司 | A kind of method for generating test case and device |
CN106354634A (en) * | 2016-08-25 | 2017-01-25 | 青岛海信传媒网络技术有限公司 | Interface testing method and device |
CN106776307A (en) * | 2016-12-05 | 2017-05-31 | 广州唯品会信息科技有限公司 | Method for testing software and system |
CN106933745A (en) * | 2017-03-30 | 2017-07-07 | 携程计算机技术(上海)有限公司 | WEB automatic interface testing methods and system |
CN107193740A (en) * | 2017-05-23 | 2017-09-22 | 郑州云海信息技术有限公司 | The software test case test system and method for a kind of Reuse-Oriented |
-
2017
- 2017-10-31 CN CN201711044187.5A patent/CN107844421B/en active Active
- 2017-11-23 WO PCT/CN2017/112618 patent/WO2019085079A1/en active Application Filing
Patent Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102831052A (en) * | 2011-06-16 | 2012-12-19 | 中国银联股份有限公司 | Automatic generating device and method for test case |
CN104331366A (en) * | 2014-10-30 | 2015-02-04 | 北京思特奇信息技术股份有限公司 | Test case design efficiency promotion method and system |
CN105630667A (en) * | 2014-11-28 | 2016-06-01 | 阿里巴巴集团控股有限公司 | Test method and terminal equipment |
CN105183633A (en) * | 2015-07-21 | 2015-12-23 | 浪潮电子信息产业股份有限公司 | Method and system for generating test case |
US9501389B1 (en) * | 2015-08-20 | 2016-11-22 | International Business Machines Corporation | Test machine management |
CN105224461A (en) * | 2015-10-23 | 2016-01-06 | 网易(杭州)网络有限公司 | A kind of generation method and apparatus of integration testing use-case |
CN106227667A (en) * | 2016-07-28 | 2016-12-14 | 南京大学 | A kind of method for generating test case of the Mobile solution of IFML based on extension |
CN106294162A (en) * | 2016-08-12 | 2017-01-04 | 江苏大学 | A kind of third party's component method for testing security based on data mining |
CN106708739A (en) * | 2016-12-30 | 2017-05-24 | 桂林电子科技大学 | Extended finite state machine (EFSM) model-based Web service case generation method and system |
CN106997322A (en) * | 2017-02-15 | 2017-08-01 | 网易宝有限公司 | Method and apparatus for automatic test |
Also Published As
Publication number | Publication date |
---|---|
CN107844421A (en) | 2018-03-27 |
WO2019085079A1 (en) | 2019-05-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN107844421B (en) | Interface testing method and device, computer equipment and storage medium | |
CN107766190B (en) | Interface testing method and device, computer equipment and storage medium | |
CN107665233B (en) | Database data processing method and device, computer equipment and storage medium | |
CN106991040B (en) | Data interface testing method and device | |
CN111045952B (en) | Software testing method, flow playback device, terminal equipment and readable storage medium | |
WO2018223717A1 (en) | Webpage front-end testing method, device, system, apparatus and readable storage medium | |
CN111026645B (en) | User interface automatic test method and device, storage medium and electronic equipment | |
CN106484611B (en) | Fuzzy test method and device based on automatic protocol adaptation | |
CN108521353B (en) | Processing method and device for positioning performance bottleneck and readable storage medium | |
CN107784552B (en) | Information push task execution method and device, computer equipment and storage medium | |
CN112241360B (en) | Test case generation method, device, equipment and storage medium | |
CN108255701B (en) | Scene testing method and mobile terminal | |
CN109726134B (en) | Interface test method and system | |
CN108459850B (en) | Method, device and system for generating test script | |
CN113032244A (en) | Interface testing method, device, computer system and computer readable storage medium | |
CN108255700B (en) | Test result generation method and device | |
CN112269746A (en) | Automatic testing method and related equipment | |
CN110543429A (en) | Test case debugging method and device and storage medium | |
CN112965711B (en) | Job testing method and device, electronic equipment and storage medium | |
CN113938412A (en) | Protocol stack testing method and device, testing system and computer readable storage medium | |
CN111506305B (en) | Tool pack generation method, device, computer equipment and readable storage medium | |
CN112346981A (en) | Joint debugging test coverage rate detection method and system | |
CN111200654A (en) | Client request error processing method and device | |
CN114003484B (en) | Log output method, device, equipment and storage medium for interface test | |
CN111104328B (en) | Use case generation method and device, computer equipment and readable storage medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |