Test data management method and device, equipment and storage medium

Abstract

The embodiment of the invention provides a test data management method, device and equipment and a computer readable storage medium, relates to the technical field of software testing, and can be applied to the field of financial science and technology. The method comprises the steps of obtaining various test requirements in a preset time period, generating corresponding test data based on the various test requirements, performing function classification on the test data, and storing the test data in a data pool; receiving a test data application request sent by a tester; determining test data demand information based on the test data application request; obtaining target test data from a data pool based on the test data demand information; and distributing the target test data to testers. According to the method, automatic generation and management of the test data are realized; according to the technical scheme, for testers, the test data does not need to be prepared manually, the related test data can be obtained only by submitting the test data application request to the system, the preparation efficiency of the test data is improved, and the purpose of obtaining the high-quality test data is achieved.

Description

Technical Field

[0001] The present application relates to the field of big data technology, and in particular to a test data management method, apparatus, device and computer-readable storage medium. Background Art

[0002] In order to ensure the stability, security and reliability of the banking system, it is necessary to conduct a comprehensive test on the banking system. During the testing process, test data preparation is crucial, which is directly related to the credibility of the test results and the operational stability of the system.

[0003] In traditional technologies, in order to ensure that test data meets the requirements of high quality and can cover test scenarios, R&D personnel or testers manually prepare test data. However, when more projects need to be tested, manually preparing test data requires a lot of manpower and material resources, is inefficient and prone to errors. Summary of the invention

[0004] Embodiments of the present application provide a test data management method, apparatus, device, and computer-readable storage medium, which can improve the efficiency of test data preparation.

[0005] In a first aspect, an embodiment of the present application provides a test data management method, including:

[0006] Acquire various test requirements within a preset time period, generate corresponding test data based on the various test requirements, and store the test data in a data pool after functional classification;

[0007] Receive test data application requests sent by testers;

[0008] Determining test data requirement information based on the test data application request;

[0009] Acquiring target test data from the data pool based on the test data requirement information;

[0010] The target test data is distributed to the tester.

[0011] In a second aspect, an embodiment of the present application provides a test data management device, including:

[0012] A test data generation module is used to obtain various test requirements within a preset time period, generate corresponding test data based on the various test requirements, and store the test data in a data pool after functional classification;

[0013] The test data allocation module is used to receive a test data application request sent by a tester; determine test data requirement information based on the test data application request; obtain target test data from the data pool based on the test data requirement information; and allocate the target test data to the tester.

[0014] In a third aspect, an embodiment of the present application provides an electronic device, comprising a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the steps of the test data management method provided in the first aspect of the embodiment of the present application are implemented.

[0015] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the steps of the test data management method provided in the first aspect of the embodiment of the present application are implemented.

[0016] In a fifth aspect, an embodiment of the present application provides a computer program product having a computer program stored thereon, and when the computer program is executed by a processor, the steps of the test data management method provided in the first aspect of the embodiment of the present application are implemented.

[0017] The technical solution provided in the embodiment of the present application generates corresponding test data based on various test requirements in a preset time period, and stores the test data in a data pool after functional classification. Subsequently, according to the test data application request of the tester, the test data requirement information is determined, and the target test data is obtained from the data pool based on the test data requirement information, and the target test data is allocated to the tester, thereby realizing the automatic generation and management of test data. For the tester, there is no need to prepare test data manually, and the relevant test data can be obtained by submitting a test data application request to the system, thereby improving the efficiency of test data preparation and achieving the purpose of obtaining high-quality test data. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 A schematic diagram of an application environment of the test data management method provided in an embodiment of the present application;

[0019] Figure 2 A flow chart of a test data management method provided in an embodiment of the present application;

[0020] Figure 3 Another flowchart of the test data management method provided in the embodiment of the present application;

[0021] Figure 4 A schematic diagram of the structure of a test data management device provided in an embodiment of the present application;

[0022] Figure 5A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0023] In order to make the purpose, technical solutions and advantages of the present application clearer, the technical solutions in the embodiments of the present application are further described in detail through the following embodiments and in combination with the accompanying drawings. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application. Those skilled in the art can make adjustments to them as needed to suit specific application scenarios. It should also be noted that, for ease of description, only the parts related to the present application are shown in the accompanying drawings, rather than all structures.

[0024] Figure 1 A schematic diagram of the application environment of the test data management method provided in the embodiment of the present application. Figure 1 , the test data management method is applied to a test data management system. The test data management system may include a terminal 101 and a server 102. The terminal 101 and the server 102 are connected via a wireless network or a wired network. The terminal 101 may be a desktop terminal or a mobile terminal. Optionally, the mobile terminal may be at least one of a PDA (personal digital assistant), a PAD (tablet computer), a PMP (portable multimedia player), a vehicle terminal (such as a vehicle navigation terminal), and a mobile phone. The server 102 may be an independent server or a server cluster consisting of multiple servers.

[0025] It should be noted that the test data management method in the embodiment of the present application can be executed separately by the terminal 101 or the server 102, or can be jointly executed by the terminal 101 and the server 102. The following method embodiment is described by taking the execution subject as an electronic device (the electronic device is the terminal 101 and / or the server 102) as an example.

[0026] Figure 2 A flow chart of a test data management method provided in an embodiment of the present application. Figure 2 As shown, the method may include:

[0027] S201, obtaining various test requirements within a preset time period, generating corresponding test data based on the various test requirements, and storing the test data in a data pool after functional classification.

[0028] In this embodiment, various test requirements for the banking system within a preset time period can be collected, including functional test requirements, performance test requirements, passability test requirements, and security test requirements, for example, various test requirements within the next week or month can be collected. Based on these test requirements, test data that meets various test requirements is generated in various ways. After obtaining the test data, the test data is cleaned, sorted, and normalized. For example, regular expressions are used to remove illegal characters, SQL statements are used to convert data, data that does not meet consistency requirements is eliminated, and for some sensitive fields, specific keys are used to deform data for sensitive fields. After preprocessing the test data, the test data is continued to be verified for passability transactions, and transactions recorded from production are played back in the test environment to check the integrity and validity of the test data. The cause analysis is performed for data that is inconsistent with the playback results and production, and the abnormal data is repaired based on the analysis results. If it cannot be repaired, the abnormal data is cleaned up. In addition, the data extraction rules can also be reversed based on the cause analysis results to ensure the accuracy of subsequent extracted data.

[0029] Furthermore, for the test data that have passed the verification, these test data can also be functionally classified, including classification by business scenario: such as debit card, credit card, counter business data, online banking business data, etc.; classification by usage scenario: such as functional testing, performance testing, passability testing, security testing, etc. That is, the test data is marked with functional labels, and the test data marked with functional labels is stored in the data pool as the basis for subsequent distribution of test data.

[0030] In some embodiments, based on various test requirements, corresponding test data can be extracted from the backup file of production data according to the data extraction rules of each data table. The data extraction rules may include full extraction rules, empty table extraction rules, associated extraction rules and / or direct extraction rules.

[0031] For data tables storing real-time information, the empty table extraction rule can be used, that is, the non-extraction strategy is adopted and only the table structure is established. For example, the log table can be processed using the empty table extraction rule.

[0032] For the parameter table, since its data volume is small and affects all range transactions, the full volume extraction rule is adopted for data extraction.

[0033] For core data tables (such as current account tables), direct extraction rules are used to extract data, and the extracted fields should take into account the data capacity and test coverage.

[0034] For non-core data tables, you can use associated extraction rules to extract data, which requires associating the core fields or non-core fields of the core data table.

[0035] For the specific extraction rules of non-core data tables, we can first build the association relationship between the core data tables and the non-core data tables. Specifically, we detect the fields with the same field name and field type in the core data tables and the non-core data tables. If there are fields with the same field name and field type in the two types of data tables, and the overlap rate of the field data values ​​of the fields in the two types of data tables exceeds the preset threshold, it is considered that the two fields record the same information, that is, the field is the association field between the core data table and the non-core data table.

[0036] Starting from the core data table, first check the associated fields of the core fields in the core data table in the non-core data table according to the above-mentioned determination rules of the associated fields. If the associated field is the unique index field of the non-core data table, the data extraction condition of the core field in the core data table is used as the data extraction condition of the non-core data table; if the associated field is not the unique index field of the non-core data table, the data extraction condition of the core field in the core data table is used as the alternative condition of the non-core data table, and continue to determine the associated fields of the non-core fields in the core data table in the non-core data table. If the non-core fields in the core data table also have associated fields in the non-core data table, the data extraction condition of the non-core fields in the core data table is also used as the alternative condition of the non-core data table, and the alternative conditions of all non-core data tables are summarized as the data extraction condition of the non-core data table. For example, the union of these alternative conditions is used as the data extraction condition of the non-core data table. In this way, the consistency of the extracted data is ensured.

[0037] In some embodiments, corresponding test data can also be generated by calling a generated transaction interface. Among them, generated transaction processes such as card opening, account opening, online banking opening, card replacement and other data preparation transactions can generate these transaction test data by calling a generated transaction interface.

[0038] In one embodiment, corresponding test data may also be generated by duplicating historical test data.

[0039] Among them, by searching the relevant tables of historical test data, and then generating corresponding test data according to the data category required for the test, it can include random number generation, regular number generation, etc.

[0040] S202: Receive a test data application request sent by a tester.

[0041] When a tester needs to conduct a test, he or she can directly initiate a test data application request in the test data management system. The system receives the test data application request submitted by the tester and parses the test data application request to obtain the test data requirement information carried in the test data application request.

[0042] S203: Determine test data requirement information based on the test data application request.

[0043] Test data requirement information may include information such as the type of data required for testing (such as different types of test data divided according to business scenarios, or test data for functional testing, test data for performance testing, or test data for pass testing divided according to usage scenarios, etc.), data structure (such as data fields, data formats, data lengths, etc.) and data volume.

[0044] S204: Obtain target test data from the data pool based on the test data requirement information.

[0045] After obtaining the test data requirement information, based on the required test data type, data structure, data volume and other information, the matching target test data is obtained from the data pool, and the target test data is assigned to the tester for testing. The tester to whom the target test data is assigned indicates that a subordinate relationship is established between the target test data and the tester, that is, the tester has the operation authority for the target test data, and other testers do not have the operation authority for the target test data.

[0046] S205: Allocate target test data to testers.

[0047] After the target test data is assigned to the tester, the status of the target test data can be modified, for example, the status of the target test data can be changed from "unused" to "in use", and the test data in use is invisible to other testers. In this way, it can be avoided that multiple testers access or modify the same test data at the same time, resulting in data inconsistency or error accumulation, or conflicts. Invisibility can reduce such data inconsistency and conflicts, and ensure the accuracy of test results.

[0048] The test data management method provided in the embodiment of the present application generates corresponding test data based on various test requirements in a preset time period, and stores the test data in a data pool after functional classification. Subsequently, according to the test data application request of the tester, the test data requirement information is determined, and the target test data is obtained from the data pool based on the test data requirement information, and the target test data is allocated to the tester, thereby realizing the automatic generation and management of the test data. For the tester, there is no need to prepare the test data manually, and the relevant test data can be obtained by submitting a test data application request to the system, thereby improving the efficiency of test data preparation and achieving the purpose of obtaining high-quality test data.

[0049] In some embodiments, optionally, Figure 3 As shown, the method may also include:

[0050] S301. Periodically perform health checks on each test data in the data pool.

[0051] S302. For the allocated test data whose health check result is unqualified, determine the target tester to whom the allocated test data is currently allocated.

[0052] S303: Send a prompt message of data anomaly to the target tester.

[0053] Specifically, the test data management system can also periodically perform health checks on various types of test data stored in the data pool, for example, using service scripts to simulate transactions on the test data to determine whether the test data is healthy. For the allocated test data with unqualified health check results, the target tester to whom the allocated test data is currently allocated is determined based on the subordinate relationship between the test data and the tester, and a prompt message of data abnormality is sent to the target tester so that the target tester can take corresponding processing measures in time. Here, the sending method of the prompt message includes but is not limited to SMS, email, and telephone. In addition, the allocated test data can also be repaired, and the repaired test data can be health checked again. After the health check result passes, the target tester is reminded in time so that the target tester can know the health status of the allocated test data in time. If the allocated test data cannot be repaired, the data status of the allocated test data is modified to "invalidated". The test data management system can regularly delete the marked "invalidated" test data to ensure that the test data in the data pool is always healthy and accurate. At the same time, deleting the invalidated test data can also release storage space, reduce the load of the data pool, and ensure that the system is in a stable operating state. In addition, when the allocated test data cannot be repaired, the test data required for the test can be automatically generated in combination with the test requirements of the target testers, including extracting test data that meets the test requirements from the production environment, or calling the generation transaction interface to generate the corresponding test data, or generating the corresponding test data by copying historical test data.

[0054] When the health check results of the assigned test data are unqualified, by sending a prompt message of data abnormality to the target tester, it can prevent the target tester from using abnormal test data without knowing it and causing erroneous test results. Timely prompts can avoid the occurrence of such problems and the need for rework and retesting, thereby improving the test efficiency of the tester and the accuracy of the test results.

[0055] In one embodiment, optionally, the method may further include: receiving a test data release request sent by a tester, and releasing the subordinate relationship between the target test data and the tester based on the test data release request.

[0056] After the tester has finished the test, the tester can also initiate a test data release request in the system to request the release of the allocated target test data. The system receives the test data release request submitted by the tester, and releases the subordinate relationship between the allocated target test data and the tester according to the test data release request. Furthermore, a health check can be performed on the released target test data to determine whether the target test data is damaged. If the health check result of the target test data passes, the data status of the target test data is changed from "in use" to "unused" and is visible to all testers as a basis for the subsequent allocation of test data. If the inspection result of the target test data fails, the target test data can be repaired. If it cannot be repaired, the data status of the target test data is changed to "obsolete" so that the obsolete test data can be cleaned up later.

[0057] By releasing the occupied test data in time, the released test data can be reallocated to other testers or projects, thus improving the reuse rate of test data.

[0058] In some embodiments, optionally, the above S205 may include: if the target test data is currently occupied, sending a prompt message indicating that the data is occupied to the tester, and after the target test data is released, allocating the target test data to the tester.

[0059] Specifically, when allocating target test data to the tester, it can also be determined whether the target test data is currently occupied. If the target test data is not currently occupied, the target test data can be allocated to the tester to form a subordinate relationship between the target test data and the tester; if the target test data is currently occupied, a prompt message indicating that the data is occupied can be sent to the tester, and the prompt message can be sent in a manner including but not limited to SMS, email, and telephone. In addition, after the target test data is released, the target test data is allocated to the tester so that the target test data belongs to only one tester at the same time, avoiding test conflicts caused by multiple testers operating the same test data at the same time. Of course, the re-allocation of the target test data here still needs to ensure that the health check result of the target test data is qualified, that is, the target test data meets the test requirements of the tester.

[0060] Furthermore, for the allocated target test data, a correspondence between the target test data and the binary log (binlog) file can be established, and the binlog file can be scanned and parsed periodically. When it is determined based on the parsing result that there is an abnormal change in the target test data, a prompt message is sent to the tester, and the tester's data recovery instruction is received to restore the target test data based on the binlog file.

[0061] Specifically, for the allocated target test data, the binary log function is turned on, and the corresponding relationship between the target test data and the binlog file is established. The binlog file records all data manipulation language (DataManipulation Language, DML) operations in the form of events, that is, the binlog file is a binary log that records all database table structure changes and table data modifications. At the same time, for the allocated target test data, the subordinate tester can also set rules for the target test data. The test data management system periodically scans and parses the binlog file. When it is determined based on the parsing result that the target test data has an abnormal change, that is, when the target test data changes that do not conform to the above-set rules, prompt information is sent to the tester in time to prompt the tester to confirm whether the change of the target test data is reasonable. If the tester confirms that the change of the target test data is unreasonable, a data recovery instruction can be triggered, and the test data management system receives the data recovery instruction triggered by the tester and restores the target test data based on the binlog file. Optionally, using the binlog file to restore the target test data can include restoring the target test data by time and / or restoring the target test data by pos position.

[0062] In this embodiment, the allocated target test data can also be monitored to promptly detect abnormal test data, and in combination with the tester's data recovery instructions, the target test data can be restored using the binlog file to ensure the accuracy and completeness of the target test data allocated to the tester, and to automatically process abnormal test data, thereby reducing manual maintenance costs and human resource consumption, thereby improving the management efficiency of test data.

[0063] Figure 4 A schematic diagram of the structure of the test data management device provided in the embodiment of the present application. Figure 4 As shown, the apparatus may include: a test data generating module 401 and a test data allocating module 402 .

[0064] Specifically, the test data generation module 401 is used to obtain various test requirements within a preset time period, generate corresponding test data based on the various test requirements, and store the test data in a data pool after functional classification;

[0065] The test data allocation module 402 is used to receive a test data application request sent by a tester; determine test data requirement information based on the test data application request; obtain target test data from the data pool based on the test data requirement information; and allocate the target test data to the tester.

[0066] Based on the above embodiment, optionally, the device further includes: a test data monitoring module.

[0067] Specifically, the test data monitoring module is used to periodically perform health checks on each test data in the data pool; for the allocated test data with unqualified health check results, determine the target tester to whom the allocated test data is currently assigned; and send a prompt message of data abnormality to the target tester.

[0068] Based on the above embodiment, optionally, the device further includes: a test data release module.

[0069] Specifically, the test data release module is used to receive a test data release request sent by the tester; based on the test data release request, release the subordinate relationship between the target data test and the tester.

[0070] Based on the above embodiment, optionally, the test data allocation module is also used to send a prompt message that the data is occupied to the tester if the target test data is currently occupied, and allocate the target test data to the tester after the target test data is released.

[0071] Based on the above embodiment, optionally, it also includes: the test data monitoring module is also used to establish a corresponding relationship between the target test data and the binlog file; the binlog file is periodically scanned and parsed, and when it is determined based on the analysis result that there is an abnormal change in the target test data, a prompt message is sent to the tester; the data recovery instruction of the tester is received, and the target test data is restored based on the binlog file.

[0072] On the basis of the above-mentioned embodiment, optionally, the test data generation module 401 is also used to extract corresponding test data from the backup file of the production data according to the data extraction rules of each data table based on the various test requirements, generate corresponding test data by calling the generation class transaction interface, and generate corresponding test data by copying historical test data.

[0073] Optionally, the data extraction rules include full extraction rules, empty table extraction rules, associated extraction rules and / or direct extraction rules.

[0074] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application, such as Figure 5 As shown, the device includes a processor 50, a memory 51, an input device 52 and an output device 53; the number of the processor 50 in the device can be one or more. Figure 5A processor 50 is taken as an example; the processor 50, memory 51, input device 52 and output device 53 in the device can be connected by a bus or other means. Figure 5 The example of connecting through bus is taken in the following.

[0075] The memory 51, as a computer-readable storage medium, can be used to store software programs, computer executable programs and modules, such as program instructions / modules corresponding to the test data management method in the embodiments of the present application (for example, the test data generation module 401 and the test data allocation module 402 in the test data management device). The processor 50 executes various functional applications and data processing of the device by running the software programs, instructions and modules stored in the memory 51, that is, implements the test data management method provided in any of the above embodiments.

[0076] The memory 51 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system and at least one application required for a function; the data storage area may store data created during the test data management process, etc. In addition, the memory 51 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 51 may further include a memory remotely arranged relative to the processor 50, and these remote memories may be connected to the device / terminal / server via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0077] The input device 52 may be used to receive input digital or character information and generate key signal input related to user settings and function control of the electronic device. The output device 53 may include a display device such as a display screen.

[0078] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented:

[0079] Acquire various test requirements within a preset time period, generate corresponding test data based on the various test requirements, and store the test data in a data pool after functional classification;

[0080] Receive test data application requests sent by testers;

[0081] Determining test data requirement information based on the test data application request;

[0082] Acquiring target test data from the data pool based on the test data requirement information;

[0083] The target test data is distributed to the tester.

[0084] In one embodiment, a computer program product is further provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0085] Acquire various test requirements within a preset time period, generate corresponding test data based on the various test requirements, and store the test data in a data pool after functional classification;

[0086] Receive test data application requests sent by testers;

[0087] Determining test data requirement information based on the test data application request;

[0088] Acquiring target test data from the data pool based on the test data requirement information;

[0089] The target test data is distributed to the tester.

[0090] The test data management device, electronic device, computer-readable storage medium, and computer program product provided in the above embodiments can execute the test data management method provided in any embodiment of the present application, and have the corresponding functional modules and beneficial effects of executing the method. For technical details not described in detail in the above embodiments, please refer to the test data management method provided in any embodiment of the present application.

[0091] Through the above description of the implementation method, the technicians in the relevant field can clearly understand that the present application can be implemented with the help of software and necessary general hardware, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), random access memory (RAM), flash memory (FLASH), hard disk or optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, server, or network device, etc.) to execute the methods of each embodiment of the present application.

[0092] It is worth noting that the various units and modules included in the above embodiments are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application.

[0093] Note that the above are only preferred embodiments of the present application and the technical principles used. Those skilled in the art will understand that the present application is not limited to the specific embodiments herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present application. Therefore, although the present application is described in more detail through the above embodiments, the present application is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present application, and the scope of the present application is determined by the scope of the appended claims.

Claims

1. A test data management method, characterized in that: include: Acquire various test requirements within a preset time period, generate corresponding test data based on the various test requirements, and store the test data in a data pool after functional classification; Receive test data application requests sent by testers; Determining test data requirement information based on the test data application request; Acquiring target test data from the data pool based on the test data requirement information; The target test data is distributed to the tester.

2. The method according to claim 1, characterized in that Also includes: Periodically performing health checks on each test data in the data pool; For the allocated test data with unqualified health check results, determine the target tester to whom the allocated test data is currently allocated; Send a prompt message of data anomaly to the target tester.

3. The method according to claim 1, characterized in that Also includes: Receiving a test data release request sent by the tester; Based on the test data release request, the subordinate relationship between the target data test and the tester is released.

4. The method according to claim 1, characterized in that: The allocating the target test data to the tester comprises: If the target test data is currently occupied, a prompt message indicating that the data is occupied is sent to the tester, and after the target test data is released, the target test data is allocated to the tester.

5. The method according to claim 1, characterized in that Also includes: Establishing a correspondence between the target test data and the binary log file; Periodically scanning and parsing the binary log file, and when determining based on the parsing result that the target test data has abnormal changes, sending a prompt message to the tester; Receive a data recovery instruction from the tester, and recover the target test data based on the binary log file.

6. The method according to claim 1, characterized in that The generating corresponding test data based on the various test requirements includes: Based on the various test requirements, corresponding test data is extracted from the backup file of production data according to the data extraction rules of each data table, corresponding test data is generated by calling the generation class transaction interface, and corresponding test data is generated by copying historical test data.

7. The method according to claim 6, characterized in that The data extraction rules include full extraction rules, empty table extraction rules, associated extraction rules and / or direct extraction rules.

8. A test data management device, characterized in that: include: A test data generation module is used to obtain various test requirements within a preset time period, generate corresponding test data based on the various test requirements, and store the test data in a data pool after functional classification; The test data allocation module is used to receive a test data application request sent by a tester; determine test data requirement information based on the test data application request; obtain target test data from the data pool based on the test data requirement information; and allocate the target test data to the tester.

9. An electronic device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images