CN115562983A - Transaction analysis method and device, electronic equipment and computer storage medium - Google Patents

Transaction analysis method and device, electronic equipment and computer storage medium Download PDF

Info

Publication number
CN115562983A
CN115562983A CN202211199120.XA CN202211199120A CN115562983A CN 115562983 A CN115562983 A CN 115562983A CN 202211199120 A CN202211199120 A CN 202211199120A CN 115562983 A CN115562983 A CN 115562983A
Authority
CN
China
Prior art keywords
transaction
target system
data
analysis result
sequence
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
Application number
CN202211199120.XA
Other languages
Chinese (zh)
Inventor
付承宏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Bank of China Ltd
Original Assignee
Bank of China Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Bank of China Ltd filed Critical Bank of China Ltd
Priority to CN202211199120.XA priority Critical patent/CN115562983A/en
Publication of CN115562983A publication Critical patent/CN115562983A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • G06F11/3696Methods or tools to render software testable
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/02Banking, e.g. interest calculation or account maintenance
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • Finance (AREA)
  • Accounting & Taxation (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Computer Hardware Design (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 discloses a transaction analysis method, a transaction analysis device, electronic equipment and a computer storage medium, which can be applied to the field of big data or the field of finance. The method comprises the steps of obtaining transaction data corresponding to a transaction to be tested; according to the sequence of the transaction codes in the transaction code list, transaction simulation tests are sequentially carried out on the target system, so that the target system can feed back corresponding transaction execution results; analyzing each transaction execution result to obtain an analysis result; for each analysis result, if the analysis result indicates that the transaction can be normally executed, determining that the transaction data of the transaction is not changed; and if the analysis result indicates that the transaction cannot be normally executed, generating and displaying information that the transaction data corresponding to the transaction has change so as to facilitate maintenance of technical personnel. The invention can quickly initiate a large amount of transactions and analyze the return message when a target system needs a large amount of tests, thereby determining whether the transaction test is normal.

Description

Transaction analysis method and device, electronic equipment and computer storage medium
Technical Field
The present invention relates to the field of transaction processing technologies, and in particular, to a transaction analysis method and apparatus, an electronic device, and a computer storage medium.
Background
In the process of adjusting the bank system, for example, modifying atomic transactions with more calls, replacing a framework, replacing a database, or modifying or updating a function point may affect corresponding transaction data, so that the transaction needs to be tested.
At present, simulation test is often performed on transactions in a manual manner to determine whether there is a change in transaction data, and when the range of affected transactions is quite large, the time required for simulation test in a manual manner is too long, and omission and errors are easily caused.
Disclosure of Invention
In view of this, embodiments of the present invention provide a transaction analysis method, a transaction analysis device, an electronic device, and a computer storage medium, so as to solve the problems in the prior art that a simulation test requires a long time and is prone to omission and errors.
In order to achieve the above purpose, the embodiments of the present invention provide the following technical solutions:
a first aspect of an embodiment of the present invention shows a transaction analysis method, including:
acquiring and storing transaction data corresponding to a transaction to be tested according to the modification requirement of the target system;
sorting transaction codes corresponding to the transaction data to obtain a transaction code list sorted according to a transaction sequence;
according to the sequence of the transaction codes in the transaction code list, transaction simulation testing is carried out on the target system in sequence, so that the target system can feed back a corresponding transaction execution result;
analyzing each transaction execution result to obtain an analysis result;
for each analysis result, if the analysis result indicates that the transaction can be normally executed, determining that the transaction data of the transaction is not changed;
and if the analysis result indicates that the transaction cannot be normally executed, generating and displaying information that the transaction data corresponding to the transaction has change so as to facilitate maintenance of technical personnel.
Optionally, the method further includes:
for each analysis result, judging whether the analysis result indicates that the transaction can be normally executed;
if the analysis result indicates that the transaction can be normally executed, determining that the transaction data of the transaction is not changed;
and if the analysis result indicates that the transaction cannot be normally executed, generating and displaying information that the transaction data corresponding to the transaction has change so as to facilitate maintenance of technical personnel.
Optionally, the performing transaction simulation tests on the target system sequentially according to the sequence of the transaction codes in the transaction code list includes:
if the transaction to be tested does not need to be bottomed, determining a corresponding message type based on each transaction code in the transaction code list;
assembling the message type and transaction data corresponding to each transaction code to generate a corresponding transaction message;
and sending transaction messages to the target system in sequence according to the sequence of the transaction codes in the transaction code list so that the target system can feed back corresponding transaction execution results.
Optionally, the performing transaction simulation tests on the target system in sequence according to the sequence of the transaction codes in the transaction code list includes:
if the transaction needing bottoming exists in the transaction to be tested, bottoming data needing bottoming is determined based on the transaction data of the transaction needing bottoming;
determining a corresponding message type based on each transaction code in the transaction code list;
assembling the transaction data of the transaction needing bottoming, bottoming data and the message type corresponding to the transaction code of the transaction to generate a corresponding transaction message;
assembling the transaction data of other transactions and the message types corresponding to the transaction codes of the transactions to generate corresponding transaction messages, wherein the other transactions are the remaining transactions to be tested except the transactions needing to be bottomed;
and sending transaction messages to the target system in sequence according to the sequence of the transaction codes in the transaction code list so that the target system can feed back corresponding transaction execution results.
Optionally, the determining whether the analysis result indicates that the transaction can be normally executed includes:
judging whether the analysis result meets a preset result corresponding to the message type of the transaction message or not for each transaction;
if yes, determining that the transaction data of the transaction is not changed;
and if the transaction data does not conform to the transaction data, generating and displaying information that the transaction data corresponding to the transaction has change so as to facilitate maintenance of technical personnel.
A second aspect of an embodiment of the present invention shows a transaction analysis apparatus, including:
the acquisition unit is used for acquiring and storing transaction data corresponding to a transaction to be tested according to the modification requirement of the target system;
the sorting unit is used for sorting the transaction codes corresponding to the transaction data to obtain a transaction code list sorted according to a transaction sequence;
the test unit is used for sequentially carrying out transaction simulation test on the target system according to the sequence of the transaction codes in the transaction code list so as to facilitate the target system to feed back a corresponding transaction execution result;
the analysis unit is used for analyzing each transaction execution result to obtain an analysis result;
the processing unit is used for determining that the transaction data of the transaction is not changed if the analysis result indicates that the transaction can be normally executed according to each analysis result; and if the analysis result indicates that the transaction cannot be normally executed, generating and displaying information that the transaction data corresponding to the transaction has changes so that a technician can maintain the information conveniently.
Optionally, the test unit is specifically configured to:
if the transaction to be tested does not need to be bottomed, determining a corresponding message type based on each transaction code in the transaction code list;
assembling the message type and the transaction data corresponding to each transaction code to generate a corresponding transaction message;
and sending transaction messages to the target system in sequence according to the sequence of the transaction codes in the transaction code list so that the target system can feed back corresponding transaction execution results.
Optionally, the test unit is specifically configured to:
if the transaction needing bottoming exists in the transaction to be tested, bottoming data needing bottoming is determined based on the transaction data of the transaction needing bottoming;
determining a corresponding message type based on each transaction code in the transaction code list;
assembling the transaction data of the transaction needing bottoming, the bottoming data and the message type corresponding to the transaction code of the transaction to generate a corresponding transaction message;
assembling the transaction data of other transactions and the message types corresponding to the transaction codes of the transactions to generate corresponding transaction messages, wherein the other transactions are the remaining transactions to be tested except the transactions needing to be bottomed;
and sending transaction messages to the target system in sequence according to the sequence of the transaction codes in the transaction code list so that the target system can feed back corresponding transaction execution results.
A third aspect of the embodiments of the present invention shows an electronic device, where the electronic device is configured to run a program, where the program is executed to perform the transaction analysis method shown in the first aspect of the embodiments of the present invention.
An embodiment of the present invention shows a fourth aspect, which shows a computer storage medium, where the storage medium includes a storage program, and when the program runs, the storage medium is controlled to execute a transaction analysis method according to the first aspect of the embodiment of the present invention.
Based on the transaction analysis method, the transaction analysis device, the electronic device and the computer storage medium provided by the embodiment of the invention, the method comprises the following steps: acquiring and storing transaction data corresponding to a transaction to be tested according to the modification requirement of the target system; sorting the transaction codes corresponding to the transaction data to obtain a transaction code list sorted according to a transaction sequence; according to the sequence of the transaction codes in the transaction code list, transaction simulation testing is carried out on the target system in sequence, so that the target system can feed back a corresponding transaction execution result; analyzing each transaction execution result to obtain an analysis result; for each analysis result, if the analysis result indicates that the transaction can be normally executed, determining that the transaction data of the transaction is not changed; and if the analysis result indicates that the transaction cannot be normally executed, generating and displaying information that the transaction data corresponding to the transaction has change so as to facilitate maintenance of technical personnel. The invention can quickly initiate a large amount of transactions and analyze the return message when a target system needs a large amount of tests, thereby determining whether the transaction test is normal. By means of the method, the testing efficiency can be improved, and the situations of omission and error can be avoided.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the prior art descriptions will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is an interaction diagram of a server and a target system according to an embodiment of the present invention;
FIG. 2 is a flow chart illustrating a transaction analysis method according to an embodiment of the present invention;
FIG. 3 is a schematic flow chart diagram illustrating another transaction analysis method according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of a transaction analysis device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In this application, 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 phrases "comprising a," "8230," "8230," or "comprising" does not exclude the presence of additional like elements in a process, method, article, or apparatus that comprises the element.
It should be noted that the transaction analysis method, the transaction analysis device, the electronic device and the computer storage medium provided by the invention can be used in the field of big data or the field of finance. The above is only an example, and does not limit the application field of the transaction analysis method provided by the present invention.
Referring to fig. 1, a schematic diagram of interaction between a server and a target system according to an embodiment of the present invention is shown.
The server 10 is connected with the target system 20.
The server 10 is a system server for transaction analysis.
The process for specifically realizing transaction analysis based on the schematic diagram comprises the following steps:
the server 10 acquires and stores transaction data corresponding to a transaction to be tested according to the modification requirement of the target system 20; sorting the transaction codes corresponding to the transaction data to obtain a transaction code list sorted according to a transaction sequence; according to the sequence of the transaction codes in the transaction code list, transaction simulation testing is carried out on the target system in sequence, so that the target system can feed back a corresponding transaction execution result; analyzing each transaction execution result to obtain an analysis result; for each analysis result, if the analysis result indicates that the transaction can be normally executed, determining that the transaction data of the transaction is not changed; and if the analysis result indicates that the transaction cannot be normally executed, generating and displaying information that the transaction data corresponding to the transaction has changes so that a technician can maintain the information conveniently.
In the embodiment of the invention, the transaction data corresponding to the transaction to be tested is acquired and stored according to the modification requirement of the target system; sorting the transaction codes corresponding to the transaction data to obtain a transaction code list sorted according to a transaction sequence; according to the sequence of the transaction codes in the transaction code list, transaction simulation testing is carried out on the target system in sequence, so that the target system can feed back a corresponding transaction execution result; analyzing each transaction execution result to obtain an analysis result; for each analysis result, if the analysis result indicates that the transaction can be normally executed, determining that the transaction data of the transaction is not changed; and if the analysis result indicates that the transaction cannot be normally executed, generating and displaying information that the transaction data corresponding to the transaction has change so as to facilitate maintenance of technical personnel. The invention can quickly initiate a large amount of transactions and analyze the return message when a target system needs a large amount of tests, thereby determining whether the transaction test is normal. By means of the method, the testing efficiency can be improved, and the situations of omission and error can be avoided.
Referring to fig. 2, a schematic flow chart of a transaction analysis method according to an embodiment of the present invention is shown, where the method includes:
step S201: and acquiring and storing transaction data corresponding to the transaction to be tested according to the modification requirement of the target system.
Alternatively, the transactions in the target system, i.e. the banking system, need to be classified according to the transaction type. The method can be divided into all payment type transactions, all over-the-counter channel transactions, all social security type transactions and the like.
Or the transaction is classified according to the branch organization number of the bank system, and specifically can be divided into the transactions of special branches such as Suzhou branches, ningbo branches, qingdao branches, dalian branches and the like.
The classified transactions include information such as transaction names and transaction data.
In the process of implementing step S201 specifically, the transaction to be tested, for example, all payment transactions, are selected according to the modification requirement of the bank system, i.e., the target system; and storing the transaction data corresponding to the transaction to be tested.
Alternatively, if there are transactions that require separate testing, certain fields may be designated to send designated data to obtain the transactions that require separate testing.
It should be noted that each transaction has a transaction code corresponding to it for uniquely identifying the transaction.
Step S202: and sorting the transaction codes corresponding to the transaction data to obtain a transaction code list sorted according to a transaction sequence.
In the process of implementing step S202 specifically, the transaction codes corresponding to the transaction data are sorted according to the execution order of the transaction existence, so as to obtain a transaction code list sorted according to the transaction order.
It should be noted that, the transaction codes may be sorted not only according to the execution order of the transactions, but also according to a predetermined order, and the embodiment of the present invention is not limited thereto.
Step S203: and carrying out transaction simulation tests on the target system in sequence according to the sequence of the transaction codes in the transaction code list so as to facilitate the target system to feed back a corresponding transaction execution result.
In the process of implementing step S203 specifically, according to the sequence of the transaction codes in the transaction code list, a simulation test is performed on the transaction corresponding to the first transaction code in the transaction code list, a transaction between a user terminal or a counter front end and a target system is simulated, and an execution result corresponding to the transaction and fed back by the target system is obtained.
Step S204: and analyzing each transaction execution result to obtain an analysis result.
In the process of implementing step S204, each transaction execution result is analyzed according to the type of the transaction message, so as to obtain an analysis result.
Such as: if the transaction is a json message, corresponding data, namely an analysis result, can be directly obtained.
Step S205: for each analysis result, determining whether the analysis result indicates that the transaction can be executed normally, if the analysis result indicates that the transaction can be executed normally, executing step S206, and if the analysis result indicates that the transaction cannot be executed normally, executing step S207.
In the process of implementing step S205 specifically, it is determined whether each analysis result indicates that the transaction can be executed normally, if the analysis result indicates that the transaction can be executed normally, step S206 is executed, and if the analysis result indicates that the transaction cannot be executed normally, step S207 is executed.
Step S206: determining that transaction data for the transaction has not changed.
In the process of implementing step S206, it is determined that there is no change in the transaction data of the transaction.
Step S207: and generating and displaying information that the transaction data corresponding to the transaction has change so as to facilitate maintenance of a technician.
In the process of implementing step S207 specifically, it is determined that there is a change in the transaction data of the transaction, and at this time, corresponding information is generated based on the transaction data and displayed, so that a technician can perform maintenance.
In the embodiment of the invention, transaction data corresponding to a transaction to be tested is obtained and stored according to the modification requirement of a target system; sorting transaction codes corresponding to the transaction data to obtain a transaction code list sorted according to a transaction sequence; according to the sequence of the transaction codes in the transaction code list, transaction simulation tests are sequentially carried out on the target system, so that the target system can feed back corresponding transaction execution results; analyzing each transaction execution result to obtain an analysis result; for each analysis result, if the analysis result indicates that the transaction can be normally executed, determining that the transaction data of the transaction is not changed; and if the analysis result indicates that the transaction cannot be normally executed, generating and displaying information that the transaction data corresponding to the transaction has change so as to facilitate maintenance of technical personnel. The invention can quickly initiate a large amount of transactions and analyze the return message when the target system needs a large amount of tests, thereby determining whether the transaction test is normal. By means of the method, the testing efficiency can be improved, and the situations of omission and error can be avoided.
Based on the transaction analysis method shown in the above embodiment of the present invention, another transaction analysis method is also shown in the embodiment of the present invention, as shown in fig. 3, the method includes:
step S301: acquiring and storing transaction data corresponding to a transaction to be tested according to the modification requirement of the target system;
step S302: sorting transaction codes corresponding to the transaction data to obtain a transaction code list sorted according to a transaction sequence;
it should be noted that the specific implementation process of step S301 to step S302 is the same as the specific implementation process of step S201 to step S202, and can be referred to each other.
Step S303: determining whether the transaction to be tested needs to be bottomed, if not, executing steps S304 to S306, and steps S312 to S314, and if so, executing steps S307 to S311, and steps S312 to S314.
Because some transactions need to be executed after other transactions are executed, if other transactions do not need to be tested, the transactions need to be laid down, so that the transactions can be directly executed without being executed after other transactions are executed. In the process of implementing step S303 specifically, for each transaction to be tested, it is determined whether the transaction to be tested can be executed directly, if yes, it is determined that bottoming is not required, and step S304 to step S306 are executed, if not, it is determined that bottoming is required, and step S307 to step S311 are executed.
Step S304: and determining a corresponding message type based on each transaction code in the transaction code list.
Optionally, the type of the message to which the transaction belongs is configured in advance according to the transaction code, that is, the corresponding relationship between the transaction code and the different types of messages is pre-established.
In the process of implementing step S304, the corresponding relationship between the transaction code and different types of messages is searched for according to each transaction code, and the type of the message corresponding to the transaction code is determined.
The message types are preset, and specifically may include an xmld message, a fixed-length message, a high-low message, a json message, and the like.
Step S305: and assembling the message type and the transaction data corresponding to each transaction code to generate a corresponding transaction message.
Optionally, different message types have different assembly modes, and a technician sets in advance according to the message types, for example: the xmld messages can be assembled in an om4j mode, the fixed-length messages and the high-low-order messages can be assembled in a bfwj mode, and the json messages can be assembled in a fastjson mode.
In the process of implementing step S305 specifically, for each transaction, a corresponding target assembly manner is determined according to the message type of the transaction, and the message type corresponding to the transaction code and the transaction data are assembled by using the target assembly manner to generate a corresponding transaction message.
Step S306: and sending transaction messages to the target system in sequence according to the sequence of the transaction codes in the transaction code list so that the target system can feed back corresponding transaction execution results.
In the process of specifically implementing step S306, for the first transaction code in the transaction code list according to the sequence of the transaction codes in the transaction code list, sending the transaction message of the first transaction code pair to the target system according to a preset sending manner, so as to simulate the transaction between the user terminal or the counter front end and the target system, and obtain the execution result corresponding to the transaction and fed back by the target system.
It should be noted that the preset sending method is set by a technician according to experience in advance, and includes a programming interface socket, a web http, a remote service call dubbo, an application mq, and the like.
Optionally, it is determined whether the transaction data meets a preset complex transaction standard, and if so, it is determined that the transaction is a complex transaction, and multiple simulation tests are required to be performed on the complex transaction in the process of performing transaction simulation tests, for example, a payment account in a certain transaction may be a debit card, a credit card, an electronic wallet, or the like, so that each payment account can perform one simulation test.
It should be noted that the preset complex transaction standard is set by a technician according to actual situations.
Step S307: and determining bottoming data needing bottoming based on the transaction data of the transaction needing bottoming.
In the process of implementing step S307, based on the transaction data of the transaction that needs to be laid, the transaction data corresponding to the transaction that needs to be executed before the transaction is acquired and used as the laid data.
Step S308: and determining a corresponding message type based on each transaction code in the transaction code list.
It should be noted that the specific implementation process of step S308 is the same as the specific implementation process of step S304, and reference may be made to this process.
Step S309: and assembling the transaction data of the transaction needing bottoming, the bottoming data and the message type corresponding to the transaction code of the transaction to generate a corresponding transaction message.
In the process of implementing step S309 specifically, for each transaction, a corresponding target assembly manner is determined according to the message type of the transaction, and the message type, the bottoming data, and the transaction data corresponding to the transaction code are assembled by using the target assembly manner to generate a corresponding transaction message.
Step S310: and assembling the transaction data of other transactions and the message type corresponding to the transaction code of the transaction to generate a corresponding transaction message.
In the process of implementing step S310 specifically, the other transactions are the remaining transactions to be tested except for the transaction to be bottomed.
It should be noted that the specific implementation procedures of step S309 and step S310 are the same as the specific implementation procedures of step S305, and can be referred to each other.
Step S311: and sending transaction messages to the target system in sequence according to the sequence of the transaction codes in the transaction code list so that the target system can feed back corresponding transaction execution results.
It should be noted that the specific implementation process of the specific implementation step S311 is the same as the specific implementation process of the step S306, and reference may be made to this process.
Step S312: and for each transaction, judging whether the analysis result meets a preset result corresponding to the message type of the transaction message, if so, executing step 313, and if not, executing step 314.
It should be noted that different message types set different preset results, for example, if a payment transaction is performed, the preset result is set to be successful.
Step S313: determining that transaction data for the transaction has not changed.
Step S314: and generating and displaying information that the transaction data corresponding to the transaction has change so as to facilitate maintenance of a technician.
It should be noted that the specific implementation of step S313 and step S314 is the same as the specific implementation of steps S206 to S207, and they can be referred to each other.
In the embodiment of the invention, transaction data corresponding to a transaction to be tested is obtained and stored according to the modification requirement of a target system; sorting transaction codes corresponding to the transaction data to obtain a transaction code list sorted according to a transaction sequence; according to the sequence of the transaction codes in the transaction code list, transaction simulation tests are sequentially carried out on the target system, so that the target system can feed back corresponding transaction execution results; analyzing each transaction execution result to obtain an analysis result; for each analysis result, if the analysis result indicates that the transaction can be normally executed, determining that the transaction data of the transaction is not changed; and if the analysis result indicates that the transaction cannot be normally executed, generating and displaying information that the transaction data corresponding to the transaction has changes so that a technician can maintain the information conveniently. The invention can quickly initiate a large amount of transactions and analyze the return message when the target system needs a large amount of tests, thereby determining whether the transaction test is normal. By means of the method, the testing efficiency can be improved, and the situations of omission and error can be avoided.
Based on the transaction analysis method shown in the above embodiment of the present invention, correspondingly, the embodiment of the present invention further discloses a schematic structural diagram of a transaction analysis device, as shown in fig. 4, the device includes:
the acquisition unit 401 is configured to acquire transaction data corresponding to a transaction to be tested according to a modification requirement of a target system, and store the transaction data;
a sorting unit 402, configured to sort the transaction codes corresponding to the transaction data to obtain a transaction code list sorted according to a transaction order;
the test unit 403 is configured to sequentially perform a transaction simulation test on the target system according to the sequence of the transaction codes in the transaction code list, so that the target system feeds back a corresponding transaction execution result;
an analysis unit 404, configured to analyze each transaction execution result to obtain an analysis result;
a processing unit 405, configured to determine, for each analysis result, that transaction data of the transaction is not changed if the analysis result indicates that the transaction can be executed normally; and if the analysis result indicates that the transaction cannot be normally executed, generating and displaying information that the transaction data corresponding to the transaction has change so as to facilitate maintenance of technical personnel.
It should be noted that, the specific principle and the implementation process of each unit in the transaction analysis device disclosed in the embodiment of the present application are the same as those of the transaction analysis recommendation method described in the embodiment of the present application, and reference may be made to corresponding parts in the transaction analysis method disclosed in the embodiment of the present application, which are not described herein again.
Optionally, based on the transaction analysis apparatus shown in the foregoing embodiment of the present invention, the test unit 403 is specifically configured to:
if the transaction to be tested does not need to be bottomed, determining a corresponding message type based on each transaction code in the transaction code list;
assembling the message type and transaction data corresponding to each transaction code to generate a corresponding transaction message;
and sending transaction messages to the target system in sequence according to the sequence of the transaction codes in the transaction code list so that the target system can feed back corresponding transaction execution results.
Optionally, based on the transaction analysis apparatus shown in the foregoing embodiment of the present invention, the test unit 403 is specifically configured to:
if the transaction needing bottoming exists in the transaction to be tested, bottoming data needing bottoming is determined based on the transaction data of the transaction needing bottoming;
determining a corresponding message type based on each transaction code in the transaction code list;
assembling the transaction data of the transaction needing bottoming, bottoming data and the message type corresponding to the transaction code of the transaction to generate a corresponding transaction message;
assembling the transaction data of other transactions and the message types corresponding to the transaction codes of the transactions to generate corresponding transaction messages, wherein the other transactions are the remaining transactions to be tested except the transactions needing to be bottomed;
and sending transaction messages to the target system in sequence according to the sequence of the transaction codes in the transaction code list so that the target system can feed back corresponding transaction execution results.
Optionally, based on the transaction analysis apparatus shown in the foregoing embodiment of the present invention, the processing unit 405 is further configured to: and judging whether the analysis result indicates that the transaction can be normally executed or not according to each analysis result.
Optionally, based on the transaction analysis apparatus shown in the foregoing embodiment of the present invention, the processing unit 405, for determining, for each analysis result, whether the analysis result indicates that the transaction can be normally executed, is specifically configured to:
judging whether the analysis result accords with a preset result corresponding to the message type of the transaction message or not for each transaction;
if yes, determining that the transaction data of the transaction is not changed;
and if the transaction data does not conform to the transaction data, generating and displaying information that the transaction data corresponding to the transaction has change so as to facilitate maintenance of technical personnel.
Based on the transaction analysis device disclosed in the embodiment of the present disclosure, the modules may be implemented by a hardware device including a processor and a memory. Specifically, the modules are stored in a memory as program units, and a processor executes the program units stored in the memory to implement transaction analysis.
The processor comprises a kernel, and the kernel calls a corresponding program unit from the memory. The kernel can be set to one or more than one, and transaction analysis is realized by adjusting kernel parameters.
The present disclosure provides a computer storage medium including a stored text processing program, wherein the program when executed by a processor implements the transaction analysis method described in fig. 2 to 3.
The embodiment of the present disclosure provides a processor, where the processor is configured to execute a program, where the program executes the transaction analysis method described in fig. 2 to 3 when running.
The disclosed embodiment provides an electronic device, and the electronic device in the disclosed embodiment can be a server, a PC, a PAD, a mobile phone and the like.
The electronic device includes at least one processor, and at least one memory coupled to the processor, and a bus.
The processor and the memory complete mutual communication through the bus. A processor for executing the program stored in the memory.
A memory for storing a program for at least: acquiring and storing transaction data corresponding to a transaction to be tested according to the modification requirement of the target system; sorting the transaction codes corresponding to the transaction data to obtain a transaction code list sorted according to a transaction sequence; according to the sequence of the transaction codes in the transaction code list, transaction simulation tests are sequentially carried out on the target system, so that the target system can feed back corresponding transaction execution results; analyzing each transaction execution result to obtain an analysis result; for each analysis result, if the analysis result indicates that the transaction can be normally executed, determining that the transaction data of the transaction is not changed; and if the analysis result indicates that the transaction cannot be normally executed, generating and displaying information that the transaction data corresponding to the transaction has change so as to facilitate maintenance of technical personnel.
The present application further provides a computer program product adapted to perform a program for initializing the following method steps when executed on an electronic device: acquiring and storing transaction data corresponding to a transaction to be tested according to the modification requirement of the target system; sorting transaction codes corresponding to the transaction data to obtain a transaction code list sorted according to a transaction sequence; according to the sequence of the transaction codes in the transaction code list, transaction simulation tests are sequentially carried out on the target system, so that the target system can feed back corresponding transaction execution results; analyzing each transaction execution result to obtain an analysis result; for each analysis result, if the analysis result indicates that the transaction can be normally executed, determining that the transaction data of the transaction is not changed; and if the analysis result indicates that the transaction cannot be normally executed, generating and displaying information that the transaction data corresponding to the transaction has changes so that a technician can maintain the information conveniently.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a device includes one or more processors (CPUs), memory, and a bus. The device may also include input/output interfaces, network interfaces, and the like.
The memory may include volatile memory in a computer readable medium, random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM), including at least one memory chip. The memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include transitory computer readable media (transmyedia) such as modulated data signals and carrier waves.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, the system or system embodiments, which are substantially similar to the method embodiments, are described in a relatively simple manner, and reference may be made to some descriptions of the method embodiments for relevant points. The above-described system and system embodiments are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Those of skill would further appreciate that the various illustrative components and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the components and steps of the various examples have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the technical solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. 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 invention. Thus, the present invention 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 transaction analysis method, the method comprising:
acquiring and storing transaction data corresponding to a transaction to be tested according to the modification requirement of the target system;
sorting the transaction codes corresponding to the transaction data to obtain a transaction code list sorted according to a transaction sequence;
according to the sequence of the transaction codes in the transaction code list, transaction simulation testing is carried out on the target system in sequence, so that the target system can feed back a corresponding transaction execution result;
analyzing each transaction execution result to obtain an analysis result;
for each analysis result, if the analysis result indicates that the transaction can be normally executed, determining that the transaction data of the transaction is not changed;
and if the analysis result indicates that the transaction cannot be normally executed, generating and displaying information that the transaction data corresponding to the transaction has change so as to facilitate maintenance of technical personnel.
2. The method of claim 1, further comprising:
for each analysis result, judging whether the analysis result indicates that the transaction can be normally executed;
if the analysis result indicates that the transaction can be normally executed, determining that the transaction data of the transaction is not changed;
and if the analysis result indicates that the transaction cannot be normally executed, generating and displaying information that the transaction data corresponding to the transaction has change so as to facilitate maintenance of technical personnel.
3. The method of claim 1, wherein said performing transaction simulation tests on said target system sequentially according to the sequence of transaction codes in the transaction code list comprises:
if the transaction to be tested does not need to be bottomed, determining a corresponding message type based on each transaction code in the transaction code list;
assembling the message type and transaction data corresponding to each transaction code to generate a corresponding transaction message;
and sending transaction messages to the target system in sequence according to the sequence of the transaction codes in the transaction code list so that the target system can feed back a corresponding transaction execution result.
4. The method of claim 1, wherein said performing transaction simulation tests on said target system sequentially according to the sequence of transaction codes in the transaction code list comprises:
if the transaction needing bottoming exists in the transaction to be tested, bottoming data needing bottoming is determined based on the transaction data of the transaction needing bottoming;
determining a corresponding message type based on each transaction code in the transaction code list;
assembling the transaction data of the transaction needing bottoming, bottoming data and the message type corresponding to the transaction code of the transaction to generate a corresponding transaction message;
assembling the transaction data of other transactions and the message types corresponding to the transaction codes of the transactions to generate corresponding transaction messages, wherein the other transactions are the remaining transactions to be tested except the transactions needing to be bottomed;
and sending transaction messages to the target system in sequence according to the sequence of the transaction codes in the transaction code list so that the target system can feed back corresponding transaction execution results.
5. The method of claim 2, wherein determining whether the analysis result indicates that the transaction can be performed normally comprises:
judging whether the analysis result accords with a preset result corresponding to the message type of the transaction message or not for each transaction;
if yes, determining that the transaction data of the transaction is not changed;
and if the data do not meet the requirements, generating and displaying information that the transaction data corresponding to the transaction have changes so that a technician can maintain the information conveniently.
6. A transaction analysis device, the device comprising:
the acquisition unit is used for acquiring and storing transaction data corresponding to a transaction to be tested according to the modification requirement of the target system;
the sorting unit is used for sorting the transaction codes corresponding to the transaction data to obtain a transaction code list sorted according to a transaction sequence;
the test unit is used for sequentially carrying out transaction simulation test on the target system according to the sequence of the transaction codes in the transaction code list so as to facilitate the target system to feed back a corresponding transaction execution result;
the analysis unit is used for analyzing each transaction execution result to obtain an analysis result;
the processing unit is used for determining that the transaction data of the transaction is not changed if the analysis result indicates that the transaction can be normally executed according to each analysis result; and if the analysis result indicates that the transaction cannot be normally executed, generating and displaying information that the transaction data corresponding to the transaction has changes so that a technician can maintain the information conveniently.
7. The device according to claim 6, characterized in that said test unit is particularly adapted to:
if the transaction to be tested does not need to be bottomed, determining a corresponding message type based on each transaction code in the transaction code list;
assembling the message type and transaction data corresponding to each transaction code to generate a corresponding transaction message;
and sending transaction messages to the target system in sequence according to the sequence of the transaction codes in the transaction code list so that the target system can feed back a corresponding transaction execution result.
8. The device according to claim 7, characterized in that the test unit is specifically configured to:
if the transaction needing bottoming exists in the transaction to be tested, bottoming data needing bottoming is determined based on the transaction data of the transaction needing bottoming;
determining a corresponding message type based on each transaction code in the transaction code list;
assembling the transaction data of the transaction needing bottoming, bottoming data and the message type corresponding to the transaction code of the transaction to generate a corresponding transaction message;
assembling transaction data of other transactions and message types corresponding to the transaction codes of the transactions to generate corresponding transaction messages, wherein the other transactions are the remaining transactions to be tested except the transactions needing to be laid;
and sending transaction messages to the target system in sequence according to the sequence of the transaction codes in the transaction code list so that the target system can feed back corresponding transaction execution results.
9. An electronic device, characterized in that the electronic device is adapted to run a program, wherein the program when running performs the transaction analysis method according to any of claims 1-5.
10. A computer storage medium, characterized in that the storage medium comprises a stored program, wherein the program, when executed, controls a device on which the storage medium is located to perform the transaction analysis method according to any one of claims 1 to 5.
CN202211199120.XA 2022-09-29 2022-09-29 Transaction analysis method and device, electronic equipment and computer storage medium Pending CN115562983A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211199120.XA CN115562983A (en) 2022-09-29 2022-09-29 Transaction analysis method and device, electronic equipment and computer storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211199120.XA CN115562983A (en) 2022-09-29 2022-09-29 Transaction analysis method and device, electronic equipment and computer storage medium

Publications (1)

Publication Number Publication Date
CN115562983A true CN115562983A (en) 2023-01-03

Family

ID=84742619

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211199120.XA Pending CN115562983A (en) 2022-09-29 2022-09-29 Transaction analysis method and device, electronic equipment and computer storage medium

Country Status (1)

Country Link
CN (1) CN115562983A (en)

Similar Documents

Publication Publication Date Title
CN106487603B (en) Response testing method and device
CN111737125B (en) Method, device and server for generating quotation data of quantized transaction
CN109582550B (en) Method, device and server for acquiring full-service scene fault set
CN109933534B (en) Method and device for determining financial test object
CN110619574A (en) Remittance data processing method, remittance data processing apparatus, electronic device, and storage medium
CN110990274A (en) Data processing method, device and system for generating test case
CN111414369A (en) Data processing method, device and equipment
WO2023284505A1 (en) Method and apparatus for code-scanning payment
US20210349920A1 (en) Method and apparatus for outputting information
CN112905451B (en) Automatic testing method and device for application program
CN114693226A (en) Approval process construction method, device, equipment and storage medium
CN115562983A (en) Transaction analysis method and device, electronic equipment and computer storage medium
CN115470139A (en) Interface testing method and related equipment
CN110610343A (en) Business process generation method and device and storage medium
CN106875268B (en) Bank account information reminding method, server and terminal
CN114116761A (en) Variable processing method, variable processing device, computer equipment and storage medium
CN115495570A (en) Application user classification method, application user evaluation method, application user classification device, application user evaluation device and application user evaluation equipment
CN109992614B (en) Data acquisition method, device and server
CN108427614B (en) Interface testing method and device based on adaptor tool
CN115437903A (en) Interface test method, device, apparatus, storage medium, and program
CN114428723A (en) Test system, system test method, related device and storage medium
CN116383095B (en) Smoking test method and system based on RPA robot and readable storage medium
CN113743948A (en) Method and device for generating transaction information file, electronic equipment and storage medium
CN111967961B (en) Data mining method and device
CN108363663B (en) Application of intelligent POS terminal to inspection bank card detection center authentication

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