A multi-machine cross-platform database product testing method, system, device and medium

Abstract

The present invention relates to the technical field of database automated testing, and provides a multi-machine cross-platform database product testing method, system, device, and medium. The method comprises: obtaining customized modules corresponding to different types of databases, and obtaining executable instructions according to test scripts; registering the implementation class corresponding to the customized module as a core module and an extension point of the core module of a database product testing framework; calling the instance manager of the core module, and generating a registry and an instance manager list according to the instance manager; calling the registry and the instance manager list, and obtaining a database instance according to the executable instructions; and calling the extension point of the core module according to the database instance to perform testing and obtain test results. The present invention achieves a doubling of the detection speed through multi-machine and multi-platform calling, and at the same time, the efficiency of use case completion is accelerated due to the reuse of use cases.

Description

Technical Field

[0001] The present invention relates to the technical field of database automation testing, and provides a multi-machine cross-platform database product testing method, system, device and medium. Background Art

[0002] Database product testing not only includes basic SQL execution, but also various driver tests, high-availability cluster tests, and various abnormal situation tests (such as power outages and network disconnections). Therefore, multiple machines and multiple instances are necessary. Multiple machines can make full use of idle machines and improve the efficiency of use case execution. Multiple machines involve cross-platform issues, and the framework needs to support various Windows (the database may have a Windows version, and the driver may also have a Windows-specific version) and Linux versions at the same time.

[0003] Database vendors may offer a variety of database products, such as online analytical processing (OLAP), online transaction processing (OLTP), and distributed systems, each corresponding to a specific product, or offering OLTP database products with different architectures. Existing technologies typically require designing separate test frameworks or modules for each type of database product, resulting in limited versatility across database product testing frameworks. Summary of the Invention

[0004] The present invention aims to solve at least one of the technical problems existing in the related art. To this end, the present invention provides a multi-machine cross-platform database product testing method, system, device and medium, which achieves adaptation to different databases and multi-machine cross-platform, and accelerates database testing.

[0005] The present invention provides a multi-machine cross-platform database product testing method, comprising:

[0006] S1: Obtain customized modules corresponding to different types of databases and obtain executable instructions based on the test script;

[0007] S2: Register the implementation class corresponding to the customized module as the core module and the extension point of the core module of the database product testing framework;

[0008] S3: calling the instance manager of the core module, and generating a registration table and an instance manager list according to the instance manager;

[0009] S4: calling the registry and instance manager list, and obtaining a database instance according to the executable instruction;

[0010] S5: Call the extension point of the core module according to the database instance to perform testing and obtain a test result.

[0011] According to a multi-machine cross-platform database product testing method provided by the present invention, step S3 includes:

[0012] S31: Generate an instance pool according to a preset number of instances and port range through the instance manager;

[0013] S32: In a multi-machine environment, obtaining a corresponding number of nodes, wherein the nodes include a master node and an agent node;

[0014] S33: Start the agent nodes and register the instance managers corresponding to the agent nodes in a registry;

[0015] S34: Start the master control node and obtain the registry, and store the instance manager in the registry and the instance manager corresponding to the master control node in an instance manager list.

[0016] According to a multi-machine cross-platform database product testing method provided by the present invention, step S33 includes:

[0017] The listening port parameters corresponding to each of the proxy nodes are obtained, the listening port parameters are parsed, and the instance manager is registered in the registry through a remote method call mechanism.

[0018] According to a multi-machine cross-platform database product testing method provided by the present invention, step S4 includes:

[0019] If the first condition is met, the database instance in the instance manager corresponding to the master control node is used preferentially;

[0020] If the second condition is met, selecting the database instances in the instance manager list in sequence according to a preset order;

[0021] The first condition includes that the executable instruction specifies that the database instance of the master control node and the database instance in the instance manager corresponding to the master control node are preferentially used, and either instance is in an idle state;

[0022] The second condition includes at least one of the following:

[0023] The executable instruction does not specify the database instance of the master node to be used preferentially;

[0024] The database instances in the instance manager corresponding to the master node are all busy and cannot meet the demand for executable instructions;

[0025] The executable instructions specify that the test tasks be evenly distributed to the database instances of each node.

[0026] According to a multi-machine cross-platform database product testing method provided by the present invention, the instance manager of the core module is called, and the database instance is obtained according to the executable instructions, including: a machine label parameter is set in the startup configuration file of the database product testing framework, each machine label parameter corresponds to a different node, and the instance of the target node is specified by the machine label parameter.

[0027] According to a multi-machine cross-platform database product testing method provided by the present invention, step S5 includes:

[0028] Compare and verify the actual results obtained after the test with the expected results, determine the status of the database instance, and if it is detected that the database instance needs to be restarted or reset, perform the restart or reset operation and detect the status of the database instance after the restart or reset.

[0029] According to a multi-machine cross-platform database product testing method provided by the present invention, the implementation class is used to implement the running application program interface corresponding to the extension point provided by the core module.

[0030] The present invention also provides a multi-machine cross-platform database product testing system, comprising:

[0031] Customized module acquisition module: obtains customized modules corresponding to different types of databases and obtains executable instructions according to test scripts;

[0032] Core module acquisition module: registers the implementation class corresponding to the customized module as the core module and extension point of the core module of the database product testing framework;

[0033] List generation module: calling the instance manager of the core module, and generating a registration table and an instance manager list according to the instance manager;

[0034] Database instance module: calling the registry and instance manager list, and obtaining the database instance according to the executable instructions;

[0035] Test module: Call the extension point of the core module according to the database instance to perform testing and obtain test results.

[0036] The present invention also provides an electronic device comprising a memory, a processor and a computer program stored in the memory and executable on the processor. When the processor executes the program, the steps of any of the above-described multi-machine cross-platform database product testing methods are implemented.

[0037] The present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the steps of any of the above-mentioned methods for testing a multi-machine cross-platform database product are implemented.

[0038] The above one or more technical solutions in the embodiments of the present invention have at least one of the following technical effects:

[0039] The present invention provides a multi-machine and cross-platform database product testing method, system, device and medium, which can double the detection speed by calling multiple machines and platforms, and at the same time accelerate the efficiency of use case completion due to use case reuse.

[0040] This invention is applicable not only to traditional relational database systems such as MySQL, Oracle, and SQL Server, but also to newer NoSQL database systems such as MongoDB and Cassandra, as well as time series databases and graph databases. This broad applicability enables the invention to meet diverse database automation testing needs.

[0041] Additional aspects and advantages of the present invention will be set forth in part in the description which follows and, in part, will be obvious from the description which follows, or may be learned by practice of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] In order to more clearly illustrate the technical solutions in the present invention or the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0043] Figure 1 The present invention provides a flowchart of a multi-machine cross-platform database product testing method.

[0044] Figure 2 This is a structural block diagram of a multi-machine cross-platform database product testing device provided by the present invention.

[0045] Figure 3 It is a structural schematic diagram of the electronic device provided by the present invention.

[0046] Reference numerals:

[0047] 101. Custom module acquisition module; 102. Core module acquisition module; 103. List generation module; 104. Database instance module; 105. Test module; 810. Processor; 820. Communication interface; 830. Memory; 840. Communication bus. DETAILED DESCRIPTION

[0048] To make the purpose, technical solutions and advantages of the present invention clearer, the technical solutions in the present invention will be clearly and completely described below. Obviously, the embodiments described are part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention. The following embodiments are used to illustrate the present invention, but are not used to limit the scope of the present invention.

[0049] In the description of this specification, the reference terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" mean that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the embodiment of the present invention. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art can combine and combine different embodiments or examples described in this specification and features of different embodiments or examples without contradiction.

[0050] The following combination Figures 1 to 3 The present invention is described.

[0051] Example

[0052] like Figure 1 As shown, Figure 1 This is a flowchart of a multi-machine cross-platform database product testing method provided by the present invention. It includes the following steps:

[0053] S1: Obtain customized modules corresponding to different types of databases and obtain executable instructions based on the test script;

[0054] S2: Register the implementation class corresponding to the customized module as the core module and the extension point of the core module of the database product testing framework;

[0055] S3: calling the instance manager of the core module, and generating a registration table and an instance manager list according to the instance manager;

[0056] S4: calling the registry and instance manager list, and obtaining a database instance according to the executable instruction;

[0057] S5: Call the extension point of the core module according to the database instance to perform testing and obtain a test result.

[0058] To build a framework that supports multiple databases, it needs to be multi-module. Modules include general modules and customized modules for each database. Each module needs to expose some interfaces for use by other modules, and each module needs its own independent class loader to avoid introducing the same dependencies but different versions between modules. Furthermore, it is required that testing can be started directly without modifying any configuration, simply by replacing the customized modules of different libraries. In the future, by adding a UI module (User Interface Design), an editor that can serve as a DSL (Domain-Specific Language) will be needed. Therefore, OSGI (Open Service Gateway Initiative) was chosen as the modular system.

[0059] Specifically, the customization module at least includes: an architecture module, a DSL parsing module, an execution result comparison module, a core module, and a database customization module.

[0060] The driver module is used to implement interaction between the test framework and various databases, establishing communication with the databases. The driver module only requires the corresponding database JDBC driver JAR file, primarily used to execute SQL and monitor instance status. While any driver (such as ODBC) can be used for the driver module, the present embodiment uses JDBC drivers because they are widely used, cross-platform compatible, and compatible with the Java language used by the framework. Each module is a plug-in project for Eclipse (a development platform).

[0061] There are also many common non-core modules, such as logging module, JSON processing, building and packaging module, uploading test results module, etc.

[0062] Specifically, the implementation class in step S2 is used to implement the running application program interface corresponding to the extension point provided by the core module.

[0063] After the framework is started, during the initialization process, the content with the extended extension points will be obtained.

[0064] The core module has an interface RunApplication. This module has an implementation class for it, and it is also one of the extended contents of the extension point. After the framework is started, it can be understood that the core module obtains the RunApplication implementation class extended by this module. After creating an object of this class, the data corresponding to the module is initialized first. For example, there may be multiple drivers, and environment variables and dependencies need to be initialized according to the configuration file.

[0065] Specifically, step S3 includes:

[0066] S31: Generate an instance pool through the instance manager according to the pre-set number of instances and port range. In the embodiment of the present invention, after the framework is started, the instance manager of the core module will expand this instance group into 10 instances as an instance pool for use in subsequent use case execution.

[0067] S32: In a multi-machine environment, a corresponding number of nodes are obtained, wherein the nodes include a master control node Controller and multiple agent nodes Agent.

[0068] S33: Start the proxy node, register the instance manager corresponding to each proxy node in the registry; obtain the listening port parameter corresponding to each proxy node, parse the listening port parameter, and register the instance manager in the registry through the remote method call mechanism.

[0069] Each Agent node adds a listening port parameter when it is started. After the framework parses this parameter, it calls the RMI Registry.rebind interface and writes the instance manager object of the node as the second parameter.

[0070] In the startup configuration file of the Controller node, add the following:

[0071] [REMOTE]

[0072] HOST=AGENT / / Agent's IP or HOST

[0073] PORT=AGENT / / The port number after the listening port parameter when the Agent starts

[0074] If there are multiple Agents, add multiple [REMOTE].

[0075] S34: Start the master control node and obtain the registry, and store the instance manager in the registry and the instance manager corresponding to the master control node in an instance manager list.

[0076] After all agents are started, start the Controller node. After the Controller node is started, it first has its own instance manager. Then, through each [REMOTE] in the configuration file, it obtains the storage object of each Agent node, and then calls the lookup interface to obtain the instance manager of each Agent node. The instance managers of all nodes are placed in an instance manager list. Later, test cases can use it to select the instance manager of any node to obtain the instance. There are currently two configurable strategies, one is to give priority to the local instance, and the other is polling.

[0077] Specifically, step S4 includes:

[0078] If the first condition is met, the database instance in the instance manager corresponding to the master control node is used preferentially;

[0079] If the second condition is met, selecting the database instances in the instance manager list in sequence according to a preset order;

[0080] The first condition includes that the executable instruction specifies that the database instance of the master control node and the database instance in the instance manager corresponding to the master control node are preferentially used, and either instance is in an idle state.

[0081] The executable instruction specifies that the database instance of the master node is in an idle state and meets the first condition;

[0082] The database instance in the instance manager corresponding to the master node is in an idle state, which meets the first condition;

[0083] The first condition is also met when the executable instruction specifies that the database instance of the master control node is used preferentially and the database instance in the instance manager corresponding to the master control node is both in an idle state.

[0084] The second condition includes at least one of the following:

[0085] The executable instruction does not specify the database instance of the master node to be used preferentially;

[0086] The database instances in the instance manager corresponding to the master node are all busy and cannot meet the demand for executable instructions;

[0087] The executable instructions specify that the test tasks be evenly distributed to the database instances of each node.

[0088] During the use case execution phase, when the DSL involves specific database features, the module's implementation class of the core module's common interface will be called to complete the task, such as the following example:

[0089] instance = system.getInstance();

[0090] instance.changeMode(ONLINE);

[0091] The first line acquires an instance. This involves many considerations, such as initializing its configuration parameters after acquisition. If the current instance pool runs out of idle instances, an instance that has already run other use cases must be used. Whether such an instance can be reused directly, requires a restart, or requires a complete reset depends on the database characteristics and use case requirements. The second line, for OLTP databases, internally executes a shell command to determine the current instance status. If it is online and the current use case does not require changes, it can be maintained. If a restart or reset is required, the corresponding command is executed and then JDBC (Java DataBase Connectivity) is used to check for a successful connection.

[0092] Specifically, the instance manager of the core module is called to obtain the database instance according to the executable instruction, including: a machine label parameter is set in the startup configuration file of the database product testing framework, each machine label parameter corresponds to a different node, and the instance of the target node is specified by the machine label parameter.

[0093] Specifically, step S5 includes:

[0094] The test results obtained after the test are compared and verified with the expected results, the status of the database instance is determined, and if it is detected that the database instance needs to be restarted or reset, the restart or reset operation is performed, and the status of the database instance after the restart or reset is detected.

[0095] In actual testing of a company's database products GBase8s / GBase8a / GBase8c database, test cases are reused among various databases, which eliminates the need for more than 60% of use case writing. Due to the support for multiple machines and multiple instances, the test case execution efficiency is increased several times (determined by the number of machines).

[0096] like Figure 2 As shown, Figure 2 This is a structural diagram of a multi-machine cross-platform database product testing device provided by the present invention. It includes:

[0097] Customized module acquisition module 101: obtains customized modules corresponding to different types of databases and obtains executable instructions according to the test script;

[0098] Core module acquisition module 102: registers the implementation class corresponding to the customized module as the core module and the extension point of the core module of the database product testing framework;

[0099] List generation module 103: calling the instance manager of the core module, and generating a registration table and an instance manager list according to the instance manager;

[0100] Database instance module 104: calling the registry and instance manager list, and obtaining a database instance according to the executable instruction;

[0101] Testing module 105: calling the extension point of the core module according to the database instance to perform testing and obtain test results.

[0102] Figure 3 An example of a physical structure diagram of an electronic device is shown below. Figure 3 As shown, the electronic device may include: a processor 810, a communication interface 820, a memory 830, and a communication bus 840, wherein the processor 810, the communication interface 820, and the memory 830 communicate with each other via the communication bus 840. The processor 810 may call the logic instructions in the memory 830 to execute a multi-machine cross-platform database product testing method, which includes:

[0103] S1: Obtain customized modules corresponding to different types of databases and obtain executable instructions based on the test script;

[0104] S2: Register the implementation class corresponding to the customized module as the core module and the extension point of the core module of the database product testing framework;

[0105] S3: calling the instance manager of the core module, and generating a registration table and an instance manager list according to the instance manager;

[0106] S4: calling the registry and instance manager list, and obtaining a database instance according to the executable instruction;

[0107] S5: Call the extension point of the core module according to the database instance to perform testing and obtain a test result.

[0108] Furthermore, the logic instructions in the aforementioned memory 830 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the portion that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product, stored in a storage medium, includes instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, mobile hard drives, read-only memories (ROMs), random access memories (RAMs), magnetic disks, or optical disks.

[0109] In another aspect, the present invention further provides a computer program product, comprising a computer program stored on a non-transitory computer-readable storage medium, wherein the computer program comprises program instructions. When the program instructions are executed by a computer, the computer is capable of performing a multi-machine cross-platform database product testing method provided by the above methods, the method comprising:

[0110] S1: Obtain customized modules corresponding to different types of databases and obtain executable instructions based on the test script;

[0111] S2: Register the implementation class corresponding to the customized module as the core module and the extension point of the core module of the database product testing framework;

[0112] S3: calling the instance manager of the core module, and generating a registration table and an instance manager list according to the instance manager;

[0113] S4: calling the registry and instance manager list, and obtaining a database instance according to the executable instruction;

[0114] S5: Call the extension point of the core module according to the database instance to perform testing and obtain a test result.

[0115] In another aspect, the present invention further provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, is implemented to perform the multi-machine cross-platform database product testing method provided above, the method comprising:

[0116] S1: Obtain customized modules corresponding to different types of databases and obtain executable instructions based on the test script;

[0117] S2: Register the implementation class corresponding to the customized module as the core module and the extension point of the core module of the database product testing framework;

[0118] S3: calling the instance manager of the core module, and generating a registration table and an instance manager list according to the instance manager;

[0119] S4: calling the registry and instance manager list, and obtaining a database instance according to the executable instruction;

[0120] S5: Call the extension point of the core module according to the database instance to perform testing and obtain a test result.

[0121] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, i.e., they may be located in one location or distributed across multiple network units. Some or all of the modules may be selected based on actual needs to achieve the objectives of the present embodiment. Persons of ordinary skill in the art will be able to understand and implement the present invention without inventive effort.

[0122] Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented using software plus a necessary general-purpose hardware platform, or of course, hardware. Based on this understanding, the essence of the above technical solution, or the portion that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a magnetic disk, or an optical disk, and includes a number of instructions for causing a computer device (such as a personal computer, server, or network device) to execute the methods described in each embodiment or certain portions of the embodiments.

[0123] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the various embodiments of the present invention.

[0124] It should be noted that the embodiments of the present disclosure can be implemented by hardware, software, or a combination of software and hardware. The hardware portion can be implemented using dedicated logic; the software portion can be stored in a memory and executed by an appropriate instruction execution system such as a microprocessor or dedicated hardware. Those skilled in the art will understand that the above-mentioned devices and methods can be implemented using computer-executable instructions and / or contained in processor control code, for example, such code is provided on a programmable memory or a data carrier such as an optical or electronic signal carrier.

[0125] In addition, although the operations of the method of the present disclosure are described in a particular order in the accompanying drawings, this does not require or imply that these operations must be performed in this particular order, or that all the operations shown must be performed to achieve the desired result. On the contrary, the steps depicted in the flow chart can change the order of execution. Additionally or alternatively, certain steps can be omitted, multiple steps can be combined into one step, and / or one step can be decomposed into multiple steps. It should also be noted that the features and functions of two or more devices according to the present disclosure can be embodied in one device. Conversely, the features and functions of a device described above can be further divided into being embodied by multiple devices.

[0126] Although the present disclosure has been described with reference to several specific embodiments, it should be understood that the present disclosure is not limited to the specific embodiments disclosed. The present disclosure is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

Claims

1. A multi-machine cross-platform database product testing method, characterized in that: include: S1: Obtain customized modules corresponding to different types of databases and obtain executable instructions based on the test script; S2: Register the implementation class corresponding to the customized module as the core module and the extension point of the core module of the database product testing framework; S3: calling the instance manager of the core module and generating a registration table and an instance manager list according to the instance manager; step S3 includes: S31: Generate an instance pool according to a preset number of instances and port range through the instance manager; S32: In a multi-machine environment, obtaining a corresponding number of nodes, wherein the nodes include a master node and an agent node; S33: Start the agent nodes and register the instance managers corresponding to the agent nodes in a registry; S34: Start the master control node and obtain the registry, and store the instance manager in the registry and the instance manager corresponding to the master control node in an instance manager list; S4: calling the registry and instance manager list, and obtaining a database instance according to the executable instruction; step S4 includes: If the first condition is met, the database instance in the instance manager corresponding to the master control node is used preferentially; If the second condition is met, selecting the database instances in the instance manager list in sequence according to a preset order; The first condition includes that the executable instruction specifies that the database instance of the master control node and the database instance in the instance manager corresponding to the master control node are preferentially used, and either instance is in an idle state; The second condition includes at least one of the following: The executable instruction does not specify the database instance of the master node to be used preferentially; The database instances in the instance manager corresponding to the master node are all busy and cannot meet the demand for executable instructions; The executable instruction specifies to evenly distribute the test tasks to the database instances of each node; S5: Call the extension point of the core module according to the database instance to perform testing and obtain a test result.

2. A multi-machine cross-platform database product testing method according to claim 1, characterized in that: Step S33 includes: The listening port parameters corresponding to each of the proxy nodes are obtained, the listening port parameters are parsed, and the instance manager is registered in the registry through a remote method call mechanism.

3. The multi-machine cross-platform database product testing method according to claim 1, characterized in that: Calling the instance manager of the core module and obtaining the database instance according to the executable instruction includes: providing a machine label parameter in the startup configuration file of the database product testing framework, each of the machine label parameters corresponding to a different node, and specifying the instance of the target node through the machine label parameter.

4. A multi-machine cross-platform database product testing method according to claim 1, characterized in that: Step S5 includes: The test results obtained after the test are compared and verified with the expected results, the status of the database instance is determined, and if it is detected that the database instance needs to be restarted or reset, the restart or reset operation is performed, and the status of the database instance after the restart or reset is detected.

5. The multi-machine cross-platform database product testing method according to claim 1, characterized in that: The implementation class is used to implement the running application program interface corresponding to the extension point provided by the core module.

6. A multi-machine cross-platform database product testing system, for executing a multi-machine cross-platform database product testing method according to any one of claims 1 to 5, characterized in that: include: Customized module acquisition module: obtains customized modules corresponding to different types of databases and obtains executable instructions according to test scripts; Core module acquisition module: registers the implementation class corresponding to the customized module as the core module and extension point of the core module of the database product testing framework; List generation module: calling the instance manager of the core module, and generating a registration table and an instance manager list according to the instance manager; Database instance module: calling the registry and instance manager list, and obtaining the database instance according to the executable instructions; Test module: Call the extension point of the core module according to the database instance to perform testing and obtain test results.

7. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the steps of the multi-machine cross-platform database product testing method according to any one of claims 1 to 5 are implemented.

8. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the multi-machine cross-platform database product testing method according to any one of claims 1 to 5 are implemented.

Images