A method and apparatus for testing database assertions

Abstract

The application provides a database assertion test method and device, the method comprises the following steps: obtaining first assertion data, wherein the first assertion data comprises a first assertion statement and a type of the first assertion statement; obtaining a database type of a target database; when the type of the first assertion statement does not match the database type of the target database, converting the first assertion statement into a target assertion statement according to the database type of the target database; wherein the assertion type of the target assertion statement matches the database type of the target database; obtaining a first assertion test result of the target database according to the target assertion statement. Therefore, when the assertion statement provided by the tester does not match the target database type, the assertion statement can be converted into an assertion statement that matches the target database, ensuring the usability of the assertion test and improving the efficiency of the assertion test.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of database testing, and in particular to a database assertion testing method and device. BACKGROUND

[0002] In a database, an assertion is a constraint condition used to define data integrity in the testing phase, which is used to ensure that the data in the database meets certain conditions or rules to guarantee the correctness and reliability of the data.

[0003] In the automated testing phase, database assertions are usually needed to verify whether the code meets the expectations of the coders. However, in the prior art, the corresponding SQL assertion syntax of different database products is not the same, so the tester needs to confirm the type of each database to be tested and write the corresponding database assertion for testing. For example, if the target is a MySQL database, a MySQL database statement needs to be written for assertion testing, which makes the existing database assertion testing inefficient. Therefore, there is an urgent need for a database assertion testing method that can overcome the problem of low efficiency of assertion testing in the prior art. SUMMARY

[0004] Therefore, the present application provides a database assertion testing method and device to improve the efficiency of assertion testing.

[0005] The technical scheme is as follows:

[0006] In a first aspect, the present application provides a database assertion testing method, which comprises:

[0007] obtaining first assertion data, wherein the first assertion data comprises a first assertion statement and a type of the first assertion statement;

[0008] obtaining a database type of a target database;

[0009] when the type of the first assertion statement does not match the database type of the target database, converting the first assertion statement into a target assertion statement according to the database type of the target database, wherein the assertion type of the target assertion statement matches the database type of the target database;

[0010] obtaining a first assertion test result of the target database according to the target assertion statement.

[0011] Optionally, after obtaining the first assertion data, the method further comprises:

[0012] Verifying correctness of the first assertion statement includes verifying correctness of the first assertion statement based on the Spring Boot framework integrating a third-party Druid data source.

[0013] Optionally, the obtaining the database type of the target database includes:

[0014] The library information of the target database is read by a business layer of the Spring Boot framework, and the library information of the target database includes a data source address and configuration information of the target database.

[0015] The target database is linked based on JDBC code of the Spring Boot framework according to the data source address and the configuration information of the target database, so as to obtain the database type of the target database.

[0016] Optionally, the converting the first assertion statement into a target assertion statement according to the database type of the target database includes:

[0017] String information of the first assertion statement is intercepted to obtain a first assertion keyword.

[0018] The first assertion keyword is converted into a target assertion keyword according to a preset assertion keyword conversion rule, a type of the first assertion statement, and the database type of the target database.

[0019] The first assertion keyword in the first assertion statement is replaced by the target assertion keyword to obtain the target assertion statement.

[0020] Optionally, the method further includes:

[0021] A business test request is sent to a target port of the target database based on an HTTP Client.

[0022] A business test result returned by the target port is received.

[0023] Optionally, after the business test result returned by the target port is received, the method further includes:

[0024] A second assertion test result of the target database is obtained according to the target assertion statement.

[0025] A final test result of the target database is determined according to the first assertion test result, the second assertion test result, and the business test result.

[0026] In a second aspect, an embodiment of the present application provides a database assertion test device, and the device includes:

[0027] The acquisition module is configured to acquire first assertion data, the first assertion data including a first assertion statement and a type of the first assertion statement;

[0028] The acquisition module is further configured to acquire a database type of the target database.

[0029] The conversion module is configured to convert the first assertion statement into a target assertion statement according to the database type of the target database when the type of the first assertion statement does not match the database type of the target database, wherein an assertion type of the target assertion statement matches the database type of the target database.

[0030] The test module is configured to acquire a first assertion test result of the target database according to the target assertion statement.

[0031] Optionally, the conversion module is configured to convert the first assertion statement into a target assertion statement according to the database type of the target database, and specifically includes: intercepting string information of the first assertion statement to obtain a first assertion keyword; converting the first assertion keyword into a target assertion keyword according to a preset assertion keyword conversion rule, the type of the first assertion statement and the database type of the target database; and replacing the first assertion keyword in the first assertion statement with the target assertion keyword to obtain the target assertion statement.

[0032] Optionally, the test module is further configured to:

[0033] send a business test request to a target port of the target database based on an HTTP Client;

[0034] receive a business test result returned by the target port.

[0035] Optionally, the test module is further configured to: after the business test result returned by the target port is received, acquire a second assertion test result of the target database according to the target assertion statement; and determine a final test result of the target database according to the first assertion test result, the second assertion test result and the business test result.

[0036] The above technical solution has the following beneficial effects:

[0037] The embodiment of the present application provides a database assertion test method, when the method is executed, first assertion data is acquired, the first assertion data comprises: a first assertion statement and a type of the first assertion statement; a database type of a target database is acquired; when the type of the first assertion statement does not match the database type of the target database, the first assertion statement is converted into a target assertion statement according to the database type of the target database; wherein, an assertion type of the target assertion statement matches the database type of the target database; a first assertion test result of the target database is acquired according to the target assertion statement. Therefore, when the assertion statement provided by the tester does not match the target database type, the assertion statement can be converted into an assertion statement matched with the target database, the availability of the assertion test is ensured, the tester does not need to recompile a new assertion statement based on the type of the target database, and the efficiency of the assertion test is improved.

[0038] The embodiment of the present application further provides a device corresponding to the above method, which has the same beneficial effects as the above method. BRIEF DESCRIPTION OF DRAWINGS

[0039] To make the technical solutions in the embodiments or the prior art clearer, the accompanying drawings needed in the embodiments or the prior art description will be briefly introduced. Obviously, the accompanying drawings in the following description are only some embodiments of the present application, and other accompanying drawings can be obtained by those skilled in the art without any creative effort.

[0040] Figure 1 A flowchart of a database assertion test method provided by the embodiment of the present application is shown in the figure.

[0041] Figure 2 A flowchart of another database assertion test method provided by the embodiment of the present application is shown in the figure.

[0042] Figure 3 A structural diagram of a database assertion test device provided by the embodiment of the present application is shown in the figure. DETAILED DESCRIPTION

[0043] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without any creative effort fall within the protection scope of the present application.

[0044] In the existing database assertion test, a tester needs to write a corresponding assertion test statement based on the type of a database to be tested, which causes the problem of low efficiency of the assertion test. In order to provide the efficiency of the assertion test, an embodiment of the present application provides a database assertion test method. Please refer to Figure 1 The method can include the following steps.

[0045] Step S100: Obtain first assertion data, the first assertion data including a first assertion statement and a type of the first assertion statement.

[0046] Specifically, the tester can initiate a database assertion test request through an automated test platform or an automated test framework, obtain the first assertion data through a preset interface or a calling instruction based on the database assertion test request, for example, obtain the first assertion data through a preset Application Programming Interface (API) or HttpClient (a client-side programming tool kit supporting the HTTP protocol) function or other calling instructions, wherein the first assertion data includes the first assertion statement and the type of the first assertion statement, and the type of the assertion statement is used to indicate the database type to which the assertion statement is applicable.

[0047] It should be noted that the tester can not pay attention to the type of the database to be tested, and write the assertion statement according to the database SQL syntax mastered by the tester, for example, the tester masters the operation syntax of the MySQL database, that is, the assertion statement can be written using the MySQL database language.

[0048] In an optional embodiment, after step S100, the method can further include verifying the correctness of the first assertion statement.

[0049] In actual application, the correctness of the first assertion statement can be verified based on the Spring Boot framework integrating a third-party Druid data source.

[0050] The Spring Boot framework is an open-source application framework on the Java platform, which provides a container with an inversion of control feature. The Druid data source supports all Java Database Connectivity (JDBC) compatible databases, including Oracle, MySQL, SQL Server and H2, etc. Meanwhile, Druid has a monitoring function, which can observe the running status of the database connection pool and SQL in real time, and help users to troubleshoot problems in the system in time. The embodiment of the present application can parse the first assertion statement through Druid, and check the grammatical correctness of the first assertion statement.

[0051] Step S200: Obtain the database type of the target database.

[0052] The first assertion statement should be matched with the assertion test of the target database. The type of the target database should be obtained for matching verification. Specifically, the above S200 can specifically include the following steps S201 to S202.

[0053] Step S201: Read the library information of the target database through the business layer of the Spring Boot framework. The library information of the target database includes the data source address and configuration information of the target database.

[0054] Step S202: Link the target database based on the JDBC code of the Spring Boot framework according to the data source address and configuration information of the target database, to obtain the database type of the target database.

[0055] The Service layer of the Spring Boot is also called the business layer, which stores business logic processing and does not directly operate the database. It has an interface and an interface implementation class, and provides methods called by the controller layer. In this embodiment, the data source address and related configuration information of the target database can be obtained based on the business logic layer, and the target database can be linked based on the Java Database Connection JDBC according to the data source address and related configuration information, so as to obtain the database type of the target database.

[0056] Step S300: When the type of the first assertion statement does not match the database type of the target database, convert the first assertion statement into a target assertion statement according to the database type of the target database; wherein the assertion type of the target assertion statement matches the database type of the target database.

[0057] It can be understood that when it is judged that the assertion statement does not match the type of the target database to be tested, the assertion statement needs to be converted to meet the assertion test of the target database.

[0058] Specifically, step S300 can specifically include the following steps S301 to S303:

[0059] Step S301: Intercept the string information of the first assertion statement to obtain the first assertion keyword.

[0060] Specifically, the assertion keyword can be intercepted by a JAVA string interception statement, for example, a subString() statement for string interception, or a split() statement for interception. The present application does not limit the interception method of the assertion keyword, and the tester can set it according to the actual situation.

[0061] Step S302: According to the preset assertion keyword conversion rule, the type of the first assertion statement, and the database type of the target database, the first assertion keyword is converted into a target assertion keyword.

[0062] In practical applications, the conversion rule of the assertion keyword should be set in advance. Specifically, the assertion keyword conversion rule can indicate the conversion rule of the assertion keyword under different types of databases. For example, the first assertion keyword is where, and the target database type is MongoDB database type. The preset assertion keyword conversion rule indicates that the first assertion keyword where should be converted into the target assertion keyword find.

[0063] Step S303: Replace the first assertion keyword in the first assertion statement with the target assertion keyword to obtain a target assertion statement.

[0064] The following is a specific example to illustrate step S300:

[0065] The first assertion statement is select number from A where name=“product name”;

[0066] The first keyword is select and where obtained by keyword extraction, and the target keyword is db. and find() obtained by preset conversion rule conversion;

[0067] The target assertion statement is db.A.find({id: product name}, number) obtained by replacing the assertion keyword.

[0068] In practical applications, the conversion of the assertion statement can be based on the Spring Boot framework, and the third-party Druid data source can be integrated by referencing Druid dependency in POM. Druid is configured to realize the calling of multiple data sources. The specific code can be as follows:

[0069] <dependency>

[0070] <groupid>com.alibaba< / groupid>

[0071] <artifactid>druid-spring-boot-starter< / artifactid>

[0072] <version> 1.1.10< / version>

[0073] < / dependency>

[0074] <dependency>

[0075] <groupid>com.alibaba< / groupid>

[0076] <artifactid>druid< / artifactid>

[0077] <version> 1.1.10< / version>

[0078] < / dependency>

[0079] The @MapperScan annotation of the Spring Boot framework is used to realize the scanning and injection of multiple data sources. The data access layer DAO can be used to receive and execute the corresponding database SQL statement. Based on the JAVA code, the target assertion statement corresponding to the target source database type is read and converted, so as to realize the conversion of the assertion statement.

[0080] Step S400: According to the target assertion statement, obtain the first assertion test result of the target database.

[0081] It can be understood that the target assertion statement is a statement matching the target database type, and the first assertion test result can be obtained by executing the assertion statement. According to the above, when the assertion statement provided by the tester does not match the target database type, the embodiment of the application can convert the assertion statement into an assertion statement matching the target database, thereby ensuring the availability of the assertion test and improving the efficiency of the assertion test.

[0082] In an optional embodiment, referring to Figure 2 The embodiment of the application provides another database assertion test method, which can include the method provided in the foregoing embodiments and can further include the following steps:

[0083] Step S500: sending a service test request to the target port of the target database based on the HTTP Client, and receiving a service test result returned by the target port.

[0084] In this step, the HTTP Client can be called to send a service test request to the target port and receive a service test result returned by the port, and the service test result can be saved in the memory. It should be noted that the service test request should be adapted to the target assertion statement in the foregoing assertion test, for example, if the target assertion statement is to capture the inventory quantity of product A, the service test request can be a request to purchase product A or a request to add the inventory of product A; based on this, the service test result returned by the target port is related to the service test request, for example, if the service test request is a request to purchase one piece of product A, the service test result can be the change in the inventory quantity of product A after responding to the service test request. Of course, the above example is only an example based on whether the inventory feedback is correct after testing the purchase of the product, and does not constitute a specific limitation of the embodiment of the application. The tester can set the specific performance of the assertion test and the service test according to the actual test requirements.

[0085] Step S600: obtaining a second assertion test result of the target database according to the target assertion statement; and determining a final test result of the target database according to the first assertion test result, the second assertion test result, and the service test result.

[0086] It can be understood that this step is performed after the service test result returned by the target port, that is, the target database has received the service test request, and the request returns the service test result. Based on this, the target assertion statement is executed again to obtain the second assertion test result, and the final test result of the target database is determined according to the first assertion test result, the second assertion test result, and the service test result.

[0087] Specifically, determining the final test result of the target database according to the first assertion test result, the second assertion test result and the business test result can include: judging whether the first assertion test result and the second assertion test result match the business test request, if not matching, determining that the final test result of the target database fails; if matching, judging again whether the first assertion test result, the second assertion test result and the business test result match, if not matching, determining that the final test result of the target database fails, if matching, determining that the final test result of the target database passes.

[0088] In an optional implementation, the method further includes: saving the final test result of the target database into a preset test report table, so as to facilitate the tester to make further operations on the target database according to the test result.

[0089] In summary, the embodiment of the application provides a database assertion test method, when the method is executed, first assertion data is acquired, the first assertion data includes: a first assertion statement and a type of the first assertion statement; a database type of a target database is acquired; when the type of the first assertion statement does not match the database type of the target database, the first assertion statement is converted into a target assertion statement according to the database type of the target database; wherein an assertion type of the target assertion statement matches the database type of the target database; a first assertion test result of the target database is acquired according to the target assertion statement. It can be seen that when the assertion statement provided by the tester does not match the target database type, the assertion statement can be converted into an assertion statement matching the target database, the usability of the assertion test is ensured, and the efficiency of the assertion test is improved.

[0090] Corresponding to the above method, the embodiment of the application further provides a database assertion test device, please refer to Figure 3 , which shows the structure diagram of the device, the device can include:

[0091] The acquisition module 301 is configured to acquire first assertion data, the first assertion data includes: a first assertion statement and a type of the first assertion statement.

[0092] The acquisition module 301 is further configured to acquire a database type of a target database.

[0093] The conversion module 302 is configured to convert the first assertion statement into a target assertion statement according to the database type of the target database when the type of the first assertion statement does not match the database type of the target database; wherein an assertion type of the target assertion statement matches the database type of the target database.

[0094] The test module 303 is configured to acquire a first assertion test result of the target database according to the target assertion statement.

[0095] In an optional implementation, the apparatus further comprises a verification module configured to verify the correctness of the first assertion statement. Specifically, the verification module is specifically configured to verify the correctness of the first assertion statement based on the Spring Boot framework integrating the third-party Druid data source.

[0096] In an optional implementation, the obtaining module 301 is specifically configured to read the library information of the target database through a business layer of the Spring Boot framework, wherein the library information of the target database comprises a data source address and configuration information of the target database; and link the target database based on a JDBC code of the Spring Boot framework according to the data source address and the configuration information of the target database, to obtain the database type of the target database.

[0097] In an optional implementation, the conversion module 302 is specifically configured to intercept the string information of the first assertion statement to obtain the first assertion keyword; convert the first assertion keyword into a target assertion keyword according to a preset assertion keyword conversion rule, the type of the first assertion statement and the database type of the target database; and replace the first assertion keyword in the first assertion statement with the target assertion keyword to obtain a target assertion statement.

[0098] In an optional implementation, the testing module 303 is further configured to send a business test request to a target port of the target database based on an HTTP Client; and receive a business test result returned by the target port.

[0099] In an optional implementation, the testing module 303 is further configured to, after receiving the business test result returned by the target port, obtain a second assertion test result of the target database according to the target assertion statement; and determine a final test result of the target database according to the first assertion test result, the second assertion test result and the business test result.

[0100] It should be noted that the steps performed by each module in the database assertion testing apparatus provided by the embodiments of the present application and the related technical features correspond to the methods provided by the embodiments of the present application. The description of the apparatus part can be referred to the foregoing method part embodiments, and will not be repeated here.

[0101] In summary, the embodiment of the present application provides a database assertion test device, the device comprises: an acquisition module, configured to acquire first assertion data, the first assertion data comprising: a first assertion statement and a type of the first assertion statement; the acquisition module is further configured to acquire a database type of a target database; a conversion module, configured to convert the first assertion statement into a target assertion statement according to the database type of the target database when the type of the first assertion statement does not match the database type of the target database; wherein the assertion type of the target assertion statement matches the database type of the target database; and a test module, configured to acquire a first assertion test result of the target database according to the target assertion statement. Thus, when the assertion statement provided by the tester does not match the target database type, the device can convert the assertion statement into an assertion statement that matches the target database, ensuring the usability of the assertion test and improving the efficiency of the assertion test.

[0102] The various embodiments in the specification are described in a progressive manner, and each embodiment focuses on the difference from other embodiments. The same or similar parts between the embodiments can be referred to each other.

[0103] Those skilled in the art can understand that the flowchart shown in the figure is only one example in which the embodiments of the present application can be implemented, and the scope of application of the embodiments of the present application is not limited by any aspect of the flowchart.

[0104] In several embodiments provided in the present application, it should be understood that the disclosed methods, devices and equipment can be implemented by other ways. For example, the above-described device embodiments are only schematic, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the shown or discussed each other can be indirect coupling or communication connection through some communication interface, device or unit, which can be electrical, mechanical or other forms.

[0105] The above description of the disclosed embodiments enables a person skilled in the art to implement or use the present application. Various modifications to the embodiments will be apparent to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method of testing database assertions, characterized by, The method comprises: obtaining first assertion data, the first assertion data comprising: a first assertion statement and a type of the first assertion statement; obtaining a database type of a target database; when the type of the first assertion statement does not match the database type of the target database, converting the first assertion statement into a target assertion statement according to the database type of the target database; wherein an assertion type of the target assertion statement matches the database type of the target database; obtaining a first assertion test result of the target database according to the target assertion statement; sending a business test request to a target port of the target database based on an HTTP Client; the business test request is adapted to the target assertion statement; receiving a business test result returned by the target port; obtaining a second assertion test result of the target database according to the target assertion statement; determining a final test result of the target database according to the first assertion test result, the second assertion test result, and the business test result.

2. The method of claim 1, wherein, After the first assertion data is obtained, the method further comprises: verifying the correctness of the first assertion statement, comprising: verifying the correctness of the first assertion statement based on a Spring Boot framework integrating a third-party Druid data source.

3. The method of claim 1, wherein, The database type of the target database is obtained by: reading library information of the target database through a business layer of a Spring Boot framework, the library information of the target database comprising: a data source address and configuration information of the target database; linking the target database based on a JDBC code of the Spring Boot framework according to the data source address and the configuration information of the target database, to obtain the database type of the target database.

4. The method according to any one of claims 1-3, characterized by, The first assertion statement is converted into a target assertion statement according to the database type of the target database, comprising: obtaining a first assertion keyword by intercepting string information of the first assertion statement; converting the first assertion keyword into a target assertion keyword according to a preset assertion keyword conversion rule, the type of the first assertion statement, and the database type of the target database; replacing the first assertion keyword in the first assertion statement with the target assertion keyword to obtain the target assertion statement.

5. A test apparatus for database assertions, characterized by The device comprises: an obtaining module, configured to obtain first assertion data, the first assertion data comprising: a first assertion statement and a type of the first assertion statement; the obtaining module is further configured to obtain a database type of a target database; a conversion module, configured to convert the first assertion statement into a target assertion statement according to the database type of the target database when the type of the first assertion statement does not match the database type of the target database; wherein an assertion type of the target assertion statement matches the database type of the target database; The test module is configured to obtain a first assertion test result of the target database according to the target assertion statement, send a business test request to a target port of the target database based on an HTTP Client, match the business test request with the target assertion statement, receive a business test result returned by the target port, obtain a second assertion test result of the target database according to the target assertion statement, and determine a final test result of the target database according to the first assertion test result, the second assertion test result and the business test result.

6. The apparatus of claim 5, wherein, The conversion module is configured to convert the first assertion statement into a target assertion statement according to a database type of the target database, and specifically includes: The conversion module is configured to convert the first assertion statement into a target assertion statement according to a database type of the target database, and specifically includes: The conversion module is configured to convert the first assertion statement into a target assertion statement according to a database type of the target database, and specifically includes: The conversion module is configured to convert the first assertion statement into a target assertion statement according to a database type of the target database, and specifically includes: The conversion module is configured to convert the first assertion statement into a target assertion statement according to a database type of the target database, and specifically includes: The conversion module is configured to convert the first assertion statement into a target assertion statement according to a database type of the target database, and specifically includes: The conversion module is configured to convert the first assertion statement into a target assertion statement according to a database type of the target database, and specifically includes: The conversion module is configured to convert the first assertion statement into a target assertion statement according to a database type of the target database, and specifically includes: The conversion module is configured to convert the first assertion statement into a target assertion statement according to a database type of the target database, and specifically includes: The conversion module is configured to convert the first assertion statement into a target assertion statement according to a database type of the target database, and specifically includes: The conversion module is configured to convert the first assertion statement into a target assertion statement according to a database type of the target database, and specifically includes: The conversion module is configured to convert the first assertion statement into a target assertion statement according to a database type of the target database, and specifically includes: The conversion module is configured to convert the first assertion statement into a target assertion statement according to a database type of the target database, and specifically includes: The conversion module is configured to convert the first assertion statement into a target assertion statement according to a database

Images