CN112286786A - Database testing method and device and server - Google Patents
Database testing method and device and server Download PDFInfo
- Publication number
- CN112286786A CN112286786A CN201910675781.7A CN201910675781A CN112286786A CN 112286786 A CN112286786 A CN 112286786A CN 201910675781 A CN201910675781 A CN 201910675781A CN 112286786 A CN112286786 A CN 112286786A
- Authority
- CN
- China
- Prior art keywords
- database
- task
- function
- test
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3692—Test management for test results analysis
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a method, a device and a server for testing a database, wherein the method for testing the database comprises the following steps: after test requirement configuration information of a database to be tested is obtained, generating a test case according to the test requirement configuration information; wherein, the test case is used for testing: at least requiring the designated function executed by a database layer in the database to be tested; creating a test task according to the test case; and testing the specified function of the database to be tested based on the test task to obtain a test result. According to the method, the test case generated according to the test requirement configuration information needs to be executed by the database layer in the database to be tested, so that the specified function executed by the database layer in the database to be tested can be tested based on the test case, and further, the automatic test of each function in the database layer is realized, and the comprehensiveness of the database test is improved.
Description
Technical Field
The invention relates to the technical field of databases, in particular to a method, a device and a server for testing a database.
Background
The database (cloud database for short) in the cloud computing environment comprises a web layer, a trove layer and a database layer; in the related art, most of the automatic tests on the cloud database only test an Application Programming Interface (API) on a web layer, or test a trove layer through an automatic test script on the trove layer which is developed and maintained by itself, and both of the two automatic test methods are difficult to realize the automatic tests on each function in the database layer, and have poor test comprehensiveness on of the cloud database.
Disclosure of Invention
The invention aims to provide a method, a device and a server for testing a database, so as to realize automatic testing of each function in a database layer and improve the comprehensiveness of database testing.
The invention provides a method for testing a database, which comprises the following steps: acquiring test requirement configuration information of a database to be tested; generating a test case according to the test requirement configuration information; wherein the test case is used for testing: at least requiring the designated function executed by the database layer in the database to be tested; creating a test task according to the test case; and testing the specified function of the database to be tested based on the test task to obtain a test result.
Further, the specified function includes one or more of the following: the system comprises a data backup function, a data recovery function, a database restart function, a database configuration change function, a database slave node adding function and a database password resetting function.
Further, the step of creating a test task according to the test case includes: if the designated function comprises a data backup function, a first database connection task, a data operation task, a data backup task and a master-slave database consistency detection task are established; if the designated function comprises a data recovery function, a first database connection task, a data operation task, a data recovery task, a first data comparison task and a master-slave database consistency detection task are established; if the designated function comprises a database restarting function, a first database connection task, a data operation task, a database restarting task, a second data comparison task and a master-slave database consistency detection task are created; if the designated function comprises a database configuration change function, a first database connection task, a data operation task, a database configuration modification task, a third data comparison task and a master-slave database consistency detection task are created; if the designated function comprises a database slave node adding function, a first database connection task, a data operation task, a database slave node adding task, a newly-added slave node connection task, a fourth data comparison task and a master-slave database consistency detection task are created; and if the designated function comprises a database password resetting function, creating a database creating task, a second database connecting task, a database password resetting task and a third database connecting task.
Further, the step of testing the designated function of the database to be tested based on the test task to obtain a test result includes: sending the test task to a cloud server, and calling a function module corresponding to the specified function in the database to be tested to execute the test task through the cloud server to obtain an execution result; and determining whether the specified function passes the test or not according to the execution result.
Further, the step of determining whether the specified function passes the test according to the execution result includes: if the test task comprises a master-slave database consistency detection task, acquiring an execution result of executing the master-slave database consistency detection task; and judging whether the execution result indicates that the data in the master database, the slave database and the backup database in the database to be tested are consistent, and if so, determining that the specified function test corresponding to the master-slave database consistency detection task passes.
Further, the step of determining whether the specified function passes the test according to the execution result includes: if the test task comprises the data comparison task corresponding to the specified function, acquiring an execution result of executing the data comparison task corresponding to the specified function; and judging whether the execution result indicates that the compared data are consistent, and if so, determining that the specified function test is passed.
The invention provides a testing device of a database, which comprises: the acquisition module is used for acquiring the test requirement configuration information of the database to be tested; the generating module is used for generating a test case according to the test requirement configuration information; wherein the test case is used for testing: at least requiring the designated function executed by the database layer in the database to be tested; the creating module is used for creating a test task according to the test case; and the test module is used for testing the specified function of the database to be tested based on the test task to obtain a test result.
Further, the specified function includes one or more of the following: the system comprises a data backup function, a data recovery function, a database restart function, a database configuration change function, a database slave node adding function and a database password resetting function.
Further, the creating module is further configured to: if the designated function comprises a data backup function, a first database connection task, a data operation task, a data backup task and a master-slave database consistency detection task are established; if the designated function comprises a data recovery function, a first database connection task, a data operation task, a data recovery task, a first data comparison task and a master-slave database consistency detection task are established; if the designated function comprises a database restarting function, a first database connection task, a data operation task, a database restarting task, a second data comparison task and a master-slave database consistency detection task are created; if the designated function comprises a database configuration change function, a first database connection task, a data operation task, a database configuration modification task, a third data comparison task and a master-slave database consistency detection task are created; if the designated function comprises a database slave node adding function, a first database connection task, a data operation task, a database slave node adding task, a newly-added slave node connection task, a fourth data comparison task and a master-slave database consistency detection task are created; and if the designated function comprises a database password resetting function, creating a database creating task, a second database connecting task, a database password resetting task and a third database connecting task.
Further, the test module is further configured to: sending the test task to a cloud server, and calling a function module corresponding to the specified function in the database to be tested to execute the test task through the cloud server to obtain an execution result; and determining whether the specified function passes the test or not according to the execution result.
The invention provides a server, which comprises a processor and a memory, wherein the memory stores machine executable instructions capable of being executed by the processor, and the processor executes the machine executable instructions to realize the test method of the database.
The present invention provides a machine-readable storage medium having stored thereon machine-executable instructions that, when invoked and executed by a processor, cause the processor to implement the above-described database testing method.
According to the method, the device and the server for testing the database, provided by the invention, after the test requirement configuration information of the to-be-tested database is obtained, the test case is generated according to the test requirement configuration information; wherein, the test case is used for testing: at least requiring the designated function executed by a database layer in the database to be tested; creating a test task according to the test case; and testing the specified function of the database to be tested based on the test task to obtain a test result. According to the method, the test case generated according to the test requirement configuration information needs to be executed by the database layer in the database to be tested, so that the specified function executed by the database layer in the database to be tested can be tested based on the test case, and further, the automatic test of each function in the database layer is realized, and the comprehensiveness of the database test is improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 is a schematic diagram of a hardware scenario of a test database according to an embodiment of the present invention;
fig. 2 is a flowchart of a method for testing a database according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of a test flow of a data recovery function according to an embodiment of the present invention;
FIG. 4 is a schematic diagram illustrating a testing process of a database restart function according to an embodiment of the present invention;
FIG. 5 is a schematic diagram illustrating a testing process of a database configuration modification function according to an embodiment of the present invention;
FIG. 6 is a schematic diagram illustrating a testing process of adding functions from nodes to a database according to an embodiment of the present invention;
FIG. 7 is a flow chart of another method for testing a database according to an embodiment of the present invention;
fig. 8 is a schematic structural diagram of a database testing apparatus according to an embodiment of the present invention;
fig. 9 is a schematic structural diagram of a server according to an embodiment of the present invention.
Detailed Description
The technical solutions of the present invention will be described clearly and completely with reference to the following embodiments, and it should be understood that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
For ease of understanding, a hardware scenario for testing a database is first described. As shown in fig. 1, the system includes a local server, a cloud server (which may also be referred to as a cloud host), and a database server to be tested, which are sequentially connected through a network. The local server is provided with test software, and the test software is used for receiving a test requirement file provided by a user; the cloud server is used for executing specific tasks such as data testing, processing and the like; the database server to be tested comprises a web layer, a trove layer and a database layer, wherein the web layer is used for receiving an access request of a user, and after the access request is obtained, the trove layer is accessed through an API (application programming interface); the trove layer is used for managing the database layer, and particularly can access the database layer through a corresponding API (application program interface); the database layer is used for storing data.
In the related art, the automated testing of the cloud database is usually performed on an interface API of a web layer, or performed on an automated testing or a manual testing of a trove layer, and because the above testing method lacks a functional verification of the database layer, it is difficult to perform the automated testing of each functional module of the database layer, for example: whether the database layer can be normally communicated or normally accessed, whether the operation on the database layer can influence the data stored in the database, whether the data acquisition of different nodes of the cluster in the cloud database is normal, whether the data of the different nodes are consistent and the like are tested. The test comprehensiveness of the cloud database is poor, and the correctness and stability of subsequent products related to the database are easily influenced.
Based on the above, embodiments of the present invention first provide a method, an apparatus, and a server for testing a database, where the technology may be applied to testing the database, especially testing the database in a cloud computing environment, that is, testing the cloud database. First, referring to a flow chart of a testing method of a database shown in fig. 2, the method includes the following steps:
step S202, obtaining the test requirement configuration information of the database to be tested.
The test requirement configuration information is usually developed or set by a test engineer, and specifically, the test engineer may develop the test requirement configuration information according to a functional requirement of the database to be tested, and the test requirement configuration information may be a test requirement configuration file. The function requirements of the database to be tested can cover the web layer, the trove layer and the database layer so as to ensure the integrity and the correctness of the function verification of the database to be tested, the test requirement configuration file corresponds to the function requirements to be tested, and a test engineer sends the test requirement configuration file to test software in the local server.
The test requirement configuration information may include a plurality of items of data information, such as: AWS (Amazon Web Services) parameters, Virtual Private Cloud (VPC) parameters, security groups ip, database predefined passwords and modified passwords, data volumes to be operated by the database, database protocols, and the like, wherein the AWS parameters may also be referred to as Amazon authentication algorithm parameters. In actual implementation, the test requirement configuration information may be stored in a test requirement configuration file, and the format of the test requirement configuration file may adopt a conf format, and of course, may also adopt other file formats.
Step S204, generating a test case according to the test requirement configuration information; wherein, the test case is used for testing: at least the designated function performed by the database layer in the database under test is required.
Based on the received test requirement configuration file, a plurality of test cases can be generated in the test software of the local server, the test cases generally include data information such as test input conditions, test execution conditions, expected results and the like, each test case is used for testing one function in the database to be tested, and the function may need to be completed by one or more layers of a web layer, a trove layer and a database layer in the database to be tested.
In this embodiment, in order to implement the test on the database layer, the test case is used to test at least a specified function that needs to be executed by the database layer in the database to be tested; specifically, the test case may test only a specific function that needs to be executed by a database layer in the database to be tested, or may test a specific function that needs to be executed cooperatively by a web layer and the database layer in the database to be tested, a specific function that needs to be executed cooperatively by a trove layer and the database layer, or a specific function that needs to be executed cooperatively by the web layer, the trove layer and the database layer. In most cases, since the database layer is the lowest layer of the database, the specified function of the test case test needs to be executed cooperatively by the web layer, the trove layer and the database layer. The designated function is generally related to data operations, such as a data backup function, a data comparison function, and the like.
And step S206, creating a test task according to the test case.
Based on the test cases, a test task matched with each test case is created in the test software of the local server to complete the verification of the function corresponding to the test case, and the test task can be understood as follows: in order to accurately verify a relevant test process to be executed by a certain function of a database to be tested, the test process may require multiple steps, for example, to verify a data backup function, a relevant database connection task, a data operation task, a consistency detection task of backup data and original data, and the like are required to be created.
And S208, testing the specified function of the database to be tested based on the test task to obtain a test result.
Performing corresponding operation on the database according to the test task established in the step; after the test task is executed, the database usually returns a task execution result, and the task execution result is analyzed, compared, calculated and the like, so that the test result can be obtained. If the test result meets the expected result, the specified function may be confirmed to pass the test, and if the test result does not meet the expected result, the specified function may be confirmed to fail the test.
According to the test method of the database provided by the embodiment of the invention, after the test requirement configuration information of the database to be tested is acquired, a test case is generated according to the test requirement configuration information; wherein, the test case is used for testing: at least requiring the designated function executed by a database layer in the database to be tested; creating a test task according to the test case; and testing the specified function of the database to be tested based on the test task to obtain a test result. According to the method, the test case generated according to the test requirement configuration information needs to be executed by the database layer in the database to be tested, so that the specified function executed by the database layer in the database to be tested can be tested based on the test case, and further, the automatic test of each function in the database layer is realized, and the comprehensiveness of the database test is improved.
The embodiment of the invention also provides another database test method, which is realized on the basis of the method in the embodiment; the method mainly describes a specific implementation process for creating a test task according to a test case, and comprises the following steps:
step 302, obtaining the test requirement configuration information of the database to be tested.
Step 304, generating a test case according to the test requirement configuration information; wherein, the test case is used for testing: at least the designated function performed by the database layer in the database under test is required.
Based on the received test requirement configuration file, several test cases may be generated in the test software of the local server, where each test case is used to test a function in the database to be tested, where the function at least includes a specified function of the database layer, and the specified function generally includes one or more of the following: the system comprises a data backup function, a data recovery function, a database restart function, a database configuration change function, a database slave node adding function and a database password resetting function.
Step 306, if the designated function includes a data backup function, a first database connection task, a data operation task, a data backup task and a master-slave database consistency detection task are created.
In order to complete the test of the data backup function, the first database connection task, the data operation task, the data backup task and the master-slave database consistency detection task need to be completed; these tasks may be specifically performed by the following steps 1-4:
step 1: and executing a first database connection task to establish a channel for accessing the database layer. Whether the to-be-tested database can be normally connected or not can be judged through the step, so that the subsequent normal access to the data stored in the to-be-tested database is facilitated; in actual implementation, the database to be tested and the cloud host can be connected through a specific API, so that the cloud host can acquire and operate data in the database to be tested.
Step 2: executing a data operation task; the data operation task may specifically be one or more of a data adding task, a data deleting task, and a data modifying task. After the database to be tested is connected, operations such as adding, deleting or modifying the data stored in the database to be tested can be performed.
And step 3: executing a data backup task; specifically, the data that has completed the data operation in step 2 may be subjected to a backup operation, and a storage address of the backup data may be specified in advance.
And 4, step 4: executing a master-slave database consistency detection task; after the data operation task and the data backup task are completed, the updated data in the master database is usually synchronized to the slave database and the backup database. By executing the task of detecting the consistency of the master database and the slave database, whether the data in the master database, the slave database and the backup database are consistent or not can be determined, and further whether the master database, the slave database and the backup database can perform data synchronization normally or not can be judged.
And 308, if the designated function comprises a data recovery function, creating a first database connection task, a data operation task, a data recovery task, a first data comparison task and a master-slave database consistency detection task.
In order to complete the test of the data recovery function, the first database connection task, the data operation task, the data recovery task, the first data comparison task and the master-slave database consistency detection task need to be completed; referring to the schematic test flow diagram of the data recovery function shown in fig. 3, these tasks may be specifically executed through the following steps S30-S34:
step S30: and executing a first database connection task to establish a channel for accessing the database layer. Whether the to-be-tested database can be normally connected or not can be judged through the step, so that the subsequent access to the data stored in the to-be-tested database is facilitated; in actual implementation, the database to be tested and the cloud host can be connected through a specific API, so that the cloud host can acquire and operate data in the database to be tested.
Step S31: executing a data operation task; the data operation task may specifically be one or more of a data adding task, a data deleting task, and a data modifying task. After the database to be tested is connected, operations such as adding, deleting or modifying the data stored in the database to be tested can be performed. Before data operation, backup processing may be performed on the original data to obtain backup data.
Step S32: performing a data recovery task; specifically, data recovery may be performed on the data that has completed the data operation in step S31, so as to obtain recovered data; the recovery data may be stored at the original address or at another designated address.
Step S33: executing a first data comparison task; specifically, the recovery data obtained in step S32 may be compared with the backup data to determine whether the recovery data is consistent with the backup data.
Step S34: executing a master-slave database consistency detection task; after the data operation task and the data recovery task are completed, the updated data in the master database is usually synchronized to the slave database and the backup database. By executing the task of detecting the consistency of the master database and the slave database, whether the data in the master database, the slave database and the backup database are consistent or not can be determined, and further whether the master database, the slave database and the backup database can perform data synchronization normally or not can be judged.
In step 310, if the designated function includes a database restart function, a first database connection task, a data operation task, a database restart task, a second data comparison task, and a master-slave database consistency detection task are created.
In order to complete the test of the database restarting function, the first database connection task, the data operation task, the database restarting task, the second data comparison task and the master-slave database consistency detection task need to be completed; referring to the schematic flow chart of the test of the database restart function shown in fig. 4, these tasks may be specifically executed through the following steps S40-S44:
step S40: and executing a first database connection task to establish a channel for accessing the database layer. Whether the to-be-tested database can be normally connected or not can be judged through the step, so that the subsequent normal access to the data stored in the to-be-tested database is facilitated; in actual implementation, the database to be tested and the cloud host can be connected through a specific API, so that the cloud host can acquire and operate data in the database to be tested.
Step S41: executing a data operation task; the data operation task may specifically be one or more of a data adding task, a data deleting task, and a data modifying task. After the database to be tested is connected, operations such as adding, deleting or modifying the data stored in the database to be tested can be performed, and the data operation process is recorded.
Step S42: executing a database restart task; specifically, the database to be tested that has completed the data operation may be restarted to obtain a restarted database.
Step S43: executing a second data comparison task; specifically, the operation process of the data recorded in the database after the restart obtained in step S42 may be compared with the operation process of the data recorded in step S41, and it is determined whether the data in the database after the restart is consistent with the data in the database before the restart.
Step S44: executing a master-slave database consistency detection task; after the data operation task and the database restart task are completed, the updated data in the master database is usually synchronized to the slave database and the backup database. By executing the task of detecting the consistency of the master database and the slave database, whether the data in the master database, the slave database and the backup database are consistent or not can be determined, and further whether the master database, the slave database and the backup database can perform data synchronization normally or not can be judged.
Step 312, if the designated function includes a database configuration modification function, a first database connection task, a data operation task, a database configuration modification task, a third data comparison task, and a master-slave database consistency detection task are created.
In order to complete the test of the database configuration change function, the first database connection task, the data operation task, the database configuration modification task, the third data comparison task and the master-slave database consistency detection task need to be completed; referring to the schematic test flow diagram of the database configuration modification function shown in fig. 5, these tasks may be specifically executed through the following steps S50-S54:
step S50: and executing a first database connection task to establish a channel for accessing the database layer. Whether the to-be-tested database can be normally connected or not can be judged through the step, so that the subsequent normal access to the data stored in the to-be-tested database is facilitated; in actual implementation, the database to be tested and the cloud host can be connected through a specific API, so that the cloud host can acquire and operate data in the database to be tested.
Step S51: executing a data operation task; the data operation task may specifically be one or more of a data adding task, a data deleting task, and a data modifying task. After the database to be tested is connected, operations such as adding, deleting or modifying the data stored in the database to be tested can be performed, and the operation process is recorded.
Step S52: executing a database configuration modification task; specifically, the configuration of the database to be tested, on which the data operation has been completed, may be modified according to the configuration parameters defined in the configuration modification code (i.e., the configuration parameters in the configuration command), so as to obtain a modified and configured database.
Step S53: executing a third data comparison task; the data in the database after the configuration modification obtained in step S52 may be compared with the data in the database before the configuration modification to determine whether the data are consistent. Specifically, the configuration information of the database after configuration modification may be obtained and compared with the configuration defined in the code (i.e., the configuration parameters in the configuration command) to determine whether the configuration information and the configuration information are consistent.
Step S54: executing a master-slave database consistency detection task; after the data operation task and the database configuration modification task are completed, the updated data in the master database is usually synchronized to the slave database and the backup database. By executing the task of detecting the consistency of the master database and the slave database, whether the data in the master database, the slave database and the backup database are consistent or not can be determined, and further whether the master database, the slave database and the backup database can perform data synchronization normally or not can be judged.
Step 314, if the designated function includes a database slave node adding function, a first database connection task, a data operation task, a database slave node adding task, a newly added slave node connection task, a fourth data comparison task and a master-slave database consistency detection task are created.
In order to complete the test of the function of adding the slave nodes of the database, the first database connection task, the data operation task, the task of adding the slave nodes of the database, the task of connecting newly added slave nodes, the fourth data comparison task and the task of detecting the consistency of the master database and the slave database need to be completed; referring to the schematic diagram of the test flow of adding functions from the nodes to the database shown in fig. 6, these tasks may be specifically executed through the following steps S60-S65:
step S60: and executing a first database connection task to establish a channel for accessing the database layer. Whether the to-be-tested database can be normally connected or not can be judged through the step, so that the subsequent access to the data stored in the to-be-tested database is facilitated; in actual implementation, the database to be tested and the cloud host can be connected through a specific API, so that the cloud host can acquire and operate data in the database to be tested.
Step S61: executing a data operation task; the data operation task may specifically be one or more of a data adding task, a data deleting task, and a data modifying task. After the database to be tested is connected, operations such as adding, deleting or modifying the data stored in the database to be tested can be performed, and the operation process can be recorded.
Step S62: executing a database slave node adding task; specifically, the number of slave nodes in the database to be tested may be increased, for example: the database to be tested is increased from one slave node to three slave nodes, and the database management system configures corresponding IP addresses and port numbers for each newly-created slave node.
Step S63: executing a new slave node connection task; and connecting each newly created slave node with the existing slave node based on the IP address and the port number of each newly created slave node, if the connection is successful, representing that the slave node is successfully added, obtaining a database after the new slave node is added, and if the connection is unsuccessful, representing that the slave node is failed to be added. After the slave node is successfully added, the data of the original slave node can be backed up to the newly added slave node.
Step S64: executing a fourth data comparison task; specifically, the data in the database after the new slave node obtained in step S63 may be compared with the data in the database of the original slave node to determine whether the two data are consistent.
Step S65: executing a master-slave database consistency detection task; after the data operation task, the database slave node adding task, and the newly added slave node connecting task are completed, the updated data in the master database is usually synchronized to the slave database and the backup database. By executing the task of detecting the consistency of the master database and the slave database, whether the data in the master database, the slave database and the backup database are consistent or not can be determined, and further whether the master database, the slave database and the backup database can perform data synchronization normally or not can be judged.
In step 316, if the designated function includes a database password reset function, a database creation task, a second database connection task, a database password reset task, and a third database connection task are created.
In order to complete the test of the password resetting function of the database, the database creating task, the second database connection task, the password resetting task of the database and the third database connection task need to be completed, wherein the second database connection task is based on the password connection database in the database creating process; the third database connection task is based on the reset password to connect the database; these tasks may be specifically performed by the following steps 1-4:
step 1: executing a database creation task; the initial password can be set according to the password policy when the database is created, and the initial password can comprise upper and lower case letters, number combination and the like.
Step 2: executing a second database connection task; and connecting the database based on the initial password in the database creating process to establish a channel for accessing the database layer. Through the step, whether the created database can be normally connected or not can be judged, and the subsequent access to the data stored in the created database is facilitated.
And step 3: executing a database password reset task; specifically, a new database password may be reset for the database created in step 1, so as to obtain the database after password resetting.
And 4, step 4: executing a third database connection task; and (4) connecting the database after password resetting based on the new database password set in the step (3) to establish a channel for accessing the database layer. Through the steps, whether the database after the password resetting can be normally connected or not can be judged, and the subsequent access to the data stored in the database after the password resetting is convenient.
And 318, testing the specified function of the database to be tested based on the test task to obtain a test result.
The embodiment of the invention provides another method for testing a database, which describes different test tasks created based on specified functions such as a data backup function, a data recovery function, a database restart function, a database configuration change function, a database slave node adding function, a database password resetting function and the like in detail, wherein the test tasks correspond to the specified functions, and the specified functions of the database to be tested are tested based on the test tasks to obtain test results. According to the method, the test case generated according to the test requirement configuration information needs to be executed by the database layer in the database to be tested, so that the specified function executed by the database layer in the database to be tested can be tested based on the test case, and further, the automatic test of each function in the database layer is realized, and the comprehensiveness of the database test is improved.
The embodiment of the invention also provides a flow chart of another database testing method, which is realized on the basis of the method of the embodiment; the method mainly describes a specific implementation process of testing the specified function of the database to be tested based on the test task to obtain the test result, as shown in fig. 7, the method comprises the following steps:
step S702, obtaining the test requirement configuration information of the database to be tested.
Step S704, generating a test case according to the test requirement configuration information; wherein, the test case is used for testing: at least the designated function performed by the database layer in the database under test is required.
Step S706, a test task is created according to the test case.
Step S708, sending the test task to a cloud server, and calling a function module corresponding to the specified function in the to-be-tested database to execute the test task through the cloud server, so as to obtain an execution result.
The cloud server and the local server can be connected through a specific API, the test software in the local server sends the test tasks created in the steps to the cloud server, and after receiving the test tasks, the cloud server calls a corresponding database connection module to connect with a database to be tested, for example: when the to-be-tested database is a Redis database, the cloud server is connected with the to-be-tested Redis database by calling a Redis module in python, and calls a data backup module, a data recovery module, a database restart module, a database configuration change module, a database slave node increasing module, a database password resetting module and the like through an OpenApi interface to execute corresponding test tasks and obtain an execution result, wherein the execution result contains running data for executing each test task.
The data backup module is a functional module corresponding to a data backup function, and is used for executing a series of tasks created for testing the data backup function; the data recovery module is a functional module corresponding to a data recovery function, and is used for executing a series of tasks created for testing the data recovery function; the database restart module is a functional module corresponding to a database restart function, and is used for executing a series of tasks created for testing the database restart function; the database configuration modification module is a functional module corresponding to the database configuration modification function, and is used for executing a series of tasks created for testing the database configuration modification function; the database slave node adding module is a functional module corresponding to the database slave node adding function and is used for executing a series of tasks created for testing the database slave node adding function; the database password reset module is a functional module corresponding to the database password reset function, and is used for executing a series of tasks created for testing the database password reset function.
Step S710, determining whether the specified function passes the test according to the execution result.
The cloud server sends the operation data in the execution result obtained in the last step to the test software in the local server, the test software determines the test result of each functional module according to the received operation data, if the test result meets the expected result, the specified function can be confirmed to pass the test, and if the test result does not meet the expected result, the specified function can be confirmed to fail the test.
Another implementation of step S710 is further described below:
(1) if the test task comprises a master-slave database consistency detection task, acquiring an execution result of executing the master-slave database consistency detection task; and judging whether the execution result indicates that the data in the master database, the slave database and the backup database in the database to be tested are consistent, and if so, determining that the specified function corresponding to the master-slave database consistency detection task passes the test.
When the designated function of the database layer in the database to be tested comprises a data backup function, after the corresponding test task is executed, if the running data of the master-slave database consistency detection task indicates that the data in the master database, the slave database and the backup database in the database to be tested are consistent, and indicates that the master database, the slave database and the backup database can normally carry out data synchronization, the data backup function in the database to be tested can be confirmed to pass the test; if the data in the master database, the slave database and the backup database are inconsistent, which indicates that the master database, the slave database and the backup database cannot perform data synchronization normally, it can be determined that the data backup function test in the database to be tested fails.
When the designated function of the database layer in the database to be tested comprises a data recovery function, after the corresponding test task is executed, if the running data of the master-slave database consistency detection task indicates that the data in the master database, the slave database and the backup database in the database to be tested are consistent, and indicates that the master database, the slave database and the backup database can normally carry out data synchronization, the data recovery function in the database to be tested can be confirmed to pass the test; if the data in the master database, the slave database and the backup database are inconsistent, which indicates that the master database, the slave database and the backup database cannot perform data synchronization normally, it can be determined that the data recovery function test in the database to be tested fails.
When the designated function of the database layer in the database to be tested comprises a database restarting function, after the corresponding test task is executed, if the running data of the master-slave database consistency detection task indicates that the data in the master database, the slave database and the backup database in the database to be tested are consistent, and indicates that the master database, the slave database and the backup database can normally perform data synchronization, the database restarting function in the database to be tested can be confirmed to pass the test; if the data in the master database, the slave database and the backup database are inconsistent, which indicates that the master database, the slave database and the backup database cannot perform data synchronization normally, it can be determined that the database restart function test in the database to be tested fails.
When the specified function of the database layer in the database to be tested comprises a database configuration change function, after the corresponding test task is executed, if the running data of the master-slave database consistency detection task indicates that the data in the master database, the slave database and the backup database in the database to be tested are consistent, and the data synchronization can be normally performed by the master database, the slave database and the backup database, the test of the database configuration change function in the database to be tested is passed; if the data in the master database, the slave database and the backup database are inconsistent, which indicates that the master database, the slave database and the backup database cannot perform data synchronization normally, it can be determined that the database configuration change function test in the database to be tested fails.
When the designated function of the database layer in the database to be tested comprises a database slave node adding function, after the corresponding test task is executed, if the running data of the master-slave database consistency detection task indicates that the data in the master database, the slave database and the backup database in the database to be tested are consistent, and indicates that the master database, the slave database and the backup database can normally perform data synchronization, the passing of the function test of the slave node in the database to be tested can be confirmed, and if the data in the master database, the slave database and the backup database are inconsistent, the data in the master database, the slave database and the backup database cannot normally perform data synchronization, the failure of the function test of the slave node adding function of the database in the database to be tested can be confirmed.
(2) If the test task comprises a data comparison task corresponding to the specified function, acquiring an execution result of the data comparison task corresponding to the specified function; and judging whether the execution result indicates that the compared data are consistent, and if so, determining that the specified function test is passed.
When the designated function of the database layer in the database to be tested comprises a data recovery function, if the running data of the corresponding data comparison task indicates that the data in the database after the data recovery is finished is consistent with the data in the backed-up database, and indicates that the data stored in the database is not influenced after the data operation task and the data recovery task are finished, the data recovery function in the database to be tested can be confirmed to be passed; and if the running data of the corresponding data comparison task indicates that the data in the database after the data recovery is finished is inconsistent with the backed-up data in the database, the data operation task and the data recovery task are finished and influence is generated on the data stored in the database, and the data recovery function test in the database to be tested can be determined to be failed.
When the designated function of the database layer in the database to be tested comprises a database restarting function, if the running data of the corresponding data comparison task indicates that the data in the database after restarting is consistent with the data operation process recorded when the data operation task is executed, the data operation task and the database restarting task are finished and no influence is generated on the data stored in the database, the test passing of the database restarting function in the database to be tested can be confirmed; if the running data of the corresponding data comparison task indicates that the data in the database after restarting is not consistent with the data operation process recorded when the data operation task is executed, the data operation task and the database restarting task are completed and then influence is generated on the data stored in the database, and it can be confirmed that the database restarting function test in the database to be tested fails.
When the specified function of the database layer in the database to be tested comprises a database configuration change function, if the running data of the corresponding data comparison task indicates that the data in the database after configuration modification is consistent with the data in the database before configuration modification, and indicates that the data operation task and the database configuration change task are finished and do not influence the data stored in the database, the test of the database configuration change function in the database to be tested is passed; and if the running data of the corresponding data comparison task indicates that the data in the database after the configuration modification is inconsistent with the data in the database before the configuration modification, the running data indicates that the data operation task and the database configuration modification task are completed and then influence is generated on the data stored in the database, the failure of the test of the database configuration modification function in the database to be tested can be confirmed.
When the designated function of the database layer in the database to be tested comprises a database slave node adding function, if the running data of the corresponding data comparison task indicates that the data in the database after the new slave node is added is consistent with the data in the database of the original slave node, the running data indicates that the data operation task, the database slave node adding task and the new slave node connecting task are completed and do not influence the data stored in the database, the test of the database slave node adding function in the database to be tested is passed; and if the running data of the corresponding data comparison task indicates that the data in the database after the newly added slave node is inconsistent with the data in the database of the original slave node, the running data indicates that the data operation task, the database slave node adding task and the newly added slave node connection task are completed and influence is exerted on the data stored in the database, the situation that the function test of the database slave node adding in the database to be tested fails can be confirmed.
According to the other testing method of the database provided by the embodiment of the invention, a testing task is created according to the test case; according to the method, a test case generated according to test requirement configuration information needs to be executed by a database layer in the database to be tested, so that the specified function executed by the database layer in the database to be tested can be tested based on the test case, and further, the automatic testing of each function in the database layer is realized, and the comprehensiveness of the database testing is improved.
Referring to fig. 8, a schematic structural diagram of a testing apparatus for a database is shown, the apparatus including: an obtaining module 80, configured to obtain test requirement configuration information of a database to be tested; the generating module 81 is configured to generate a test case according to the test requirement configuration information; wherein the test case is used for testing: at least requiring the designated function executed by a database layer in the database to be tested; a creating module 82, configured to create a test task according to the test case; and the test module 83 is configured to test the specified function of the database to be tested based on the test task to obtain a test result.
The testing device of the database acquires the testing requirement configuration information of the database to be tested, and then generates a testing case according to the testing requirement configuration information; wherein, the test case is used for testing: at least requiring the designated function executed by a database layer in the database to be tested; creating a test task according to the test case; and testing the specified function of the database to be tested based on the test task to obtain a test result. The device needs the execution of the database layer in the database to be tested according to the test case generated by the test requirement configuration information, so that the specified function executed by the database layer in the database to be tested can be tested based on the test case, and further, the automatic test of each function in the database layer is realized, thereby improving the comprehensiveness of the database test.
Further, the specified function includes one or more of the following: the system comprises a data backup function, a data recovery function, a database restart function, a database configuration change function, a database slave node adding function and a database password resetting function.
Further, the creating module 82 is further configured to: if the designated function comprises a data backup function, a first database connection task, a data operation task, a data backup task and a master-slave database consistency detection task are established; if the designated function comprises a data recovery function, a first database connection task, a data operation task, a data recovery task, a first data comparison task and a master-slave database consistency detection task are established; if the designated function comprises a database restarting function, a first database connection task, a data operation task, a database restarting task, a second data comparison task and a master-slave database consistency detection task are established; if the designated function comprises a database configuration change function, a first database connection task, a data operation task, a database configuration modification task, a third data comparison task and a master-slave database consistency detection task are created; if the designated function comprises a database slave node adding function, a first database connection task, a data operation task, a database slave node adding task, a newly-added slave node connection task, a fourth data comparison task and a master-slave database consistency detection task are created; and if the designated function comprises a database password resetting function, creating a database creating task, a second database connecting task, a database password resetting task and a third database connecting task.
Further, the testing module 83 is further configured to: sending the test task to a cloud server, and calling a functional module corresponding to the specified function in a database to be tested to execute the test task through the cloud server to obtain an execution result; and determining whether the specified function passes the test according to the execution result.
Further, the testing module 83 is further configured to: if the test task comprises a master-slave database consistency detection task, acquiring an execution result of executing the master-slave database consistency detection task; and judging whether the execution result indicates that the data in the master database, the slave database and the backup database in the database to be tested are consistent, and if so, determining that the specified function corresponding to the master-slave database consistency detection task passes through the test.
Further, the testing module 83 is further configured to: if the test task comprises a data comparison task corresponding to the specified function, acquiring an execution result of the data comparison task corresponding to the specified function; and judging whether the execution result indicates that the compared data are consistent, and if so, determining that the specified function test is passed.
The implementation principle and the technical effect of the testing device for the database provided by the embodiment of the invention are the same as those of the testing method for the database, and for the sake of brief description, the corresponding contents in the testing method for the database can be referred to where the embodiment of the testing device for the database is not mentioned.
An embodiment of the present invention further provides a server, as shown in fig. 9, where the server includes a processor 90 and a memory 91, where the memory 91 stores machine executable instructions capable of being executed by the processor 90, and the processor 90 executes the machine executable instructions to implement the method for testing the database.
Further, the server shown in fig. 9 further includes a bus 92 and a communication interface 93, and the processor 90, the communication interface 93 and the memory 91 are connected by the bus 92.
The Memory 91 may include a high-speed Random Access Memory (RAM) and may further include a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. The communication connection between the network element of the system and at least one other network element is realized through at least one communication interface 93 (which may be wired or wireless), and the internet, a wide area network, a local network, a metropolitan area network, and the like can be used. Bus 92 may be an ISA bus, PCI bus, EISA bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one double-headed arrow is shown in FIG. 9, but this does not indicate only one bus or one type of bus.
The processor 90 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 90. The Processor 90 may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the device can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, or a discrete hardware component. The various methods, steps and logic blocks disclosed in the embodiments of the present invention may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present invention may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in the memory 91, and the processor 90 reads the information in the memory 91 and performs the steps of the method of the previous embodiment in combination with the hardware thereof.
The embodiment of the present invention further provides a machine-readable storage medium, where the machine-readable storage medium stores machine-executable instructions, and when the machine-executable instructions are called and executed by a processor, the machine-executable instructions cause the processor to implement the method for testing the database, and specific implementation may refer to method embodiments, and is not described herein again.
The method and apparatus for testing a database and the computer program product of the server provided in the embodiments of the present invention include a computer-readable storage medium storing a program code, where instructions included in the program code may be used to execute the method described in the foregoing method embodiments, and specific implementation may refer to the method embodiments, and will not be described herein again.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.
Claims (12)
1. A method for testing a database, the method comprising:
acquiring test requirement configuration information of a database to be tested;
generating a test case according to the test requirement configuration information; wherein the test case is used for testing: at least requiring the designated function executed by the database layer in the database to be tested;
creating a test task according to the test case;
and testing the specified function of the database to be tested based on the test task to obtain a test result.
2. The method of claim 1, wherein the specified function comprises one or more of: the system comprises a data backup function, a data recovery function, a database restart function, a database configuration change function, a database slave node adding function and a database password resetting function.
3. The method of claim 2, wherein the step of creating a test task from the test case comprises:
if the designated function comprises a data backup function, a first database connection task, a data operation task, a data backup task and a master-slave database consistency detection task are established;
if the designated function comprises a data recovery function, a first database connection task, a data operation task, a data recovery task, a first data comparison task and a master-slave database consistency detection task are established;
if the designated function comprises a database restarting function, a first database connection task, a data operation task, a database restarting task, a second data comparison task and a master-slave database consistency detection task are created;
if the designated function comprises a database configuration change function, a first database connection task, a data operation task, a database configuration modification task, a third data comparison task and a master-slave database consistency detection task are created;
if the designated function comprises a database slave node adding function, a first database connection task, a data operation task, a database slave node adding task, a newly-added slave node connection task, a fourth data comparison task and a master-slave database consistency detection task are created;
and if the designated function comprises a database password resetting function, creating a database creating task, a second database connecting task, a database password resetting task and a third database connecting task.
4. The method of claim 1, wherein the step of testing the designated function of the database under test based on the test task to obtain a test result comprises:
sending the test task to a cloud server, and calling a function module corresponding to the specified function in the database to be tested to execute the test task through the cloud server to obtain an execution result;
and determining whether the specified function passes the test or not according to the execution result.
5. The method of claim 4, wherein the step of determining whether the specified function passes the test according to the execution result comprises:
if the test task comprises a master-slave database consistency detection task, acquiring an execution result of executing the master-slave database consistency detection task;
and judging whether the execution result indicates that the data in the master database, the slave database and the backup database in the database to be tested are consistent, and if so, determining that the specified function test corresponding to the master-slave database consistency detection task passes.
6. The method of claim 4, wherein the step of determining whether the specified function passes the test according to the execution result comprises:
if the test task comprises the data comparison task corresponding to the specified function, acquiring an execution result of executing the data comparison task corresponding to the specified function;
and judging whether the execution result indicates that the compared data are consistent, and if so, determining that the specified function test is passed.
7. An apparatus for testing a database, the apparatus comprising:
the acquisition module is used for acquiring the test requirement configuration information of the database to be tested;
the generating module is used for generating a test case according to the test requirement configuration information; wherein the test case is used for testing: at least requiring the designated function executed by the database layer in the database to be tested;
the creating module is used for creating a test task according to the test case;
and the test module is used for testing the specified function of the database to be tested based on the test task to obtain a test result.
8. The apparatus of claim 7, wherein the specified function comprises one or more of: the system comprises a data backup function, a data recovery function, a database restart function, a database configuration change function, a database slave node adding function and a database password resetting function.
9. The apparatus of claim 8, wherein the creation module is further configured to:
if the designated function comprises a data backup function, a first database connection task, a data operation task, a data backup task and a master-slave database consistency detection task are established;
if the designated function comprises a data recovery function, a first database connection task, a data operation task, a data recovery task, a first data comparison task and a master-slave database consistency detection task are established;
if the designated function comprises a database restarting function, a first database connection task, a data operation task, a database restarting task, a second data comparison task and a master-slave database consistency detection task are created;
if the designated function comprises a database configuration change function, a first database connection task, a data operation task, a database configuration modification task, a third data comparison task and a master-slave database consistency detection task are created;
if the designated function comprises a database slave node adding function, a first database connection task, a data operation task, a database slave node adding task, a newly-added slave node connection task, a fourth data comparison task and a master-slave database consistency detection task are created;
and if the designated function comprises a database password resetting function, creating a database creating task, a second database connecting task, a database password resetting task and a third database connecting task.
10. The apparatus of claim 7, wherein the testing module is further configured to:
sending the test task to a cloud server, and calling a function module corresponding to the specified function in the database to be tested to execute the test task through the cloud server to obtain an execution result;
and determining whether the specified function passes the test or not according to the execution result.
11. A server comprising a processor and a memory, the memory storing machine executable instructions executable by the processor, the processor executing the machine executable instructions to implement a method of testing a database as claimed in any one of claims 1 to 6.
12. A machine-readable storage medium having stored thereon machine-executable instructions which, when invoked and executed by a processor, cause the processor to carry out a method of testing a database according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910675781.7A CN112286786A (en) | 2019-07-24 | 2019-07-24 | Database testing method and device and server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910675781.7A CN112286786A (en) | 2019-07-24 | 2019-07-24 | Database testing method and device and server |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112286786A true CN112286786A (en) | 2021-01-29 |
Family
ID=74418799
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910675781.7A Pending CN112286786A (en) | 2019-07-24 | 2019-07-24 | Database testing method and device and server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112286786A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113505073A (en) * | 2021-07-15 | 2021-10-15 | 北京金山云网络技术有限公司 | Database performance test method, device, equipment and medium |
| WO2023051073A1 (en) * | 2021-09-30 | 2023-04-06 | 中兴通讯股份有限公司 | Database test method, distributed database, and storage medium |
-
2019
- 2019-07-24 CN CN201910675781.7A patent/CN112286786A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113505073A (en) * | 2021-07-15 | 2021-10-15 | 北京金山云网络技术有限公司 | Database performance test method, device, equipment and medium |
| WO2023051073A1 (en) * | 2021-09-30 | 2023-04-06 | 中兴通讯股份有限公司 | Database test method, distributed database, and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109032611B (en) | Script deployment method and device, computer equipment and storage medium | |
| CN109240924B (en) | Application program testing method and device | |
| CN110908909A (en) | Automatic testing method and device, storage medium and equipment | |
| CN111191250B (en) | Verification method and device, verification device, server and terminal | |
| CN110088744A (en) | A kind of database maintenance method and its system | |
| CN112286786A (en) | Database testing method and device and server | |
| CN112162924A (en) | Interface automation test method and device, computer equipment and storage medium | |
| CN115495142A (en) | Cloud resource arranging method and device, computer equipment and storage medium | |
| US11227051B2 (en) | Method for detecting computer virus, computing device, and storage medium | |
| US20200233674A1 (en) | Automatically configuring boot order in recovery operations | |
| CN116089285A (en) | Database testing method and device, electronic equipment and readable medium | |
| CN114116170A (en) | Timed task execution method and device, computer equipment and storage medium | |
| CN111756594B (en) | Control method of pressure test, computer device and computer readable storage medium | |
| CN112256532A (en) | Test interface generation method and device, computer equipment and readable storage medium | |
| CN115328814A (en) | Fault injection method, device, equipment and storage medium based on image pair | |
| CN111736917B (en) | Data verification method and device, computer equipment and storage medium | |
| CN109240906B (en) | Database configuration information adaptation method and device, computer equipment and storage medium | |
| CN113704123A (en) | Interface test method, device, equipment and storage medium | |
| CN111475400A (en) | Verification method of service platform and related equipment | |
| CN110795142A (en) | Configuration file generation method and device | |
| CN106648558B (en) | Control method and device for TPL (tire pressure level) Dataflow | |
| CN115640236B (en) | Script quality detection method and computing device | |
| CN117556809B (en) | Parameter verification result generation method and device, verification platform and storage medium | |
| CN117573144A (en) | Method and device for deploying elastic search cluster, storage medium and equipment | |
| CN112445761B (en) | File checking method and device and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |