CN117591426A - Bank transaction comparison method, device, equipment and readable storage medium - Google Patents
Bank transaction comparison method, device, equipment and readable storage medium Download PDFInfo
- Publication number
- CN117591426A CN117591426A CN202311645658.3A CN202311645658A CN117591426A CN 117591426 A CN117591426 A CN 117591426A CN 202311645658 A CN202311645658 A CN 202311645658A CN 117591426 A CN117591426 A CN 117591426A
- Authority
- CN
- China
- Prior art keywords
- transaction
- tested
- field
- message
- target
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 45
- 238000006243 chemical reaction Methods 0.000 claims abstract description 26
- 238000004519 manufacturing process Methods 0.000 claims abstract description 25
- 238000012360 testing method Methods 0.000 description 13
- 238000012545 processing Methods 0.000 description 7
- 230000008569 process Effects 0.000 description 5
- 230000009471 action Effects 0.000 description 3
- 238000000586 desensitisation Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 230000007547 defect Effects 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000012216 screening Methods 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 230000001133 acceleration Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000013508 migration Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3692—Test management for test results analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/02—Banking, e.g. interest calculation or account maintenance
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Business, Economics & Management (AREA)
- Physics & Mathematics (AREA)
- Accounting & Taxation (AREA)
- General Engineering & Computer Science (AREA)
- Quality & Reliability (AREA)
- Computer Hardware Design (AREA)
- Finance (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- Technology Law (AREA)
- General Business, Economics & Management (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application provides a bank transaction comparison method, a device, equipment and a readable storage medium, which are used for acquiring a transaction code to be tested corresponding to a transaction to be tested, determining a message to be converted from a host production log database by using the code, and performing format conversion to the message to be converted to obtain a target message; determining two fields to be compared by using the two messages respectively, and if the characteristic fields of the two messages are the same as the fields to be compared, sending the messages to be converted to a target host, and simultaneously sending the target messages to a target distributed system; acquiring first data to be compared and second data to be compared; respectively comparing the data to be compared with standard comparison data to determine a first comparison result and a second transaction comparison result; comparing the falling list of the transaction to be tested with a standard falling list corresponding to the transaction code to be tested in a transaction database, and determining a falling list comparison result of the transaction to be tested; and determining a comparison result of the transaction to be tested. And the bank transaction comparison efficiency is improved.
Description
Technical Field
The present application relates to the field of data processing technologies, and in particular, to a banking transaction comparison method, apparatus, device, and readable storage medium.
Background
At present, when banks conduct transaction comparison, staff is generally required to conduct comparison manually, when comparison is conducted manually, in order to verify the correctness of core transaction logic, test cases with a large number of manual writing are required to conduct verification, the flow is complex, the time consumption is long, the real input condition is difficult to truly restore, and the defects of test scenes and deviation from production input possibly exist.
Therefore, there is a need for a banking transaction comparison method that improves the banking transaction comparison efficiency.
Disclosure of Invention
In view of the foregoing, the present application provides a banking transaction comparison method, apparatus, device and readable storage medium for improving the banking transaction comparison efficiency.
In a first aspect, the present application provides a banking transaction comparison method, the method comprising:
acquiring a transaction code to be tested corresponding to the transaction to be tested;
determining a message to be converted from a host production log database by using the transaction code to be tested;
performing format conversion on the message to be converted to obtain a target message;
determining a first field to be compared from a database of the target host by using the message to be converted;
determining a second field to be compared from a database of the distributed system by using the target message;
if the characteristic field of the message to be converted is the same as the first field to be compared and the characteristic field of the target message is the same as the second field to be compared, sending the message to be converted to the target host, and simultaneously sending the target message to the target distributed system;
acquiring first data to be compared fed back by the target host and second data to be compared fed back by the target distributed system;
comparing the first data to be compared with the first standard comparison data to determine a first comparison result;
comparing the second data to be compared with second standard comparison data to determine a second transaction comparison result;
comparing the falling list of the to-be-tested transaction with a standard falling list corresponding to the to-be-tested transaction code in a transaction database, and determining a falling list comparison result of the to-be-tested transaction;
and determining the comparison result of the to-be-tested transaction by using the first comparison result, the second comparison result and the falling table comparison result of the to-be-tested transaction.
In one possible implementation manner, the determining, by using the transaction code to be tested, a message to be converted from a host production log database includes:
desensitizing a log to be processed in a host production log database to obtain a log to be screened;
and determining the message to be converted corresponding to the transaction code to be tested from the log to be screened by using the transaction code to be tested.
In one possible implementation manner, the performing format conversion on the message to be converted to obtain a target message includes:
and converting the format of the message to be converted into a JSON format by using a preset message conversion tool to obtain a target message.
In one possible implementation manner, the comparing the first data to be compared with the first standard comparison data to determine a first comparison result includes:
comparing the field of the first comparison data with the field of the first standard comparison data;
if the field of the first comparison data is the same as the field of the first standard comparison data, recording that the first comparison result is the same;
and if the field of the first comparison data is different from the field of the first standard comparison data, respectively recording the first comparison data and the first standard comparison data.
In one possible implementation manner, the comparing the second data to be compared with the second standard comparison data to determine a second transaction comparison result includes:
comparing the field of the second comparison data with the field of the second standard comparison data;
if the field of the second comparison data is the same as the field of the second standard comparison data, recording that the second comparison result is the same;
and if the field of the second comparison data is different from the field of the second standard comparison data, recording the second comparison data and the second standard comparison data respectively.
In one possible implementation, the table dropping includes: a target account number feature field and a target client number feature field, the standard drop table comprising: standard account number feature field and standard customer number feature field;
comparing the falling list of the to-be-tested transaction with a standard falling list corresponding to the to-be-tested transaction code in a transaction database, and determining a falling list comparison result of the to-be-tested transaction, wherein the method comprises the following steps:
comparing the target account characteristic field of the transaction to be tested with the standard account characteristic field;
if the target account number characteristic field and the standard account number characteristic field of the to-be-tested transaction are the same, comparing the target client number characteristic field and the standard client number characteristic field of the to-be-tested transaction;
if the target customer number characteristic field and the standard customer number characteristic field of the to-be-tested transaction are the same, the falling table of the to-be-tested transaction is the same as the standard falling table corresponding to the to-be-tested transaction code in the transaction database, and the comparison result of the falling table of the to-be-tested transaction is the same.
In a second aspect, the present application provides a banking transaction contrast device, the device comprising:
the first acquisition module is used for acquiring a transaction code to be tested corresponding to the transaction to be tested;
the first determining module is used for determining a message to be converted from a host production log database by utilizing the transaction code to be tested;
the conversion module is used for carrying out format conversion on the message to be converted to obtain a target message;
the second determining module is used for determining a first field to be compared from a database of the target host by utilizing the message to be converted;
a third determining module, configured to determine a second field to be compared from a database of the distributed system by using the target packet;
the sending module is configured to send the message to be converted to the target host, and send the target message to the target distributed system at the same time, if the feature field of the message to be converted is the same as the first field to be compared and the feature field of the target message is the same as the second field to be compared;
the second acquisition module is used for acquiring first data to be compared fed back by the target host and second data to be compared fed back by the target distributed system;
the fourth determining module is used for comparing the first data to be compared with the first standard comparison data to determine a first comparison result;
a fifth determining module, configured to compare the second data to be compared with second standard comparison data, and determine a second transaction comparison result;
the sixth determining module is used for comparing the falling list of the to-be-tested transaction with the standard falling list corresponding to the to-be-tested transaction code in the transaction database, and determining a falling list comparison result of the to-be-tested transaction;
and a seventh determining module, configured to determine a comparison result of the to-be-tested transaction by using the first comparison result, the second comparison result, and the falling table comparison result of the to-be-tested transaction.
In one possible implementation manner, the first determining module is specifically configured to:
desensitizing a log to be processed in a host production log database to obtain a log to be screened;
and determining the message to be converted corresponding to the transaction code to be tested from the log to be screened by using the transaction code to be tested.
In one possible implementation manner, the conversion module is specifically configured to:
and converting the format of the message to be converted into a JSON format by using a preset message conversion tool to obtain a target message.
In one possible implementation manner, the fourth determining module is specifically configured to:
comparing the field of the first comparison data with the field of the first standard comparison data;
if the field of the first comparison data is the same as the field of the first standard comparison data, recording that the first comparison result is the same;
and if the field of the first comparison data is different from the field of the first standard comparison data, respectively recording the first comparison data and the first standard comparison data.
In one possible implementation manner, the fifth determining module is specifically configured to:
comparing the field of the second comparison data with the field of the second standard comparison data;
if the field of the second comparison data is the same as the field of the second standard comparison data, recording that the second comparison result is the same;
and if the field of the second comparison data is different from the field of the second standard comparison data, recording the second comparison data and the second standard comparison data respectively.
In one possible implementation, the table dropping includes: a target account number feature field and a target client number feature field, the standard drop table comprising: standard account number feature field and standard customer number feature field; the sixth determining module is specifically configured to include: comparing the target account characteristic field of the transaction to be tested with the standard account characteristic field; if the target account number characteristic field and the standard account number characteristic field of the to-be-tested transaction are the same, comparing the target client number characteristic field and the standard client number characteristic field of the to-be-tested transaction; if the target customer number characteristic field and the standard customer number characteristic field of the to-be-tested transaction are the same, the falling table of the to-be-tested transaction is the same as the standard falling table corresponding to the to-be-tested transaction code in the transaction database, and the comparison result of the falling table of the to-be-tested transaction is the same.
In a third aspect, the present application provides a banking transaction comparison device, comprising: a memory and a processor;
the memory is used for storing one or more programs;
the processor is configured to implement the banking transaction comparison method according to the first aspect described above when the one or more programs are executed by the processor.
In a fourth aspect, the present application provides a computer readable storage medium storing instructions that, when executed on a device, cause the device to perform a banking transaction comparison method as described in the first aspect above.
From this, this application has following beneficial effect:
the application provides a bank transaction comparison method, a device, equipment and a readable storage medium, firstly, a transaction code to be tested corresponding to a transaction to be tested is obtained, and a message to be converted is determined from a host production log database by using the transaction code to be tested; performing format conversion on the message to be converted to obtain a target message; determining a first field to be compared from a database of the target host by using the message to be converted; determining a second field to be compared from a database of the distributed system by using the target message; if the characteristic field of the message to be converted is the same as the first field to be compared and the characteristic field of the target message is the same as the second field to be compared, sending the message to be converted to the target host, and simultaneously sending the target message to the target distributed system; acquiring first data to be compared fed back by the target host and second data to be compared fed back by the target distributed system; comparing the first data to be compared with the first standard comparison data to determine a first comparison result; comparing the second data to be compared with second standard comparison data to determine a second transaction comparison result; comparing the falling list of the to-be-tested transaction with a standard falling list corresponding to the to-be-tested transaction code in a transaction database, and determining a falling list comparison result of the to-be-tested transaction; and determining the comparison result of the to-be-tested transaction by using the first comparison result, the second comparison result and the falling table comparison result of the to-be-tested transaction. Therefore, in the application, the to-be-converted message is determined by using the to-be-tested transaction code, the to-be-converted message is converted into the target message, the to-be-compared fields corresponding to the to-be-converted message and the target message are respectively obtained by using the to-be-converted message and the target message, the to-be-compared fields are respectively sent to the target host computer and the target distributed system, the data fed back by the target host computer and the target distributed system are obtained, and finally, the comparison result of the to-be-tested transaction is determined by using the data fed back by the target host computer and the target distributed system and the falling table of the to-be-tested transaction. Therefore, when the transaction comparison is carried out, the comparison result is determined by utilizing the target host, the target distributed system and the falling table, and the bank transaction comparison efficiency is improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only embodiments of the present invention, and that other drawings can be obtained according to the provided drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of a method for comparing banking transactions according to an embodiment of the present disclosure;
fig. 2 is a schematic device structure diagram of a banking transaction comparing device according to an embodiment of the present application.
Detailed Description
In order to facilitate understanding and explanation of the technical solutions provided in the embodiments of the present application, the terms that may be related to the embodiments of the present application and the background art of the present application will be described below:
log playback: the method is that a real transaction log in a production system is obtained, after desensitization treatment, the real transaction log is imported into the system in a test environment, and the system performs playback execution again according to the messages in the log.
Distributed core system: the system refers to a business core processing system based on a distributed architecture, such as bank deposit, loan and the like, and generally uses a distributed database.
Transaction comparison test: and comparing the transaction processing results of the source system and the target system.
With the acceleration of banking digital transformation, distributed architecture matures, and more commercial banks begin to migrate the existing host core system to the distributed architecture to build the distributed core system. In this context, in order to ensure the correctness of the post-migration transaction logic, the scenario of core system transaction contrast testing is more and more frequent. Traditional manual comparison test is low in efficiency, complex in flow, long in time and single in comparison scene.
Further, with the wide applicability of distributed architecture, banking industry gradually upgrades core systems in order to meet better system expansion and performance requirements. The main content is to upgrade the original host architecture into a distributed architecture and to migrate the original host transaction program to the distributed architecture. The comparison test has good application in the construction of the distributed core system, and the correctness of the transaction processing of the distributed core system can be rapidly verified through the comparison of the processing results of the transaction of the distributed core system (distributed system) and the original host system. In addition, in order to ensure the feasibility of the comparison result, the real production scene and transaction message input are replayed through log replay, so that the function of the distributed core system transaction is verified more rapidly and accurately.
However, at present, the comparison test is manually performed on the distributed core system, and firstly, the process is tedious and the time is long. The manual test firstly prepares the messages of the two systems of the source host system and the target distributed core system, and simultaneously, after the transaction is sent to the two systems, the result returned by the transaction is checked manually, and the processing result of the transaction is checked in the source host and the target distributed core system, so that the whole flow is complex, and the operation time is long. Secondly, when the logic branches of one transaction are more, in order to verify the correctness of the distributed core transaction logic, a large number of test cases are required to be manually written for verification, the actual input condition is difficult to truly restore, and the defects of the test scene and the deviation from the production input possibly exist. Therefore, there is a need for a banking transaction comparison method that improves the banking transaction comparison efficiency.
The inventive concept of the present application is specifically as follows: according to the method, an automatic method is adopted to replace manual comparison, log playback is used to compare transaction return messages between a host core system and a distributed core system and database table falling conditions, and automation of comparison test and diversification of comparison scenes are achieved. Meanwhile, the functions of message conversion, comparison field setting and the like provided by the application have excellent applicability, and can be suitable for systems and transaction conditions with various input formats.
Specifically, the application provides a bank transaction comparison method, a device, equipment and a readable storage medium, firstly, a transaction code to be tested corresponding to a transaction to be tested is obtained, and a message to be converted is determined from a host production log database by using the transaction code to be tested; performing format conversion on the message to be converted to obtain a target message; determining a first field to be compared from a database of the target host by using the message to be converted; determining a second field to be compared from a database of the distributed system by using the target message; if the characteristic field of the message to be converted is the same as the first field to be compared and the characteristic field of the target message is the same as the second field to be compared, sending the message to be converted to the target host, and simultaneously sending the target message to the target distributed system; acquiring first data to be compared fed back by the target host and second data to be compared fed back by the target distributed system; comparing the first data to be compared with the first standard comparison data to determine a first comparison result; comparing the second data to be compared with second standard comparison data to determine a second transaction comparison result; comparing the falling list of the to-be-tested transaction with a standard falling list corresponding to the to-be-tested transaction code in a transaction database, and determining a falling list comparison result of the to-be-tested transaction; and determining the comparison result of the to-be-tested transaction by using the first comparison result, the second comparison result and the falling table comparison result of the to-be-tested transaction. Therefore, in the application, the to-be-converted message is determined by using the to-be-tested transaction code, the to-be-converted message is converted into the target message, the to-be-compared fields corresponding to the to-be-converted message and the target message are respectively obtained by using the to-be-converted message and the target message, the to-be-compared fields are respectively sent to the target host computer and the target distributed system, the data fed back by the target host computer and the target distributed system are obtained, and finally, the comparison result of the to-be-tested transaction is determined by using the data fed back by the target host computer and the target distributed system and the falling table of the to-be-tested transaction. Therefore, when the transaction comparison is carried out, the comparison result is determined by utilizing the target host, the target distributed system and the falling table, and the bank transaction comparison efficiency is improved.
In order to facilitate understanding of the technical solutions provided by the embodiments of the present application, a method and an apparatus for checking prize data provided by the embodiments of the present application are described below with reference to the accompanying drawings.
First, referring to fig. 1, a method flow diagram of a prize data checking method according to an embodiment of the present application is shown, where the method specifically includes S101-S111.
It can be understood that the configuration of parameters needs to be performed in advance, specifically, the host database address and the distributed database address, the database user, the database password, the source host and the target distributed system test address, the host and the distributed system transaction interface document are input, and the corresponding relation between the host and the distributed database table structure and the field is input.
S101: and acquiring a transaction code to be tested corresponding to the transaction to be tested.
In this embodiment, the transaction code to be tested may be obtained from a database of transaction codes to be tested, or the transaction code to be tested may be determined from the transaction data sent by the client, where the specific obtaining mode of the transaction code to be tested is not limited.
S102: and determining the message to be converted from a host production log database by using the transaction code to be tested.
Transaction log screening is required in this embodiment: the method comprises the steps of obtaining a host production log from a production log database, performing desensitization treatment, obtaining a host transaction message with input from the general log according to a transaction code to be tested, and screening a plurality of messages of the transaction at one time. Specifically, determining a host production log from a production log database, wherein the host production log is a log to be processed, and performing desensitization processing on the log to be processed in the host production log database to obtain a log to be screened; and determining the message to be converted corresponding to the transaction code to be tested from the log to be screened by using the transaction code to be tested.
S103: and carrying out format conversion on the message to be converted to obtain a target message.
In this embodiment, a preset message conversion tool is used to convert the format of the message to be converted into JSON format, so as to obtain the target message.
It can be understood that the message to be converted is a host message, and the host message is generally in a NETE format, and according to the description of the host and the interface document of the distributed system, the message in the NETE format is converted into a JSON format suitable for the distributed system in the message conversion tool.
S104: and determining a first field to be compared from a database of the target host by using the message to be converted.
The field to be compared can be determined from the database of the target host by using the message, and the field to be compared is a field corresponding to the pre-configured field and the message to be converted. The corresponding relation between the fields to be compared and the conversion message can be determined through a preset relation table.
S105: and determining a second field to be compared from the database of the distributed system by utilizing the target message.
The field to be compared can be determined from a database of the distributed system by utilizing the target message, and the field to be compared is a field which is configured in advance and corresponds to the target message. The corresponding relation between the field to be compared and the target message can be determined through a preset relation table.
S106: and if the characteristic field of the message to be converted is the same as the first field to be compared, and the characteristic field of the target message is the same as the second field to be compared, sending the message to be converted to the target host, and simultaneously sending the target message to the target distributed system.
It can be understood that if the feature field of the message to be converted is the same as the first field to be compared, and the feature field of the target message is the same as the second field to be compared, the message to be converted is sent to the target host, and the target message is sent to the target distributed system.
Furthermore, the message in the host NETE format can be sent to the host from small to large according to the time sequence of each record in the log, and meanwhile, the distributed system JSON message is used for sending to the distributed system.
S107: and acquiring the first data to be compared fed back by the target host and the second data to be compared fed back by the target distributed system.
And sending the message to be converted to the target host, and simultaneously recording transaction return results of the two systems after sending the target message to the target distributed system, namely recording data to be compared fed back by the target host and data to be compared fed back by the target distributed system. Thus, the data to be compared fed back by the target host and the data to be compared fed back by the target distributed system can be obtained.
S108: and comparing the first data to be compared with the first standard comparison data to determine a first comparison result.
And returning a field (a field of data to be compared fed back by the target host), comparing the returned results of the transaction (the field to be compared determined by the transaction code to be tested corresponding to the transaction to be tested), if the returned results are consistent, recording the consistency in the message comparison results on the playback record, and if the returned results are inconsistent, recording the returned results of the two systems respectively. Specifically, in this embodiment, the field of the first comparison data may be compared with the field of the first standard comparison data; if the field of the first comparison data is the same as the field of the first standard comparison data, recording that the first comparison result is the same; and if the field of the first comparison data is different from the field of the first standard comparison data, respectively recording the first comparison data and the first standard comparison data.
S109: and comparing the second data to be compared with the second standard comparison data to determine a second transaction comparison result.
In this embodiment, the field of the second comparison data may be compared with the field of the second standard comparison data; if the field of the second comparison data is the same as the field of the second standard comparison data, recording that the second comparison result is the same; and if the field of the second comparison data is different from the field of the second standard comparison data, recording the second comparison data and the second standard comparison data respectively.
S110: and comparing the falling list of the to-be-tested transaction with the standard falling list corresponding to the to-be-tested transaction code in the transaction database, and determining the falling list comparison result of the to-be-tested transaction.
The falling table comprises: a target account number feature field and a target client number feature field, the standard drop table comprising: standard account number feature field and standard customer number feature field;
comparing the falling list of the to-be-tested transaction with a standard falling list corresponding to the to-be-tested transaction code in a transaction database, and determining a falling list comparison result of the to-be-tested transaction, wherein the falling list comparison result specifically comprises:
comparing the target account characteristic field of the transaction to be tested with the standard account characteristic field; if the target account number characteristic field and the standard account number characteristic field of the to-be-tested transaction are the same, comparing the target client number characteristic field and the standard client number characteristic field of the to-be-tested transaction; if the target customer number characteristic field and the standard customer number characteristic field of the to-be-tested transaction are the same, the falling table of the to-be-tested transaction is the same as the standard falling table corresponding to the to-be-tested transaction code in the transaction database, and the comparison result of the falling table of the to-be-tested transaction is the same. At this time, it may also be recorded that the target account number feature field and the standard account number feature field of the transaction to be tested are the same, and that the target account number feature field and the standard account number feature field of the transaction to be tested are the same.
It should be noted that, when comparing the target account number characteristic field and the standard account number characteristic field of the to-be-tested transaction, if the target account number characteristic field and the standard account number characteristic field of the to-be-tested transaction are different, the target account number characteristic field and the standard account number characteristic field of the to-be-tested transaction are recorded respectively.
When the target client number characteristic field and the standard client number characteristic field of the to-be-tested transaction are compared, if the target client number characteristic field and the standard client number characteristic field of the to-be-tested transaction are different, the target account number characteristic field and the standard account number characteristic field of the to-be-tested transaction are respectively recorded.
It should be noted that, the comparison process may also be to compare the target customer number feature field of the transaction to be tested with the standard customer number feature field; if the target client number characteristic field and the standard client number characteristic field of the to-be-tested transaction are the same, comparing the target account number characteristic field and the standard account number characteristic field of the to-be-tested transaction; if the target account number characteristic field and the standard account number characteristic field of the to-be-tested transaction are the same, the falling table of the to-be-tested transaction is the same as the standard falling table corresponding to the to-be-tested transaction code in the transaction database, and the falling table comparison result of the to-be-tested transaction is recorded to be the same.
S111: and determining the comparison result of the to-be-tested transaction by using the first comparison result, the second comparison result and the falling table comparison result of the to-be-tested transaction.
It can be understood that if the recorded first comparison result is the same, the recorded second comparison result is the same, and the recorded falling table comparison result of the to-be-tested transaction is the same, it can be determined that the comparison result of the to-be-tested transaction is the same.
Based on the related content of S101-S111, in the present application, the to-be-converted message is determined by using the to-be-tested transaction code, and is converted into the target message, then the to-be-converted message and the target message are respectively used to obtain the to-be-compared fields corresponding to the to-be-converted message and the target message, and then the to-be-compared fields are respectively sent to the target host and the target distributed system to obtain the data fed back by the target host and the target distributed system, and finally the comparison result of the to-be-tested transaction is determined by using the data fed back by the target host and the target distributed system and the falling table of the to-be-tested transaction. Therefore, when the transaction comparison is carried out, the comparison result is determined by utilizing the target host, the target distributed system and the falling table, and the bank transaction comparison efficiency is improved.
Corresponding to the method described in fig. 1, the embodiment of the present application further provides a prize bank transaction comparing device, which is used for implementing the method in fig. 1, and the bank transaction comparing device provided in the embodiment of the present application may be applied to a computer terminal or various mobile devices, and the structural schematic diagram of the device is shown in fig. 2, where the prize bank transaction comparing device specifically includes:
it will be appreciated that in a second aspect, the present application provides a banking transaction contrast device, the device comprising:
a first obtaining module 201, configured to obtain a transaction code to be tested corresponding to a transaction to be tested;
202 a first determining module, configured to determine, by using the transaction code to be tested, a message to be converted from a host production log database;
203 a conversion module, configured to perform format conversion on the message to be converted to obtain a target message;
a second determining module, configured to determine a first field to be compared from a database of the target host by using the message to be converted;
205 a third determining module, configured to determine a second field to be compared from a database of the distributed system by using the target packet;
206 a sending module, configured to send the message to be converted to the target host, and send the target message to the target distributed system at the same time, if the feature field of the message to be converted is the same as the first field to be compared and the feature field of the target message is the same as the second field to be compared;
207 a second obtaining module, configured to obtain first data to be compared fed back by the target host and second data to be compared fed back by the target distributed system;
208 a fourth determining module, configured to compare the first data to be compared with the first standard comparison data, and determine a first comparison result;
209 a fifth determining module, configured to compare the second data to be compared with second standard comparison data, and determine a second transaction comparison result;
210 a sixth determining module, configured to compare the falling table of the to-be-tested transaction with a standard falling table corresponding to the to-be-tested transaction code in a transaction database, and determine a falling table comparison result of the to-be-tested transaction;
and 211 a seventh determining module, configured to determine a comparison result of the to-be-tested transaction by using the first comparison result, the second comparison result, and the falling table comparison result of the to-be-tested transaction.
In one possible implementation manner, the first determining module 202 is specifically configured to:
desensitizing a log to be processed in a host production log database to obtain a log to be screened;
and determining the message to be converted corresponding to the transaction code to be tested from the log to be screened by using the transaction code to be tested.
In one possible implementation manner, the conversion module 203 is specifically configured to:
and converting the format of the message to be converted into a JSON format by using a preset message conversion tool to obtain a target message.
In one possible implementation manner, the fourth determining module 208 is specifically configured to:
comparing the field of the first comparison data with the field of the first standard comparison data;
if the field of the first comparison data is the same as the field of the first standard comparison data, recording that the first comparison result is the same;
and if the field of the first comparison data is different from the field of the first standard comparison data, respectively recording the first comparison data and the first standard comparison data.
In one possible implementation manner, the fifth determining module 209 is specifically configured to:
comparing the field of the second comparison data with the field of the second standard comparison data;
if the field of the second comparison data is the same as the field of the second standard comparison data, recording that the second comparison result is the same;
and if the field of the second comparison data is different from the field of the second standard comparison data, recording the second comparison data and the second standard comparison data respectively.
In one possible implementation, the table dropping includes: a target account number feature field and a target client number feature field, the standard drop table comprising: standard account number feature field and standard customer number feature field;
the sixth determining module 210 is specifically configured to include:
comparing the target account characteristic field of the transaction to be tested with the standard account characteristic field; if the target account number characteristic field and the standard account number characteristic field of the to-be-tested transaction are the same, comparing the target client number characteristic field and the standard client number characteristic field of the to-be-tested transaction; if the target customer number characteristic field and the standard customer number characteristic field of the to-be-tested transaction are the same, the falling table of the to-be-tested transaction is the same as the standard falling table corresponding to the to-be-tested transaction code in the transaction database, and the comparison result of the falling table of the to-be-tested transaction is the same.
In a third aspect, the present application provides a banking transaction comparison device, comprising: a memory and a processor;
the memory is used for storing one or more programs;
the processor is configured to implement a banking transaction comparison method according to any one of the above embodiments when the one or more programs are executed by the processor.
In a fourth aspect, the present application provides a computer readable storage medium storing instructions that, when executed on a device, cause the device to perform a banking transaction comparison method as described in any of the embodiments above.
It is further noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended 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 (10)
1. A method for comparing banking transactions, the method comprising:
acquiring a transaction code to be tested corresponding to the transaction to be tested;
determining a message to be converted from a host production log database by using the transaction code to be tested;
performing format conversion on the message to be converted to obtain a target message;
determining a first field to be compared from a database of the target host by using the message to be converted;
determining a second field to be compared from a database of the distributed system by using the target message;
if the characteristic field of the message to be converted is the same as the first field to be compared and the characteristic field of the target message is the same as the second field to be compared, sending the message to be converted to the target host, and simultaneously sending the target message to the target distributed system;
acquiring first data to be compared fed back by the target host and second data to be compared fed back by the target distributed system;
comparing the first data to be compared with the first standard comparison data to determine a first comparison result;
comparing the second data to be compared with second standard comparison data to determine a second transaction comparison result;
comparing the falling list of the to-be-tested transaction with a standard falling list corresponding to the to-be-tested transaction code in a transaction database, and determining a falling list comparison result of the to-be-tested transaction;
and determining the comparison result of the to-be-tested transaction by using the first comparison result, the second comparison result and the falling table comparison result of the to-be-tested transaction.
2. The method of claim 1, wherein determining the message to be converted from the host production log database using the transaction code to be tested comprises:
desensitizing a log to be processed in a host production log database to obtain a log to be screened;
and determining the message to be converted corresponding to the transaction code to be tested from the log to be screened by using the transaction code to be tested.
3. The method of claim 1, wherein the performing format conversion on the message to be converted to obtain a target message includes:
and converting the format of the message to be converted into a JSON format by using a preset message conversion tool to obtain a target message.
4. The method of claim 1, wherein comparing the first data to be compared with first standard comparison data to determine a first comparison result comprises:
comparing the field of the first comparison data with the field of the first standard comparison data;
if the field of the first comparison data is the same as the field of the first standard comparison data, recording that the first comparison result is the same;
and if the field of the first comparison data is different from the field of the first standard comparison data, respectively recording the first comparison data and the first standard comparison data.
5. The method of claim 1, wherein comparing the second data to be compared with second standard comparison data to determine a second transaction comparison result comprises:
comparing the field of the second comparison data with the field of the second standard comparison data;
if the field of the second comparison data is the same as the field of the second standard comparison data, recording that the second comparison result is the same;
and if the field of the second comparison data is different from the field of the second standard comparison data, recording the second comparison data and the second standard comparison data respectively.
6. The method of claim 1, wherein the dropping the table comprises: a target account number feature field and a target client number feature field, the standard drop table comprising: standard account number feature field and standard customer number feature field;
comparing the falling list of the to-be-tested transaction with a standard falling list corresponding to the to-be-tested transaction code in a transaction database, and determining a falling list comparison result of the to-be-tested transaction, wherein the method comprises the following steps:
comparing the target account characteristic field of the transaction to be tested with the standard account characteristic field;
if the target account number characteristic field and the standard account number characteristic field of the to-be-tested transaction are the same, comparing the target client number characteristic field and the standard client number characteristic field of the to-be-tested transaction;
if the target customer number characteristic field and the standard customer number characteristic field of the to-be-tested transaction are the same, the falling table of the to-be-tested transaction is the same as the standard falling table corresponding to the to-be-tested transaction code in the transaction database, and the comparison result of the falling table of the to-be-tested transaction is the same.
7. A banking transaction contrast device, the device comprising:
the first acquisition module is used for acquiring a transaction code to be tested corresponding to the transaction to be tested;
the first determining module is used for determining a message to be converted from a host production log database by utilizing the transaction code to be tested;
the conversion module is used for carrying out format conversion on the message to be converted to obtain a target message;
the second determining module is used for determining a first field to be compared from a database of the target host by utilizing the message to be converted;
a third determining module, configured to determine a second field to be compared from a database of the distributed system by using the target packet;
the sending module is configured to send the message to be converted to the target host, and send the target message to the target distributed system at the same time, if the feature field of the message to be converted is the same as the first field to be compared and the feature field of the target message is the same as the second field to be compared;
the second acquisition module is used for acquiring first data to be compared fed back by the target host and second data to be compared fed back by the target distributed system;
the fourth determining module is used for comparing the first data to be compared with the first standard comparison data to determine a first comparison result;
a fifth determining module, configured to compare the second data to be compared with second standard comparison data, and determine a second transaction comparison result;
the sixth determining module is used for comparing the falling list of the to-be-tested transaction with the standard falling list corresponding to the to-be-tested transaction code in the transaction database, and determining a falling list comparison result of the to-be-tested transaction;
and a seventh determining module, configured to determine a comparison result of the to-be-tested transaction by using the first comparison result, the second comparison result, and the falling table comparison result of the to-be-tested transaction.
8. The apparatus of claim 6, wherein the conversion module is specifically configured to:
and converting the format of the message to be converted into a JSON format by using a preset message conversion tool to obtain a target message.
9. A banking transaction contrast device, comprising: a memory and a processor;
the memory is used for storing one or more programs;
the processor being configured to implement the method of any of claims 1-6 when the one or more programs are executed by the processor.
10. A computer readable storage medium storing instructions which, when run on a device, cause the device to perform the method of any one of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311645658.3A CN117591426A (en) | 2023-12-04 | 2023-12-04 | Bank transaction comparison method, device, equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311645658.3A CN117591426A (en) | 2023-12-04 | 2023-12-04 | Bank transaction comparison method, device, equipment and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117591426A true CN117591426A (en) | 2024-02-23 |
Family
ID=89916519
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311645658.3A Pending CN117591426A (en) | 2023-12-04 | 2023-12-04 | Bank transaction comparison method, device, equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117591426A (en) |
-
2023
- 2023-12-04 CN CN202311645658.3A patent/CN117591426A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107122296B (en) | Method and apparatus for data assertion for test interface | |
| CN108763076A (en) | A kind of Software Automatic Testing Method, device, equipment and medium | |
| CN113110995B (en) | System migration testing method and device | |
| CN114880240B (en) | Automatic test system and method for equipment of Internet of things, storage medium and equipment | |
| CN112488652A (en) | Work order auditing method, system, terminal and storage medium | |
| WO2021169280A1 (en) | Virtual disk check code generation method, apparatus and device, and storage medium | |
| CN112905262A (en) | Configuration method and device of aerospace measurement and control system | |
| CN115757150A (en) | Production environment testing method, device, equipment and storage medium | |
| CN101510172B (en) | Test system and method | |
| CN112631920A (en) | Test method, test device, electronic equipment and readable storage medium | |
| CN117707946A (en) | Test script generation method and device for browser | |
| CN111159003B (en) | Batch processing test method and device | |
| CN111949537A (en) | Interface test method, device, equipment and medium | |
| CN117591426A (en) | Bank transaction comparison method, device, equipment and readable storage medium | |
| CN113238940B (en) | Interface test result comparison method, device, equipment and storage medium | |
| CN112307029B (en) | Bill data storage and bill generation methods, devices, server and storage medium | |
| CN115080401A (en) | Automatic testing method and related device | |
| CN113760696A (en) | Program problem positioning method and device, electronic equipment and storage medium | |
| CN115701591A (en) | Business process testing method, device, medium and electronic equipment | |
| CN114048123A (en) | Method and device for auditing terminal authentication report | |
| CN111625458A (en) | Service system testing method, device and equipment | |
| CN118261143B (en) | Json data analysis method, device, equipment and medium in Unity environment | |
| CN112307131B (en) | Equipment inspection method, system, electronic equipment and storage medium | |
| CN117130946B (en) | Test scene generation method and device, electronic equipment and readable storage medium | |
| CN116795723B (en) | Chain unit test processing method and device and computer equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |