CN110750434A - Interface testing method, apparatus, electronic device, and computer-readable storage medium - Google Patents

Abstract

The invention discloses an interface testing method, device, electronic device and computer-readable storage medium. The method includes: acquiring a development document of the interface to be tested; extracting test-related information from the development document; generating and saving a test item corresponding to the interface to be tested according to the test-related information; Select the request to perform the interface test on the corresponding interface to be tested. The technical solution provides an automatic collection of interfaces in the testing phase, and the corresponding test items can be reused during actual testing, which realizes the loose coupling between interface entry and testing, is flexible and reliable, and completes interface testing compared to manually configuring interfaces. Improved efficiency and accuracy.

Description

Interface testing method, apparatus, electronic device, and computer-readable storage medium

technical field

The present invention relates to the field of interface testing, in particular to an interface testing method, apparatus, electronic device and computer-readable storage medium.

Background technique

Interface testing is a type of testing that tests the interface between system components. Interface testing is mainly used to detect the interaction points between the external system and the system and between the various internal subsystems. The focus of the test is to check the data exchange, transfer and control management process, as well as the mutual logical dependencies between systems.

The object of the interface test is the interface, and for a project, the interface may be added, modified or deleted. In the prior art, when an interface is tested, a complex manual configuration process needs to be performed on the interface to be tested, which is inefficient.

SUMMARY OF THE INVENTION

In view of the above problems, the present invention is proposed to provide an interface testing method, apparatus, electronic device and computer readable storage medium that overcome the above problems or at least partially solve the above problems.

According to one aspect of the present invention, an interface testing method is provided, comprising:

Obtain the development documentation of the interface to be tested;

extracting test-related information from the development documentation;

Generate and save a test item corresponding to the interface to be tested according to the test-related information;

In response to the selection request for the test item, the interface test is performed on the corresponding interface to be tested.

Optionally, the obtaining the development document of the interface to be tested includes:

When the preset time condition is met, obtain the development document of the interface to be tested from the pre-configured address;

and / or,

When the save event of the development document of the interface to be tested is known, the development document of the interface to be tested is acquired from a preconfigured address.

Optionally, the development document is written based on the annotation specification of the programming language used for development.

Optionally, the test-related information includes one or more of the following:

Interface address, interface name, interface parameters, interface return value.

Optionally, in response to the selection request for the test item, performing an interface test on the corresponding interface to be tested includes:

Provide an interface test interface, and display an interface test list including one or more test items in the interface test interface;

A request for selecting a test item in the interface test list is received, a test case corresponding to the selected test item is acquired, and an interface test is performed on the interface to be tested.

Optionally, the method further includes:

Provide test case generation interface;

Receive data construction conditions through the test case generation interface;

Corresponding test cases are generated according to the data construction conditions.

Optionally, the data construction conditions include one or more of the following:

Construct interface test data based on interface parameters;

Construct interface test data based on database connection information;

Constructs interface test data based on cached addresses.

Optionally, the generating corresponding interface test data according to the data construction conditions includes:

Inserting interface test data in the corresponding database according to the database connection information, so as to use the inserted interface test data to perform interface test when performing interface test on the corresponding interface to be tested;

and / or,

Construct a database query statement according to the database connection information, so as to use the data queried by the database query statement to perform interface testing when performing interface testing on the corresponding interface to be tested;

and / or,

The interface test data is inserted into the corresponding cache according to the cache address, so as to use the inserted interface test data to perform the interface test when the interface test is performed on the corresponding interface to be tested.

Optionally, the method further includes:

Receive verification configuration information through the interface test interface;

After the interface test is completed, the verification is performed according to the verification configuration information, and a test result corresponding to the interface test is further generated.

Optionally, the performing verification according to the verification configuration information includes one or more of the following:

verifying the return value of the interface to be tested according to the verification configuration information;

The corresponding data is queried from the target database according to the database query statement in the verification configuration information, and the read data is verified according to the verification configuration information;

A log corresponding to the completed interface test is acquired, a corresponding part of the log is extracted from the log according to the verification configuration information, and the extracted part of the log is verified.

According to another aspect of the present invention, an interface testing device is provided, comprising:

The acquisition unit is suitable for acquiring the development documents of the interface to be tested;

an extraction unit, adapted to extract test-related information from the development document;

a test item unit, adapted to generate and save a test item corresponding to the interface to be tested according to the test-related information;

The test unit is adapted to perform interface test on the corresponding interface to be tested in response to the selection request for the test item.

Optionally, the obtaining unit is adapted to obtain the development document of the interface to be tested from a pre-configured address when a preset time condition is met; and/or, upon learning of the saving event of the development document of the interface to be tested , obtain the development document of the interface to be tested from the pre-configured address.

Optionally, the development document is written based on the annotation specification of the programming language used for development.

Optionally, the test-related information includes one or more of the following:

Interface address, interface name, interface parameters, interface return value.

Optionally, the test unit is adapted to provide an interface test interface, and displays an interface test list including one or more test items in the interface test interface; receives a request for selecting a test item in the interface test list, and obtains For the test case corresponding to the selected test item, the interface test is performed on the interface to be tested.

Optionally, the device also includes:

The test case unit is adapted to provide a test case generation interface; receive data construction conditions through the test case generation interface; and generate corresponding test cases according to the data construction conditions.

Optionally, the data construction conditions include one or more of the following: constructing interface test data based on interface parameters; constructing interface test data based on database connection information; constructing interface test data based on cache addresses.

Optionally, the test case unit is adapted to insert interface test data in the corresponding database according to the database connection information, so as to use the inserted interface test data to perform the interface test when the interface test is performed on the corresponding interface to be tested; and /or, constructing a database query statement according to the database connection information, so as to use the data queried by the database query statement to perform an interface test when performing an interface test on a corresponding interface to be tested; and/or, according to the cache address in The interface test data is inserted into the corresponding cache, so as to use the inserted interface test data to perform the interface test when the interface test is performed on the corresponding interface to be tested.

Optionally, the device further includes:

The verification unit is adapted to receive verification configuration information through the interface test interface; after the interface test is completed, perform verification according to the verification configuration information and further generate a test result corresponding to the interface test.

Optionally, the verification unit is adapted to verify the return value of the interface to be tested according to the verification configuration information; and/or, according to the database query statement in the verification configuration information The corresponding data is queried in the target database, and the read data is verified according to the verification configuration information; and/or, the log corresponding to the completed interface test is acquired, and the log is obtained from the log according to the verification configuration information. Extract the corresponding part of the log, and verify the extracted part of the log.

According to yet another aspect of the present invention, there is provided an electronic device comprising: a processor; and a memory arranged to store computer-executable instructions that, when executed, cause the processor to perform any of the above a described method.

According to yet another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores one or more programs, the one or more programs, when executed by a processor, implements the following: Any of the methods described above.

It can be seen from the above that the technical solution of the present invention can automatically generate and save the test items corresponding to the interface to be tested by acquiring the development document of the interface to be tested and extract the relevant test information from it. The selection request of the test item can realize the interface test of the corresponding interface to be tested. The technical solution provides an automatic collection of interfaces in the testing phase, and the corresponding test items can be reused during actual testing, which realizes the loose coupling between interface entry and testing, is flexible and reliable, and completes interface testing compared to manually configuring interfaces. Improved efficiency and accuracy.

The above description is only an overview of the technical solutions of the present invention, in order to be able to understand the technical means of the present invention more clearly, it can be implemented according to the content of the description, and in order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand , the following specific embodiments of the present invention are given.

Description of drawings

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are for the purpose of illustrating preferred embodiments only and are not to be considered limiting of the invention. Also, the same components are denoted by the same reference numerals throughout the drawings. In the attached image:

1 shows a schematic flowchart of an interface testing method according to an embodiment of the present invention;

2 shows a schematic structural diagram of an interface testing device according to an embodiment of the present invention;

FIG. 3 shows a schematic structural diagram of an electronic device according to an embodiment of the present invention;

FIG. 4 shows a schematic structural diagram of a computer-readable storage medium according to an embodiment of the present invention.

Detailed ways

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided so that the present disclosure will be more thoroughly understood, and will fully convey the scope of the present disclosure to those skilled in the art.

FIG. 1 shows a schematic flowchart of an interface testing method according to an embodiment of the present invention. As shown in Figure 1, the method includes:

Step S110, acquiring a development document of the interface to be tested. The development document may be written by the developer during the interface development process. Specifically, in an embodiment of the present invention, in the above method, the development document is written based on the annotation specification of the programming language used for development.

For example, the interface of the website can usually be developed using the PHP language, and the development document can be written by using the PHP annotation specification PHPDoc. In this way, since the development document complies with the specification of the fixed format, the test-related information can be conveniently and automatically read from the development document, as shown in step S120.

Step S120, extracting test-related information from the development document.

In an embodiment of the present invention, in the above method, the test-related information includes one or more of the following: an interface address, an interface name, an interface parameter, and an interface return value. For example, the interface return value is annotated with "@return" in PHPDoc, the interface name is annotated with "@name", and so on.

Step S130: Generate and save a test item corresponding to the interface to be tested according to the test-related information.

Taking the service provided by the test platform as an example in the specific implementation, the test items corresponding to each interface to be tested are saved in the test platform, realizing the automatic entry of the interface. In the prior art, if you want to implement interface testing, you need developers to provide testers with test-related information and implement manual entry or manual configuration of the interface. The interactive medium actually still requires developers to manually enter the interface, so there will inevitably be misoperations, which are not only inefficient, but also not accurate.

Step S140, in response to the selection request for the test item, perform an interface test on the corresponding interface to be tested.

It can be seen that the method shown in FIG. 1 can automatically generate and save the test items corresponding to the interface to be tested by obtaining the development document of the interface to be tested, and extract relevant test information from it. The selection request of the item can realize the interface test of the corresponding interface to be tested. The technical solution provides an automatic collection of interfaces in the testing phase, and the corresponding test items can be reused during actual testing, which realizes the loose coupling between interface entry and testing, is flexible and reliable, and completes interface testing compared to manually configuring interfaces. Improved efficiency and accuracy.

In an embodiment of the present invention, in the above method, acquiring the development document of the interface to be tested includes: when a preset time condition is satisfied, acquiring the development document of the interface to be tested from a preconfigured address; and/or, after learning During the save event of the development document of the interface to be tested, the development document of the interface to be tested is obtained from the pre-configured address.

In one way, the development documents can be obtained from the address provided by the developer (such as the path in the file system or the address of the development document database) every fixed time (for example, half an hour), or the development document can be obtained at a fixed time every day. . In another method, considering that the former method is not very time-sensitive, and there may be a lot of repetitive work (for example, the development documents obtained several times in a row are the same), for example, the HOOK technology can be used to obtain the development documents of the interface to be tested. save event. In this way, the development documents can be obtained when the development documents are added or modified. Of course, the save event of the development document that knows the interface to be tested may also be manually notified by the developer, or implemented in other ways.

In an embodiment of the present invention, in the above method, in response to a request for selecting a test item, performing an interface test on a corresponding interface to be tested includes: providing an interface test interface, and displaying in the interface test interface includes one or more tests The interface test list of the item; receive the selection request for the test item in the interface test list, obtain the test case corresponding to the selected test item, and perform the interface test on the interface to be tested.

In this embodiment, when performing an interface test, the user can obtain an interface test list including one or more test items by accessing a graphical interface test interface, command line, etc., so that the user can choose which interfaces to perform test.

Interface testing is also usually implemented by relying on test cases. Here, test cases can be submitted by users, for example, testers pre-write some test cases.

Considering a scenario such as a test platform, it is a good idea to effectively manage test cases on the test platform, such as dividing into multiple levels and managing some test cases as test case groups. However, if the test cases are only managed and saved on the platform, it cannot be said that all the needs of testers can be met. For example, writing test cases is a time-consuming task.

In an embodiment of the present invention, the above-mentioned method further includes: providing a test case generation interface; receiving data construction conditions through the test case generation interface; and generating corresponding test cases according to the data construction conditions.

In this embodiment, a test case generation interface may be provided by, for example, a test platform, thereby realizing platform-based test case generation. The most important thing in a test case is usually to construct appropriate data, such as testing the robustness of an interface, and deliberately passing float data to an interface that can only accept int data. In this embodiment, the user only needs to provide the data construction conditions,

Specifically, in an embodiment of the present invention, in the above method, the data construction conditions include one or more of the following: constructing interface test data based on interface parameters; constructing interface test data based on database connection information; constructing based on cache addresses Interface test data.

The example of constructing data based on interface parameters has been shown above, and data that is correct or incorrect for the interface can be constructed according to the type, scope, etc. of the interface parameters. It can also support the transfer of variables between interfaces, and use the return value of the previous interface as the parameter of the next interface, so that multiple interfaces can be chained together to achieve a complete function, simulating the process of real user operation and calling the interface, to achieve the structure Data integrity and test simulation.

Several other ways are also provided in this embodiment: constructing data based on database connection information; constructing data based on cache addresses. This is because many interfaces require access to databases or caches. In order to test these scenarios, such data structures are provided. Wherein, the database connection information may be only the configuration of the database connection in advance, and only the database name needs to be provided when the data construction conditions are provided.

In an embodiment of the present invention, in the above method, generating the corresponding test case according to the data construction conditions includes: inserting interface test data into the corresponding database according to the database connection information, so as to use the interface test data when performing the interface test on the corresponding interface to be tested. The inserted interface test data is used for interface testing; and/or, a database query statement is constructed according to the database connection information, so as to use the data queried by the database query statement to perform interface testing when performing the interface test on the corresponding interface to be tested; and/or, The interface test data is inserted into the corresponding cache according to the cache address, so as to use the inserted interface test data to perform the interface test when the interface test is performed on the corresponding interface to be tested.

It can be seen that, only the database connection information and/or the cache address need to be preconfigured, and the desired interface test data can be inserted in the corresponding position to complete the interface test. For example, if an interface needs to access the user name in the database to check whether the user name has been registered, the corresponding interface test data needs to be inserted into the database.

In practice, many developers are accustomed to using redis to cache some data, such as the number of visits, whether it has been visited, etc. If the real simulation of these data requires other complicated steps in the early stage to obtain the data, it may also be necessary to repeat Constructing data multiple times is inefficient, so data construction can be achieved by directly setting the corresponding values in redis (such as the key and value of the input construction).

In an embodiment of the present invention, the above method further includes: receiving verification configuration information through an interface test interface; after the interface test is completed, performing verification according to the verification configuration information and further generating a test result corresponding to the interface test.

This embodiment may be mainly aimed at the scenario of functional testing, that is, testing whether the return value of an interface is correct, etc. For example, in an embodiment of the present invention, in the above method, the verification according to the verification configuration information includes one of the following or Various: According to the verification configuration information, the return value of the interface to be tested is verified; the corresponding data is queried from the target database according to the database query statement in the verification configuration information, and the read data is verified according to the verification configuration information The log corresponding to the completed interface test is obtained, the corresponding part of the log is extracted from the log according to the verification configuration information, and the extracted part of the log is verified.

Generally speaking, verifying the return value is the most important part in the interface test. In this embodiment, two other verification methods are also provided, so that the number of parts that can be verified increases and the test result is more accurate. For example, if an interface needs to write data to the database, the corresponding verification configuration information can include a sql query statement to check whether the data has been successfully written to the database; another example is to extract some key strings from the log. information, etc. Usually, the correctness of the field pages of some databases cannot be directly detected, and they have a great impact on other modules or the overall business integrity. If manual inspection is performed, frequent page operations are required, and then sql ( Structured query language) statement query, which involves a series of operations such as applying for database permissions, connecting to the database, and writing sql. In this embodiment, the sql statement for checking only needs to be input once, and the correctness can be checked automatically and the result is returned. Testing has also become simple and convenient.

For log verification, you need to configure the machine, path, and access method of the log to be verified in advance. Then in the validator, you need to select the corresponding file name, enter the field to be checked, and also support multi-field check. In a specific business scenario, there are often files that interact between two modules. If you manually verify the files, it is very cumbersome. The format and content of the files need to be checked one by one, and the problem of test omission is easy to occur. Here, you can enter important fields to be concerned about, or the content of all lines, execute the use case, and automatically check all the content, which is simple and convenient. In addition, key parameters can also be extracted from the format of the file as a standard for the uniqueness of the file content to prevent the interaction between previous use cases.

FIG. 2 shows a schematic structural diagram of an interface testing apparatus according to an embodiment of the present invention. As shown in FIG. 2, the interface testing apparatus 200 includes:

The obtaining unit 210 is adapted to obtain the development document of the interface to be tested. The development document may be written by the developer during the interface development process. Specifically, in an embodiment of the present invention, in the above device, the development document is written based on the annotation specification of the programming language used for development.

For example, the interface of the website can usually be developed using the PHP language, and the development document can be written by using the PHP annotation specification PHPDoc. In this way, since the development document complies with the specification of the fixed format, the test-related information can be conveniently and automatically read from the development document, as shown in step S120.

The extraction unit 220 is adapted to extract test-related information from the development document.

In an embodiment of the present invention, in the above device, the test-related information includes one or more of the following: an interface address, an interface name, an interface parameter, and an interface return value. For example, the interface return value is annotated with "@return" in PHPDoc, the interface name is annotated with "@name", and so on.

The test item unit 230 is adapted to generate and save the test item corresponding to the interface to be tested according to the test-related information.

Taking the service provided by the test platform as an example in the specific implementation, the test items corresponding to each interface to be tested are saved in the test platform, realizing the automatic entry of the interface. In the prior art, if you want to implement interface testing, you need developers to provide testers with test-related information and implement manual entry or manual configuration of the interface. The interactive medium actually still requires developers to manually enter the interface, so there will inevitably be misoperations, which are not only inefficient, but also not accurate.

The testing unit 240 is adapted to perform an interface test on the corresponding interface to be tested in response to a request for selecting a test item.

It can be seen that the device shown in FIG. 2 can automatically generate and save the test items corresponding to the interface to be tested by acquiring the development document of the interface to be tested and extract the relevant test information from it. The selection request of the item can realize the interface test of the corresponding interface to be tested. The technical solution provides an automatic collection of interfaces in the testing phase, and the corresponding test items can be reused during actual testing, which realizes the loose coupling between interface entry and testing, is flexible and reliable, and completes interface testing compared to manually configuring interfaces. Improved efficiency and accuracy.

In an embodiment of the present invention, in the above-mentioned apparatus, the obtaining unit 210 is adapted to obtain the development document of the interface to be tested from a preconfigured address when a preset time condition is satisfied; and/or, after obtaining the interface to be tested During the save event of the development document, obtain the development document of the interface to be tested from the pre-configured address.

In one way, the development documents can be obtained from the address provided by the developer (such as the path in the file system or the address of the development document database) every fixed time (for example, half an hour), or the development document can be obtained at a fixed time every day. . In another method, considering that the former method is not very time-sensitive, and there may be a lot of repetitive work (for example, the development documents obtained several times in a row are the same), for example, the HOOK technology can be used to obtain the development documents of the interface to be tested. save event. In this way, the development documents can be obtained when the development documents are added or modified. Of course, the save event of the development document that knows the interface to be tested may also be manually notified by the developer, or implemented in other ways.

In an embodiment of the present invention, in the above device, the testing unit 240 is adapted to provide an interface testing interface, and display an interface testing list including one or more test items in the interface testing interface; Item selection request, obtain the test case corresponding to the selected test item, and perform interface testing on the interface to be tested.

In this embodiment, when performing an interface test, the user can obtain an interface test list including one or more test items by accessing a graphical interface test interface, command line, etc., so that the user can choose which interfaces to perform test.

Interface testing is also usually implemented by relying on test cases. Here, test cases can be submitted by users, for example, testers pre-write some test cases.

Considering a scenario such as a test platform, it is a good idea to effectively manage test cases on the test platform, such as dividing into multiple levels and managing some test cases as test case groups. However, if the test cases are only managed and saved on the platform, it cannot be said that all the needs of testers can be met. For example, writing test cases is a time-consuming task.

In an embodiment of the present invention, the above device further includes: a test case unit, adapted to provide a test case generation interface; receive data construction conditions through the test case generation interface; and generate corresponding test cases according to the data construction conditions.

In this embodiment, a test case generation interface may be provided by, for example, a test platform, thereby realizing platform-based test case generation. The most important thing in a test case is usually to construct appropriate data, such as testing the robustness of an interface, and deliberately passing float data to an interface that can only accept int data. In this embodiment, the user only needs to provide data construction conditions,

Specifically, in an embodiment of the present invention, in the above device, the data construction conditions include one or more of the following: constructing interface test data based on interface parameters; constructing interface test data based on database connection information; constructing based on cache addresses Interface test data.

The example of constructing data based on interface parameters has been shown above, and data that is correct or incorrect for the interface can be constructed according to the type, scope, etc. of the interface parameters. It can also support the transfer of variables between interfaces, and use the return value of the previous interface as the parameter of the next interface, so that multiple interfaces can be chained together to achieve a complete function, simulating the process of real user operation and calling the interface, to achieve the structure Data integrity and test simulation.

Several other ways are also provided in this embodiment: constructing data based on database connection information; constructing data based on cache addresses. This is because many interfaces require access to databases or caches, and in order to test these scenarios, such data structures are provided. Wherein, the database connection information may be only the configuration of the database connection in advance, and only the database name needs to be provided when the data construction conditions are provided.

In an embodiment of the present invention, in the above device, the test case unit is adapted to insert interface test data into the corresponding database according to the database connection information, so as to use the inserted interface test data when performing the interface test on the corresponding interface to be tested. Perform an interface test; and/or, construct a database query statement according to the database connection information, so as to use the data queried by the database query statement to perform the interface test when performing the interface test on the corresponding interface to be tested; and/or, according to the cache address in the corresponding The interface test data is inserted into the cache, so as to use the inserted interface test data to perform the interface test when the interface test is performed on the corresponding interface to be tested.

It can be seen that, only the database connection information and/or the cache address need to be preconfigured, and the desired interface test data can be inserted in the corresponding position to complete the interface test. For example, if an interface needs to access the user name in the database to check whether the user name has been registered, the corresponding interface test data needs to be inserted into the database.

In practice, many developers are accustomed to using redis to cache some data, such as the number of visits, whether it has been visited, etc. If the real simulation of these data requires other complicated steps in the early stage to obtain the data, it may also be necessary to repeat Constructing data multiple times is inefficient, so data construction can be achieved by directly setting the corresponding values in redis (such as the key and value of the input construction).

In an embodiment of the present invention, the above device further includes: a verification unit, adapted to receive verification configuration information through an interface test interface; after the interface test is completed, perform verification according to the verification configuration information and further generate and interface test corresponding test results.

This embodiment may be mainly aimed at the scenario of functional testing, that is, testing whether the return value of an interface is correct, etc. For example, in an embodiment of the present invention, in the above-mentioned apparatus, the verification unit is adapted to perform the test to be tested according to the verification configuration information Verify the return value of the interface; and/or, query the corresponding data from the target database according to the database query statement in the verification configuration information, and verify the read data according to the verification configuration information; and/or, obtain For the log corresponding to the completed interface test, extract the corresponding part of the log from the log according to the verification configuration information, and verify the extracted part of the log.

Generally speaking, verifying the return value is the most important part in the interface test. In this embodiment, two other verification methods are also provided, so that the number of parts that can be verified increases and the test result is more accurate. For example, if an interface needs to write data to the database, the corresponding verification configuration information can include a sql query statement to check whether the data has been successfully written to the database; another example is to extract some key strings from the log. information, etc. Usually, the correctness of the field pages of some databases cannot be directly detected, and they have a great impact on other modules or the overall business integrity. If manual inspection is performed, frequent page operations are required, and then sql statements are written. Query involves a series of operations such as applying for database permissions, connecting to databases, and writing sql. In this embodiment, the sql statement for checking only needs to be input once, and the correctness can be checked automatically and the result is returned. Testing has also become simple and convenient.

For log verification, you need to configure the machine, path, and access method of the log to be verified in advance. Then in the validator, you need to select the corresponding file name, enter the field to be checked, and also support multi-field check. In a specific business scenario, there are often files that interact between two modules. If you manually verify the files, it is very cumbersome. The format and content of the files need to be checked one by one, and the problem of test omission is easy to occur. Here, you can enter important fields to be concerned about, or the content of all lines, execute the use case, and automatically check all the content, which is simple and convenient. In addition, key parameters can also be extracted from the format of the file as a standard for the uniqueness of the file content to prevent the interaction between previous use cases.

It can also be seen from the above embodiments that the interface testing apparatus can provide platform services, for example, implemented on the server side.

To sum up, the technical solution of the present invention can automatically generate and save the test items corresponding to the interface to be tested by acquiring the development document of the interface to be tested, and extract the relevant test information from it. The selection request for the test item can implement the interface test on the corresponding interface to be tested. The technical solution provides an automatic collection of interfaces in the testing phase, and the corresponding test items can be reused during actual testing, which realizes the loose coupling between interface entry and testing, is flexible and reliable, and completes interface testing compared to manually configuring interfaces. Improved efficiency and accuracy.

It should be noted:

The algorithms and displays provided herein are not inherently related to any particular computer, virtual appliance, or other device. Various general-purpose devices can also be used with the teachings based on this. The structure required to construct such a device is apparent from the above description. Furthermore, the present invention is not directed to any particular programming language. It is to be understood that various programming languages may be used to implement the inventions described herein, and that the descriptions of specific languages above are intended to disclose the best mode for carrying out the invention.

In the description provided herein, numerous specific details are set forth. It will be understood, however, that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.

Similarly, it is to be understood that in the above description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together into a single embodiment, figure, or its description. This disclosure, however, should not be construed as reflecting an intention that the invention as claimed requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the Detailed Description are hereby expressly incorporated into this Detailed Description, with each claim standing on its own as a separate embodiment of this invention.

Those skilled in the art will understand that the modules in the device in the embodiment can be adaptively changed and arranged in one or more devices different from the embodiment. The modules or units or components in the embodiments may be combined into one module or unit or component, and further they may be divided into multiple sub-modules or sub-units or sub-assemblies. All features disclosed in this specification (including accompanying claims, abstract and drawings) and any method so disclosed may be employed in any combination, unless at least some of such features and/or procedures or elements are mutually exclusive. All processes or units of equipment are combined. Each feature disclosed in this specification (including accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.

Furthermore, those skilled in the art will appreciate that although some of the embodiments described herein include certain features, but not others, included in other embodiments, that combinations of features of different embodiments are intended to be within the scope of the invention within and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.

Various component embodiments of the present invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art should understand that a microprocessor or a digital signal processor (DSP) may be used in practice to implement some or all functions of some or all components of the interface testing apparatus according to the embodiments of the present invention. The present invention can also be implemented as apparatus or apparatus programs (eg, computer programs and computer program products) for performing part or all of the methods described herein. Such a program implementing the present invention may be stored on a computer-readable medium, or may be in the form of one or more signals. Such signals may be downloaded from Internet sites, or provided on carrier signals, or in any other form.

For example, FIG. 3 shows a schematic structural diagram of an electronic device according to an embodiment of the present invention. The electronic device includes a processor 310 and a memory 320 arranged to store computer-executable instructions (computer-readable program code). The memory 320 may be an electronic memory such as flash memory, EEPROM (Electrically Erasable Programmable Read Only Memory), EPROM, hard disk, or ROM. The memory 320 has storage space 330 for storing computer readable program code 331 for performing any of the method steps in the above-described methods. For example, the storage space 330 for storing computer-readable program code may include various computer-readable program codes 331 for implementing various steps in the above methods, respectively. Computer readable program code 331 can be read from or written to one or more computer program products. These computer program products include program code carriers such as hard disks, compact disks (CDs), memory cards or floppy disks. Such a computer program product is typically a computer-readable storage medium as described in FIG. 4 . FIG. 4 shows a schematic structural diagram of a computer-readable storage medium according to an embodiment of the present invention. The computer-readable storage medium 400 stores computer-readable program code 331 for performing the method steps according to the invention, which can be read by the processor 310 of the electronic device 300 when the computer-readable program code 331 is executed by the electronic device 300 , causing the electronic device 300 to execute each step in the above-described method. Specifically, the computer-readable program code 331 stored in the computer-readable storage medium can execute the method shown in any of the above-described embodiments. The computer readable program code 331 may be compressed in a suitable form.

It should be noted that the above-described embodiments illustrate rather than limit the invention, and that alternative embodiments may be devised by those skilled in the art without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention can be implemented by means of hardware comprising several different elements and by means of a suitably programmed computer. In a unit claim enumerating several means, several of these means may be embodied by one and the same item of hardware. The use of the words first, second, and third, etc. do not denote any order. These words can be interpreted as names.

The embodiment of the present invention discloses A1, an interface testing method, comprising:

Obtain the development documentation of the interface to be tested;

extracting test-related information from the development documentation;

Generate and save a test item corresponding to the interface to be tested according to the test-related information;

In response to the selection request for the test item, the interface test is performed on the corresponding interface to be tested.

A2. The method of A1, wherein the obtaining the development document of the interface to be tested includes:

When the preset time condition is met, obtain the development document of the interface to be tested from the pre-configured address;

and / or,

When the save event of the development document of the interface to be tested is known, the development document of the interface to be tested is acquired from a preconfigured address.

A3. The method of A1, wherein the development document is written based on an annotation specification of a programming language used for development.

A4. The method of A1, wherein the test-related information includes one or more of the following:

Interface address, interface name, interface parameters, interface return value.

A5. The method of A1, wherein, in response to the selection request for the test item, performing an interface test on the corresponding interface to be tested includes:

Provide an interface test interface, and display an interface test list including one or more test items in the interface test interface;

A request for selecting a test item in the interface test list is received, a test case corresponding to the selected test item is acquired, and an interface test is performed on the interface to be tested.

A6. The method of A5, wherein the method further comprises:

Provide test case generation interface;

Receive data construction conditions through the test case generation interface;

Corresponding test cases are generated according to the data construction conditions.

A7. The method according to A6, wherein the data construction conditions include one or more of the following:

Construct interface test data based on interface parameters;

Construct interface test data based on database connection information;

Constructs interface test data based on cached addresses.

A8. The method according to A7, wherein the generating a corresponding test case according to the data construction condition includes:

Inserting interface test data in the corresponding database according to the database connection information, so as to use the inserted interface test data to perform interface test when performing interface test on the corresponding interface to be tested;

and / or,

Construct a database query statement according to the database connection information, so as to use the data queried by the database query statement to perform interface testing when performing interface testing on the corresponding interface to be tested;

and / or,

The interface test data is inserted into the corresponding cache according to the cache address, so as to use the inserted interface test data to perform the interface test when the interface test is performed on the corresponding interface to be tested.

A9. The method of A5, wherein the method further comprises:

Receive verification configuration information through the interface test interface;

After the interface test is completed, the verification is performed according to the verification configuration information, and a test result corresponding to the interface test is further generated.

A10. The method according to A9, wherein the performing verification according to the verification configuration information includes one or more of the following:

verifying the return value of the interface to be tested according to the verification configuration information;

The corresponding data is queried from the target database according to the database query statement in the verification configuration information, and the read data is verified according to the verification configuration information;

A log corresponding to the completed interface test is acquired, a corresponding part of the log is extracted from the log according to the verification configuration information, and the extracted part of the log is verified.

The embodiment of the present invention also discloses B11, an interface testing device, comprising:

The acquisition unit is suitable for acquiring the development documents of the interface to be tested;

an extraction unit, adapted to extract test-related information from the development document;

a test item unit, adapted to generate and save a test item corresponding to the interface to be tested according to the test-related information;

The test unit is adapted to perform interface test on the corresponding interface to be tested in response to the selection request for the test item.

B12. The device of B11, wherein,

The obtaining unit is adapted to obtain the development document of the interface to be tested from a pre-configured address when a preset time condition is met; and/or, when learning the saving event of the development document of the interface to be tested, from the pre-configured address. The configured address obtains the development documentation of the interface to be tested.

B13. The apparatus of B11, wherein the development document is written based on an annotation specification of a programming language used for development.

B14. The device according to B11, wherein the test-related information includes one or more of the following:

Interface address, interface name, interface parameters, interface return value.

B15. The device of B11, wherein,

The test unit is adapted to provide an interface test interface, and an interface test list including one or more test items is displayed in the interface test interface; a request for selecting a test item in the interface test list is received, and the selected test The test case corresponding to the item is used, and the interface test is performed on the interface to be tested.

B16. The device according to B15, wherein the device further comprises:

The test case unit is adapted to provide a test case generation interface; receive data construction conditions through the test case generation interface; and generate corresponding test cases according to the data construction conditions.

B17. The device according to B16, wherein the data construction conditions include one or more of the following: constructing interface test data based on interface parameters; constructing interface test data based on database addresses; constructing interface test data based on cache addresses.

B18. The device of B17, wherein,

The test case unit is adapted to insert interface test data into the corresponding database according to the database connection information, so as to use the inserted interface test data to perform interface testing when performing interface testing on the corresponding interface to be tested; and/or, according to The database connection information constructs a database query statement, so as to use the data queried by the database query statement to perform an interface test when performing an interface test on the corresponding interface to be tested; and/or, inserting into the corresponding cache according to the cache address The interface test data is used to perform the interface test using the inserted interface test data when the interface test is performed on the corresponding interface to be tested.

B19. The device of B15, wherein the device further comprises:

The verification unit is adapted to receive verification configuration information through the interface test interface; after the interface test is completed, perform verification according to the verification configuration information and further generate a test result corresponding to the interface test.

B20. The device of B19, wherein,

The verification unit is adapted to verify the return value of the interface to be tested according to the verification configuration information; and/or, query from the target database according to the database query statement in the verification configuration information outputting corresponding data, and verifying the read data according to the verification configuration information; and/or, acquiring a log corresponding to the completed interface test, and extracting the corresponding part from the log according to the verification configuration information log, and verify the extracted part of the log.

Embodiments of the present invention also disclose C21, an electronic device, wherein the electronic device comprises: a processor; and a memory arranged to store computer-executable instructions that, when executed, cause the processing The device performs the method as described in any one of A1-A10.

The embodiment of the present invention also discloses D22, a computer-readable storage medium, wherein the computer-readable storage medium stores one or more programs, and the one or more programs, when executed by the processor, implement the following The method of any one of A1-A10.

Claims (10)

1. An interface testing method, comprising:

acquiring a development document of an interface to be tested;

extracting test-related information from the development document;

generating and storing a test item corresponding to the interface to be tested according to the test related information;

and responding to the selection request of the test item, and performing interface test on the corresponding interface to be tested.

2. The method of claim 1, wherein said obtaining a development document for an interface to be tested comprises:

when a preset time condition is met, acquiring a development document of an interface to be tested from a pre-configured address;

and/or the presence of a gas in the gas,

and when the storage event of the development document of the interface to be tested is obtained, obtaining the development document of the interface to be tested from a pre-configured address.

3. The method of claim 1, wherein the development document is written based on an annotation specification of a programming language used for development.

4. The method of claim 1, wherein the test-related information comprises one or more of:

interface address, interface name, interface parameter, interface return value.

5. An interface test apparatus comprising:

the acquisition unit is suitable for acquiring a development document of the interface to be tested;

an extraction unit adapted to extract test-related information from the development document;

the test item unit is suitable for generating and storing a test item corresponding to the interface to be tested according to the test related information;

and the test unit is suitable for responding to the selection request of the test item and carrying out interface test on the corresponding interface to be tested.

6. The apparatus of claim 5, wherein,

the acquisition unit is suitable for acquiring a development document of the interface to be tested from a pre-configured address when a preset time condition is met; and/or acquiring the development document of the interface to be tested from a pre-configured address when the storage event of the development document of the interface to be tested is known.

7. The apparatus of claim 5, wherein the development document is written based on an annotation specification of a programming language used for development.

8. The apparatus of claim 5, wherein the test-related information comprises one or more of:

interface address, interface name, interface parameter, interface return value.

9. An electronic device, wherein the electronic device comprises: a processor; and a memory arranged to store computer-executable instructions that, when executed, cause the processor to perform the method of any one of claims 1-4.

10. A computer readable storage medium, wherein the computer readable storage medium stores one or more programs which, when executed by a processor, implement the method of any of claims 1-4.

Images