Financial system migration test method and device, computer device and storage medium

Abstract

The application relates to a financial system migration test method and device, computer equipment and a storage medium, relates to the technical field of system migration test, and can be used in the field of financial technology or other related fields. The method comprises the following steps: acquiring first financial business data stored in a host database and acquiring corresponding second financial business data in a platform database; determining first field data of a preset field from the first financial business data and determining second field data of the preset field from the second financial business data; acquiring a data structure corresponding to the first field data, performing decoding processing on the first field data according to the data structure, and obtaining decoding results corresponding to respective first subfield data; comparing the respective decoding results with respective second subfield data, and outputting a test list as a financial system migration test result according to a comparison result. The method can improve the efficiency of financial system migration test.

Description

Technical Field

[0001] This application relates to the field of system migration testing technology, and in particular to a method, apparatus, computer equipment, storage medium and computer program product for financial system migration testing. Background Technology

[0002] With the development of fintech, a system migration technique has emerged that utilizes a general-purpose platform system to replace the existing mainframe system, thereby reducing reliance on large mainframe systems. Furthermore, to ensure the stable operation of the financial business system after migration, the migration process typically needs to be tested. This testing can be achieved by comparing the financial business data stored in the mainframe database with the financial business data stored in the platform database.

[0003] However, the financial business data currently stored in the host database typically contains large fields, and the data within these large fields is usually defined according to different data structures. Each field has a different encoding, and the number of bytes stored per character varies depending on the encoding. This encoding is inconsistent with the encoding stored in the platform database, making comparison testing impossible. Therefore, the migration testing efficiency of the existing financial system is low. Summary of the Invention

[0004] Therefore, it is necessary to provide a financial system migration testing method, apparatus, computer equipment, computer-readable storage medium, and computer program product that can improve the efficiency of financial system migration testing in response to the above-mentioned technical problems.

[0005] Firstly, this application provides a method for testing the migration of a financial system, the method comprising:

[0006] The system retrieves first financial business data to be compared from the host database and second financial business data corresponding to the first financial business data from the platform database; the host database is the database of the financial system to be migrated, and the platform database is the database of the financial system after the system migration.

[0007] The first field data of the preset field is determined from the first financial business data, and the second field data of the preset field is determined from the second financial business data; the first field data is composed of the first subfield data of multiple subfields, and the second field data is composed of the second subfield data of the multiple subfields;

[0008] Obtain the data structure corresponding to the preset first field data, and perform decoding processing on the first field data according to the data structure to obtain the decoding results corresponding to each of the first subfield data.

[0009] The decoding results corresponding to each of the first sub-field data are compared with the data of each of the second sub-fields. Based on the comparison results, the first financial business data is output to the test list, and the test list is used as the result of the financial system migration test.

[0010] In one embodiment, the data structure includes: the data length of each first sub-field data and the data type of each first sub-field data; the step of decoding the first field data according to the data structure to obtain the decoding result corresponding to each first sub-field data includes: obtaining the hexadecimal code corresponding to the first field data, and determining the hexadecimal code corresponding to each first sub-field data from the hexadecimal code corresponding to the first field data according to the data length and data type of each first sub-field data; and decoding the hexadecimal code corresponding to each first sub-field data according to the data type of each first sub-field data to obtain the decoding result corresponding to each first sub-field data.

[0011] In one embodiment, the step of decoding the hexadecimal code corresponding to each of the first sub-field data according to the data type of each first sub-field data to obtain the decoding result corresponding to each of the first sub-field data includes: obtaining the current hexadecimal code corresponding to the current first sub-field data; if the data type of the current first sub-field data is not ASCII, converting the current hexadecimal code into a character array to obtain the decoding result corresponding to the current first sub-field data; if the data type of the current first sub-field data is ASCII, converting the current hexadecimal code into a string to obtain the decoding result corresponding to the current first sub-field data.

[0012] In one embodiment, obtaining the first financial business data to be compared stored in the host database includes: obtaining the target financial application name and the target financial business type to be tested; obtaining candidate financial business data whose financial application name is the target financial application name and whose financial business type is the target financial business type from the log table of the host database; obtaining the data modification time corresponding to each candidate financial business data, and taking the candidate financial business data with the latest data modification time and not output to the test success list as the first financial business data to be compared.

[0013] In one embodiment, obtaining the second financial business data corresponding to the first financial business data stored in the platform database includes: obtaining the channel log number corresponding to the first financial business data from the log table of the host database; and taking the financial business data in the log table of the platform database whose channel log number is the same as the channel log number corresponding to the first financial business data as the second financial business data.

[0014] In one embodiment, obtaining the data structure corresponding to the preset first field data includes: querying a data structure correspondence table based on the target financial application name and the target financial business type; the data structure correspondence table stores the correspondence between each financial application name and each financial business type and multiple data structures; and obtaining the data structure corresponding to the target financial application name and the target financial business type through the data structure correspondence table, as the data structure corresponding to the first field data.

[0015] In one embodiment, the financial system migration testing method further includes: in response to an update operation on the data structure to be updated, performing the update operation on the data structure to be updated; the update operation includes at least one of: changing the data length of a sub-field contained in the data structure to be updated, changing the data type of a sub-field contained in the data structure to be updated, deleting a sub-field contained in the data structure to be updated, and adding a sub-field contained in the data structure to be updated.

[0016] In one embodiment, comparing the decoding results corresponding to each of the first sub-field data with each of the second sub-field data, and outputting the first financial business data to a test list based on the comparison results, includes: obtaining the current decoding result and the current second sub-field data that has the same sub-field as the current decoding result; the current decoding result is any one of the decoding results corresponding to each of the first sub-field data; comparing the current decoding result with the current second sub-field data; if the current decoding result is different from the current second sub-field data, outputting the first financial business data to a test failure list, and recording the current decoding result, the current second sub-field data, and the sub-fields of the current decoding result in the test failure list; if each of the current decoding results is the same as each of the current second sub-field data, outputting the first financial business data to a test success list.

[0017] In one embodiment, the financial system migration testing method further includes: if the platform database does not store the second financial business data corresponding to the first financial business data, outputting the first financial business data to the test failure list.

[0018] Secondly, this application also provides a financial system migration testing apparatus, the apparatus comprising:

[0019] The test data acquisition module is used to acquire the first financial business data to be compared stored in the host database, and to acquire the second financial business data corresponding to the first financial business data stored in the platform database; the host database is the database of the financial system to be migrated, and the platform database is the database of the financial system after the system migration.

[0020] The field data acquisition module is used to determine first field data of a preset field from the first financial business data, and to determine second field data of the preset field from the second financial business data; the first field data is composed of first subfield data of multiple subfields, and the second field data is composed of second subfield data of the multiple subfields;

[0021] The field data decoding module is used to obtain the data structure corresponding to the preset first field data, and to perform decoding processing on the first field data according to the data structure to obtain the decoding results corresponding to each of the first sub-field data.

[0022] The test result output module is used to compare the decoding results corresponding to each of the first sub-field data with each of the second sub-field data, output the first financial business data to the test list according to the comparison results, and use the test list as the financial system migration test result.

[0023] Thirdly, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to perform the following steps:

[0024] The system retrieves first financial business data to be compared from the host database and second financial business data corresponding to the first financial business data from the platform database; the host database is the database of the financial system to be migrated, and the platform database is the database of the financial system after the system migration.

[0025] The first field data of the preset field is determined from the first financial business data, and the second field data of the preset field is determined from the second financial business data; the first field data is composed of the first subfield data of multiple subfields, and the second field data is composed of the second subfield data of the multiple subfields;

[0026] Obtain the data structure corresponding to the preset first field data, and perform decoding processing on the first field data according to the data structure to obtain the decoding results corresponding to each of the first subfield data.

[0027] The decoding results corresponding to each of the first sub-field data are compared with the data of each of the second sub-fields. Based on the comparison results, the first financial business data is output to the test list, and the test list is used as the result of the financial system migration test.

[0028] Fourthly, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, performs the following steps:

[0029] The system retrieves first financial business data to be compared from the host database and second financial business data corresponding to the first financial business data from the platform database; the host database is the database of the financial system to be migrated, and the platform database is the database of the financial system after the system migration.

[0030] The first field data of the preset field is determined from the first financial business data, and the second field data of the preset field is determined from the second financial business data; the first field data is composed of the first subfield data of multiple subfields, and the second field data is composed of the second subfield data of the multiple subfields;

[0031] Obtain the data structure corresponding to the preset first field data, and perform decoding processing on the first field data according to the data structure to obtain the decoding results corresponding to each of the first subfield data.

[0032] The decoding results corresponding to each of the first sub-field data are compared with the data of each of the second sub-fields. Based on the comparison results, the first financial business data is output to the test list, and the test list is used as the result of the financial system migration test.

[0033] Fifthly, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, performs the following steps:

[0034] The system retrieves first financial business data to be compared from the host database and second financial business data corresponding to the first financial business data from the platform database; the host database is the database of the financial system to be migrated, and the platform database is the database of the financial system after the system migration.

[0035] The first field data of the preset field is determined from the first financial business data, and the second field data of the preset field is determined from the second financial business data; the first field data is composed of the first subfield data of multiple subfields, and the second field data is composed of the second subfield data of the multiple subfields;

[0036] Obtain the data structure corresponding to the preset first field data, and perform decoding processing on the first field data according to the data structure to obtain the decoding results corresponding to each of the first subfield data.

[0037] The decoding results corresponding to each of the first sub-field data are compared with the data of each of the second sub-fields. Based on the comparison results, the first financial business data is output to the test list, and the test list is used as the result of the financial system migration test.

[0038] The aforementioned financial system migration testing method, apparatus, computer equipment, storage medium, and computer program product acquire first financial business data to be compared stored in a host database and second financial business data corresponding to the first financial business data stored in a platform database; the host database is the database of the financial system to be migrated, and the platform database is the database of the financial system after the system migration; a first field of preset fields is determined from the first financial business data, and a second field of preset fields is determined from the second financial business data; the first field data consists of first subfield data of multiple subfields, and the second field data consists of second subfield data of multiple subfields; the data structure corresponding to the preset first field data is acquired, and the first field data is decoded according to the data structure to obtain the decoding results corresponding to each first subfield data; the decoding results corresponding to each first subfield data are compared with each second subfield data, and the first financial business data is output to a test list according to the comparison results, and the test list is used as the financial system migration test result. This application improves the efficiency of financial system migration testing by obtaining first field data containing multiple subfields stored in the host database and second field data containing multiple subfields in the platform database during system migration testing. It then decodes each subfield of the first field data using a pre-defined data structure corresponding to the first field data and compares the decoded results with those of the second field data to output a corresponding test list as the financial system migration test result. This achieves data comparison for different field code systems and different single-character storage byte counts, thereby improving the efficiency of financial system migration testing. Attached Figure Description

[0039] Figure 1 This is a flowchart illustrating a financial system migration testing method in one embodiment;

[0040] Figure 2 This is a flowchart illustrating the process of obtaining the decoding result corresponding to the first subfield data in one embodiment;

[0041] Figure 3 This is a flowchart illustrating the process of obtaining the decoding result corresponding to the first subfield data in another embodiment;

[0042] Figure 4 This is a schematic diagram of the process for obtaining the first financial business data to be compared in one embodiment;

[0043] Figure 5 This is a flowchart illustrating the process of outputting first financial business data to a test list in one embodiment;

[0044] Figure 6This is a schematic diagram of the structure of a large-field data comparison test system in one embodiment;

[0045] Figure 7 This is a schematic diagram of the data structure input device in one embodiment;

[0046] Figure 8 This is a schematic diagram of the structure of an automatic decoding device in one embodiment;

[0047] Figure 9 This is a schematic diagram of the automatic association comparison device in one embodiment;

[0048] Figure 10 This is a schematic diagram of the structure of a result report output device in one embodiment;

[0049] Figure 11 This is a structural block diagram of a financial system migration test apparatus in one embodiment;

[0050] Figure 12 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0051] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0052] In one embodiment, such as Figure 1 As shown, a migration testing method for a financial system is provided. This embodiment illustrates the method applied to a terminal, but it is understood that the method can also be applied to a server, and to a system including both a terminal and a server, and implemented through the interaction between the terminal and the server. In this embodiment, the method includes the following steps:

[0053] Step S101: Obtain the first financial business data to be compared stored in the host database, and obtain the second financial business data corresponding to the first financial business data stored in the platform database; the host database is the database of the financial system to be migrated, and the platform database is the database of the financial system after the system migration.

[0054] The first financial business data refers to the financial business data used for data comparison. This data can be stored in the host database, which refers to the old financial business system before the system migration, i.e., the host system's database. The second financial business data, stored in the platform database, is used to compare with the first financial business data. The platform database refers to the new financial business system after the system migration, i.e., the database of the general platform system. Specifically, during the financial system migration test, the terminal can first extract the first financial business data for system migration test data comparison from the host database, and then obtain the corresponding second financial business data from the platform database.

[0055] Step S102: Determine the first field data of the preset field from the first financial business data, and determine the second field data of the preset field from the second financial business data; the first field data consists of the first subfield data of multiple subfields, and the second field data consists of the second subfield data of multiple subfields.

[0056] The first field data refers to the field data of a pre-defined field in the first financial business data, while the second field data refers to the field data of a pre-defined field in the second financial business data. In this embodiment, the financial business data stored in the financial business system consists of field data of multiple fields, and the pre-defined field is one of the aforementioned multiple fields. The field data corresponding to this field can also consist of multiple subfields. The first subfield data refers to the field data of each subfield in the first field data, and the second subfield data refers to the field data of each subfield in the second field data.

[0057] For example, the fields of certain financial transaction data may include: a channel log number field, a financial transaction type field, a large field containing multiple subfields, and a financial transaction trigger time field, etc. The large field may contain subfields such as account number, account document type, and account contact information. After receiving the first financial transaction data, the terminal can first use the large field data from the first financial transaction data as the first field of a preset field. This first field data can store multiple first subfield data, including account number, account document type, and account contact information. Similarly, the terminal can also use the large field data from the second financial transaction data as the second field of a preset field. This second field data can also store multiple second subfield data, including account number, account document type, and account contact information.

[0058] Step S103: Obtain the data structure corresponding to the preset first field data, and decode the first field data according to the data structure to obtain the decoding results corresponding to each first subfield data.

[0059] The data structure refers to the data structure of the first field data. This data structure may contain the data types or data lengths corresponding to the multiple sub-field data that make up the first field data. In this embodiment, the data structure of the first field data may be preset. The terminal may first obtain the preset data structure for the first field data, and then perform decoding processing on the first field data based on the above data structure to obtain the decoding results corresponding to each first sub-field data that makes up the first field data.

[0060] Step S104: Compare the decoding results corresponding to each first subfield data with each second subfield data, output the first financial business data to the test list based on the comparison results, and use the test list as the financial system migration test result.

[0061] Finally, the terminal can compare the decoding result corresponding to each first subfield data with each second subfield data, and then output the first financial business data to the test list based on the comparison result as the result of the financial system migration test.

[0062] For example, the first field data may contain multiple first subfield data such as account number, account document type, and account contact information. After obtaining the above first field data, the terminal can decode each first subfield data based on the data structure of the first field data, thereby obtaining the decoding results of the account number, the account document type, and the account contact information respectively. The above decoding results can be compared with the multiple second subfield data of the account number, account document type, and account contact information contained in the second field data. After obtaining the comparison results, the first financial business data can be output to the corresponding test list as the test result of the financial system migration.

[0063] In the aforementioned financial system migration testing method, the following steps are taken: First financial business data to be compared is obtained from the host database, and second financial business data corresponding to the first financial business data is obtained from the platform database. The host database is the database of the financial system to be migrated, and the platform database is the database of the financial system after migration. First field data with preset fields is determined from the first financial business data, and second field data with preset fields is determined from the second financial business data. The first field data consists of first subfield data of multiple subfields, and the second field data consists of second subfield data of multiple subfields. The data structure corresponding to the preset first field data is obtained, and the first field data is decoded according to the data structure to obtain the decoding results corresponding to each first subfield data. The decoding results corresponding to each first subfield data are compared with each second subfield data. Based on the comparison results, the first financial business data is output to the test list, and the test list is used as the financial system migration test result. This application improves the efficiency of financial system migration testing by obtaining first field data containing multiple subfields stored in the host database and second field data containing multiple subfields in the platform database during system migration testing. It then decodes each subfield of the first field data using a pre-defined data structure corresponding to the first field data and compares the decoded results with those of the second field data to output a corresponding test list as the financial system migration test result. This achieves data comparison for different field code systems and different single-character storage byte counts, thereby improving the efficiency of financial system migration testing.

[0064] In one embodiment, the data structure includes: the data length of each first subfield data, and the data type of each first subfield data; such as Figure 2 As shown, step S103 may further include:

[0065] Step S201: Obtain the hexadecimal code corresponding to the first field data, and determine the hexadecimal code corresponding to each first subfield data from the hexadecimal code corresponding to the first field data according to the data length and data type of each first subfield data.

[0066] In this embodiment, the data structure corresponding to the first field data can store the data length of each first sub-field data and the data type of each first sub-field data. For example, the data structure corresponding to the first field data records that the data type of the account number is a character type, i.e., char type, and the data length is 20 digits; the data type of the account document type is an integer type, i.e. int type, and the data length is 3 digits; and the data type of the account contact information is a character type, and the data length is 20 digits, and so on.

[0067] Specifically, after receiving the first field data, the terminal can first perform hexadecimal conversion on the first field data to obtain the corresponding hexadecimal code. Furthermore, based on the data length and data type of each first subfield data, the terminal can determine the hexadecimal code of each first subfield data from the hexadecimal code corresponding to the first field data. For example, if the account number is of type char and has a data length of 20 digits, after hexadecimal conversion, the account number data length will become 40 digits. The terminal can then use the first 40 digits of the hexadecimal code corresponding to the first field data as the hexadecimal code for the account number. Thus, through the above method, the terminal can obtain the hexadecimal code corresponding to each first subfield data.

[0068] Step S202: According to the data type of each first subfield data, the hexadecimal code corresponding to each first subfield data is decoded to obtain the decoding result corresponding to each first subfield data.

[0069] After obtaining the first subfield data, the terminal can decode the hexadecimal code corresponding to each first subfield data according to the data type of each subfield data, thereby obtaining the decoding result corresponding to each first subfield data.

[0070] In this embodiment, the terminal can first perform hexadecimal conversion on the first field data to obtain the hexadecimal code. Then, based on the data length and data type of the first subfield data, the terminal can obtain the hexadecimal code of each first subfield data. Furthermore, based on the data type of each first subfield data, the terminal can perform decoding processing on the hexadecimal codes respectively. In this way, the accuracy of the decoding of the first subfield data can be improved.

[0071] Furthermore, such as Figure 3 As shown, step S202 may further include:

[0072] Step S301: Obtain the current hexadecimal code corresponding to the current first subfield data.

[0073] The current first subfield data can be any one of the first subfield data, while the current hexadecimal code refers to the hexadecimal code corresponding to the current first subfield data. Specifically, the terminal can use any one of the first subfield data contained in the first field data as the current first subfield data, and use the hexadecimal code corresponding to the current first subfield data as the current hexadecimal code.

[0074] Step S302: If the data type of the current first subfield data is not ASCII, convert the current hexadecimal code into a character array to obtain the decoding result corresponding to the current first subfield data.

[0075] If the current first subfield data is not of ASCII type, for example, if the current first subfield data is of char type or int type, the terminal will convert the current hexadecimal code into a character array. The specific conversion method can be to convert every 2 hexadecimal values ​​in the current hexadecimal code into a character array, so that the data length of the converted decoding result is half of the current hexadecimal code.

[0076] For example, for non-ASCII subfield data, the specific encoding process can be implemented using the following code:

[0077]

[0078] Step S303: If the data type of the current first subfield data is ASCII, convert the current hexadecimal code into a string to obtain the decoding result corresponding to the current first subfield data.

[0079] If the current first subfield data is of ASCII type, the terminal will convert the current hexadecimal code into a string. Specifically, the conversion method can be to convert every 4 hexadecimal values ​​in the current hexadecimal code into a character array, so that the data length of the converted decoding result is one-quarter of the current hexadecimal code.

[0080] For example, for ASCII type subfield data, the specific encoding process can be implemented using the following code:

[0081]

[0082] In this embodiment, for the first subfield data, the corresponding hexadecimal code can be decoded based on the data type of each first subfield data. For non-ASCII types, the hexadecimal code can be converted into a character array, while for ASCII types, the hexadecimal code can be converted into a string. By doing so, the accuracy of the decoded result can be improved.

[0083] In one embodiment, such as Figure 4 As shown, step S101 may further include:

[0084] Step S401: Obtain the name of the target financial application to be tested, as well as the type of target financial business.

[0085] Here, the target financial application name refers to the application name corresponding to the financial business data to be tested, while the target financial business type refers to the business type corresponding to the financial business data to be tested. In this embodiment, the test user can pre-set the application name and business type for which financial business data comparison testing is required. The terminal can then use the aforementioned application name as the target financial application name and the aforementioned financial business type as the target financial business type.

[0086] Step S402: Obtain candidate financial business data from the log table of the host database, where the financial application name is the target financial application name and the financial business type is the target financial business type.

[0087] Candidate financial business data refers to financial business data stored in the host database where the financial application name is the target financial application name and the financial business type is the target financial business type. In this embodiment, the log table of the host database can store various types of financial business data, and each type of financial business data corresponds to a financial application name field and a financial business type field. The terminal can filter out financial business data from the above log table where the financial application name field matches the target financial application name and the financial business type field matches the target financial business type, as candidate financial business data.

[0088] Step S403: Obtain the data modification time corresponding to each candidate financial business data, and take the candidate financial business data with the latest data modification time that has not been output to the test success list as the first financial business data to be compared.

[0089] The data modification time refers to the time when the candidate financial business data was last modified. If a candidate financial business data is generated for the first time, then the generation time is used as the data modification time. If a candidate financial business data has been generated and then modified, then the time of the last modification of the candidate financial business data is used as the data modification time. In this embodiment, the financial business data stored in the log table of the host database, in addition to the financial application name field and the financial business type field, may also include a data modification time field. The terminal 101 can obtain the data modification time corresponding to each candidate financial business data based on the data modification time field of each candidate financial business data.

[0090] The test success list represents the test results that indicate a successful test. This list can include both a test success list and a test failure list. The test success list records financial business data that has passed the system migration test and is stored in the host database, while the test failure list records financial business data that failed the system migration test and is also stored in the host database. Therefore, the financial business data stored in the host database includes three types: financial business data that has passed the system migration test, financial business data that failed the system migration test, and financial business data that has not yet undergone system migration testing. Furthermore, if financial business data has already passed the system migration test, it does not need to be tested again. Therefore, after receiving candidate financial business data, the terminal can select the candidate financial business data with the most recent modification time (i.e., the most recently modified data) that has not been output to the test success list (i.e., the financial business data that has not yet passed the system migration test) as the first financial business data to be compared.

[0091] In this embodiment, the terminal can obtain the name of the target financial application to be tested and the type of target financial business. After filtering out candidate financial business data, the candidate financial business data with the latest data modification time and not output to the test success list is used as the first financial business data for data comparison test. This can improve the efficiency of system migration test while ensuring the accuracy of system migration.

[0092] Furthermore, step S101 may further include: obtaining the channel log number corresponding to the first financial business data from the log table of the host database; and using the financial business data stored in the log table of the platform database whose channel log number is the same as the channel log number corresponding to the first financial business data as the second financial business data.

[0093] The channel log number refers to the log number corresponding to the first financial business data, and each financial business data has a different channel log number, which can be used to identify the financial business data. In this embodiment, the log table of the host database can store the channel log numbers corresponding to each financial business data. After the terminal determines the first financial business data, it can obtain the channel log number corresponding to the first financial business data. Then, it can use the channel log number to search the log table of the platform database to find the financial business data with the same channel log number as the first financial business data, which will be used as the second financial business data.

[0094] For example, the host database's log table stores financial business data A1, financial business data B1, and financial business data C1, with corresponding channel log numbers A, B, and C, respectively. The platform database's log table stores financial business data A2, financial business data B2, and financial business data C2, with corresponding channel log numbers A, B, and C, respectively. If financial business data A1 is identified as the first financial business data, then the terminal can use the channel log number corresponding to financial business data A1, i.e., log number A, to search the platform database's log table and use the financial business data corresponding to log number A, i.e., financial business data A2, as the second financial business data.

[0095] In this embodiment, the terminal can use the channel log number corresponding to the first financial business data recorded in the log table of the host database to search for the second financial business data with the same channel log number. The efficiency of obtaining the second financial business data can be improved by the above method.

[0096] In addition, step S103 may further include: querying the data structure correspondence table according to the target financial application name and the target financial business type; the data structure correspondence table stores the correspondence between each financial application name and each financial business type and multiple data structures; and obtaining the data structure corresponding to the target financial application name and the target financial business type through the data structure correspondence table, as the data structure corresponding to the first field data.

[0097] The data structure mapping table is used to store the mapping relationships between data structures. This table records the correspondence between different financial application names, different financial business types, and various preset field data data structures. Therefore, the terminal can use this mapping table to obtain the data structure corresponding to the first financial business data. Furthermore, since the financial application name corresponding to the first financial business data is the target application name, and the financial business type corresponding to the first financial business data is the target financial business type, the terminal can use the target application name and target financial business type to query the data structure mapping table and use the data structure corresponding to the target application name and target financial business type as the data structure corresponding to the first field data.

[0098] In this embodiment, a data structure correspondence table with various application names, financial business types, and data structures can be pre-constructed. This table can then be used to query the data structure corresponding to the target financial application name and the target financial business type, which serves as the data structure corresponding to the first field data. This improves the efficiency of data structure retrieval.

[0099] In one embodiment, the financial system migration testing method may further include: performing an update operation on the data structure to be updated in response to an update operation on the data structure to be updated; the update operation includes at least one of: changing the data length of a subfield contained in the data structure to be updated, changing the data type of a subfield contained in the data structure to be updated, deleting a subfield contained in the data structure to be updated, and adding a subfield contained in the data structure to be updated.

[0100] The data structure to be updated refers to the data structure of the preset field data that needs to be updated. The update operation refers to the operation used to update the data structure, which can be triggered by the user. Since the data structure can store the data type and length of each sub-field in the preset field data, the update operation can include various types, such as changing the length of a sub-field in the data structure to be updated, deleting a sub-field, adding a sub-field, or changing the data type of a sub-field, etc.

[0101] Specifically, if a user needs to update the data structure of a preset field, an update operation for updating the data structure can be triggered. The terminal can then use the data structure that the user needs to update as the data structure to be updated and perform the corresponding data structure update operation on the data structure to be updated. For example, it can change the data length or data type of a sub-field contained therein, or it can add or delete a sub-field.

[0102] In this embodiment, the user can also update the data structure by triggering an update operation to update the data structure, thereby further improving the real-time accuracy of data structure storage.

[0103] In one embodiment, such as Figure 5 As shown, step S104 may further include:

[0104] Step S501: Obtain the current decoding result and the current second subfield data that is the same as the subfield of the current decoding result; the current decoding result is any one of the decoding results corresponding to the first subfield data.

[0105] Step S502: Compare the current decoding result with the current second subfield data.

[0106] The current decoding result refers to any one of the decoding results corresponding to the first subfield data. Since the first field data contains multiple first subfield data, the number of decoding results obtained after decoding the first subfield data can also be multiple, and the current decoding result can be any one of these multiple decoding results. The current second subfield data refers to the second subfield data that is the same as the subfield of the current decoding result. Similar to the first subfield data, the second field data can also contain multiple second subfield data, each corresponding to a different subfield. The current second subfield data is the second subfield data that is the same as the subfield of the current decoding result.

[0107] For example, the first field data includes subfield data A1, subfield data B1, and subfield data C1, which correspond to subfield A, subfield B, and subfield C, respectively. After the terminal decodes the above subfield data A1, subfield data B1, and subfield data C1, if the decoding result of subfield data A1 is taken as the current decoding result, then the subfield data A2 corresponding to subfield A in the second field data can be taken as the current second subfield data.

[0108] Specifically, after determining the current decoding result, the terminal can identify the second subfield data that is identical to the subfield of the current decoding result and use it as the current second subfield data. Then, the terminal can compare the current decoding result with the current second subfield data to obtain a comparison result for each current decoding result and the current second subfield data.

[0109] Step S503: If the current decoding result is different from the current second subfield data, output the first financial business data to the test failure list, and record the current decoding result, the current second subfield data, and the subfield of the current decoding result in the test failure list.

[0110] The test failure list is used to record the first financial business data that failed the system migration test. In this embodiment, if the current decoding result and the current second subfield data are different, the terminal can output the first financial business data to the test failure list. At the same time, the test failure list can also add records of the current decoding result, the current second subfield data, and the subfield of the current decoding result to indicate which subfield in the first financial business data has a comparison error, and store the subfield data corresponding to that subfield.

[0111] Step S504: If all current decoding results are the same as all current second subfield data, output the first financial business data to the test success list.

[0112] If each current decoding result is the same as the corresponding current second subfield data, indicating that the data content stored in the first field data and the second field data is the same, then the terminal can consider that the system migration test for the first financial business data has passed, and can therefore output it to the test success list.

[0113] In this embodiment, the terminal can also compare each current decoding result with the corresponding second subfield data to determine whether the first financial business data has passed the system migration test, and output them to the test success list and the test failure list respectively. This method can improve the accuracy of the system migration test.

[0114] In addition, the financial system migration testing method may also include: if the platform database does not store the second financial business data corresponding to the first financial business data, outputting the first financial business data to the test failure list.

[0115] If the platform database does not store the second financial business data corresponding to the first financial business data, that is, if a certain financial business data is only stored in the host database and not in the platform database, the terminal will consider that the financial business data cannot pass the system migration test, and will therefore output the first financial business data to the test failure list.

[0116] In this embodiment, if the platform database does not store the second financial business data corresponding to the first financial business data, the terminal can also output the financial business data to the test failure list, thereby further ensuring the accuracy of the system migration test.

[0117] In one embodiment, a method for comparing large-field data is also provided. This method can be applied during system migration testing. It can flexibly decode large-field data in the host database based on different host data structures, different field encoding systems, and different byte counts for single-character storage. It then associates the recorded channel log numbers with platform database records for batch automatic comparison, improving testing efficiency. This method can be applied to systems such as... Figure 6 The large-field data comparison test system shown below has the following specific functions:

[0118] Data structure input device 1: This device can customize different host large field data structures, and supports adding, modifying and deleting data structures.

[0119] Automatic decoding device 2: This device automatically decodes large field data of the host according to the data structure defined by device 1.

[0120] Automatic association comparison device 3: This device automatically searches for the corresponding record in the associated platform database based on the decoding result of device 2 and performs automatic comparison.

[0121] Result report output device 4: Based on the operation results of device 3, input success reports and failure reports respectively, and provide details of failure reports.

[0122] Figure 7 This is a schematic diagram of the internal structure of the data structure input device 1, in which:

[0123] New input unit 11: Allows for customization of different host large field data structures. It can be arbitrarily customized according to different application systems and business types. For example, the data structure of application A and business type A can be shown in Table 1:

[0124] Table 1. Data Structure Diagram for Data Structure A

[0125]

[0126] Customer number char(15) Document Types Int(3) ID number ASCII(20) Name ASCII(10) address ASCII(60) cell phone Int(15)

[0127] The name, type, and length of each subfield in the above large field A can be freely changed.

[0128] Adjusting input unit 12: Existing data structures can be modified. Fields, types, and lengths can be adjusted arbitrarily. For example, the newly added data structure can be adjusted as shown in Table 2:

[0129] Table 1. Schematic diagram of the adjusted data structure for large field data A.

[0130] field name type illustrate Customer number char(20) Modify field length Document Types Int(3) ID number char(20) Modify field type Name ASCII(10) address ASCII(60) Delete this field cell phone Int(15) Mail char(20) Add a field

[0131] Delete input unit 13: You can directly delete an existing data structure, such as directly deleting the data structure of the large field data A defined above. To delete an index, use the application name + business type.

[0132] Figure 8 This is a schematic diagram of the internal structure of the automatic decoding device 2, such as... Figure 8 As shown, where:

[0133] Sorting and Filtering Unit 21: This unit aims to improve program efficiency and consists of the following steps:

[0134] Step 1: The large fields are recorded in the host log table. Before comparison, records of the same application and transaction are sorted in descending order of log recording time, and the most recently modified record is retrieved. The log table data structure is shown in Table 3 below:

[0135] Table 3. Schematic diagram of log table data structure

[0136]

[0137]

[0138] Step 2: Retrieves the success records of the success report output device 4 and the success record output unit 41 of the success report in a self-loop manner. It queries whether there is already a successfully verified record based on the application name and business type. If there is, it will not be verified again and will continue to process the next record.

[0139] Decoding unit 22: Decodes the large fields of the records obtained by sorting and filtering unit 21 according to the data structure of device 1, which involves the following steps:

[0140] Step 1: Obtain the hexadecimal code of the large field value and assign it to the variable S:

[0141] Query log records from the database by searching the channel log number field, and convert the returned large field to hexadecimal using the HEX function: SELECT hex(large field) FROM host log table WHERE channel log number = 'channel log number filtered by sorting filter unit 21'

[0142] Step 2: For non-ASCII fields, such as the large field data 1, the structure is data structure A as shown in Table 1, and its specific storage method is shown in Table 3:

[0143] Table 3 shows a storage diagram of the main field data 1.

[0144] field name type Specific value Account number char(20) 100001 Document Types Int(3) 001 ID number char(20) ID Number A Name ASCII(10) NameA cell phone Int(15) Mobile number A Mail char(20) Email address A

[0145] The non-ASCII fields are shown in Table 4, including:

[0146] Table 4. Schematic diagram of non-ASCII code field storage for major data field 1.

[0147] field name type Specific value Account number char(20) 100001 Document Types Int(3) 001 ID number char(20) ID Number A cell phone Int(15) Mobile number A Mail char(20) Email address A

[0148] These fields are then encoded using the mainframe encoding rules:

[0149]

[0150]

[0151] Step 3: For ASCII fields, use the hexadecimal ASCII to string conversion rules for encoding. For example, for large field data 1 above, the ASCII fields can be shown in Table 5, including:

[0152] Table 5. Schematic diagram of non-ASCII code field storage for major field data.

[0153] field name type Specific value Name ASCII(10) NameA

[0154] Define a function `decode` that takes a large numerical value as input and processes it in the variable `value`.

[0155]

[0156]

[0157] Figure 9 This is a schematic diagram of the internal structure of the automatic correlation and comparison device 3, in which:

[0158] Log table comparison unit 31: Based on the decoding result of device 2, and according to the channel log number, the platform table records are queried, and the large field values ​​after host decoding are compared with the corresponding large field values ​​of the platform. For example, the record value of financial data 1 in the host log table can be shown in Table 6:

[0159] Table 6. Schematic diagram of the storage of financial data 1

[0160]

[0161] The specific values ​​of the large field are shown in Table 3. Then, the platform log table record can be found according to the channel log number A, and the large field values ​​after decoding by the automatic decoding device 2 can be compared to see if they are consistent.

[0162] Figure 10 The diagram shown is an internal composition diagram of the result report output device 4, in which:

[0163] Successful result output unit 41: Outputs the successful comparison record of device 3 to the successful report list. An example is as follows:

[0164] If the above records match, they will be directly output to the success list. The structure and specific values ​​are shown in Table 7.

[0165] Table 7 Success List Results Report

[0166] Channel Log Number Business type Comparison time result Number A Business Type A Comparison time A success

[0167] Failure Result Output Unit 42: Outputs the comparison failure records of device 3, along with details of inconsistent field values, to the failure report list. It has the following branches:

[0168] Branch 1: If there is no corresponding record in the platform table, the error list will be as shown in Table 8.

[0169] Table 8 Failure List Results Report

[0170]

[0171] Branch 2: If the field values ​​in the platform table are inconsistent, the error list will be as shown in Table 9.

[0172] Table 9 Failure List Results Report

[0173]

[0174] The output also shows inconsistent field details, as shown in Table 10:

[0175] Table 10: Details of Inconsistent Fields

[0176] Channel Log Number Inconsistent field names Host value Platform value Number A Document Types 000 001 Number A Name NameA Name B Number A cell phone Mobile number A Phone number B

[0177] This embodiment provides a method or apparatus that can flexibly decode large field data of a host computer based on different data structures, different field encoding systems, and different numbers of bytes stored per character. It can also perform batch automatic comparison by associating the recorded channel log numbers with the platform database records, thereby improving testing efficiency.

[0178] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0179] Based on the same inventive concept, this application also provides a financial system migration testing apparatus for implementing the financial system migration testing method described above. The solution provided by this apparatus is similar to the implementation scheme described in the above method; therefore, the specific limitations in one or more embodiments of the financial system migration testing apparatus provided below can be found in the limitations of the financial system migration testing method described above, and will not be repeated here.

[0180] In one embodiment, such as Figure 11 As shown, a financial system migration testing device is provided, comprising: a test data acquisition module 1101, a field data acquisition module 1102, a field data decoding module 1103, and a test result output module 1104, wherein:

[0181] The test data acquisition module 1101 is used to acquire the first financial business data to be compared stored in the host database, and to acquire the second financial business data corresponding to the first financial business data stored in the platform database; the host database is the database of the financial system to be migrated, and the platform database is the database of the financial system after the system migration.

[0182] The field data acquisition module 1102 is used to determine the first field data of the preset field from the first financial business data, and to determine the second field data of the preset field from the second financial business data; the first field data consists of the first subfield data of multiple subfields, and the second field data consists of the second subfield data of multiple subfields;

[0183] The field data decoding module 1103 is used to obtain the data structure corresponding to the preset first field data, and to decode the first field data according to the data structure to obtain the decoding results corresponding to each first subfield data.

[0184] The test result output module 1104 is used to compare the decoding results corresponding to each first subfield data with each second subfield data, output the first financial business data to the test list based on the comparison results, and use the test list as the financial system migration test result.

[0185] In one embodiment, the data structure includes: the data length of each first subfield data and the data type of each first subfield data; the field data decoding module 1103 is further used to obtain the hexadecimal code corresponding to the first field data, and determine the hexadecimal code corresponding to each first subfield data from the hexadecimal code corresponding to the first field data according to the data length and data type of each first subfield data; and perform decoding processing on the hexadecimal code corresponding to each first subfield data according to the data type of each first subfield data to obtain the decoding result corresponding to each first subfield data respectively.

[0186] In one embodiment, the field data decoding module 1103 is further configured to obtain the current hexadecimal code corresponding to the current first subfield data; if the data type of the current first subfield data is not ASCII, the current hexadecimal code is converted into a character array to obtain the decoding result corresponding to the current first subfield data; if the data type of the current first subfield data is ASCII, the current hexadecimal code is converted into a string to obtain the decoding result corresponding to the current first subfield data.

[0187] In one embodiment, the test data acquisition module 1101 is further used to acquire the target financial application name to be tested and the target financial business type; acquire candidate financial business data whose financial application name is the target financial application name and whose financial business type is the target financial business type from the log table of the host database; acquire the data modification time corresponding to each candidate financial business data, and take the candidate financial business data with the latest data modification time and not output to the test success list as the first financial business data to be compared.

[0188] In one embodiment, the test data acquisition module 1101 is further configured to obtain the channel log number corresponding to the first financial business data from the log table of the host database; and to use the financial business data in the log table of the platform database whose channel log number is the same as the channel log number corresponding to the first financial business data as the second financial business data.

[0189] In one embodiment, the field data decoding module 1103 is further configured to query a data structure correspondence table based on the target financial application name and the target financial business type; the data structure correspondence table stores the correspondence between each financial application name and each financial business type and multiple data structures; through the data structure correspondence table, the data structure corresponding to the target financial application name and the target financial business type is obtained as the data structure corresponding to the first field data.

[0190] In one embodiment, the financial system migration testing apparatus further includes: a data structure update module, configured to perform an update operation on the data structure to be updated in response to an update operation on the data structure to be updated; the update operation includes at least one of: changing the data length of a subfield contained in the data structure to be updated, changing the data type of a subfield contained in the data structure to be updated, deleting a subfield contained in the data structure to be updated, and adding a subfield contained in the data structure to be updated.

[0191] In one embodiment, the test result output module 1104 is further configured to obtain the current decoding result and the current second subfield data that is the same as the subfield of the current decoding result; the current decoding result is any one of the decoding results corresponding to the first subfield data; compare the current decoding result with the current second subfield data; if the current decoding result is different from the current second subfield data, output the first financial business data to the test failure list, and record the current decoding result, the current second subfield data, and the subfield of the current decoding result in the test failure list; if each current decoding result is the same as each current second subfield data, output the first financial business data to the test success list.

[0192] In one embodiment, the test result output module 1104 is further configured to output the first financial business data to the test failure list if the platform database does not store the second financial business data corresponding to the first financial business data.

[0193] Each module in the aforementioned financial system migration testing device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of a computer device in hardware form or independent of it, or stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0194] In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 12 As shown, the computer device includes a processor, memory, communication interface, display screen, and input devices connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a financial system migration testing method. The display screen can be an LCD screen or an e-ink screen. The input devices can be a touch layer covering the display screen, buttons, a trackball, or a touchpad on the computer device's casing, or an external keyboard, touchpad, or mouse.

[0195] Those skilled in the art will understand that Figure 12 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0196] In one embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.

[0197] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above method embodiments.

[0198] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0199] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0200] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0201] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0202] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A method for migration testing of a financial system, characterized in that, The method includes: The system retrieves first financial business data to be compared from the host database and second financial business data corresponding to the first financial business data from the platform database; the host database is the database of the financial system to be migrated, and the platform database is the database of the financial system after the system migration. The first field data of the preset field is determined from the first financial business data, and the second field data of the preset field is determined from the second financial business data; the first field data is composed of the first subfield data of multiple subfields, and the second field data is composed of the second subfield data of the multiple subfields; Obtain the preset data structure corresponding to the first field data, and decode the first field data according to the data structure to obtain the decoding result corresponding to each of the first sub-field data. The data structure includes: the data length of each of the first sub-field data and the data type of each of the first sub-field data. Specifically, according to the data structure, the first field data is decoded to obtain the decoding results corresponding to each of the first sub-field data, including: obtaining the hexadecimal code corresponding to the first field data, and determining the hexadecimal code corresponding to each of the first sub-field data from the hexadecimal code corresponding to the first field data according to the data length and data type of each of the first sub-field data; and decoding the hexadecimal code corresponding to each of the first sub-field data according to the data type of each of the first sub-field data to obtain the decoding results corresponding to each of the first sub-field data. The decoding results corresponding to each of the first sub-field data are compared with the data of each of the second sub-fields. Based on the comparison results, the first financial business data is output to the test list, and the test list is used as the result of the financial system migration test.

2. The method according to claim 1, characterized in that, The step of decoding the hexadecimal code corresponding to each of the first sub-field data according to the data type of each first sub-field data to obtain the decoding result corresponding to each of the first sub-field data includes: Get the current hexadecimal code corresponding to the current first subfield data; If the data type of the current first subfield data is not ASCII, the current hexadecimal code is converted into a character array to obtain the decoding result corresponding to the current first subfield data; If the data type of the current first subfield data is ASCII, the current hexadecimal code is converted into a string to obtain the decoding result corresponding to the current first subfield data.

3. The method according to claim 1, characterized in that, The acquisition of the first financial business data to be compared, stored in the host database, includes: Obtain the name of the target financial application to be tested, as well as the type of target financial business; Retrieve candidate financial business data from the log table of the host database, where the financial application name is the target financial application name and the financial business type is the target financial business type; Obtain the data modification time corresponding to each candidate financial business data, and take the candidate financial business data with the latest data modification time that has not been output to the test success list as the first financial business data to be compared.

4. The method according to claim 3, characterized in that, The acquisition of the second financial business data corresponding to the first financial business data stored in the platform database includes: Obtain the channel log number corresponding to the first financial business data from the log table of the host database; The financial business data stored in the log table of the platform database that has the same channel log number as the channel log number corresponding to the first financial business data is used as the second financial business data.

5. The method according to claim 3, characterized in that, The step of obtaining the data structure corresponding to the preset first field data includes: Based on the target financial application name and the target financial business type, query the data structure correspondence table; the data structure correspondence table stores the correspondence between each financial application name and each financial business type and multiple data structures; The data structure corresponding to the target financial application name and the target financial business type is obtained through the data structure correspondence table, and used as the data structure corresponding to the first field data.

6. The method according to claim 3, characterized in that, The method further includes: In response to an update operation on a data structure to be updated, the update operation is performed on the data structure to be updated; the update operation includes at least one of: changing the data length of a sub-field contained in the data structure to be updated, changing the data type of a sub-field contained in the data structure to be updated, deleting a sub-field contained in the data structure to be updated, and adding a sub-field contained in the data structure to be updated.

7. The method according to any one of claims 1 to 6, characterized in that, The step of comparing the decoding results corresponding to each of the first sub-field data with each of the second sub-field data, and outputting the first financial business data to the test list based on the comparison results, includes: Obtain the current decoding result, and the current second subfield data that is identical to the subfield of the current decoding result; the current decoding result is any one of the decoding results corresponding to the first subfield data. Compare the current decoding result with the current second subfield data; If the current decoding result is different from the current second subfield data, the first financial business data is output to the test failure list, and the current decoding result, the current second subfield data, and the subfields of the current decoding result are recorded in the test failure list. If each of the current decoding results is the same as each of the current second subfield data, the first financial business data is output to the test success list.

8. The method according to claim 7, characterized in that, The method further includes: If the platform database does not store the second financial business data corresponding to the first financial business data, the first financial business data will be output to the test failure list.

9. A financial system migration testing device, characterized in that, The device includes: The test data acquisition module is used to acquire the first financial business data to be compared stored in the host database, and to acquire the second financial business data corresponding to the first financial business data stored in the platform database; the host database is the database of the financial system to be migrated, and the platform database is the database of the financial system after the system migration. The field data acquisition module is used to determine first field data of a preset field from the first financial business data, and to determine second field data of the preset field from the second financial business data; the first field data is composed of first subfield data of multiple subfields, and the second field data is composed of second subfield data of the multiple subfields; The field data decoding module is used to obtain the data structure corresponding to the preset first field data, and to perform decoding processing on the first field data according to the data structure to obtain the decoding results corresponding to each first sub-field data respectively. The data structure includes: the data length of each first sub-field data and the data type of each first sub-field data. The field data decoding module is further configured to: obtain the hexadecimal code corresponding to the first field data, and determine the hexadecimal code corresponding to each first sub-field data from the hexadecimal code corresponding to the first field data according to the data length and data type of each first sub-field data; and perform decoding processing on the hexadecimal code corresponding to each first sub-field data according to the data type of each first sub-field data to obtain the decoding result corresponding to each first sub-field data respectively. The test result output module is used to compare the decoding results corresponding to each of the first sub-field data with each of the second sub-field data, output the first financial business data to the test list according to the comparison results, and use the test list as the financial system migration test result.

10. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 8.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 8.

12. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 8.

Images