CN114385483B - Database interface testing method, device, equipment and storage medium - Google Patents

Abstract

The present application relates to a database interface testing method, device, equipment and storage medium, and relates to the field of database testing. The database interface testing method comprises: running a test case instance of a database to be tested; during the running process, using target parameters to call the general interface of the database to be tested; identifying the operation type interface corresponding to the target parameter through the general interface, and calling the operation type interface to obtain test data and return it; testing the test data through the test case instance. The present application is used to solve the problem of needing to rewrite test cases when testing different databases.

Description

Database interface testing method, device, equipment and storage medium

Technical Field

The present application relates to the field of database testing, and in particular to a database interface testing method, device, equipment and storage medium.

Background Art

In order to meet the growing performance needs of customers, the blockchain platform continues to break through performance bottlenecks, including continuous optimization and transformation of storage modules, and design of a variety of KV (Key-Value, key-value pair storage data) databases that rely on underlying storage. Each KV database provides a complete set of database interfaces for external service calls, and the database can be tested separately to compare performance optimization effects, which brings a lot of repeated testing work.

Generally speaking, when it comes to database testing, there are many open source performance benchmarking tools such as sysbench and unit testing tools such as DBUnit in the industry. However, there are no ready-made open source testing tools for database integration testing or interface testing.

The completeness test of database functions is generally conducted by covering the interfaces provided by the database, designing the value range of the corresponding interface parameters, and splicing multiple interfaces for interface scenario testing. If the test object changes to a new database, the test scripts of this part of the database cannot be reused. Generally, the test scenario will be redesigned to verify the functional completeness of another database. This part of the work brings a lot of repeated testing work.

Summary of the invention

The present application provides a database interface testing method, apparatus, device and storage medium to solve the problem of needing to rewrite test cases when testing different databases.

In a first aspect, an embodiment of the present application provides a database interface testing method, comprising:

Run the test case instance of the database to be tested;

During the operation, the universal interface of the database to be tested is called using target parameters;

Identify the operation type interface corresponding to the target parameter through the general interface, and call the operation type interface to obtain test data and return it;

The test data is tested through the test case instance.

Optionally, before identifying the operation type interface corresponding to the target parameter through the universal interface, the method further includes:

The operation type interface is encapsulated according to the format of the general interface.

Optionally, after testing the test data through the test case instance, the method further includes:

Get test results;

A test report is generated according to the test results.

Optionally, the operation type interface includes a query and modify type interface;

During the operation, the universal interface of the database to be tested is called using target parameters, including:

During the operation, the query interface and the modification interface of the database to be tested are called using the target parameters;

The step of identifying the operation type interface corresponding to the target parameter through the general interface includes:

The query and modification type interface corresponding to the target parameter is identified through the query interface and the modification interface.

Optionally, the operation type interface includes a query and delete type interface;

During the operation, the universal interface of the database to be tested is called using target parameters, including:

During the operation, the query interface and the deletion interface of the database to be tested are called using the target parameters;

The step of identifying the operation type interface corresponding to the target parameter through the general interface includes:

The query and delete type interface corresponding to the target parameter is identified through the query interface and the delete interface.

Optionally, during the running process, before calling the universal interface of the database to be tested with the target parameter, the method further includes:

The general interface is configured, wherein the general interface includes at least one of adding an interface, deleting an interface, modifying an interface, and querying an interface.

Optionally, before running the test case instance of the database to be tested, the method further includes:

The test case instance is obtained from a general test case set, wherein the general test case set includes at least one of a test case for general database operations, a test case for scenario-based database operations, and a test case for a specified database.

In a second aspect, an embodiment of the present application provides a database interface testing device, including:

The running module is used to run the test case instance of the database to be tested;

A calling module, used to call the general interface of the database to be tested using target parameters during operation;

An identification module, used to identify the operation type interface corresponding to the target parameter through the general interface, and call the operation type interface to obtain test data and return it;

A processing module is used to test the test data through the test case instance.

Optionally, the database interface testing device further includes a packaging module;

The encapsulation module is used to encapsulate the operation type interface according to the format of the general interface.

Optionally, the database interface testing device further includes a first acquisition module and a generation module;

The first acquisition module is used to obtain the test result;

The generating module is used to generate a test report according to the test result.

Optionally, the operation type interface includes a query and modify type interface;

The calling module is specifically used to call the query interface and modification interface of the database to be tested using target parameters during the running process;

The identification module is specifically used to identify the query and modification type interface corresponding to the target parameter through the query interface and the modification interface, and call the query and modification type interface to obtain test data and return it.

Optionally, the operation type interface includes a query and delete type interface;

The calling module is specifically used to call the query interface and the deletion interface of the database to be tested using the target parameters during the running process;

The identification module is specifically used to identify the query and delete type interface corresponding to the target parameter through the query interface and the delete interface, and call the query and delete type interface to obtain test data and return it.

Optionally, the database interface testing device further includes a configuration module;

The configuration module is used to configure the general interface, wherein the general interface includes at least one of adding an interface, deleting an interface, modifying an interface, and querying an interface.

Optionally, the database interface testing device further includes a second acquisition module;

The second acquisition module is used to acquire the test case instance from a general test case set, wherein the general test case set includes at least one of a test case for general database operations, a test case for scenario-based database operations, and a test case for a specified database.

In a third aspect, an embodiment of the present application provides an electronic device, comprising: a processor, a memory, and a communication bus, wherein the processor and the memory communicate with each other via the communication bus;

The memory is used to store computer programs;

The processor is used to execute the program stored in the memory to implement the database interface testing method described in the first aspect.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the database interface testing method described in the first aspect.

The above technical solution provided by the embodiment of the present application has the following advantages over the prior art: the method provided by the embodiment of the present application runs a test case instance of the database to be tested, and during the running process, uses target parameters to call the general interface of the database to be tested, identifies the operation type interface corresponding to the target parameter through the general interface, and calls the operation type interface to obtain test data and return it, and tests the test data through the test case instance.

Compared with the prior art, when testing different databases, it is necessary to rewrite the test cases. In this application, it is not necessary to rewrite the test cases. By calling the general interface of the database to be tested during the process of running the test case instance of the database to be tested, and performing subsequent operations through the general interface, the test case instance only needs to be written according to the general interface, which is applicable to different databases, and can implement the same test case instance to test different databases. The general interfaces of different databases are the same, and the operation type interfaces of different databases are different. The specific operations of different databases are to identify the operation type interface corresponding to the target parameter through the general interface, and to call the operation type interface to obtain test data and return it, so as to call the operation type interface through the general interface, and then implement the test case instance to test the specific database to be tested. It is realized that the same test case instance tests different databases to verify the functional completeness of the database, without the need to write a large number of test cases, which greatly improves the test efficiency and shortens the database object function verification cycle.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

FIG1 is a schematic diagram of the architecture of a database interface testing system in an embodiment of the present application;

FIG2 is a schematic diagram of a method flow chart of a database interface test in an embodiment of the present application;

FIG3 is a schematic diagram of a method flow chart of a database interface test in a specific embodiment of the present application;

FIG4 is a schematic diagram of a method flow chart of a database interface test in a specific embodiment of the present application;

FIG5 is a schematic diagram of the structure of a database interface testing device in an embodiment of the present application;

FIG. 6 is a schematic diagram of the structure of an electronic device in an embodiment of the present application.

DETAILED DESCRIPTION

In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

In an embodiment of the present application, a database interface testing method is provided, which is applied to a database interface testing system.

In an embodiment of the present application, as shown in FIG1 , the database interface testing system includes a use case set, an execution layer, and an adaptation layer.

Test case set: mainly composed of test cases, each test case consists of parameter configuration and test script. Parameter configuration can directly specify the number of concurrent threads and thread loops for the test case. Parameter configuration can be set as needed.

Execution layer: mainly performs test case execution. The execution layer can set the random concurrent execution mode of test cases to simulate random read and write operations on the database in the test scenario. The test report interpretation module is responsible for collecting test results and submitting them to the visualization tool for test result reporting. The test case execution module will execute pre-defined test cases. The interface implementation part will convert the database operations of general operations into operations of a specific database, and finally feed back the test results to the test report collection module. The report will finally display the test results in a visual way.

Adaptation layer: includes common, utils and dbs. common provides some basic common operations and encapsulation of some small tool operations. utils encapsulates some common operations on common databases. dbs connects to the database objects to be tested and encapsulation of these database interfaces.

In the embodiment of the present application, as shown in FIG2 , the method flow of the database interface test mainly includes:

Step 201: Run the test case instance of the database to be tested.

In a specific embodiment, before running the test case instance of the database to be tested, the database interface testing method also includes: obtaining a test case instance from a general test case set, wherein the general test case set includes at least one of test cases for general database operations, test cases for scenario-based database operations, and test cases for specified databases.

Test cases for common database operations refer to test cases for common database operations such as adding, deleting, modifying, and querying. Test cases for scenario-based database operations refer to test cases for scenario-based database operations such as random concurrent execution mode. Test cases for specified databases refer to test cases that only work for specified databases, and decorators such as pytest.mark.skip or other methods are required to filter out unmatched databases. The set of common test cases is defined in advance.

There is no need to rewrite the test case instance each time when testing different databases. You only need to obtain the test case instance suitable for the database to be tested from the pre-defined general test case set.

Step 202: During the running process, the general interface of the database to be tested is called using target parameters.

The target parameter can be the type of the general interface that needs to be called, for example, the target parameter is the query interface and the modification interface. The target parameter can also be the operation type corresponding to the operation type interface of the database to be tested, for example, the target parameter is the query and modification type. The target parameter can also be an expression described by the operation type interface according to the format of the general interface. For example, the target parameter is operation type interface A = k1*general interface a+k2*general interface b, which is an expression describing the operation type interface A according to the format of general interface a and general interface b, and k1 and k2 are constants.

The type of the general interface to be called can be determined according to the target parameter. The target parameter can also be other parameters as needed, and the present application does not limit the specific content of the target parameter.

In a specific embodiment, during the running process, before calling the universal interface of the database to be tested with target parameters, the database interface testing method also includes: configuring the universal interface, wherein the universal interface includes at least one of adding interface, deleting interface, modifying interface and querying interface.

Adding an interface, deleting an interface, modifying an interface, and querying an interface are common database operations that are used frequently.

The general interface may include general database operations, such as Insert, Delete, Update, Select, Write, Read, Reset, Roolback, Close, New, etc. The general interface may also include general operations of the iterators provided by the database, such as NewIterator, Seek, First, Last, Next, Prev, Key, Value, Release, etc.

Common interface is applicable to different databases.

Step 203: Identify the operation type interface corresponding to the target parameter through the general interface, and call the operation type interface to obtain test data and return it.

The target parameter can be the type of the general interface that needs to be called, for example, the target parameter is the query interface and the modification interface. The target parameter can also be the operation type corresponding to the operation type interface of the database to be tested, for example, the target parameter is the query and modification type. The target parameter can also be an expression described by the operation type interface according to the format of the general interface. For example, the target parameter is operation type interface A = k1*general interface a+k2*general interface b, which is an expression describing the operation type interface A according to the format of general interface a and general interface b, and k1 and k2 are constants.

The type of operation type interface to be called can be determined according to the target parameter. The target parameter can also be other parameters as needed, and the present application does not limit the specific content of the target parameter.

The test data may be acquired by calling the operation type interface through the general interface, and the test data may be acquired from the database to be tested by calling the operation type interface through the general interface.

In a specific embodiment, before identifying the operation type interface corresponding to the target parameter through the general interface, the database interface testing method further includes: encapsulating the operation type interface according to the format of the general interface.

According to the format of the general interface, the operation type interface is encapsulated. For example, operation type interface A = k1*general interface a + k2*general interface b. Operation type interface A is encapsulated according to the format of general interface a and general interface b. k1 and k2 are constants. Database attributes will be directly written into the interface for creating the database.

In a specific embodiment, the operation type interface includes a query and modify type interface. During the operation, the general interface of the database to be tested is called using the target parameter, including: during the operation, the query interface and the modify interface of the database to be tested are called using the target parameter. Through the general interface, the operation type interface corresponding to the target parameter is identified, including: through the query interface and the modify interface, the query and modify type interface corresponding to the target parameter is identified.

When the operation type interface includes a query and modify type interface, the common interfaces that need to be called are the query interface and the modify interface. Through the query interface and the modify interface, the query and modify type interface corresponding to the target parameter is identified, and the query and modify type interface is called to obtain test data and return it.

In a specific embodiment, the operation type interface includes a query and delete type interface. During the operation, the general interface of the database to be tested is called using the target parameter, including: during the operation, the query interface and the delete interface of the database to be tested are called using the target parameter. Through the general interface, the operation type interface corresponding to the target parameter is identified, including: through the query interface and the delete interface, the query and delete type interface corresponding to the target parameter is identified.

When the operation type interface includes the query and delete type interface, the common interfaces that need to be called are the query interface and the delete interface. Through the query interface and the delete interface, the query and delete type interface corresponding to the target parameter is identified, and the query and delete type interface is called to obtain the test data and return it.

As required, the operation type interface may further include other interfaces, which can be used to call the general interface corresponding to the operation type interface, and to call the operation type interface through the general interface to obtain test data and return it.

Step 204: Test the test data through the test case instance.

In a specific embodiment, after testing the test data through the test case instance, the database interface testing method further includes: obtaining the test result; and generating a test report according to the test result.

The test report is displayed through a visualization tool.

In a specific embodiment, as shown in FIG3 , the method flow of database interface testing mainly includes:

Step 301, obtaining a test case instance from a general test case set.

Step 302: Run the test case instance of the database to be tested.

Step 303: During the running process, the general interface of the database to be tested is called using the target parameters.

Step 304: Identify the operation type interface corresponding to the target parameter through the general interface, and call the operation type interface to obtain test data and return it.

Step 305: Test the test data through the test case instance.

Step 306, obtaining test results.

Step 307: Generate a test report based on the test results.

In a specific embodiment, as shown in FIG4 , the method flow of database interface testing mainly includes:

Step 401 , encapsulate the interface of the database db1 to be tested according to the format of the general interface of the test framework, and define the database properties of db1 in the configuration file of db1 , so that the properties defined in advance take effect when starting db1 .

Step 402: Generate a test case instance of db1 in the test framework according to the defined general test case template.

Step 403: execute the test case instance and obtain a test report.

In summary, the method provided in the embodiment of the present application runs a test case instance of the database to be tested. During the running process, the general interface of the database to be tested is called using the target parameters. Through the general interface, the operation type interface corresponding to the target parameters is identified, and the operation type interface is called to obtain test data and return it, and the test data is tested through the test case instance.

Compared with the prior art, when testing different databases, it is necessary to rewrite the test cases. In this application, it is not necessary to rewrite the test cases. By calling the general interface of the database to be tested during the process of running the test case instance of the database to be tested, and performing subsequent operations through the general interface, the test case instance only needs to be written according to the general interface, which is applicable to different databases, and can implement the same test case instance to test different databases. The general interfaces of different databases are the same, and the operation type interfaces of different databases are different. The specific operations of different databases are to identify the operation type interface corresponding to the target parameter through the general interface, and to call the operation type interface to obtain test data and return it, so as to call the operation type interface through the general interface, and then implement the test case instance to test the specific database to be tested. It is realized that the same test case instance tests different databases to verify the functional completeness of the database, without the need to write a large number of test cases, which greatly improves the test efficiency and shortens the database object function verification cycle.

Based on the same concept, a database interface testing device is provided in the embodiment of the present application. The specific implementation of the device can refer to the description of the method embodiment part, and the repeated parts will not be repeated. As shown in FIG5, the device mainly includes:

Running module 501, used to run the test case instance of the database to be tested;

A calling module 502 is used to call the general interface of the database to be tested using target parameters during the running process;

An identification module 503 is used to identify the operation type interface corresponding to the target parameter through the general interface, and call the operation type interface to obtain test data and return it;

The processing module 504 is used to test the test data through the test case instance.

Optionally, the database interface testing device further includes a packaging module;

The encapsulation module is used to encapsulate the operation type interface according to the format of the general interface.

Optionally, the database interface testing device further includes a first acquisition module and a generation module;

The first acquisition module is used to obtain the test result;

The generating module is used to generate a test report according to the test result.

Optionally, the operation type interface includes a query and modify type interface;

The calling module is specifically used to call the query interface and modification interface of the database to be tested using target parameters during the running process;

The identification module is specifically used to identify the query and modification type interface corresponding to the target parameter through the query interface and the modification interface, and call the query and modification type interface to obtain test data and return it.

Optionally, the operation type interface includes a query and delete type interface;

The calling module is specifically used to call the query interface and the deletion interface of the database to be tested using the target parameters during the running process;

The identification module is specifically used to identify the query and delete type interface corresponding to the target parameter through the query interface and the delete interface, and call the query and delete type interface to obtain test data and return it.

Optionally, the database interface testing device further includes a configuration module;

The configuration module is used to configure the general interface, wherein the general interface includes at least one of adding an interface, deleting an interface, modifying an interface, and querying an interface.

Optionally, the database interface testing device further includes a second acquisition module;

The second acquisition module is used to acquire the test case instance from a general test case set, wherein the general test case set includes at least one of a test case for general database operations, a test case for scenario-based database operations, and a test case for a specified database.

Based on the same concept, an electronic device is also provided in an embodiment of the present application, as shown in FIG6 , the electronic device mainly includes: a processor 601, a memory 602 and a communication bus 603, wherein the processor 601 and the memory 602 communicate with each other through the communication bus 603. The memory 602 stores a program executable by the processor 601, and the processor 601 executes the program stored in the memory 602 to implement the following steps:

Run the test case instance of the database to be tested; during the running process, use the target parameters to call the general interface of the database to be tested; through the general interface, identify the operation type interface corresponding to the target parameters, and call the operation type interface to obtain test data and return it; test the test data through the test case instance.

The communication bus 603 mentioned in the above electronic device can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus 603 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in FIG6 , but it does not mean that there is only one bus or one type of bus.

The memory 602 may include a random access memory (RAM) or a non-volatile memory, such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the processor 601.

The above-mentioned processor 601 can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc., and can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.

In another embodiment of the present application, a computer-readable storage medium is provided, in which a computer program is stored. When the computer program runs on a computer, the computer executes the database interface testing method described in the above embodiment.

In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instruction is loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network or other programmable device. The computer instruction can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instruction is transmitted from a website site, a computer, a server or a data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server, a data center, etc. that contains one or more available media integration. The available medium can be a magnetic medium (such as a floppy disk, a hard disk, a magnetic tape, etc.), an optical medium (such as a DVD) or a semiconductor medium (such as a solid-state hard disk), etc.

It should be noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

The foregoing is merely a specific embodiment of the present invention, which enables those skilled in the art to understand or implement the present invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features claimed herein.

Claims (8)

1. A database interface testing method, characterized by comprising: Running a test case instance of the database to be tested, wherein the test case instance is obtained from a general test case set; During the operation, the universal interface of the database to be tested is called using target parameters; Identify the operation type interface corresponding to the target parameter through the general interface, and call the operation type interface to obtain test data and return it; Testing the test data through the test case instance; The target parameter is the type of the general interface to be called, or the target parameter is the operation type corresponding to the operation type interface of the database to be tested, or the target parameter is an expression described by the operation type interface according to the format of the general interface; The universal interface at least includes an add interface, a delete interface, a modify interface and a query interface, and the universal interface is applicable to different databases; The method further includes: encapsulating an operation type interface according to a format of a general interface, wherein the operation type interface = a first general interface + a second general interface. 2. The database interface testing method according to claim 1, characterized in that after the test data is tested by the test case instance, the method further comprises: Get test results; A test report is generated according to the test results. 3. The database interface testing method according to claim 1, wherein the operation type interface comprises a query and modify type interface; During the operation, the universal interface of the database to be tested is called using target parameters, including: During the operation, the query interface and the modification interface of the database to be tested are called using the target parameters; The step of identifying the operation type interface corresponding to the target parameter through the general interface includes: The query and modification type interface corresponding to the target parameter is identified through the query interface and the modification interface. 4. The database interface testing method according to claim 1, wherein the operation type interface comprises a query and delete type interface; During the operation, the universal interface of the database to be tested is called using target parameters, including: During the operation, the query interface and the deletion interface of the database to be tested are called using the target parameters; The step of identifying the operation type interface corresponding to the target parameter through the general interface includes: The query and delete type interface corresponding to the target parameter is identified through the query interface and the delete interface. 5. The database interface testing method according to claim 1 is characterized in that the general test case set includes at least one of a test case for general database operations, a test case for scenario-based database operations, and a test case for a specified database. 6. A database interface testing device, comprising: A running module, used to run a test case instance of the database to be tested, wherein the test case instance is obtained from a general test case set; A calling module, used to call the general interface of the database to be tested using target parameters during operation; An identification module, used to identify the operation type interface corresponding to the target parameter through the general interface, and call the operation type interface to obtain test data and return it; A processing module, used for testing the test data through the test case instance; The target parameter is the type of the general interface to be called, or the target parameter is the operation type corresponding to the operation type interface of the database to be tested, or the target parameter is an expression described by the operation type interface according to the format of the general interface; The general interface includes at least an add interface, a delete interface, a modify interface and a query interface, and the general interface is applicable to different databases; The device further comprises: encapsulating an operation type interface according to a format of a general interface, wherein the operation type interface = a first general interface + a second general interface. 7. An electronic device, comprising: a processor, a memory and a communication bus, wherein the processor and the memory communicate with each other via the communication bus; The memory is used to store computer programs; The processor is used to execute the program stored in the memory to implement the database interface testing method according to any one of claims 1 to 5. 8. A computer-readable storage medium storing a computer program, wherein when the computer program is executed by a processor, the database interface testing method according to any one of claims 1 to 5 is implemented.