WO2021189348A1

WO2021189348A1 - Database synchronization test method and apparatus, and computer device and storage medium

Info

Publication number: WO2021189348A1
Application number: PCT/CN2020/081367
Authority: WO
Inventors: 梁焕勋
Original assignee: 深圳市欢太科技有限公司; Oppo广东移动通信有限公司
Priority date: 2020-03-26
Filing date: 2020-03-26
Publication date: 2021-09-30
Also published as: CN115136120A

Abstract

A database synchronization test method and apparatus, and a computer device and a storage medium, relating to the technical field of computers. The method comprises: obtaining a unique identifier of a target test case from a configuration file, the target test case being used for testing whether data between at least two databases is synchronized (201); according to the unique identifier of the target test case, invoking the target test case by means of a target interface, the target interface providing test logic of the target test case (202); and according to the target test result outputted after invoking the target test case, performing a synchronization test on the data between the at least two databases (203). According to the method, in a scenario where data between at least two databases is synchronized, a synchronization test on the data between the at least two databases is achieved by means of a target test case and a target interface, avoiding the rewriting of each test case in the at least two databases, thereby improving the extensibility of each test case in this scenario.

Description

Database synchronization test method, device, computer equipment and storage medium

Technical field

This application relates to the field of computer technology, in particular to a database synchronization test method, device, computer equipment and storage medium.

Background technique

With the development of the computer technology field, the database is an inaccessible tool in the field of computer equipment, and developers can test the database through test cases.

At present, code designers can create various test cases in computer equipment, and run the created test cases in computer equipment. For example, different programming language environments, such as Java language environment, Kotlin language environment, C++ language environment, etc., can be run in the computer equipment. When a database needs to be tested, developers can write test cases in different programming language environments and run them in computer equipment to test the database.

For the scenario of data synchronization between multiple databases, how to use test cases to perform synchronization tests on the databases, there is currently no perfect solution.

Summary of the invention

The embodiments of the present application provide a database synchronization test method, device, computer equipment, and storage medium, which can implement synchronization testing in a scenario of data synchronization between multiple databases, and improve the scalability of test cases in this scenario. The technical solution is as follows:

On the one hand, an embodiment of the present application provides a database synchronization test method, the method is executed by a computer device, and the method includes:

Obtaining the unique identifier of the target test case from the configuration file, where the target test case is used to test whether the data between at least two databases is synchronized;

According to the unique identifier of the target test case, call the target test case through a target interface, and the target interface provides the test logic of the target test case;

According to the target test result output after invoking the target test case, a synchronization test is performed on the data between the at least two databases.

On the other hand, an embodiment of the present application provides a database synchronization test device, the device is used in a computer device, and the device includes:

An identification acquisition module, configured to acquire a unique identification of a target test case from a configuration file, the target test case being used to test whether the data between at least two databases is synchronized;

The calling module is used to call the target test case through a target interface according to the unique identifier of the target test case, and the target interface provides the test logic of the target test case;

The test module is configured to perform a synchronization test on the data between the at least two databases according to the target test result output after calling the target test case.

In another aspect, an embodiment of the present application also provides a computer device, the computer device includes a processor and a memory, the memory stores at least one instruction, at least one program, code set, or instruction set, the at least one The instructions, the at least one program, the code set or the instruction set are loaded and executed by the processor to implement the database synchronization test method as described above.

In another aspect, an embodiment of the present application also provides a computer-readable storage medium, and the storage medium stores at least one instruction, at least one program, code set, or instruction set, and the at least one instruction, the at least one The program, the code set or the instruction set is loaded and executed by the processor to realize the database synchronization test method as described above.

The beneficial effects brought about by the technical solutions provided by the embodiments of the present application include at least:

By obtaining the unique identifier of the target test case used to test whether the data between at least two databases is synchronized, the target test case is called using the target interface that provides the test logic of the target test case, and the target test result is output, and the target is passed The test result performs a synchronization test on the data between at least two databases. In the scenario where the data between at least two databases is synchronized, the application can realize the synchronization test of the data between at least two databases through the target test case and the target interface, which avoids the need for each test case in the at least two databases. The rewriting of, thus improving the scalability of each test case in this scenario.

Description of the drawings

In order to more clearly describe the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings that need to be used in the description of the embodiments. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative work.

Fig. 1 is a schematic structural diagram of a database synchronization provided by an exemplary embodiment of the present application;

FIG. 2 is a method flowchart of a database synchronization test method related to an exemplary embodiment of the present application;

FIG. 3 is a method flowchart of a database synchronization test method related to an exemplary embodiment of the present application;

FIG. 4 is a schematic diagram of an interface of a test case calling interface related to an exemplary embodiment of the present application;

FIG. 5 is a schematic diagram of an interface of a test case calling interface related to an exemplary embodiment of the present application;

Fig. 6 is a schematic structural diagram of a computer device provided by an exemplary embodiment of the present application;

FIG. 7 is a flowchart of a method for performing a database synchronization test method performed by a computer device in FIG. 6 according to an exemplary embodiment of the present application;

FIG. 8 is a structural block diagram of a database synchronization test device provided by an exemplary embodiment of the present application;

Fig. 9 is a schematic structural diagram of a computer device provided by an exemplary embodiment of the present application.

Detailed ways

The exemplary embodiments will be described in detail here, and examples thereof are shown in the accompanying drawings. When the following description refers to the accompanying drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementation manners described in the following exemplary embodiments do not represent all implementation manners consistent with the present application. On the contrary, they are merely examples of devices and methods consistent with some aspects of the application as detailed in the appended claims.

The solution provided in this application can be used in a real-world scenario in which data from multiple databases are synchronized to call test cases in the process of program code development. In order to facilitate understanding, the following first briefly introduces some terms and scenario architecture.

Test case (Test Case): refers to the source code created when testing a software product, which can include code such as test targets, test environment, input data, test steps, expected results, test scripts, etc. In other words, a test case is a set of test inputs, execution conditions, and expected results prepared for a certain source code to be tested, which can be used to verify whether the function of the source code to be tested is normal.

Please refer to FIG. 1, which shows a schematic structural diagram of a database synchronization provided by an exemplary embodiment of the present application. As shown in Fig. 1, a computer device 100 and several databases 110 are included.

Optionally, the aforementioned computer device 100 may be a terminal device installed with development tools and having test cases written, for example, the computer device may be a mobile phone, a tablet computer, a notebook computer, a desktop computer, and so on.

For example, the above-mentioned computer device 100 also includes a test case writing interface 101, and a developer can write a test case for any one of several databases 110 in the test case writing interface 101, so as to realize the test case.

Optionally, in the foregoing several databases 110, data between at least two databases needs to be synchronized. For example, the data in database one is synchronized with the data in database two. The data in database two is generally fixed. The data in database one is prone to increase or decrease. When the data in database one increases or decreases, database two The data in is also increased or decreased in the same way.

Optionally, the computer device 100 and several databases 110 may be connected through a communication network, and the communication network may be a wireless network or a wired network.

Optionally, the aforementioned wireless network or wired network uses standard communication technologies and/or protocols. The network is usually the Internet, but it can also be any network, including but not limited to Local Area Network (LAN), Metropolitan Area Network (MAN), Wide Area Network (MAN), mobile, wired or wireless networks , Private network or any combination of virtual private network. In some embodiments, technologies and/or formats including HyperText Mark-up Language (HTML), Extensible Markup Language (XML), etc. are used to represent data exchanged over the network. In addition, you can also use such things as Secure Socket Layer (SSL), Transport Layer Security (TLS), Virtual Private Network (VPN), Internet Protocol Security (IPsec) Wait for conventional encryption technology to encrypt all or some links. In other embodiments, customized and/or dedicated data communication technologies can also be used to replace or supplement the aforementioned data communication technologies.

In order to achieve synchronization testing in the scenario of data synchronization between multiple databases, and to improve the scalability of test cases in this scenario, an embodiment of the present application provides a database synchronization test method, which can be applied to the above-mentioned FIG. 1 In the scenario architecture, the test of data synchronization between multiple databases can be realized. Please refer to FIG. 2, which shows a method flowchart of a database synchronization test method involved in an exemplary embodiment of the present application. The method can be applied to the scenario architecture shown in FIG. Computer equipment execution. As shown in Figure 2, the database synchronization test method may include the following steps.

Step 201: Obtain a unique identifier of a target test case from a configuration file. The target test case is used to test whether the data between at least two databases is synchronized.

Among them, the unique identifier of the target test case may be the name of the target test case. The target test case can test whether the data between at least two databases is synchronized.

Step 202: According to the unique identifier of the target test case, call the target test case through the target interface, and the target interface provides the test logic of the target test case.

Step 203: Perform a synchronization test on the data between at least two databases according to the target test result output after calling the target test case.

In summary, by obtaining the unique identifier of the target test case used to test whether the data between at least two databases is synchronized, the target test case is invoked using the target interface that provides the test logic of the target test case, and the target test is output As a result, a synchronization test is performed on the data between at least two databases through the target test result. In the scenario where the data between at least two databases is synchronized, the application can realize the synchronization test of the data between at least two databases through the target test case and the target interface, which avoids the need for each test case in the at least two databases. The rewriting of, thus improving the scalability of each test case in this scenario.

In a possible implementation manner, this application can also maintain a target container, which can store various test cases written by developers, and this application can associate the unique identifier of the test case with the test case. When When the test case is invoked, the unique identifier of the test case can be used to find the corresponding test case from the target container.

Please refer to FIG. 3, which shows a method flowchart of a database synchronization test method involved in an exemplary embodiment of the present application. The method can be applied to the scenario architecture shown in FIG. Computer equipment execution. As shown in Figure 3, the database synchronization test method may include the following steps.

Step 301: Register the target test case in the target container by way of annotation.

Among them, the target test case is used to test whether the data between at least two databases is synchronized.

Optionally, the target container may be maintained inside the computer equipment, or may be maintained in other computer equipment or servers outside the computer equipment. After a target test case is written in the computer equipment, the computer equipment can register the target test case in the target container for centralized management through annotations. For example, the target container is a Spring IOC (Inversion of Control) container. The target container may store test cases for detecting whether the data between database one and database two is synchronized, and may also store test cases for detecting whether the data between database three, database four, and database five are synchronized.

Optionally, synchronization between at least two databases means that when data in any one of the at least two databases increases or decreases, the other databases increase or decrease the same data accordingly. For example, between two databases, when data in one database increases or decreases, the other database also increases or decreases the same data. Or, between the three databases, when the data of one database increases or decreases, the other two databases also increase or decrease the same data.

Step 302: Add the unique identifier of the target test case in the configuration file.

Optionally, in the process of annotating the target test case to the target container, the computer device may write a configuration file, and add the unique identifier of the target test case to the configuration file. In a possible implementation manner, the unique identifier of the target test case may be the name of the target test case. In this application, the configuration file can be used to store the unique identification of each target test case. When the computer device registers a target test case in the target container, the computer device can add the name of the target test case to the configuration file. Optionally, the configuration file can also be maintained in the computer device itself or in the server.

Step 303: Obtain the unique identifier of the target test case from the configuration file.

Optionally, when detecting whether the data between at least two databases is synchronized, the computer device may obtain the unique identifier of a certain target test case through the configuration file, and call the target test case through the unique identifier.

In a possible implementation, the computer device can provide a unique identification input box for the target test case. The computer device receives the input unique identification of the target test case, and searches for the target from the configuration file according to the unique identification of the target test case. The unique identifier of the test case. Please refer to FIG. 4, which shows an interface diagram of a test case calling interface involved in an exemplary embodiment of the present application. As shown in Figure 4, the interface 400 contains an identification input box 401, a confirmation control 402, and a cancellation control 403. The user can enter the name of the target test case in the identification input box 401 and click the confirmation control 402, and the computer device can Find the name of the target test case that is the same as the user input in the configuration file.

In a possible implementation manner, the computer device can provide a unique identification selection control corresponding to the above configuration file, and the computer device can receive the selection operation of the unique identification selection control, thereby obtaining the uniqueness of a certain target test case in the configuration file. Logo. Please refer to FIG. 5, which shows an interface schematic diagram of a test case invoking interface related to an exemplary embodiment of the present application. As shown in Figure 5, the interface 500 includes a logo selection control 501. The logo selection control 501 can provide the names of all test cases included in the configuration file. The user can directly select a certain item in the configuration file through the logo selection control 501. The name of the test case.

Step 304: According to the unique identifier of the target test case, obtain the target test case corresponding to the unique identifier of the target test case from the target container.

Optionally, the computer device may obtain the target test case corresponding to the unique identification from the target container through the unique identification of the target test case determined above.

Step 305: Obtain the initialization data and test logic of the target test case according to the unique identifier of the target test case.

Optionally, the target interface in this application can define the synchronization test process of the database, and the initialization data and test logic of the target test case are provided through the target interface. After the computer device obtains the unique identifier of the target test case, it can obtain the initialization data and test logic of the target test case through the target interface. For example, for target test case 1, the target interface provides the test case 1 with prepareData() method to initialize data and execute() method test logic. When the name of the target test case selected by the user is target test case 1, then the computer The device can obtain the initialization data of the prepareData() method and the test logic of the execute() method provided by the target interface.

Step 306: Invoke the target test case through the target interface according to the initialization data and the test logic.

The computer device can call the target test case according to the acquired initialization data and test logic to complete the operation of the target test case.

Step 307: Perform a synchronization test on the data between at least two databases according to the target test result output after calling the target test case.

That is, the computer device detects whether the data between at least two databases corresponding to the target test case is synchronized according to the test result output after running the target test case.

In a possible implementation manner, the computer device can determine that the data between the at least two databases is synchronized in response to the output format of the target test result conforming to the first format. For example, when the computer device has synchronized the data between at least two databases, it can output the test results in a unified format after running the target test case. If the target test result output after calling the target test case is the same as the format, the computer device It can be determined that the data between at least two databases has been synchronized, and the data between at least two databases is consistent. Correspondingly, if the target test result output after calling the target test case is different from the above unified format, the computer device can determine that the data between at least two databases is inconsistent.

In addition, this application associates the test case with the test case through the name of the test case. When the test case needs to be called, the corresponding test case is selected by the name of the test case, so as to test whether the data in at least two databases is consistent. This synchronous testing process improves the efficiency of testing whether the data between the two databases is consistent.

In a possible implementation manner, the above-mentioned target container and configuration file are both in a computer device. Please refer to FIG. 6, which shows a schematic structural diagram of a computer device provided by an exemplary embodiment of the present application. As shown in FIG. 6, the computer device includes a calling module 601, a test interface 602, a target container module 603, a configuration file module 604, and a test case module 605.

The calling module 601 can obtain the name of the target test case from the configuration file module 604, and call the target test case by the name of the target test case in the obtained configuration file.

The test interface 602 can provide test logic for different target test cases. The computer device obtains the corresponding test logic by calling the name of the target test case in the module 601, and implements the call of the test case through the test interface.

The target container module 603 registers the test case module 605 with each target test in itself for centralized management, and provides corresponding test cases for the test interface 602. Correspondingly, the test case module 605 can register the target test case in the target container module 603.

Please refer to FIG. 7, which shows a flowchart of a method for a computer device to perform a database synchronization test method for a computer device in FIG. 6 according to an exemplary embodiment of the present application. As shown in Figure 7, the computer device may include the following steps:

Step 701: Write a target test case in the computer device.

Step 702: The computer device adds the target test case to the configuration file.

Step 703: The computer device registers the target test case in the target container.

In step 704, the computer device records the names of all target test cases.

Among them, the computer equipment records the names of all target test cases in the configuration file module.

Step 705: The computer device maintains all target test cases in the target container.

Step 706: The computer device discovers all target test cases through the configuration file.

Optionally, the calling module in the computer device may search for the name of the same target test case from the configuration file module through the name of the target test case, and the configuration file module returns the name of the target test case to the calling module.

Step 707: The computer device obtains the target test case corresponding to the name of the target test case from the target container.

In step 708, the computer device completes the test process of the target test case through the test interface.

Optionally, for this step, reference may be made to the description of step 305 to step 307 in the foregoing embodiment, which will not be repeated here.

The following are device embodiments of this application, which can be used to implement the method embodiments of this application. For details that are not disclosed in the device embodiments of this application, please refer to the method embodiments of this application.

Fig. 8 is a structural block diagram of a database synchronization test device provided by an exemplary embodiment of the present application. The database synchronization test device can be used in the computer device shown in FIG. 1 to perform all or part of the steps in the method shown in the corresponding embodiment of FIG. 2, FIG. 3, or FIG. 7. The database synchronization test device may include the following modules:

The identification acquiring module 801 is configured to acquire a unique identification of a target test case from a configuration file, where the target test case is used to test whether the data between at least two databases is synchronized;

The calling module 802 is configured to call the target test case through a target interface according to the unique identifier of the target test case, and the target interface provides the test logic of the target test case;

The test module 803 is configured to perform a synchronization test on the data between the at least two databases according to the target test result output after calling the target test case.

Optionally, the calling module 802 includes: a first acquiring unit, a second acquiring unit, and a calling unit;

The first obtaining unit is configured to obtain the target test case according to the unique identifier of the target test case;

The second obtaining module is configured to obtain the initialization data and the test logic of the target test case according to the unique identifier of the target test case;

The calling unit is configured to call the target test case through the target interface according to the initialization data and the test logic.

Optionally, the device further includes:

The registration module is used to register the target test case in the target container by way of annotation;

Add module, used to add the unique identifier of the target test case in the configuration file;

The first obtaining unit is further configured to obtain the target test case corresponding to the unique identifier of the target test case from the target container according to the unique identifier of the target test case.

Optionally, the identification acquiring module 801 includes: a receiving unit and a searching unit;

The receiving unit is configured to receive the input unique identifier of the target test case;

The search unit is configured to search for the unique identification of the target test case from the configuration file according to the unique identification of the target test case.

Optionally, the test module 803 is further configured to determine that the data between the at least two databases is synchronized in response to the output format of the target test result conforming to the first format.

Optionally, when the data of any one of the at least two databases increases or decreases, the remaining databases increase or decrease the same data accordingly.

It should be noted that when the device provided in the above embodiment executes the above steps, only the division of the above functional modules is used as an example. In actual applications, the above functions can be allocated by different functional modules as required, that is, the device The internal structure is divided into different functional modules to complete all or part of the functions described above. In addition, the device provided in the foregoing embodiment and the method embodiment of the foregoing database synchronization test method belong to the same concept. For the specific implementation process, please refer to the method embodiment, which will not be repeated here.

Fig. 9 is a schematic structural diagram of a computer device provided by an exemplary embodiment of the present application. The computer device 900 includes a central processing unit (CPU) 901, a system memory 904 including a random access memory (Random Access Memory, RAM) 902 and a read only memory (Read Only Memory, ROM) 903, and a connection The system memory 904 and the system bus 905 of the central processing unit 901. The computer device 900 also includes a basic input/output system (Input/Output System, I/O system) 906 that helps to transfer information between various devices in the computer, and is used to store an operating system 912, application programs 913, and other programs. The mass storage device 907 of the module 914.

The basic input/output system 906 includes a display 908 for displaying information and an input device 909 such as a mouse and a keyboard for the user to input information. The display 908 and the input device 909 are both connected to the central processing unit 901 through the input and output controller 910 connected to the system bus 905. The basic input/output system 906 may also include an input and output controller 910 for receiving and processing input from multiple other devices such as a keyboard, a mouse, or an electronic stylus. Similarly, the input and output controller 910 also provides output to a display screen, a printer, or other types of output devices.

The mass storage device 907 is connected to the central processing unit 901 through a mass storage controller (not shown) connected to the system bus 905. The mass storage device 907 and its associated computer readable medium provide non-volatile storage for the computer device 900. That is, the mass storage device 907 may include a computer-readable medium (not shown) such as a hard disk or a CD-ROM (Compact Disc Read-Only Memory) drive.

The computer-readable media may include computer storage media and communication media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storing information such as computer readable instructions, data structures, program modules or other data. Computer storage media include RAM, ROM, EPROM (Erasable Programmable Read Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash memory or other solid state Storage of its technology, CD-ROM, DVD (Digital Video Disc, high-density digital video disc) or other optical storage, tape cartridges, magnetic tape, disk storage or other magnetic storage devices. Of course, those skilled in the art may know that the computer storage medium is not limited to the above-mentioned types. The aforementioned system memory 904 and mass storage device 907 may be collectively referred to as a memory.

The computer device 900 may be connected to the Internet or other network devices through the network interface unit 911 connected to the system bus 905.

The memory further includes one or more programs, and the one or more programs are stored in the memory. The central processing unit 901 executes the one or more programs to implement the methods provided in the foregoing embodiments of the present application. All or part of the steps performed by a computer device.

In an exemplary embodiment, a computer-readable storage medium is also provided, and the storage medium stores at least one instruction, at least one program, a code set, or an instruction set, the at least one instruction, the at least one program The code set or instruction set can be loaded and executed by a processor (also referred to as a central processing unit) of a computer device to complete all or part of the steps of the method shown in each embodiment of the present application. For example, the non-transitory computer-readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.

After considering the specification and practicing the invention disclosed herein, those skilled in the art will easily think of other embodiments of the present application. This application is intended to cover any variations, uses, or adaptive changes of this application. These variations, uses, or adaptive changes follow the general principles of this application and include common knowledge or customary technical means in the technical field that are not disclosed in this application. . The description and the embodiments are only regarded as exemplary, and the true scope and spirit of the application are pointed out by the following claims.

It should be understood that the present application is not limited to the precise structure that has been described above and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the application is only limited by the appended claims.

Claims

A database synchronization test method, characterized in that the method is executed by a computer device, and the method includes:

Obtaining the unique identifier of the target test case from the configuration file, where the target test case is used to test whether the data between at least two databases is synchronized;

According to the unique identifier of the target test case, call the target test case through a target interface, and the target interface provides the test logic of the target test case;

According to the target test result output after invoking the target test case, a synchronization test is performed on the data between the at least two databases.
The method according to claim 1, wherein the invoking the target test case through a target interface according to the unique identifier of the target test case comprises:

Obtaining the target test case according to the unique identifier of the target test case;

Acquiring the initialization data and the test logic of the target test case according to the unique identifier of the target test case;

Invoke the target test case through the target interface according to the initialization data and the test logic.
The method according to claim 2, wherein the method further comprises:

Register the target test case in the target container by way of annotation;

Adding the unique identifier of the target test case to the configuration file;

The acquiring the target test case according to the unique identifier of the target test case includes:

According to the unique identifier of the target test case, the target test case corresponding to the unique identifier of the target test case is obtained from the target container.
The method according to claim 1, wherein the obtaining the unique identifier of the target test case from the configuration file comprises:

Receiving the input unique identifier of the target test case;

According to the unique identifier of the target test case, the unique identifier of the target test case is searched from the configuration file.
The method according to claim 1, wherein the performing a synchronization test on the data between the at least two databases according to the target test result output after invoking the target test case comprises:

In response to the output format of the target test result conforming to the first format, it is determined that the data between the at least two databases is synchronized.
The method according to any one of claims 1 to 5, wherein when the data of any one of the at least two databases increases or decreases, the other databases increase or decrease the same data accordingly.
A database synchronization test device, characterized in that the device is used in computer equipment, and the device includes:

An identification acquisition module, configured to acquire a unique identification of a target test case from a configuration file, the target test case being used to test whether the data between at least two databases is synchronized;

The calling module is used to call the target test case through a target interface according to the unique identifier of the target test case, and the target interface provides the test logic of the target test case;

The test module is configured to perform a synchronization test on the data between the at least two databases according to the target test result output after calling the target test case.
8. The device according to claim 7, wherein the calling module comprises: a first acquiring unit, a second acquiring unit, and a calling unit;

The first obtaining unit is configured to obtain the target test case according to the unique identifier of the target test case;

The second acquisition module is configured to acquire the initialization data and the test logic of the target test case according to the unique identifier of the target test case;

The calling unit is configured to call the target test case through the target interface according to the initialization data and the test logic.
A computer device, wherein the computer device includes a processor and a memory, and the memory stores at least one instruction, at least one program, a code set, or an instruction set, the at least one instruction, the at least one program The code set or instruction set is loaded and executed by the processor to realize the database synchronization test method according to any one of claims 1 to 6.
A computer-readable storage medium, wherein the storage medium stores at least one instruction, at least one program, code set or instruction set, the at least one instruction, the at least one program, the code set or The instruction set is loaded and executed by the processor to realize the database synchronization test method according to any one of claims 1 to 6.