CN116560982A

CN116560982A - Database test method, device, equipment and medium

Info

Publication number: CN116560982A
Application number: CN202310447807.9A
Authority: CN
Inventors: 孟令逍; 景晓; 关华; 顾钊铨; 余涛; 向夏雨; 周琥晨; 陈元; 赵昂霄
Original assignee: Peng Cheng Laboratory
Current assignee: Peng Cheng Laboratory
Priority date: 2023-04-20
Filing date: 2023-04-20
Publication date: 2023-08-08

Abstract

The present disclosure provides database testing methods, apparatus, devices, and media. The database testing method comprises the following steps: acquiring a test task aiming at a source database to be tested; based on the test task, a test database matched with the source database is established; acquiring a first test case in a first test suite; the first test case is operated by using the test data table, and a test result is returned after the operation is finished; deleting data generated by running the first test cases in the test data table so as to run the next first test case in the first test suite by using the test data table; and deleting the test database after all the first test cases in the first test suite are operated. The embodiment of the disclosure can improve the accuracy and stability of database test. The embodiment of the disclosure can be applied to scenes such as database testing of large-scale distributed environments such as federal shooting ranges.

Description

Database test method, device, equipment and medium

Technical Field

The present disclosure relates to the field of big data, and in particular, to a database testing method, apparatus, device, and medium.

Background

In order to ensure that the database can accurately and efficiently manage data and perform data tasks, the database needs to be tested. Database testing requires testing for multiple task scenarios within the database (e.g., data processing, database consistency, etc.). When the test cases of a plurality of test tasks are operated concurrently, the test cases of each test task interact with the database at the same time, and the test failure of a certain test task is easily caused by inconsistent database contents. If a separate database test environment is created for each test case, a significant amount of system resources are consumed, resulting in a program crash.

Disclosure of Invention

The embodiment of the disclosure provides a database test method, a device, equipment and a medium, which can avoid the mutual influence of test cases of each test task, can also avoid program breakdown caused by excessive memory occupation in the test process, and improves the accuracy and stability of database test.

According to an aspect of the present disclosure, there is provided a database test method including:

acquiring a test task aiming at a source database to be tested;

based on the test task, a test database matched with the source database is established, wherein the test database comprises a test data table;

acquiring a first test case in a first test suite, wherein the first test suite is a set of a plurality of first test cases corresponding to the test task;

operating the first test case by using the test data table, and returning a test result after the operation is finished;

deleting data generated by the first test case in the test data table so as to use the test data table to run the next first test case in the first test suite;

and deleting the test database after all the first test cases in the first test suite are operated.

According to an aspect of the present disclosure, there is provided a database test apparatus including:

the first acquisition unit acquires a test task aiming at a source database to be tested;

the first establishing unit establishes a test database matched with the source database based on the test task, wherein the test database comprises a test data table;

the second acquisition unit acquires first test cases in a first test suite, wherein the first test suite is a set of a plurality of first test cases corresponding to the test task;

the first operation unit is used for operating the first test case by utilizing the test data table and returning a test result after the operation is finished;

the first deleting unit is used for deleting the data generated by running the first test cases in the test data table so as to run the next first test cases in the first test suite by using the test data table;

and the second deleting unit is used for deleting the test database after all the first test cases in the first test suite are operated.

Further, the first establishing unit is specifically configured to:

generating a test database identifier for the test database;

Acquiring a test database establishment file, wherein the test database establishment file comprises test database establishment sentences and test data table establishment sentences, and the test data table establishment sentences are generated based on the source database and the test tasks;

running the test database creation file, creating the test database based on the test database creation statement, and creating the test data table in the test database based on the test data table creation statement;

and returning an operation result of the test database identifier and the test database establishment file.

Further, the first establishing unit is specifically configured to:

acquiring a time stamp when the test database is generated;

acquiring a machine identifier of a server executing the database test method;

invoking a random number generation method to obtain a method identifier of the random number generation method, wherein the random number generation method is stored in the server, and each random number generation method has a corresponding method identifier;

generating a random number by using the random number generation method;

the test database identification is generated based on the timestamp, the machine identification, the method identification, and the random number.

Further, the first test kit is constructed by:

acquiring first keywords of a plurality of test cases;

acquiring second keywords of a plurality of test tasks;

and classifying the test cases into the first test suite corresponding to the test task according to the matching condition of the first keyword and the second keyword.

Further, classifying the test case into the first test suite corresponding to the test task includes:

generating a task pointer according to the test task;

directing the task pointer to the area where the test case is stored;

the task pointer is stored in the first test suite.

Further, the first test case is obtained by:

acquiring a preset universal code, wherein the universal code comprises a universal test statement and a random character string generated by test;

constructing the first test case by utilizing the universal code and the test task;

further, the first operation unit is specifically configured to:

constructing a first test environment of the first test case, wherein the first test environment is constructed by using a preset case environment template;

And in the first test environment, the first test case is operated by utilizing the test data table.

Further, the database test device further includes:

the second building unit is used for building a second test environment for database test;

the second test environment is constructed in the following manner;

acquiring a preset database test environment;

and adjusting the preset database test environment based on the test task to obtain the second test environment.

Further, the database test method is applied to the test of the middle stage of the federal range data, and the test task corresponds to the test task of the middle stage of the federal range data;

the obtaining the test task aiming at the source database to be tested comprises the following steps:

acquiring a test task of the middle stage of the federal shooting range data, and determining a test task type of the middle stage of the federal shooting range data, wherein the test task type comprises knowledge graph data construction, file scanning and data authority verification;

generating the first test suite according to the test task type, and determining the first test case in the first test suite;

the running the first test case by using the test data table includes:

Determining the test sequence of the first test case according to the test task type;

and operating the first test case by using the test data table according to the test sequence.

According to an aspect of the present disclosure, there is provided an electronic device comprising a memory storing a computer program and a processor implementing a database test method as described above when executing the computer program.

According to an aspect of the present disclosure, there is provided a computer-readable storage medium storing a computer program which, when executed by a processor, implements a database test method as described above.

According to an aspect of the present disclosure, there is provided a computer program product comprising a computer program which is read and executed by a processor of a computer device, causing the computer device to perform the database test method as described above.

In the embodiment of the disclosure, a test database is established according to a source database to be tested and a test task. The test database is used for testing the test cases in the unique test suite corresponding to each test task. The test database comprises a plurality of test data tables, and data generated in the process of running one test case can be filled in the test data tables. After each test case is tested, the test data table is emptied so that the next test case can use the test data table. And deleting the test database when all the test cases in the test suite are operated. Through the process, the embodiment of the disclosure realizes data isolation among the test cases of different test tasks, and avoids the mutual influence among the test cases; the test cases in the same test suite can use the same test data table, and an independent test data table is not required to be established for each test case, so that excessive system memory is avoided. Therefore, the database test accuracy and stability are improved by the embodiment of the disclosure.

Additional features and advantages of the disclosure will be set forth in the description which follows, and in part will be apparent from the description, or may be learned by practice of the disclosure. The objectives and other advantages of the disclosure will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.

Drawings

The accompanying drawings are included to provide a further understanding of the disclosed embodiments and are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and together with the description serve to explain, without limitation, the disclosed embodiments.

FIG. 1 is a architectural diagram of a database testing method provided by an embodiment of the present disclosure;

FIG. 2 is a flow chart of a database testing method of an embodiment of the present disclosure;

FIG. 3 is a specific flowchart of step 220 of FIG. 2;

FIG. 4 is a specific flow chart of step 310 of FIG. 3;

FIG. 5 is a schematic diagram of a specific structure of a test database representation;

FIG. 6 is a particular flow chart for creating a first test suite;

FIG. 7 is a specific flow chart of step 630 in FIG. 6;

FIG. 8 is a particular flowchart for building a first test case;

FIG. 9 is a specific flowchart of step 240 of FIG. 2;

FIG. 10 is a particular flow diagram of building a second test environment;

FIG. 11 is a system architecture diagram of a federal range;

FIG. 12 is a particular flow chart of an embodiment of the present disclosure as applied to a stage in federal range data;

FIG. 13 is an overall flowchart of a database testing method provided by an embodiment of the present disclosure;

FIG. 14 is a block diagram of a database testing apparatus according to an embodiment of the present disclosure;

FIG. 15 is a terminal block diagram of the database test method shown in FIG. 2 according to an embodiment of the present disclosure;

fig. 16 is a server configuration diagram of the database test method shown in fig. 2 according to an embodiment of the present disclosure.

Detailed Description

In order to make the objects, technical solutions and advantages of the present disclosure more apparent, the present disclosure will be further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present disclosure.

Before proceeding to further detailed description of the disclosed embodiments, the terms and terms involved in the disclosed embodiments are described, which are applicable to the following explanation:

database test: the database test is a test of the database structure, the data table and the data calling relation among the database structure and the data table of the software system according to the database design specification. The database test includes: database design testing, data consistency testing, database capacity testing, database performance testing, database pressure testing, and the like.

Testing of database design means testing whether the database conforms to standardized design, whether the content of each entity is comprehensive, etc.;

the data consistency test needs to test whether the primary key of the data table is unique, whether the primary external key relation among tables is consistent in name, data type and field length, etc.;

database capacity testing refers to estimating the storable capacity of a database;

the database performance test is to test whether the database meets the load requirement, find out the method for optimizing the database and improving the performance of the database;

database stress testing refers to testing whether a database object can effectively withstand concurrent access from multiple users. These objects are mainly: index, trigger, stored procedure, etc.

Federal range: based on the virtualization technology, the network architecture, system equipment, the running state of the business process and the running environment in the real network space are simulated and reproduced. The system is used for supporting network security talent cultivation, network attack and defense training, security product evaluation and network new technology verification; providing a training place for the real security countermeasure of the network technology.

System architecture and scenario description applied to embodiments of the present disclosure

Fig. 1 is a system architecture diagram to which a database test method according to an embodiment of the present disclosure is applied. It includes a terminal 140, the internet 130, a gateway 120, a server 110, etc.

Terminal 140 is a device for initiating database testing. It includes desktop computers, laptop computers, PDAs (personal digital assistants), dedicated terminals, and the like. In addition, the device can be a single device or a set of a plurality of devices. For example, a plurality of devices are connected via a lan, and a display device is commonly used for cooperative operation, so as to form a terminal 140. The terminal 140 may also communicate with the internet 130 in a wired or wireless manner, exchanging data.

Server 110 refers to a computer system capable of servicing database test requests initiated by terminal 140. The server 110 is required to have high stability, security, performance, etc. as compared with the general terminal 140. The server 110 may be one high-performance computer in a network platform, a cluster of multiple high-performance computers, a portion of one high-performance computer (e.g., a virtual machine), a combination of portions of multiple high-performance computers (e.g., virtual machines), etc.

Gateway 120 is also known as an intersubnetwork connector, protocol converter. The gateway realizes network interconnection on a transmission layer and is a computer system or device which acts as a conversion function. The gateway is a translator between two systems using different communication protocols, data formats or languages, and even architectures that are quite different. At the same time, the gateway may also provide filtering and security functions. The message sent by the terminal 140 to the server 110 is to be sent to the corresponding server 110 through the gateway 120. A message sent by the server 110 to the terminal 140 is also sent to the corresponding terminal 140 through the gateway 120.

The embodiments of the present disclosure may be applied in a variety of scenarios. For example, database testing of platforms in data of federal range platforms. The data center of the federal range platform is used as a core module and is responsible for data collection and storage, data processing and analysis, data sharing and exchange, management and maintenance. The data center station needs to process test data from a plurality of subsystems of a plurality of sub-ranges, so that in order to ensure that the data center station can efficiently and accurately store and process data, the data center station has a plurality of test tasks for performing database test, and test cases of different test tasks are concurrently operated.

For example, a test for performing a data deletion operation on a data center station at the same time, and a test for searching data using an association between data tables. If the test cases of the two test tasks are not isolated, when the data to be searched for by a certain search test case is deleted in the test for deleting the data, the search test case can show that the test fails. By the database test method of the embodiment of the disclosure, different test databases are respectively built for the deletion test and the search test, and each test database comprises a test data table. Each test database corresponds to only one test suite, and the test suite comprises test cases for corresponding test tasks. And running the test cases in the corresponding test suite in the test database, and after the running of one test case is finished, emptying the test data table in the test database so as to use the next test case. And deleting the test database after all the test cases in the test suite are operated.

The above is a process of performing database testing using the test of the data center of the federal range as an example.

General description of embodiments of the disclosure

According to one embodiment of the present disclosure, a database testing method is provided.

In the process of testing the database, the situation that test cases under a plurality of test tasks are parallel often occurs, and at this time, the fact that the test of a certain test case fails due to inconsistent database contents in the test process may occur. If a separate test database is created for each test case, then in the case of more test cases, the program may crash due to excessive memory resources. The embodiment of the disclosure provides a test method for isolating test cases of different test tasks, and the test cases of the same test task can use the same database to run the test, so that the mutual influence between the test cases is avoided, excessive occupation of memory resources is avoided, and the accuracy and stability of the database test are improved.

According to one embodiment of the present disclosure, as shown in fig. 2, a database test method includes:

step 210, obtaining a test task aiming at a source database to be tested;

step 220, based on the test task, a test database matched with the source database is established, wherein the test database comprises a test data table;

Step 230, acquiring a first test case in a first test suite, wherein the first test suite is a set of a plurality of first test cases corresponding to a test task;

step 240, running the first test case by using the test data table, and returning a test result after the running is finished;

step 250, deleting data generated by the first test case in the test data table so as to use the test data table to run the next first test case in the first test suite;

step 260, deleting the test database after all the first test cases in the first test suite are run.

The following is a detailed description of steps 210-260

In step 210, the test task indicates which function of the source database to be tested is tested, for example, the test task may be: the data of the data table of the database is added, deleted, modified, or searched for, etc., the interface of the association table is tested by combining the business logic, or the performance of the database is tested, etc. Different test cases are required to be used for testing according to different test tasks. The test task is initiated by a tester, which may be that the tester generates the test task through the terminal 140, and after receiving the test task, the server 110 tests the source database to be tested.

In step 220, test cases of different test tasks are isolated. And establishing a test database for each test task, wherein the test cases corresponding to the test tasks run in the corresponding test databases.

The test database comprises a test data table, the test database is used for running the test cases, and the test data table is used for storing data generated in the process of running the test cases. In one embodiment, as shown in fig. 3, building a database based on a source database to be tested and a test task, includes:

step 310, generating a test database identifier for the test database;

step 320, obtaining a test database building file; the test database creation file comprises test database creation sentences and test data table creation sentences, wherein the test data table creation sentences are generated based on a source database and test tasks;

step 330, running a test database creation file, creating a test database based on the test database creation statement, creating a statement based on the test data table, and creating a test data table in the test database;

and step 340, returning the running result of the test database identification and test database establishment file.

In step 310, since each test task corresponds to only one test database, when the test database is built, a unique test database identifier is generated for the test database to ensure the uniqueness of the test database.

In one embodiment, as shown in FIG. 4, generating a test database identification for a test database includes:

step 410, obtaining a time stamp when the test database is generated;

step 420, obtaining a machine identifier of a server executing the database test method;

step 430, calling a random number generation method to obtain a method identifier of the random number generation method, wherein the random number generation method is stored in a server, and each random number generation method has a corresponding method identifier;

step 440, generating a random number by using a random number generation method;

step 450, generating a test database identification based on the timestamp, the machine identification, the method identification, and the random number.

In step 410, the system time of the server 110 at the time of generating the test database is obtained as a time stamp. The accuracy of the time stamp is limited by the clock accuracy of the server 110, e.g. the clock accuracy of the server is at most in the order of milliseconds, and the time accuracy of the time stamp is at most not more than in the order of milliseconds. The accuracy of the time stamp needs to be consistent with the system time, so that the test database identifiers of the test databases generated at different times are ensured to be different.

In step 420, if server 110 is a cluster of multiple computer systems, then a distinction is required between the computers that generated the test database. The machine identifiers of different computers are different, so that the uniqueness of the test databases generated in the different computers at the server level is ensured.

In step 430, the random number generation method is used to generate a random number, and a plurality of random number generation methods are stored in the server 110, where each random number generation method has a unique method identifier in the server 110 and is used to invoke the random number generation method. When the test database identifier is generated, a random number generation method is randomly called for generating a random number. The method identification of the random number generation method is used as a part of the test data identification, and the generated test database identification can be unique at the object level in the server through the method identification.

In step 440, a random number is generated using the random number generation method in step 430, where each generated random number may be different, thereby achieving millisecond-level uniqueness of the test database identification at the internal object level.

In step 450, a test database identification is generated based on the timestamp, the machine identification, the method identification, and the random number. Illustratively, the structure of the test database identifier is shown in FIG. 5, where the test database identifier contains 32 bits, with 1-8 bits as the timestamp of the system time; the 9-16 bits are used as the machine identification of the computer in the server cluster for generating the test database identification; 17-24 bits are used as a method identifier of a random number generation method for generating random numbers; 25-32 bits are used as the random number generated by the random number generation method.

The advantage of steps 410-450 is that test database identifications generated at different times can be distinguished by a time stamp, test database identifications generated at the same time can be distinguished by a machine identification, test database identifications generated at the same time by the same computer system can be distinguished by a random number generation method used, and test database identifications generated at the same time by the same computer system using the same random number generation method can be distinguished by a random number. Therefore, the combination of the time stamp, the machine identifier, the method identifier and the random number improves the distinguishing degree of the test database identifier and ensures the uniqueness of the test database identifier.

It should be noted that, in the process of generating the test database, the steps 410, 420, 430, and 440 may be performed in any order, or may be performed in parallel.

In step 320, the test database creation file is a database script file, and the test database creation file is used to create a test database according to the test task. The test database creation file contains test database creation sentences and test data table creation sentences. The test database is randomly created by test database creation sentences, and the test data table creation sentences are generated based on the source database and the test tasks. That is, an empty test database is randomly created through the test database creation statement, and is used for isolating test cases of different test tasks; and then creating a test data table in the empty test database through the test data table creation statement. The test data table is used for running test cases, so the test data table needs to meet the requirements of test tasks. For example, the test task needs to look up data through associations between source data tables in the source database, then the test data tables need to have the same fields and associations as the source data tables.

After the test task is acquired, a test database creation file is generated by the source database and the test task so as to execute subsequent steps.

In step 330, the test database creation file is run, and the statements in the test database creation file are sequentially executed. Firstly, creating a statement of a test database, and creating a test database environment based on the statement; this is followed by a test data table creation statement that is executed in turn to create the test data table required for the test task. If an error occurs in the process of executing the statement, the creation is stopped and the program is terminated.

In step 340, after the test database creation file is finished, the test database identifier and the operation result are returned to check whether there is an error or warning information.

Because the sentences in the test database creation file are executed one by one, the test data in the test database are created one by one, and if the operation result is returned after all the sentences are executed, the efficiency is lower. Thus, in one embodiment, when a test library build file is run, a sub-process is created for the run, and the sub-thread is used to read the run results. For example, by using the internal technology of the Li nux system, a subprocess is created for the running process of the test database building file by calling a "fork" function through a "pop" function, a channel is formed between the running process of the test database building file and the subprocess, and the running result output by the running process is directly used as the input of the subprocess.

In this embodiment, the test library establishes that each sentence in the file runs, outputs the running result of the sentence, and directly inputs the running result as a subprocess, so as to be convenient for acquiring the running result in real time after each sentence runs. Therefore, the present embodiment has an advantage in that the reading efficiency of the operation result is improved.

The advantage of steps 310-340 is that the uniqueness of the test database is guaranteed by generating an identification for the test database; the efficiency of creating the test database and the test data table is improved by creating the file through the test database, and when the operation errors occur, the file is created through the test database, so that the error can be conveniently checked.

In step 230, after the test database is created, a first test suite needs to be acquired. The first test suite is a collection of first test cases for a test task. The first test suite operates in a single test database, and any two different first test suites can no longer operate in the same test database, so that different test tasks are isolated from each other by the first test suite.

In one embodiment, as shown in fig. 6, the first test kit is constructed by:

Step 610, obtaining first keywords of a plurality of test cases;

step 620, obtaining second keywords of a plurality of test tasks;

step 630, classifying the test cases into the first test suite corresponding to the test task according to the matching condition of the first keyword and the second keyword.

The first keyword is used to indicate a test task applicable to the test case, for example, the first keyword is: "add data", "security test", or "load test", etc.

The second keyword is used to indicate key information of the test task. For example, the second keyword is: "add data", "security test", or "load test", etc.

And according to the matching condition of the first keyword and the second keyword, the test cases are used as the first test cases to be included in the first test suite corresponding to the test task. For example, the first test suite shown in table 1:

TABLE 1

As shown in Table 1, the first test suite A corresponds to the test task A, the second keyword of the test task A is a "safety test", and the first keywords of the test cases A-D are not necessarily identical to the second keyword, but have a higher matching degree, so that the test cases A-D are classified into the first test suite A for responding to the test task A.

In one embodiment, as shown in fig. 7, classifying test cases into a first test suite corresponding to a test task includes:

step 710, generating a task pointer according to the test task;

step 720, pointing the task pointer to the area where the test case is stored;

step 730, storing the task pointer in the first test suite.

Different test tasks have corresponding different task pointers, and the test cases pointed by the task pointers are the test cases which can be used for processing the corresponding test tasks.

And according to the matching condition of the first keyword and the second keyword, pointing the task pointer to a test case storage area with higher matching degree, and then storing the task pointer in the first test suite. When the first test case in the first test suite needs to be used, the first test case can be found through the task pointer. The first test suite has stored therein a plurality of task pointers of the first test suite. The embodiment has the advantages that the space occupied by the first test case is larger, so that in the first test suite, the first test case is stored by storing the task pointer instead of the task pointer, and the space utilization rate is improved.

The embodiment of steps 610-630 has the advantages that the obtained first test case result in the first test suite is more accurate, and the test cases conforming to the test scene cannot be ignored because the keywords are not completely consistent, so that the construction accuracy and comprehensiveness of the first test suite are improved.

In one embodiment, as shown in FIG. 8, the first test case is obtained by:

step 810, acquiring a preset universal code, wherein the universal code comprises a universal test statement and a random character string generated by test;

step 820, constructing a first test case by using the universal code and the test task;

there are differences in code between test cases, but there are also generic parts. The universal code comprises universal test sentences and random character strings generated by testing. The universal code is preset. When a first test case needs to be constructed, a general code is acquired first, then codes of other parts are supplemented according to the test task, and if the first test case needs to be constructed, the general code is adaptively modified. Through the steps, a complete first test case is formed.

The method and the device have the advantages that the code does not need to be rewritten for each first test case, one first test case is formed by combining the universal code and the custom code, and the efficiency of acquiring the first test case is saved.

In step 240, a first test case in the first test suite is sequentially run in the test data table, and after each test case is run, a running result is returned to check whether the first test case passes.

In one embodiment, as shown in FIG. 9, running a first test case using a test data table includes:

step 910, a first test environment of a first test case is constructed, wherein the first test environment is constructed by using a preset case environment template;

and step 920, in the first test environment, running the first test case by using the test data table.

The first test environments of each first test case may differ, for example, some first test cases require the use of specific steps to open, commit, rollback the database, etc. Therefore, the first test environment of each first test case needs to be set so as to meet the requirements of different first test cases on the test environment.

The first test environment may be constructed by a preset use case environment template. If the first test case has no specific requirement on the test environment, a preset case environment template can be directly used as the first test environment; if the first test case has specific requirements on the test environment, the specific part can be modified in a preset case environment template to acquire the first test environment.

The method and the device have the advantages that the first test environment is built based on the preset use case environment template, and the building efficiency of the first test environment is improved.

In step 250, after one of the first test cases in the first test suite is run, data generated in the running process exists in the test data table. To prevent the impact on the testing of the next first test case, the data in the test data table needs to be emptied.

In one embodiment, flushing data in a test data table includes:

acquiring a test data table emptying file;

canceling the external key constraint of the test data table;

operating a test data table emptying file, and deleting data in the test data table;

restoring the external key constraint of the test data table;

deleting the temporary file;

and obtaining an operation result.

The test data table emptying file is used for emptying the data in the test data table.

The foreign key of the test data table establishes an association for the two test data tables to constrain the consistency and integrity of the data in the two tables. If the data in one table changes, the data in the table associated with the foreign key will also change. Therefore, in order to delete the data in the test data table, it is necessary to cancel the foreign key constraint, that is, cancel the association relationship between the two tables.

And running the test data table emptying file for deleting the data in the test data table. And after the data are completely emptied, the foreign key constraint of the test data table is recovered so as to facilitate the operation of the next first test case.

And deleting the temporary file generated in the running process of the first test case so as to prevent the temporary file from affecting the running of the next first test case. The temporary file may be: a temporary table, statement log, or temporary index file generated during the running of the first test case, etc.

The operation result shows whether an error occurs in the operation process of the test database emptying file, and if the error does not exist, the next first test case can be executed; if errors exist, the error reasons need to be found, the corresponding problems are solved, and the test data table emptying operation is carried out again.

The embodiment has the advantages that all data in the test data table are ensured to be emptied, the operation of the next first test case is not influenced by residual data, an independent environment is provided for the operation of the test case, and the operation stability of the test case is improved.

In step 260, when all the first test cases in the first test suite are running, the test database needs to be deleted to prevent the test database from affecting the original development environment.

In one embodiment, deleting the test database includes:

acquiring a test database deletion file;

Operating a test database to delete files;

and obtaining an operation result.

The process of deleting the test database is the reverse of building the test database. The test database deleting file comprises test database deleting sentences and test data table deleting sentences.

When the test database deleting file is operated, the test data table deleting statement is executed first, and after the test data table deleting is completed, the empty test database is deleted.

After the test database deleted file is operated, an operation result is obtained to check whether an error occurs in the operation process.

In one embodiment, as described in the foregoing embodiment of creating a test database, a sub-process is created for the running process of creating a file for the test database, such that a channel is formed between the running process and the sub-process. Similarly, a subprocess can be created for the operation process of the deleted file of the test database, the operation result is directly used as the input of the subprocess, and the subprocess can directly read the operation result of the statement in the deleted file of the database. The embodiment improves the reading efficiency of the operation result.

Deleting the test database has the advantage that the test database does not affect the environment of the source database. The stability of the source database is ensured.

In one embodiment, before acquiring the test task for the source database to be tested, the database test method further includes: the framework database tests a second test environment;

as shown in fig. 10, the second test environment is constructed by:

step 1010, acquiring a preset database test environment;

and 1020, adjusting a preset database test environment based on the test task to obtain a second test environment.

The database test environment construction comprises the following steps: setting of environment variables, installation and configuration of test tools, setting of database connections, etc. If the test environment needs to be reset every time a test task is performed, a lot of effort is consumed.

Thus, in the embodiments of the present disclosure, a database test environment is preset in which each module is independent of each other, that is, the content in one module changes without affecting the other modules.

If a part needing to be changed exists in the preset environment, the second test environment can be obtained by changing the corresponding module, other modules are not required to be changed, and the other modules are not influenced. For example, when a change occurs in the server environment in which the database test is performed, the database test environment needs to be reconstructed. At this time, only the setting of the environment variable is required to be modified, and other modules are not required to be changed.

The method has the advantages that all modules of the database testing environment are mutually independent, the mutual influence among the modules is not needed to be considered, and the flexibility of the construction of the testing environment is improved; if the second test environment is changed, the module which is changed is only required to be modified without reconstruction, so that the workload of the testers is reduced, and the working efficiency is improved.

The embodiment of the disclosure is suitable for a large-scale distributed environment, in particular an application environment with frequent database call. Such as the federal range environment. Thus, in one embodiment, the database test method is applied to the testing of a table in federal range data, and the test task corresponds to the table test task in federal range data.

The architecture of the federal range is shown in fig. 11. The federal range includes a plurality of sub-ranges and data entry levels. The sub-ranges are mutually independent and noninterfere, each sub-range comprises a plurality of subsystems, and the subsystems are mutually related and work cooperatively. A data center interacts with each sub-range to store data from multiple subsystems of each sub-range. The data center provides a storage environment for multiple types of data. The data type may be: file information data, data source information data, experimental activity information data, knowledge graph data and the like.

In this embodiment, the testing of the table in the binding shooting range data, as shown in fig. 12, acquires a testing task for a source database to be tested, including:

step 211, acquiring a test task of a table in the federal shooting range data, and determining a test task type of the test task of the table in the federal shooting range data;

step 212, generating a first test suite according to the test task type, and determining a first test case in the first test suite.

The task type of the platform test task in the federation range data is the application scene of the platform in the federation range data. The data center test is performed aiming at the application scene, so that the data center can efficiently and correctly execute the operation required in the application scene. The task types include: constructing a knowledge graph, scanning a file, verifying data authority and the like. For example, the federal shooting range data testing task is to perform data processing tests (such as increasing, decreasing, modifying and searching of data) aiming at building a knowledge graph, the task content of the testing task is the data processing tests, and the testing task type of the testing task is the building of the knowledge graph.

The first test suite is generated according to the test task type, and the first test case in the first test suite is used for testing the federal range data center test task corresponding to the test task type. For example, the task content of the task is a data processing test, the test task type is a building knowledge graph, and then the first test case in the first test suite is a test case for the data processing test related to the building knowledge graph.

Running a first test case using a test data table, comprising:

step 241, determining a test sequence of the first test case according to the test task type;

and step 242, running the first test case by using the test data table according to the test sequence.

According to the test task types, the first test cases in the first test suite can be ordered so that the first test cases which are more suitable for the test tasks are preferentially operated.

For example, the test task type is to construct a knowledge graph, and the data volume of each first test case test in the first test suite is different. In order to test the performance of building the knowledge graph, the first test cases can be ordered according to the data size, and the first test cases with large data size are operated preferentially. Because the requirement of constructing the knowledge graph on the capacity of the data center is higher, the priority test of the repeated test cases can be ensured by sequencing the first test cases according to the data volume, and the timeliness of the test is improved.

For another example, the test task type is a file query, and the first test suite is mainly used for testing the efficiency and accuracy of the query. Therefore, the first test cases can be ordered according to the length of the preset running time, and the first test cases with short preset running time are preferentially run. If the test process can be completed within the preset operation time and an accurate query result is obtained, the first test cases with the longer preset operation time do not need to be completely operated, and some extreme cases or special cases can be selected for operation. The test efficiency is improved.

In summary, the advantage of the application of the embodiment of the disclosure to the data center test of the federal target range is that the first test cases can be tested in a sequence according to the test task type, so that the important test cases are preferentially operated, the obtained test result is more suitable for the application scenario of the data center of the federal target range, the timeliness of the data center test is improved, and the stability and accuracy of the task execution of the data center of the federal target range are further improved.

It should be noted that any of the foregoing embodiments may be used to test the data center of the bang range.

FIG. 13 is an overall flowchart of performing database testing according to an embodiment of the present disclosure, including:

step 1310, constructing a test project, preparing test data, and obtaining configuration parameters required by a test environment. This process occurs at the beginning of the test, requiring preparation of test data for the test project, providing configuration parameters required for the current test environment, such as user name, password, and port information required for the database connection. When all the test tasks in the test environment are completed, the test engineering needs to be deleted.

Step 1320, for the test task, a test database is established, and a test data table is created in the test database.

Step 1330, setting parameters before the test case, and defining the test task for executing the test case.

Step 1340, executing the test cases in the test suite in the test database.

Step 1350, after the execution of one test case is completed, the test data table is emptied.

Step 1360, deleting the test database and the test data table when all the test cases in the test suite are executed.

Apparatus and device descriptions of embodiments of the present disclosure

It will be appreciated that, although the steps in the various flowcharts described above are shown in succession in the order indicated by the arrows, the steps are not necessarily executed in the order indicated by the arrows. The steps are not strictly limited in order unless explicitly stated in the present embodiment, and may be performed in other orders. Moreover, at least some of the steps in the flowcharts described above may include a plurality of steps or stages that are not necessarily performed at the same time but may be performed at different times, and the order of execution of the steps or stages is not necessarily sequential, but may be performed in turn or alternately with at least a portion of the steps or stages in other steps or other steps.

In the various embodiments of the present application, when related processing is performed according to data related to characteristics of a target object, such as attribute information or attribute information set of the target object, permission or consent of the target object is obtained first, and the collection, use, processing, and the like of the data comply with related laws and regulations and standards of related countries and regions. In addition, when the embodiment of the application needs to acquire the attribute information of the target object, the independent permission or independent consent of the target object is acquired through a popup window or a jump to a confirmation page or the like, and after the independent permission or independent consent of the target object is explicitly acquired, the necessary target object related data for enabling the embodiment of the application to normally operate is acquired.

Fig. 14 is a block diagram of a database test apparatus 1400 provided in an embodiment of the present disclosure. The database test apparatus 1400 includes:

a first obtaining unit 1410 that obtains a test task for a source database to be tested;

a first establishing unit 1420, which establishes a test database matched with the source database based on the test task, wherein the test database includes a test data table;

A second obtaining unit 1430 that obtains a first test case in a first test suite, the first test suite being a set of a plurality of first test cases corresponding to a test task;

the first operation unit 1440 is configured to operate the first test case by using the test data table, and return a test result after the operation is finished;

a first deleting unit 1450 configured to delete data generated by the first test case in the test data table, so as to use the test data table to run a next first test case in the first test suite;

the second deleting unit 1460 is configured to delete the test database after all the first test cases in the first test suite are run.

Further, the first establishing unit 1420 is specifically configured to:

generating a test database identifier for the test database;

acquiring a test database establishment file, wherein the test database establishment file comprises test database establishment sentences and test data table establishment sentences, and the test data table establishment sentences are generated based on a source database and test tasks;

running a test database creation file, creating sentences based on the test database, creating sentences based on the test data table, and creating the test data table in the test database;

And returning the running result of the test database identifier and the test database establishment file.

Further, the first establishing unit 1420 is specifically configured to:

acquiring a time stamp when a test database is generated;

acquiring a machine identifier of a server executing a database test method;

calling a random number generation method to obtain a method identifier of the random number generation method, wherein the random number generation method is stored in a server, and each random number generation method has a corresponding method identifier;

generating a random number by using a random number generation method;

a test database identification is generated based on the timestamp, the machine identification, the method identification, and the random number.

Further, the first test kit is constructed by:

acquiring first keywords of a plurality of test cases;

acquiring second keywords of a plurality of test tasks;

and classifying the test cases into a first test suite corresponding to the test task according to the matching condition of the first keyword and the second keyword.

Further, classifying the test case into a first test suite corresponding to the test task includes:

generating a task pointer according to the test task;

pointing the task pointer to the area where the test case is stored;

The task pointer is stored in the first test suite.

Further, the first test case is obtained by:

constructing a first test case by using the universal code and the test task;

further, the first operation unit 1440 is specifically configured to:

constructing a first test environment of a first test case, wherein the first test environment is constructed by using a preset case environment template;

in a first test environment, a first test case is run using a test data table.

Further, the database test apparatus 1400 further includes:

a second establishing unit (not shown) for constructing a second test environment for database testing;

the second test environment is constructed in the following manner;

acquiring a preset database test environment;

and adjusting a preset database test environment based on the test task to obtain a second test environment.

Further, the database testing device 1400 is applied to testing of the middle stage of the federal shooting range data, and the testing task corresponds to the middle stage testing task of the federal shooting range data;

in the federal range data, the first acquisition unit 1410 is specifically configured to:

Acquiring a test task of a middle stage of the federal shooting range data, and determining a test task type of the test task of the middle stage of the federal shooting range data, wherein the test task type comprises knowledge graph data construction, file scanning and data authority verification;

generating a first test suite according to the test task type, and determining a first test case in the first test suite;

the first operation unit 1440 is specifically configured to:

determining a test sequence of the first test case according to the test task type;

and according to the test sequence, using the test data table to run the first test case.

Referring to fig. 15, fig. 15 is a block diagram of a portion of a subject terminal implementing an embodiment of the present disclosure, the subject terminal including: radio Frequency (RF) circuitry 1510, memory 1515, input unit 1530, display unit 1540, sensor 1550, audio circuitry 1560, wireless fidelity (wireless fidelity, wiFi) module 1570, processor 1580, and power supply 1590. It will be appreciated by those skilled in the art that the subject terminal structure shown in fig. 15 is not limiting of a cell phone or computer, and may include more or fewer components than shown, or may combine certain components, or a different arrangement of components.

The RF circuit 1510 may be used for receiving and transmitting signals during a message or a call, and particularly, after receiving downlink information of a base station, the signal is processed by the processor 1580; in addition, the data of the design uplink is sent to the base station.

The memory 1515 may be used to store software programs and modules, and the processor 1580 executes the software programs and modules stored in the memory 1515 to thereby perform various functional applications and data processing of the object terminal.

The input unit 1530 may be used to receive input numerical or character information and generate key signal inputs related to the setting of the object terminal and the function control. In particular, the input unit 1530 may include a touch panel 1531 and other input devices 1532.

The display unit 1540 may be used to display input information or provided information and various menus of the object terminal. The display unit 1540 may include a display panel 1541.

Audio circuitry 1560, speakers 1561, and microphone 1562 may provide an audio interface.

In this embodiment, the processor 1580 included in the object terminal may perform the database test method of the previous embodiment.

The object terminal of the embodiment of the disclosure includes, but is not limited to, a mobile phone, a computer, an intelligent voice interaction device, an intelligent household appliance, a vehicle-mounted terminal, an aircraft and the like. Embodiments of the present invention may be applied to a variety of scenarios including, but not limited to, data security, blockchain, data storage, information technology, and the like.

Fig. 16 is a block diagram of a portion of a server embodying an embodiment of the present disclosure. The servers may vary widely by configuration or performance, and may include one or more central processing units (Central Processing Units, simply CPU) 1622 (e.g., one or more processors) and memory 1632, one or more storage media 1630 (e.g., one or more mass storage devices) that store applications 1642 or data 1644. Wherein memory 1632 and storage medium 1630 may be transitory or persistent. The program stored on the storage medium 1630 may include one or more modules (not shown), each of which may include a series of instruction operations on the server 1600. Further, the central processor 1622 may be configured to communicate with a storage medium 1630 to execute a series of instruction operations on the storage medium 1630 on the server 1600.

The server 1600 may also include one or more power supplies 1626, one or more wired or wireless network interfaces 1650, one or more input output interfaces 1658, and/or one or more operating systems 1641, such as Windows Server, mac OS XTM, unixTM, linuxTM, freeBSDTM, and the like.

The central processor 1622 in the server 1600 may be used to perform the database testing methods of embodiments of the present disclosure.

The disclosed embodiments also provide a computer readable storage medium storing program code for performing the database test method of the foregoing embodiments.

The disclosed embodiments also provide a computer program product comprising a computer program. The processor of the computer device reads the computer program and executes it, causing the computer device to execute the database test method described above.

The terms "first," "second," "third," "fourth," and the like in the description of the present disclosure and in the above-described figures, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the disclosure described herein may be capable of operation in sequences other than those illustrated or described herein, for example. Furthermore, the terms "comprises," "comprising," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed or inherent to such process, method, article, or apparatus.

It should be understood that in this disclosure, "at least one" means one or more, and "a plurality" means two or more. "and/or" for describing the association relationship of the association object, the representation may have three relationships, for example, "a and/or B" may represent: only a, only B and both a and B are present, wherein a, B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (one) of a, b or c may represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", wherein a, b, c may be single or plural.

It should be understood that in the description of the embodiments of the present disclosure, the meaning of a plurality (or multiple) is two or more, and that greater than, less than, exceeding, etc. is understood to not include the present number, and that greater than, less than, within, etc. is understood to include the present number.

In the several embodiments provided in the present disclosure, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of elements is merely a logical functional division, and there may be additional divisions of actual implementation, e.g., multiple elements or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present disclosure may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present disclosure may be embodied in essence or a part contributing to the prior art or all or part of the technical solution in the form of a software product stored in a storage medium, including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods of the various embodiments of the present disclosure. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

It should also be appreciated that the various implementations provided by the embodiments of the present disclosure may be arbitrarily combined to achieve different technical effects.

The above is a specific description of the embodiments of the present disclosure, but the present disclosure is not limited to the above embodiments, and various equivalent modifications and substitutions can be made by those skilled in the art without departing from the spirit of the present disclosure, and are included in the scope of the present disclosure as defined in the claims.

Claims

1. A database testing method, comprising:

acquiring a test task aiming at a source database to be tested;

2. The database testing method according to claim 1, wherein the creating a test database matching the source database based on the test task comprises:

generating a test database identifier for the test database;

3. The database testing method according to claim 2, wherein said generating a test database identification for the test database comprises:

acquiring a time stamp when the test database is generated;

Acquiring a machine identifier of a server executing the database test method;

generating a random number by using the random number generation method;

4. The database testing method of claim 1, wherein the first test suite is constructed by:

acquiring first keywords of a plurality of test cases;

acquiring second keywords of a plurality of test tasks;

5. The database testing method of claim 4, wherein classifying the test case into the first test suite corresponding to the test task comprises:

generating a task pointer according to the test task;

Directing the task pointer to the area where the test case is stored;

the task pointer is stored in the first test suite.

6. The database testing method of claim 1, wherein the first test case is obtained by:

and constructing the first test case by utilizing the universal code and the test task.

7. The database testing method of claim 1, wherein the running the first test case using the test data table comprises:

8. The database testing method according to claim 1, wherein prior to the acquiring the test task for the source database to be tested, the database testing method further comprises: constructing a second test environment for database testing;

The second test environment is constructed in the following manner;

acquiring a preset database test environment;

9. The database test method according to claim 1, wherein the database test method is applied to the test of the middle stage of the federal range data, and the test task corresponds to the middle stage test task of the federal range data;

the running the first test case by using the test data table includes:

10. A database testing apparatus, comprising:

11. An electronic device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the database testing method according to any of claims 1 to 9 when executing the computer program.

12. A computer readable storage medium storing a computer program, characterized in that the computer program, when executed by a processor, implements the database testing method according to any one of claims 1 to 9.

13. A computer program product comprising a computer program which is read and executed by a processor of a computer device, causing the computer device to perform the database test method according to any one of claims 1 to 9.