Method and apparatus for making test data usable across multiple systems based on data cleaning

Abstract

This invention provides a method and apparatus for enabling the usability of test data across multiple systems based on data cleaning. The method involves: determining whether business data of a specified type in each benchmark system conforms to a preset verification rule corresponding to that type; for each benchmark system, if the business data of the specified type in the benchmark system does not conform to the corresponding preset verification rule, modifying the business data of the specified type in the benchmark system according to the preset verification rule; determining whether the first business data of the specified type in the target benchmark system is the same as the second business data in other downstream systems; if the first business data and the second business data are different, modifying the second business data in other downstream systems that is different from the first business data. By modifying erroneous or inconsistent business data, business data is synchronized to multiple downstream systems, making the business data of multiple systems consistent and reusable, improving the utilization rate of business data, and reducing resource waste.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a method and apparatus for making test data available across multiple systems based on data cleaning. Background Technology

[0002] With the advancement of computer technology, digital transformation in the financial industry is imperative. In this process, to meet the testing needs of newly developed software business functions, which may be added or changed, extensive business data is often used to test the software.

[0003] However, due to different sources of business data or different times when business data is captured, a large amount of inconsistent or erroneous existing business data is stored in the test environment. This existing business data cannot be reused, resulting in a waste of resources. Summary of the Invention

[0004] In view of this, embodiments of the present invention provide a method and apparatus for making test data available across multiple systems based on data cleaning, in order to solve the problem that existing test data cannot be reused due to inconsistency or errors.

[0005] To achieve the above objectives, the embodiments of the present invention provide the following technical solutions:

[0006] The first aspect of this invention discloses a method for making test data available across multiple systems based on data cleaning, the method comprising:

[0007] Determine whether the specified type of business data in each benchmark system conforms to the preset verification rules corresponding to the specified type, wherein different benchmark systems correspond to different specified types of business data;

[0008] For each benchmark system, if the business data of a specified type in the benchmark system does not conform to the corresponding preset verification rule, the business data of the specified type in the benchmark system shall be modified according to the preset verification rule.

[0009] Determine whether first business data of a specified type in the target benchmark system is the same as second business data in other downstream systems, wherein the first business data and the second business data are business data of the same specified type, the target benchmark system is any of the benchmark systems, and the downstream systems are determined according to the flow direction of the specified type of business data in the benchmark system;

[0010] If the first service data of a specified type in the target benchmark system is different from the second service data in other downstream systems, the second service data in the other downstream systems shall be modified based on the first service data.

[0011] Preferably, the method further includes:

[0012] Obtain the third service data carried in the supplementary instruction, wherein the third service data is service data of the same type as the first service data in the downstream system;

[0013] According to the preset verification rules corresponding to the specified type of the third business data, the correctness of the third business data is verified to obtain incremental business data.

[0014] The incremental service data is stored in the target baseline system, and the incremental service data is synchronized to other downstream systems.

[0015] Preferably, storing the incremental service data in the target baseline system includes:

[0016] The data of each field in the incremental business data is stored in the corresponding field of the target benchmark system.

[0017] Preferably, the method further includes:

[0018] Delete special characters stored in the specified type of business data in the benchmark system.

[0019] Preferably, the method further includes:

[0020] When a query command is received, the business data that meets the query requirements carried in the query command is obtained from the benchmark system.

[0021] A second aspect of this invention discloses an apparatus for enabling the use of test data across multiple systems based on data cleaning, the apparatus comprising:

[0022] The first judgment unit is used to judge whether the business data of a specified type in each benchmark system conforms to the preset verification rules corresponding to the specified type, wherein different benchmark systems correspond to different specified types of business data;

[0023] The first modification unit is used to modify the specified type of business data in the benchmark system according to the preset verification rule if the specified type of business data in the benchmark system does not conform to the corresponding preset verification rule for each benchmark system.

[0024] The second judgment unit is used to determine whether the first business data of a specified type in the target benchmark system is the same as the second business data of other downstream systems, wherein the first business data and the second business data are business data of the same specified type, the target benchmark system is any of the benchmark systems, and the downstream system is determined according to the flow direction of the specified type of business data in the benchmark system.

[0025] The second modification unit is used to modify the second service data of the other downstream systems based on the first service data if the first service data of a specified type in the target benchmark system is different from the second service data of the other downstream systems.

[0026] Preferably, the device further includes:

[0027] The acquisition unit is used to acquire the third service data carried in the supplementary instruction, wherein the third service data is service data of the same type as the first service data in the downstream system;

[0028] The verification unit is used to verify the correctness of the third business data according to the preset verification rules corresponding to the specified type of the third business data, so as to obtain incremental business data.

[0029] The synchronization unit is used to store the incremental service data in the target baseline system and synchronize the incremental service data to other downstream systems.

[0030] Preferably, the synchronization unit is specifically used for:

[0031] The data of each field in the incremental business data is stored in the corresponding field of the target benchmark system.

[0032] Preferably, the device further includes:

[0033] The deletion unit is used to delete special characters stored in the specified type of business data in the benchmark system.

[0034] Preferably, the device further includes:

[0035] The query unit is used to, when a query command is received, retrieve the business data that meets the query requirements carried in the query command from the benchmark system.

[0036] Based on the above embodiments of the present invention, a method and apparatus for enabling the usability of test data across multiple systems based on data cleaning are provided. The method comprises: determining whether business data of a specified type in each benchmark system conforms to a preset verification rule corresponding to the specified type; for each benchmark system, if the business data of a specified type in the benchmark system does not conform to the corresponding preset verification rule, modifying the business data of the specified type in the benchmark system according to the preset verification rule; determining whether the first business data of a specified type in the target benchmark system is the same as the second business data in other downstream systems; if the first business data of a specified type in the target benchmark system is different from the second business data in other downstream systems, modifying the second business data in other downstream systems that is different from the first business data. By modifying erroneous or inconsistent business data, business data is synchronized to multiple downstream systems, making the business data of multiple systems consistent and reusable, improving the utilization rate of business data, and reducing resource waste. Attached Figure Description

[0037] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0038] Figure 1 A flowchart illustrating a method for enabling the availability of test data across multiple systems based on data cleaning, as provided in this embodiment of the invention;

[0039] Figure 2 Another flowchart of a method for making test data available across multiple systems based on data cleaning, provided by an embodiment of the present invention;

[0040] Figure 3 This is a structural block diagram of an apparatus for enabling the use of test data between multiple systems based on data cleaning, provided as an embodiment of the present invention. Detailed Implementation

[0041] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0042] In this application, the terms "comprising," "including," or any other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0043] As can be seen from the background technology, due to different sources of business data or different times when business data is captured, a large amount of inconsistent or erroneous existing business data is stored in the test environment. This existing business data cannot be reused, resulting in a waste of resources.

[0044] Therefore, embodiments of the present invention provide a method and apparatus for achieving the usability of test data across multiple systems based on data cleaning. The method determines whether business data of a specified type in each benchmark system conforms to a preset verification rule corresponding to that type. For each benchmark system, if the business data of a specified type in the benchmark system does not conform to the corresponding preset verification rule, the business data is modified according to the preset verification rule. The method also determines whether the first business data of a specified type in the target benchmark system is the same as the second business data in other downstream systems. If they are different, based on the first business data, the second business data in other downstream systems that are different from the first business data are modified to make the first business data and the second business data the same. By processing existing business data, the consistency of existing business data is achieved, solving the problems of inconsistency and unavailability of problematic data between systems, and improving the usability of existing business data.

[0045] join Figure 1 The diagram illustrates a flowchart of a method for making test data available across multiple systems based on data cleaning, according to an embodiment of the present invention. The data cleaning method includes:

[0046] Step S101: Determine whether the specified type of business data in each benchmark system conforms to the preset verification rules corresponding to the specified type. If the specified type of business data in the benchmark system does not conform to the preset verification rules corresponding to the specified type, proceed to step S102; if the specified type of business data in the benchmark system conforms to the preset verification rules corresponding to the specified type, proceed to step S103.

[0047] It should be noted that the system contains multiple types of business data. Each specified type of business data corresponds to a baseline system. Different baseline systems correspond to different specified types of business data, and different specified types correspond to different preset verification rules.

[0048] For example: System A contains business data of types a, b, and c, and System A is the base system for business data of type a; System B contains business data of types a, b, and c, and System B is the base system for business data of type b; System C contains business data of types a, b, and c, and System C is the base system for business data of type c.

[0049] Understandably, based on the source and flow of business data, the baseline system and downstream system corresponding to a specified type of business data are identified.

[0050] For example: For business data related to individual customers, the enterprise-level individual customer information management system is identified as the baseline system. For business data of the "debit card" type, the core business system is identified as the baseline system.

[0051] In the specific implementation of step S101, it is determined whether the business data of a specified type in each benchmark system conforms to the preset verification rules corresponding to the specified type. If the business data of a specified type in the benchmark system does not conform to the preset verification rules corresponding to the specified type, it is indicated that the business data that does not conform to the corresponding preset verification rules needs to be modified, and step S102 is executed; if the business data of a specified type in the benchmark system conforms to the preset verification rules corresponding to the specified type, step S103 is executed.

[0052] Understandably, determining whether business data of a specified type in each benchmark system conforms to the preset verification rules corresponding to that type mainly involves verifying the key fields in the business data. For example, when the specified type is "private customer," the verification fields are: ID number, ID type, customer name, and mobile phone number. That is, it checks whether the ID number of the private customer is compliant and correct, and whether the ID number matches the ID type; it also checks whether the name and mobile phone number of the private customer are compliant and correct.

[0053] For example, when the specified type is "corporate customer", the validation fields are: organization number, business license number and customer name, that is, to determine whether the organization number, business license number and customer name are compliant and correct.

[0054] In some embodiments, it is necessary to handle abnormal situations. For example, some systems may store business data packets containing special characters (such as quotation marks) in their databases, which may cause program crashes. Therefore, it is necessary to read and filter the special characters contained in the business data to delete the special characters stored in the specified type of business data in the baseline system.

[0055] Step S102: Modify the specified type of business data in the baseline system according to the preset verification rules.

[0056] It should be noted that business data of a specified type in the baseline system that does not conform to the corresponding preset verification rules will be modified to conform to the corresponding preset verification rules.

[0057] For example: In the benchmark system, Class A business data corresponds to Class A preset verification rules. If some existing Class A business data A1 does not conform to the Class A preset verification rules, then A1 will be modified according to the Class A preset verification rules to make A1 conform to the Class A preset verification rules.

[0058] In the specific implementation step S102, when the business data of a specified type in the benchmark system does not conform to the preset verification rules corresponding to the specified type, the business data of the specified type in the benchmark system is modified according to the preset verification rules.

[0059] Understandably, after verifying the correctness of the specified type of business data in the benchmark system using the above methods, it is necessary to compare and filter out problematic data of the specified type of business data in other systems. For specific implementation, please refer to the following steps.

[0060] Step S103: Determine whether the first service data of a specified type in the target benchmark system is the same as the second service data in other downstream systems. If the first service data of a specified type in the target benchmark system is different from the second service data in other downstream systems, proceed to step S104. If the first service data of a specified type in the target benchmark system is the same as the second service data in other downstream systems, then end the data cleaning process.

[0061] It should be noted that the target benchmark system can be any benchmark system, and the first business data and the second business data are business data of the same specified type.

[0062] It is understandable that the target benchmark system can be the benchmark system corresponding to a certain type of business data. Based on the flow of the specified type of business data, other systems that contain the same specified type of business data are the downstream systems of the target benchmark system.

[0063] It should be noted that each type of business data corresponds to multiple downstream systems. Therefore, each business system may be the baseline system for a specific type of business data, or it may be a downstream system for other specific types of business data.

[0064] For example: System A contains business data of types a, b, and c, and System A is the base system for business data of type a; System B contains business data of types a, b, and c, and System B is the base system for business data of type b; System C contains business data of types a, b, and c, and System C is the base system for business data of type c.

[0065] At this point, for business data of type a, system A is the baseline system, and systems B and C are downstream systems of system A; for business data of type b, system B is the baseline system, and systems A and C are downstream systems of system B; for business data of type c, system C is the baseline system, and systems A and B are downstream systems of system C.

[0066] It is understandable that determining whether the first business data of a specified type in the target benchmark system is the same as the second business data in other downstream systems means determining whether the business data in other downstream systems is consistent with the business data in the target benchmark system for the same specified type of business data.

[0067] Specifically, first confirm that the first and second business data are comparing the same business data, and then compare them one by one according to the order of each field.

[0068] For example: For business data of type a, determine whether the business data of type a in benchmark system A is the same as the business data of type a in system B, and determine whether the business data of type a in benchmark system A is the same as the business data of type a in system C.

[0069] In the specific implementation step S103, it is determined whether the first service data of a specified type in the target benchmark system is the same as the second service data of other downstream systems. If the first service data of a specified type in the target benchmark system is different from the second service data of other downstream systems, step S104 is executed. If the first service data of a specified type in the target benchmark system is the same as the second service data of other downstream systems, it is indicated that the service data of the specified type in all systems is consistent, and the data cleaning ends.

[0070] Step S104: Modify the second business data of other downstream systems based on the first business data.

[0071] It is understandable that if the first business data of a specified type in the target benchmark system is different from the second business data in other downstream systems, the second business data in other downstream systems will be modified based on the first business data.

[0072] It should be noted that, based on the first business data, the second business data in other downstream systems that are inconsistent with the first business data are modified so that all the second business data in other downstream systems are the same as the first business data in the target benchmark system.

[0073] For example, Table 1 shows the business data of a customer named "Zhang San" before data cleaning. There are inconsistencies between these business data. The baseline system is ECIFP. At this time, the erroneous business data is corrected based on the business data in the baseline system. See Table 2 for the business data of the customer "Zhang San" after data cleaning.

[0074] Table 1

[0075] Customer number Types of documents ID number Name Phone number ECIFP 3303736020 CC01000151 330824xxxxxxxx5000 Zhang San 1820000xxxx ECAS 3303736020 1 330824xxxxxxxx5000 3303736020 1820000xxxx EBIC 3303736020 1 330824xxxxxxxx5000 3303736020 -- NBANK 3303736020 1 330824xxxxxxxx5000 Zhang San 1820000xxxx NEXCH 3303736020 1 330824xxxxxxxx5000 3303736020 1820000xxxx

[0076] Table 2

[0077] Customer number Types of documents ID number Name Phone number ECIFP 3303736020 CC01000151 330824xxxxxxxx5000 Zhang San 1820000xxxx ECAS 3303736020 1 330824xxxxxxxx5000 Zhang San 1820000xxxx EBIC 3303736020 1 330824xxxxxxxx5000 Zhang San -- NBANK 3303736020 1 330824xxxxxxxx5000 Zhang San 1820000xxxx NEXCH 3303736020 1 330824xxxxxxxx5000 Zhang San 1820000xxxx

[0078] The above steps describe methods for cleaning business data. After cleaning business data using this method, the specified type of business data will be identical in the target baseline system and other downstream systems.

[0079] It should be noted that the above data cleaning methods are triggered in batches. Batch triggering is generally organized by the data management party and includes three types of trigger scenarios: regular cleaning, the addition of a new system to the data cleaning scope, or on-demand cleaning. On-demand cleaning means cleaning is initiated based on the needs of the user (data user).

[0080] In this embodiment of the invention, preset verification rules are used to verify the correctness of specified types of business data in the benchmark system, ensuring that all specified types of business data in the benchmark system are correct and usable. The system then checks whether specified types of business data in other downstream systems are inconsistent with those in the benchmark system. If inconsistencies are found, the inconsistent specified types of business data in other downstream systems are modified using the benchmark system as a reference. This process unifies the specified types of business data across all systems, ensuring that the specified types of business data are correct and usable in all systems. This improves the utilization rate of existing business data.

[0081] In some specific implementations, availability verification can be used to verify the availability of erroneous or inconsistent business data. For example, if debit card data in the financial IC card system (downstream system) and the core business system (baseline system) is inconsistent, after data cleaning using a data cleaning method, availability verification can be performed by initiating a "9772 IC Card - Transfer and Cash Top-up" process through the front-end system. Under normal test conditions, after data cleaning, the debit card data can complete the transaction normally.

[0082] It should be noted that the front-desk system is a banking business system, a counter service system for tellers. In other words, it's the system used by bank tellers to process transactions when customers visit a branch.

[0083] It is understandable that different business data uses different transactions for availability verification.

[0084] It should be noted that if availability verification still has problems after data cleaning, it may be because the data structure of the data in the baseline system or downstream system has changed (for example, a field is added / modified / deleted in the database table of the baseline system). In this case, the preset verification rules or cleaning rules need to be optimized.

[0085] In some embodiments, when a query command is received, business data that meets the query requirements is obtained from the benchmark system according to the query requirements carried in the query command.

[0086] Understandably, when testers need to use specific types of business data for testing, they can obtain the required business data from the benchmark system. However, they cannot obtain that specific type of business data from downstream systems of the benchmark system at this time, because downstream systems may contain more business data than the benchmark system, and there is no guarantee that this extra business data is consistent and accurate across different systems.

[0087] If you need to use business data that is redundant in these downstream systems compared to the baseline system, you can collect this redundant business data from the downstream systems, save it to the baseline system, and then use the baseline system as the standard to synchronize the data with other downstream systems. For details, please see the following content.

[0088] It should be noted that, since aggregating redundant business data will cause the amount of business data in the benchmark system to increase continuously, in actual use, a user-triggered approach is generally adopted. That is, after the tester queries the specified business data from the downstream system and provides the availability result of the specified business data, the user sends a supplementary instruction to supplement the specified business data to the benchmark system, triggering the process of cleaning up redundant business data.

[0089] See Figure 2 This diagram illustrates another flowchart of a method for making test data available across multiple systems based on data cleaning, according to an embodiment of the present invention. The data cleaning method includes:

[0090] Step S201: Determine whether the specified type of business data in each benchmark system conforms to the preset verification rules corresponding to the specified type. If the specified type of business data in the benchmark system does not conform to the preset verification rules corresponding to the specified type, proceed to step S202; if the specified type of business data in the benchmark system conforms to the preset verification rules corresponding to the specified type, proceed to step S203.

[0091] Step S202: Modify the specified type of business data in the baseline system according to the preset verification rules.

[0092] Step S203: Determine whether the first service data of a specified type in the target benchmark system is the same as the second service data in other downstream systems. If the first service data of a specified type in the target benchmark system is different from the second service data in other downstream systems, proceed to step S204; if the first service data of a specified type in the target benchmark system is the same as the second service data in other downstream systems, proceed to step S205.

[0093] Step S204: Modify the second business data of other downstream systems based on the first business data.

[0094] It should be noted that the specific implementation principles of steps S201 to S204 are the same as those of steps S101 to S104 in the above embodiments, and will not be repeated here.

[0095] Step S205: Obtain the third service data carried in the supplementary instruction.

[0096] In the specific implementation step S205, a supplementary instruction carrying third service data sent by the user is received. The third service data is the service data specified by the user.

[0097] It is understandable that the third business data is the specified business data of the same type as the first business data in the downstream system.

[0098] For example: If business data A, business data B, and business data C of type 1 are required in the downstream system, but the base system of type 1 does not contain business data A, business data B, and business data C, then supplementary instructions are generated based on business data A, business data B, and business data C. After processing business data A, business data B, and business data C according to the supplementary instructions, they are added to the base system.

[0099] It should be noted that the specific details of processing business data A, business data B, and business data C and supplementing them into the baseline system are as follows.

[0100] Step S206: According to the preset verification rules corresponding to the specified type of the third business data, the correctness of the third business data is verified to obtain the incremental business data.

[0101] It is understandable that, since there may be erroneous business data in the third business data, it is necessary to verify the correctness of the third business data, modify the erroneous business data in the third business data, and thus obtain incremental business data.

[0102] Step S207: Store the incremental business data in the target baseline system and synchronize the incremental business data to other baseline systems.

[0103] It is understandable that storing incremental business data in the target baseline system involves finding the corresponding second field in the target baseline system based on each first field in the incremental business data, and then storing the business data in the target baseline system.

[0104] For example, if the incremental business data includes: Customer ID: 3303736021, ID type: 2, ID number: 330824xxxxxxxx5111, Name: Li Si, and Mobile number: 1510000xxxx; then, based on the first field "Customer ID, ID type, ID number, Name, and Mobile number", the corresponding second field "Customer ID, ID type, ID number, Name, and Mobile number" will be searched in the target baseline system to store the incremental business data in the target baseline system one by one.

[0105] It should be noted that after the incremental business data is stored in the target benchmark system, the target benchmark system stores all business data of the specified type. At this time, the incremental business data in the target benchmark system is synchronized to other benchmark systems to ensure that the business data of the specified type in other benchmark systems is consistent, accurate and available with the target benchmark system.

[0106] In this embodiment of the invention, data cleaning is performed on the existing business data of a specified type in the baseline system, and the same specified type of business data in other downstream systems is synchronized. The specified business data of a specified type in other downstream systems that are more than those in the baseline system are processed and stored in the baseline system. The specified type of business data in the baseline system is synchronized to other downstream systems again, which greatly improves the availability of existing business data in all systems.

[0107] Corresponding to the method for making test data usable across multiple systems based on data cleaning provided in the above embodiments of the present invention, see also... Figure 3 The diagram shows a structural block diagram of an apparatus for enabling the availability of test data between multiple systems based on data cleaning, according to an embodiment of the present invention. The data cleaning apparatus includes: a first judgment unit 301, a first modification unit 302, a second judgment unit 303, and a second modification unit 304.

[0108] The first judgment unit 301 is used to determine whether the business data of a specified type in each benchmark system conforms to the preset verification rules corresponding to the specified type. Different benchmark systems correspond to different specified types of business data. If the business data of the specified type conforms to the preset verification rules corresponding to the specified type, the second judgment unit 303 is executed; if the business data of the specified type does not conform to the preset verification rules corresponding to the specified type, the first modification unit 302 is executed.

[0109] The first modification unit 302 is used to modify the specified type of business data in the benchmark system according to the preset verification rules if the specified type of business data in the benchmark system does not conform to the corresponding preset verification rules.

[0110] The second judgment unit 303 is used to determine whether the first business data of a specified type in the target benchmark system is the same as the second business data in other downstream systems. The first and second business data are business data of the same specified type, the target benchmark system is any benchmark system, and the downstream systems are determined based on the flow of the specified type of business data in the benchmark system. If the first business data of the specified type is the same as the second business data in other downstream systems, data cleaning ends; if the first business data of the specified type is not the same as the second business data in other downstream systems, the second modification unit 304 is executed.

[0111] The second modification unit 304 is used to modify the second business data of other downstream systems based on the first business data if the first business data of a specified type in the target reference system is different from the second business data of other downstream systems.

[0112] In this embodiment of the invention, existing business data in multiple systems are processed uniformly, and erroneous business data is corrected to ensure consistency and availability of business data across multiple systems, effectively guaranteeing the availability of existing data in the test environment.

[0113] Preferred, combined Figure 3 The data cleaning device also includes an acquisition unit, a standard processing unit, and a synchronization unit.

[0114] The acquisition unit is used to acquire the third business data carried in the supplementary instruction. The third business data is business data of the same type as the first business data in the downstream system.

[0115] The verification unit is used to verify the correctness of the third business data according to the preset verification rules corresponding to the specified type of the third business data, so as to obtain the incremental business data.

[0116] The synchronization unit is used to store incremental business data to the target baseline system and synchronize the incremental business data to other downstream systems.

[0117] In the specific implementation, the synchronization unit is used to store the data of each field in the incremental business data into the corresponding fields of the target baseline system.

[0118] Preferred, combined Figure 3 The data cleaning device also includes a deletion unit for deleting special characters stored in business data of a specified type in the baseline system.

[0119] Preferred, combined Figure 3 The data cleaning device also includes a query unit, which, when a query command is received, retrieves business data that meets the query requirements from the baseline system based on the query requirements carried in the query command.

[0120] In summary, the embodiments of the present invention provide a method and apparatus for making test data available across multiple systems based on data cleaning. Using business data of a specified type in a benchmark system as a standard, business data of the same specified type in other systems is synchronized. This solves problems such as inconsistent sources of existing business data between systems, inconsistent entry times into the test environment, and inconsistent usage and updates. It also processes erroneous business data, improves the accuracy of business data, keeps business data fresh, and solves the problem of business data being unusable or even unavailable.

[0121] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, for system or system embodiments, since they are basically similar to method embodiments, the description is relatively simple, and relevant parts can be referred to the descriptions in the method embodiments. The systems and system embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0122] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0123] The above description of the disclosed embodiments enables those skilled in the art to make or use the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the scope of the invention. Therefore, the invention is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for making test data usable across multiple systems based on data cleaning, characterized in that, The method includes: Determine whether the specified type of business data in each benchmark system conforms to the preset verification rules corresponding to the specified type, wherein different benchmark systems correspond to different specified types of business data; For each benchmark system, if the business data of a specified type in the benchmark system does not conform to the corresponding preset verification rule, the business data of the specified type in the benchmark system shall be modified according to the preset verification rule. Determine whether first business data of a specified type in the target benchmark system is the same as second business data in other downstream systems, wherein the first business data and the second business data are business data of the same specified type, the target benchmark system is any of the benchmark systems, and the downstream systems are determined according to the flow direction of the specified type of business data in the benchmark system; If the first service data of a specified type in the target benchmark system is different from the second service data in other downstream systems, the second service data in the other downstream systems shall be modified based on the first service data.

2. The method according to claim 1, characterized in that, The method further includes: Obtain the third service data carried in the supplementary instruction, wherein the third service data is service data of the same type as the first service data in the downstream system; According to the preset verification rules corresponding to the specified type of the third business data, the correctness of the third business data is verified to obtain incremental business data. The incremental service data is stored in the target baseline system, and the incremental service data is synchronized to other downstream systems.

3. The method according to claim 2, characterized in that, The step of storing the incremental service data in the target baseline system includes: The data of each field in the incremental business data is stored in the corresponding field of the target benchmark system.

4. The method according to claim 1, characterized in that, The method further includes: Delete special characters stored in the specified type of business data in the benchmark system.

5. The method according to claim 1, characterized in that, The method further includes: When a query command is received, the business data that meets the query requirements carried in the query command is obtained from the benchmark system.

6. An apparatus for enabling the use of test data across multiple systems based on data cleaning, characterized in that, The device includes: The first judgment unit is used to judge whether the business data of a specified type in each benchmark system conforms to the preset verification rules corresponding to the specified type, wherein different benchmark systems correspond to different specified types of business data; The first modification unit is used to modify the specified type of business data in the benchmark system according to the preset verification rule if the specified type of business data in the benchmark system does not conform to the corresponding preset verification rule for each benchmark system. The second judgment unit is used to determine whether the first business data of a specified type in the target benchmark system is the same as the second business data of other downstream systems, wherein the first business data and the second business data are business data of the same specified type, the target benchmark system is any of the benchmark systems, and the downstream system is determined according to the flow direction of the specified type of business data in the benchmark system. The second modification unit is used to modify the second service data of the other downstream systems based on the first service data if the first service data of a specified type in the target benchmark system is different from the second service data of the other downstream systems.

7. The apparatus according to claim 6, characterized in that, The device further includes: The acquisition unit is used to acquire the third service data carried in the supplementary instruction, wherein the third service data is service data of the same type as the first service data in the downstream system; The verification unit is used to verify the correctness of the third business data according to the preset verification rules corresponding to the specified type of the third business data, so as to obtain incremental business data. The synchronization unit is used to store the incremental service data in the target baseline system and synchronize the incremental service data to other downstream systems.

8. The apparatus according to claim 7, characterized in that, The synchronization unit is specifically used for: The data of each field in the incremental business data is stored in the corresponding field of the target benchmark system.

9. The apparatus according to claim 6, characterized in that, The device further includes: The deletion unit is used to delete special characters stored in the specified type of business data in the benchmark system.

10. The apparatus according to claim 6, characterized in that, The device further includes: The query unit is used to, when a query command is received, retrieve the business data that meets the query requirements carried in the query command from the benchmark system.

Images