CN117033246A - Transaction playback processing method, device, equipment and storage medium - Google Patents
Transaction playback processing method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN117033246A CN117033246A CN202311248218.4A CN202311248218A CN117033246A CN 117033246 A CN117033246 A CN 117033246A CN 202311248218 A CN202311248218 A CN 202311248218A CN 117033246 A CN117033246 A CN 117033246A
- Authority
- CN
- China
- Prior art keywords
- transaction
- data
- actual
- playback
- result
- 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
- 238000003672 processing method Methods 0.000 title claims abstract description 22
- 238000003860 storage Methods 0.000 title claims abstract description 14
- 238000012545 processing Methods 0.000 claims abstract description 105
- 238000000034 method Methods 0.000 claims abstract description 50
- 238000004458 analytical method Methods 0.000 claims abstract description 45
- 238000007781 pre-processing Methods 0.000 claims abstract description 33
- 238000004088 simulation Methods 0.000 claims abstract description 30
- 238000012360 testing method Methods 0.000 claims abstract description 21
- 238000001914 filtration Methods 0.000 claims description 21
- 238000012216 screening Methods 0.000 claims description 17
- 230000008569 process Effects 0.000 claims description 15
- 238000004590 computer program Methods 0.000 claims description 6
- 238000004519 manufacturing process Methods 0.000 abstract description 18
- 238000005516 engineering process Methods 0.000 abstract description 9
- 238000004891 communication Methods 0.000 description 11
- 238000010586 diagram Methods 0.000 description 7
- 230000003287 optical effect Effects 0.000 description 5
- 238000011160 research Methods 0.000 description 5
- 238000002360 preparation method Methods 0.000 description 4
- 230000005236 sound signal Effects 0.000 description 4
- 230000008676 import Effects 0.000 description 3
- 230000003068 static effect Effects 0.000 description 3
- 230000001133 acceleration Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 238000012827 research and development Methods 0.000 description 2
- 239000011435 rock Substances 0.000 description 2
- 238000011144 upstream manufacturing Methods 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000000586 desensitisation Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000003384 imaging method Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000001960 triggered effect 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/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
-
- 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
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application provides a transaction playback processing method, a device, equipment and a storage medium, and relates to the field of financial science and technology. The method comprises the following steps: receiving a playback request sent by a terminal, and analyzing the request to obtain transaction time and application identification; acquiring actual transaction data and actual transaction results corresponding to the application identifiers based on the transaction time, wherein the actual transaction data comprises log data and transaction environment data; preprocessing the log data to obtain log data to be played back; simulating an actual transaction environment based on the transaction environment data and a pre-configured test environment, and performing transaction playback processing in the simulated transaction environment by adopting a pre-configured MOCK tool based on log data to be played back to obtain a simulation transaction result; and analyzing the actual transaction result and the simulated transaction result, obtaining an analysis result and transmitting the analysis result to the terminal. The method provided by the application can accurately simulate the production environment, obtain a completely accurate playback result, and avoid the influence of time sequence by adopting MOCK.
Description
Technical Field
The present application relates to the field of financial science and technology, and in particular, to a transaction playback processing method, apparatus, device, and storage medium.
Background
At present, when an upstream application calls a downstream application, the conditions of inconsistent field length, unnecessary transmission, date format and the like of interface document description often occur in a production environment, so that related production problems occur, and production data is required to be subjected to transaction playback processing in a test environment.
At present, during transaction playback processing, a byte code recording mode is generally adopted for transaction playback, the byte code is recorded in a corresponding tangent point class and is loaded into a classLoader, and the byte code compiled by the java class is changed, so that the transaction playback is performed.
However, the playback process using the bytecode recording cannot accurately simulate the production environment, resulting in inaccurate results obtained by the playback process. Moreover, the byte code mode cannot be accurate to the moment when each transaction occurs, so that the production rule deployed by service personnel is invalid, the simulation transaction cannot be performed according to the time sequence, and the result is also influenced.
Disclosure of Invention
The application provides a transaction playback processing method, a device, equipment and a storage medium, which are used for solving the technical problem that the playback processing cannot accurately simulate the production environment, so that the result obtained by the playback processing is inaccurate.
In a first aspect, the present application provides a transaction playback processing method, including:
receiving a playback request sent by a terminal, analyzing the playback request, and acquiring transaction time and an application identifier;
acquiring actual transaction data corresponding to the application identifier and an actual transaction result corresponding to the actual transaction data based on the transaction time, wherein the actual transaction data comprises: log data and transaction environment data;
preprocessing the log data to obtain log data to be played back, wherein the preprocessing comprises the following steps: screening, filtering and decrypting;
simulating an actual transaction environment based on the transaction environment data and a pre-configured test environment, and performing transaction playback processing in the simulated transaction environment by adopting a pre-configured MOCK tool based on the log data to be played back to obtain a simulation transaction result;
and analyzing the actual transaction result and the simulated transaction result to obtain corresponding analysis results, and sending the analysis results to the terminal.
Optionally, the acquiring actual transaction data corresponding to the application identifier and an actual transaction result corresponding to the actual transaction data based on the transaction time includes:
Determining whether the application identifier is an application identifier corresponding to a local application;
if yes, searching actual transaction data matched with the transaction time and an actual transaction result corresponding to the actual transaction data in a local cache database, and acquiring the matched actual transaction data and the actual transaction result corresponding to the actual transaction data;
if not, acquiring actual transaction data matched with the transaction time and an actual transaction result corresponding to the actual transaction data from an external cache database corresponding to the external application.
Optionally, the preprocessing the log data to obtain log data to be played back includes:
acquiring a service type identifier and a key field corresponding to the service type identifier in the playback request, screening the log data based on the service type identifier, and acquiring first log data matched with the service type identifier;
filtering the matched first log data based on the key field to obtain second log data matched with the key field;
and decrypting the encrypted data in the matched second log data to obtain log data to be played back.
Optionally, the transaction environment data includes: bottom account data and snapshot data;
the simulating an actual transaction environment based on the transaction environment data and a pre-configured test environment, performing transaction playback processing in the simulated transaction environment by using a pre-configured MOCK tool based on the log data to be played back, and obtaining a simulated transaction result, including:
importing the ledger data and the snapshot data into a pre-configured test environment to simulate an actual transaction environment;
performing transaction playback processing based on the log data by adopting a preconfigured playback tool in the simulated transaction environment;
in the process of transaction playback, for each transaction in the log data to be played back, acquiring actual transaction return information by adopting a pre-configured MOCK tool based on the transaction identifier corresponding to each transaction, determining a simulation transaction result of each transaction based on the actual transaction return information corresponding to each transaction and a matched pre-set business rule, and recording the transaction identifier corresponding to each transaction and the corresponding simulation transaction result in a data table until the transaction playback is completed, thereby acquiring a simulation transaction result table.
Optionally, for each transaction in the log data to be played back, acquiring, by using a preconfigured dock tool, actual transaction return information based on a transaction identifier corresponding to each transaction, including:
For each transaction in the log data to be replayed, reading actual transaction return information matched with the transaction identifier corresponding to the transaction in an actual transaction log in a local cache database by adopting a pre-configured MOCK tool based on the transaction identifier corresponding to the transaction;
the actual transaction log includes: the transaction identification corresponding to each transaction and the corresponding actual transaction return information.
Optionally, the analyzing the actual transaction result and the simulated transaction result to obtain corresponding analysis results includes:
comparing the simulated transaction result table with an actual transaction result table;
if the simulated transaction results in the simulated transaction result table are consistent with the corresponding actual transaction results in the actual transaction result table, the analysis result is successful in transaction playback;
and if any simulated transaction result in the simulated transaction result table is inconsistent with the corresponding actual transaction result in the actual transaction result table, the analysis result is that the transaction playback fails.
Optionally, the transaction playback processing method further includes:
acquiring a playback processing type in the playback request, and determining a transaction playback processing mode based on the playback processing type;
If the playback processing type is partial link playback, performing transaction playback processing based on the log data in a simulated transaction environment by adopting a pre-configured MOCK tool;
and if the playback processing type is full-link playback, performing full-link transaction playback processing based on the log data in the simulated transaction environment.
In a second aspect, the present application provides a transaction playback processing apparatus comprising:
the receiving and transmitting unit is used for receiving a playback request sent by the terminal, analyzing the playback request and acquiring transaction time and application identification;
the acquiring unit is configured to acquire actual transaction data corresponding to the application identifier and an actual transaction result corresponding to the actual transaction data based on the transaction time, where the actual transaction data includes: log data and transaction environment data;
the processing unit is used for preprocessing the log data to obtain log data to be played back, and the preprocessing comprises the following steps: screening, filtering and decrypting;
the transaction playback unit is used for simulating an actual transaction environment based on the transaction environment data and a pre-configured test environment, and performing transaction playback processing in the simulated transaction environment by adopting a pre-configured MOCK tool based on the log data to be played back to obtain a simulation transaction result;
The processing unit is also used for analyzing the actual transaction result and the simulated transaction result to obtain a corresponding analysis result;
and the receiving and transmitting unit is also used for transmitting the analysis result to the terminal.
In a third aspect, the present application provides an electronic device comprising: a processor, a memory, and a transceiver;
a processor, memory, and transceiver circuitry interconnect;
the memory stores computer-executable instructions;
a transceiver for transceiving data;
the processor executes computer-executable instructions stored in the memory to cause the processor to perform the method as described in the first aspect.
In a fourth aspect, the present application provides a computer-readable storage medium having stored therein computer-executable instructions for performing the method according to the first aspect when executed by a processor.
In a fifth aspect, the application provides a computer program product comprising a computer program which, when executed by a processor, implements the method of the first aspect.
The application provides a transaction playback processing method, a device, equipment and a storage medium, which are used for receiving a playback request sent by a terminal, analyzing the playback request, acquiring transaction time and application identification, and acquiring actual transaction data corresponding to the application identification and actual transaction results corresponding to the actual transaction data based on the transaction time, wherein the actual transaction data comprises log data and transaction environment data, further preprocessing the log data to obtain the log data to be played back, and the preprocessing comprises the following steps: the method comprises screening processing, filtering processing and decryption processing, further carrying out transaction playback processing based on transaction environment data and pre-configured MOCK tools based on log data to be played back, obtaining a simulation transaction result, analyzing an actual transaction result and the simulation transaction result, obtaining a corresponding analysis result, feeding back the analysis result to a terminal, and accurately simulating a production environment, so that research personnel can obtain more accurate playback results, and the influence caused by time sequence can be avoided by adopting a MOCK mode.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.
Fig. 1 is a schematic diagram of a network architecture of a transaction playback processing method according to the present application;
FIG. 2 is a schematic flow chart of a transaction playback processing method according to the present application;
FIG. 3 is a flow chart of another transaction playback processing method according to the present application;
fig. 4 is a schematic structural diagram of a transaction playback processing device provided by the present application;
FIG. 5 is a first block diagram of an electronic device for implementing the transaction playback processing method of the present application;
fig. 6 is a second block diagram of an electronic device for implementing the transaction playback processing method of the present application.
Specific embodiments of the present application have been shown by way of the above drawings and will be described in more detail below. The drawings and the written description are not intended to limit the scope of the inventive concepts in any way, but rather to illustrate the inventive concepts to those skilled in the art by reference to the specific embodiments.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the accompanying claims.
It should be noted that, the user information (including but not limited to user equipment information, user personal information, etc.) and the data (including but not limited to data for analysis, stored data, presented data, etc.) related to the present application are information and data authorized by the user or fully authorized by each party, and the collection, use and processing of the related data need to comply with related laws and regulations and standards, and provide corresponding operation entries for the user to select authorization or rejection.
It should be noted that the transaction playback processing method, apparatus, device and storage medium of the present application may be used in the field of financial technology, and may be used in any field other than the field of financial technology.
For a clear understanding of the technical solutions of the present application, the prior art solutions will be described in detail first.
At present, when an upstream application calls a downstream application, the conditions of inconsistent field length, unnecessary transmission, date format and the like of interface document description often occur in a production environment, and the verification of an interface is imperfect, and because of many calling parties, the interface is not easy to limit in a strong verification mode, related production problems occur, and production data is required to be subjected to transaction playback processing in a test environment. At present, during transaction playback processing, a byte code recording mode is generally adopted for transaction playback, the byte code is recorded in a corresponding tangent point class and is loaded into a classLoader, and the byte code compiled by the java class is changed, so that the transaction playback is performed.
However, the playback process using the bytecode recording cannot accurately simulate the production environment, resulting in inaccurate results obtained by the playback process. Moreover, analog transactions cannot be performed in time sequence, and the results are also affected.
Therefore, aiming at the technical problem that in the prior art, the playback processing cannot accurately simulate the production environment, and the result obtained by the playback processing is not accurate enough, the inventor finds that in the study, a playback request sent by a receiving terminal is analyzed, the playback request is analyzed, the transaction time and the application identifier are obtained, the actual transaction data corresponding to the application identifier and the actual transaction result corresponding to the actual transaction data are obtained based on the transaction time, wherein the actual transaction data comprise log data and transaction environment data, the log data are further preprocessed, the log data to be played back are obtained, and the preprocessing comprises: the method comprises screening processing, filtering processing and decryption processing, further carrying out transaction playback processing based on transaction environment data and pre-configured MOCK tools based on log data to be played back, obtaining a simulation transaction result, analyzing an actual transaction result and the simulation transaction result, obtaining a corresponding analysis result, feeding back the analysis result to a terminal, and accurately simulating a production environment, so that research personnel can obtain more accurate playback results, and the influence caused by time sequence can be avoided by adopting a MOCK mode.
The inventor proposes the technical scheme of the embodiment of the application based on the creative discovery. The following describes a network architecture and an application scenario of the transaction playback processing method provided by the embodiment of the application.
As shown in fig. 1, the network architecture corresponding to the transaction playback processing method provided by the embodiment of the present application includes: the terminal 1 and the server 2 are in communication connection, a user inputs transaction time and application identification in an input box of an operation interface of a client side of the terminal 1, and clicks a confirmation key, so that a playback request is triggered, the server 2 receives the playback request sent by the terminal 1, analyzes the playback request, and obtains the transaction time and the application identification; the server 2 obtains actual transaction data corresponding to the application identifier and actual transaction results corresponding to the actual transaction data based on the transaction time, wherein the actual transaction data comprises: log data and transaction environment data; the server 2 pre-processes the log data to obtain log data to be played back, wherein the pre-processing comprises: screening, filtering and decrypting; the server 2 simulates an actual transaction environment based on the transaction environment data and a pre-configured test environment, and adopts a pre-configured MOCK tool to perform transaction playback processing based on log data to be played back in the simulated transaction environment to obtain a simulated transaction result; the server 2 analyzes the actual transaction result and the simulated transaction result to obtain corresponding analysis results, and sends the analysis results to the terminal 1, so that the production environment can be accurately simulated, research and development personnel can obtain more accurate playback results, and the influence caused by time sequence can be avoided by adopting a MOCK mode.
The application provides a transaction playback processing method, which aims to solve the technical problems in the prior art.
The following describes the technical scheme of the present application and how the technical scheme of the present application solves the above technical problems in detail with specific embodiments. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.
Fig. 2 is a flow chart of a transaction playback processing method provided by the application, and the method is applied to electronic equipment. Wherein the electronic device may be a digital computer representing various forms. Such as cellular telephones, smart phones, laptops, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframes, and other suitable computers. As shown in fig. 2, the method includes:
step 201, receiving a playback request sent by a terminal, analyzing the playback request, and obtaining transaction time and application identification.
In this embodiment, the electronic device receives a playback request sent by the terminal, parses the playback request, and obtains a transaction time and an application identifier, where the application identifier may be a name of an application program. The main flow of transaction playback is data acquisition, preprocessing of the data, preparation of playback environment, introduction of MOCK, transaction playback and result analysis.
Step 202, acquiring actual transaction data corresponding to the application identifier and an actual transaction result corresponding to the actual transaction data based on the transaction time, wherein the actual transaction data comprises: log data and transaction context data.
In this embodiment, the acquiring data refers to acquiring actual transaction data and a corresponding actual transaction result, and acquiring actual transaction data corresponding to an application identifier and an actual transaction result corresponding to the actual transaction data based on transaction time, where the actual transaction data includes log data and transaction environment data, the transaction environment data includes ledger data and snapshot data, and the ledger data includes: data in a rule engine correlation table, engine switching variables, etc. Log data is core data that concatenates the entire transaction flow. The snapshot data is used to compare the status of the database when open versus when closed. The actual transaction results are used to compare with the simulated transaction results.
Step 203, preprocessing the log data to obtain log data to be played back, where the preprocessing includes: screening, filtering and decrypting.
In this embodiment, preprocessing of the data refers to preprocessing of log data, so as to obtain log data to be played back, where preprocessing includes filtering data, filtering processing, and decryption processing.
Step 204, simulating an actual transaction environment based on the transaction environment data and the pre-configured test environment, and performing transaction playback processing in the simulated transaction environment by adopting a pre-configured MOCK tool based on log data to be played back to obtain a simulation transaction result.
In this embodiment, the above-mentioned playback environment is prepared to simulate an actual transaction environment, specifically, the actual transaction environment is simulated based on the transaction environment data and the pre-configured test environment, and the pre-configured MOCK tool is adopted in the simulated transaction environment to perform transaction playback processing based on the log data to be played back, so as to obtain a simulated transaction result.
And 205, analyzing the actual transaction result and the simulated transaction result to obtain corresponding analysis results, and sending the analysis results to the terminal.
In this embodiment, the actual transaction result and the simulated transaction result are analyzed, specifically, the simulated transaction result is compared with the actual transaction result, an analysis result is obtained according to the comparison result, and the analysis result is further sent to the terminal, so that research personnel can obtain a more accurate playback result.
The application, receiving the playback request sent by the terminal, analyzing the playback request, obtaining the transaction time and the application identifier, and obtaining the actual transaction data corresponding to the application identifier and the actual transaction result corresponding to the actual transaction data based on the transaction time, wherein the actual transaction data comprises log data and transaction environment data, further preprocessing the log data to obtain the log data to be played back, and the preprocessing comprises: the method comprises screening processing, filtering processing and decryption processing, further carrying out transaction playback processing based on transaction environment data and pre-configured MOCK tools based on log data to be played back, obtaining a simulation transaction result, analyzing an actual transaction result and the simulation transaction result, obtaining a corresponding analysis result, feeding back the analysis result to a terminal, and accurately simulating a production environment, so that research personnel can obtain more accurate playback results, and the influence caused by time sequence can be avoided by adopting a MOCK mode.
Fig. 3 is a flow chart of another transaction playback processing method provided by the present application, where the method is applied to an electronic device, as shown in fig. 3, and the method includes:
step 301, receiving a playback request sent by a terminal, analyzing the playback request, and obtaining transaction time and an application identifier.
In this embodiment, the electronic device receives a playback request sent by the terminal, parses the playback request, and obtains a transaction time and an application identifier, where the application identifier may be a name of an application program. The main flow of transaction playback is data acquisition, preprocessing of the data, preparation of playback environment, MOCK introduction, transaction playback and result analysis.
Step 302, acquiring actual transaction data corresponding to the application identifier and an actual transaction result corresponding to the actual transaction data based on the transaction time, wherein the actual transaction data comprises: log data and transaction context data.
In this embodiment, the acquiring data refers to acquiring actual transaction data and a corresponding actual transaction result, and acquiring actual transaction data corresponding to an application identifier and an actual transaction result corresponding to the actual transaction data based on transaction time, where the actual transaction data includes log data and transaction environment data, the transaction environment data includes ledger data and snapshot data, and the ledger data includes: data in a rule engine correlation table, engine switching variables, etc. Log data is core data that concatenates the entire transaction flow. The snapshot data is used to compare the status of the database when open versus when closed. The actual transaction results are used to compare with the simulated transaction results.
In one possible implementation manner, acquiring actual transaction data corresponding to the application identifier and an actual transaction result corresponding to the actual transaction data based on the transaction time includes:
determining whether the application identifier is an application identifier corresponding to the local application; if yes, searching actual transaction data matched with the transaction time and an actual transaction result corresponding to the actual transaction data in a local cache database, and acquiring the matched actual transaction data and the actual transaction result corresponding to the actual transaction data; if not, acquiring actual transaction data matched with the transaction time and an actual transaction result corresponding to the actual transaction data from an external cache database corresponding to the external application.
In this embodiment, it is determined whether the application identifier is an application identifier corresponding to the local application, if the application identifier is an application identifier corresponding to the local application, data is obtained in a local cache database, specifically, actual transaction data and a corresponding actual transaction result matched with the transaction time are searched in the local cache database, and the matched actual transaction data and an actual transaction result corresponding to the actual transaction data are further obtained; if the application identifier is not the application identifier corresponding to the local application, the description data is not stored in the local cache database, and the actual transaction data matched with the transaction time and the actual transaction result corresponding to the actual transaction data are further obtained from the external cache database corresponding to the external application. The local cache database can be Aerospike, NOS, redis, the external cache database can be Aerospike, NOS, redis, and the cache databases are high-efficiency cache databases, so that the response speed is high.
Step 303, preprocessing the log data to obtain log data to be played back, where the preprocessing includes: screening, filtering and decrypting.
In this embodiment, preprocessing of the data refers to preprocessing of log data, so as to obtain log data to be played back, where preprocessing includes filtering data, filtering processing, and decryption processing.
In one possible implementation, preprocessing log data to obtain log data to be played back includes:
acquiring a service type identifier and a key field corresponding to the service type identifier in a playback request, screening log data based on the service type identifier, and acquiring first log data matched with the service type identifier; filtering the matched first log data based on the key field to obtain second log data matched with the key field; and decrypting the encrypted data in the matched second log data to obtain log data to be played back.
In this embodiment, preprocessing includes screening data, filtering processing, and decryption processing, specifically, screening specific data from a plurality of log data, obtaining a service type identifier in a playback request and a key field corresponding to the service type identifier, and screening the log data based on the service type identifier to obtain first log data matched with the service type identifier; the filtering processing is to obtain effective data, and the first log data matched with the key field is filtered based on the key field to obtain second log data matched with the key field; the decryption processing is to perform anti-desensitization on the data, namely, the decryption processing is performed on the encrypted data in the matched second log data in the decryption process of the encrypted data, so as to obtain the log data to be played back. If the encrypted data has no effect on the playback result, decryption may be omitted.
Step 304, simulating an actual transaction environment based on the transaction environment data and the pre-configured test environment.
In step 305, a playback processing type in the playback request is acquired, and a transaction playback processing mode is determined based on the playback processing type.
And 306, if the playback processing type is partial link playback, performing transaction playback processing in the simulated transaction environment by adopting a pre-configured MOCK tool based on log data to be played back, and obtaining a simulated transaction result.
In this embodiment, the preparation of the playback environment is to simulate an actual transaction environment, specifically, simulate an actual transaction environment based on transaction environment data and a pre-configured test environment, further obtain a playback processing type in a playback request, where the type is divided into a partial link playback and a full link playback, determine a transaction playback processing mode based on the playback processing type, and if the playback processing type is the partial link playback, perform a transaction playback process in the simulated transaction environment based on log data to be played back by using a pre-configured MOCK tool, so as to obtain a simulated transaction result.
Optionally, if the playback processing type is full link playback, full link transaction playback processing is performed based on the log data in the simulated transaction environment.
In this embodiment, full-link log playback is performed without using a MOCK method, and partial link log playback is performed with a MOCK method, and if the playback processing type is full-link playback, full-link transaction playback processing is performed based on log data in a simulated transaction environment without using a MOCK tool. It should be noted that, the partial link playback is applicable to a transaction link with a cache database, and if the cache is not used, full link playback may be used.
In one possible implementation, the transaction context data includes: bottom account data and snapshot data;
simulating an actual transaction environment based on the transaction environment data and a pre-configured test environment, performing transaction playback processing in the simulated transaction environment by adopting a pre-configured MOCK tool based on log data to be played back, and obtaining a simulated transaction result, wherein the method comprises the following steps of:
importing the ledger data and the snapshot data into a pre-configured test environment to simulate an actual transaction environment; performing transaction playback processing based on the log data in the simulated transaction environment by adopting a preconfigured playback tool; in the process of transaction playback, for each transaction in log data to be played back, acquiring actual transaction return information by adopting a pre-configured MOCK tool based on a transaction identifier corresponding to each transaction, determining a simulation transaction result of each transaction based on the actual transaction return information corresponding to each transaction and a matched preset business rule, and recording the transaction identifier corresponding to each transaction and the corresponding simulation transaction result in a data table until the transaction playback is completed, thereby acquiring a simulation transaction result table.
In this embodiment, the transaction environment data includes: the preparation of the background data and the snapshot data is mainly to import the background data and the snapshot data into a pre-configured test environment so as to simulate an actual transaction environment, a pre-configured playback tool is adopted in the simulated transaction environment to carry out transaction playback processing based on log data, a playback tool is used for calling an import to carry out production transaction simulation, in the process of carrying out transaction playback, for each transaction in the log data to be played back, a pre-configured MOCK tool is adopted to acquire actual transaction return information based on a transaction identifier corresponding to each transaction, the time sequence problem needs to be considered in the process of transaction playback, if the simulation transaction cannot be carried out according to the time sequence, the effect on the result needs to be compensated from other steps in the whole playback process, and the influence caused by the time sequence problem can be avoided by adopting the MOCK mode. Further, determining a simulation transaction result of each transaction based on the actual transaction return information corresponding to each transaction and the matched preset business rule, and recording the transaction identification corresponding to each transaction and the corresponding simulation transaction result in a data table until the transaction playback is completed, so as to obtain a simulation transaction result table.
It should be noted that, the actual playback may be divided into full-link log playback and partial-link log playback, where full-link log playback is performed without using a rock manner, and partial-link log playback is performed with a rock manner.
Optionally, for each transaction in the log data to be played back, acquiring actual transaction return information by using a preconfigured MOCK tool based on a transaction identifier corresponding to each transaction, including:
for each transaction in log data to be replayed, reading actual transaction return information matched with a transaction identifier corresponding to each transaction in an actual transaction log in a local cache database by adopting a pre-configured MOCK tool based on the transaction identifier corresponding to each transaction; the actual transaction log includes: the transaction identification corresponding to each transaction and the corresponding actual transaction return information.
In this embodiment, actual transaction return information is obtained by using a MOCK tool, and for each transaction in log data to be played back, the actual transaction return information matched with the transaction identifier corresponding to each transaction in an actual transaction log in a local cache database is read by using a preconfigured MOCK tool based on the transaction identifier corresponding to each transaction, where the actual transaction log includes the transaction identifier corresponding to each transaction and the corresponding actual transaction return information.
Step 307, analyzing the actual transaction result and the simulated transaction result, obtaining a corresponding analysis result, and sending the analysis result to the terminal.
In this embodiment, the actual transaction result and the simulated transaction result are analyzed, specifically, the simulated transaction result is compared with the actual transaction result, the analysis result is obtained according to the comparison result, and the analysis result is further sent to the terminal, so that research personnel obtain a more accurate playback result, and the influence caused by time sequence can be avoided by adopting a MOCK mode.
In one possible implementation, analyzing the actual transaction result and the simulated transaction result to obtain corresponding analysis results includes:
comparing the simulated transaction result table with the actual transaction result table; if the simulated transaction results in the simulated transaction result table are consistent with the corresponding actual transaction results in the actual transaction result table, the analysis result is successful in transaction playback; if any simulated transaction result in the simulated transaction result table is inconsistent with the corresponding actual transaction result in the actual transaction result table, the analysis result is that the transaction playback fails.
In this embodiment, comparing the simulated transaction result with the actual transaction result, and obtaining an analysis result according to the comparison result, specifically comparing the simulated transaction result table with the actual transaction result table, and if each simulated transaction result in the simulated transaction result table is consistent with the corresponding actual transaction result in the actual transaction result table, determining that the analysis result is successful in transaction playback; if any simulated transaction result in the simulated transaction result table is inconsistent with the corresponding actual transaction result in the actual transaction result table, determining that the analysis result is the transaction playback failure.
The application can accurately simulate the production environment, so that research and development personnel can obtain more accurate playback results, and the influence caused by time sequence can be avoided by adopting a MOCK mode.
Fig. 4 is a schematic structural diagram of a transaction playback processing device according to the present application, and as shown in fig. 4, a transaction playback processing device 400 according to the present embodiment includes a transceiver unit 401, an obtaining unit 402, a processing unit 403, and a transaction playback unit 404.
The transceiver unit 401 is configured to receive a playback request sent by a terminal, analyze the playback request, and obtain a transaction time and an application identifier. The obtaining unit 402 is configured to obtain actual transaction data corresponding to the application identifier and an actual transaction result corresponding to the actual transaction data based on the transaction time, where the actual transaction data includes: log data and transaction context data. The processing unit 403 is configured to perform preprocessing on log data to obtain log data to be played back, where the preprocessing includes: screening, filtering and decrypting. The transaction playback unit 404 is configured to simulate an actual transaction environment based on the transaction environment data and a pre-configured test environment, and perform transaction playback processing in the simulated transaction environment by using a pre-configured MOCK tool based on log data to be played back, so as to obtain a simulated transaction result. The processing unit 403 is further configured to analyze the actual transaction result and the simulated transaction result, and obtain a corresponding analysis result. The transceiver unit 401 is further configured to send the analysis result to the terminal.
Optionally, the obtaining unit 402 is further configured to determine whether the application identifier is an application identifier corresponding to the local application; if yes, searching actual transaction data matched with the transaction time and an actual transaction result corresponding to the actual transaction data in a local cache database, and acquiring the matched actual transaction data and the actual transaction result corresponding to the actual transaction data; if not, acquiring actual transaction data matched with the transaction time and an actual transaction result corresponding to the actual transaction data from an external cache database corresponding to the external application.
Optionally, the processing unit 403 is further configured to obtain a service type identifier in the playback request and a key field corresponding to the service type identifier, and screen log data based on the service type identifier, to obtain first log data matched with the service type identifier; filtering the matched first log data based on the key field to obtain second log data matched with the key field; and decrypting the encrypted data in the matched second log data to obtain log data to be played back.
Optionally, the transaction playback unit 404 is further configured to import the ledger data and the snapshot data into a pre-configured testing environment to simulate an actual transaction environment; performing transaction playback processing based on the log data in the simulated transaction environment by adopting a preconfigured playback tool; in the process of transaction playback, for each transaction in log data to be played back, acquiring actual transaction return information by adopting a pre-configured MOCK tool based on a transaction identifier corresponding to each transaction, determining a simulation transaction result of each transaction based on the actual transaction return information corresponding to each transaction and a matched preset business rule, and recording the transaction identifier corresponding to each transaction and the corresponding simulation transaction result in a data table until the transaction playback is completed, thereby acquiring a simulation transaction result table.
Optionally, the transaction playback unit 404 is further configured to, for each transaction in the log data to be played back, read, by using a preconfigured MOCK tool, actual transaction return information in the local cache database, which is matched with a transaction identifier corresponding to each transaction, in an actual transaction log corresponding to the transaction; the actual transaction log includes: the transaction identification corresponding to each transaction and the corresponding actual transaction return information.
Optionally, the processing unit 403 is further configured to compare the simulated transaction result table with the actual transaction result table; if the simulated transaction results in the simulated transaction result table are consistent with the corresponding actual transaction results in the actual transaction result table, the analysis result is successful in transaction playback; if any simulated transaction result in the simulated transaction result table is inconsistent with the corresponding actual transaction result in the actual transaction result table, the analysis result is that the transaction playback fails.
Optionally, the obtaining unit 402 is further configured to obtain a playback processing type in the playback request. The processing unit 403 is further configured to determine a transaction playback processing manner based on the playback processing type; if the playback processing type is partial link playback, performing transaction playback processing based on log data in a simulated transaction environment by adopting a pre-configured MOCK tool; and if the playback processing type is full-link playback, performing full-link transaction playback processing based on the log data in the simulated transaction environment.
Fig. 5 is a first block diagram of an electronic device for implementing the transaction playback processing method of the present application, and as shown in fig. 5, the electronic device 500 includes: a memory 501, a processor 502 and a transceiver 503.
Processor 502, memory 501 and transceiver 503 are electrically interconnected;
a transceiver 503 for transmitting and receiving data;
memory 501 stores computer-executable instructions;
processor 502 executes computer-executable instructions stored in memory 501, causing processor 502 to perform the methods provided by any of the embodiments described above.
Fig. 6 is a second block diagram of an electronic device, which may be a computer, a digital broadcast terminal, a messaging device, a tablet device, a personal digital assistant, a server cluster, etc., as shown in fig. 6, for implementing the transaction playback processing method of the present application.
Electronic device 800 may include one or more of the following components: a processing component 802, a memory 804, a power component 806, a multimedia component 808, an audio component 810, an input/output (I/O) interface 812, a sensor component 814, and a communication component 816.
The processing component 802 generally controls overall operation of the electronic device 800, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to perform all or part of the steps of the methods described above. Further, the processing component 802 can include one or more modules that facilitate interactions between the processing component 802 and other components. For example, the processing component 802 can include a multimedia module to facilitate interaction between the multimedia component 808 and the processing component 802.
The memory 804 is configured to store various types of data to support operations at the electronic device 800. Examples of such data include instructions for any application or method operating on the electronic device 800, contact data, phonebook data, messages, pictures, videos, and so forth. The memory 804 may be implemented by any type or combination of volatile or nonvolatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.
The power supply component 806 provides power to the various components of the electronic device 800. The power components 806 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for the electronic device 800.
The multimedia component 808 includes a screen between the electronic device 800 and the user that provides an output interface. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may sense not only the boundary of a touch or sliding action, but also the duration and pressure associated with the touch or sliding operation. In some embodiments, the multimedia component 808 includes a front camera and/or a rear camera. When the electronic device 800 is in an operational mode, such as a shooting mode or a video mode, the front camera and/or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have focal length and optical zoom capabilities.
The audio component 810 is configured to output and/or input audio signals. For example, the audio component 810 includes a Microphone (MIC) configured to receive external audio signals when the electronic device 800 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may be further stored in the memory 804 or transmitted via the communication component 816. In some embodiments, audio component 810 further includes a speaker for outputting audio signals.
The I/O interface 812 provides an interface between the processing component 802 and peripheral interface modules, which may be a keyboard, click wheel, buttons, etc. These buttons may include, but are not limited to: homepage button, volume button, start button, and lock button.
The sensor assembly 814 includes one or more sensors for providing status assessment of various aspects of the electronic device 800. For example, the sensor assembly 814 may detect an on/off state of the electronic device 800, a relative positioning of the components, such as a display and keypad of the electronic device 800, the sensor assembly 814 may also detect a change in position of the electronic device 800 or a component of the electronic device 800, the presence or absence of a user's contact with the electronic device 800, an orientation or acceleration/deceleration of the electronic device 800, and a change in temperature of the electronic device 800. The sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 814 may also include an acceleration sensor, a gyroscopic sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
The communication component 816 is configured to facilitate communication between the electronic device 800 and other devices, either wired or wireless. The electronic device 800 may access a wireless network based on a communication standard, such as WiFi,2G, or 3G, or a combination thereof. In one exemplary embodiment, the communication component 816 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component 816 further includes a Near Field Communication (NFC) module to facilitate short range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, ultra Wideband (UWB) technology, bluetooth (BT) technology, and other technologies.
In an exemplary embodiment, the electronic device 800 may be implemented by one or more Application Specific Integrated Circuits (ASICs), digital Signal Processors (DSPs), digital Signal Processing Devices (DSPDs), programmable Logic Devices (PLDs), field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic elements for executing the methods described above.
In an exemplary embodiment, a non-transitory computer readable storage medium is also provided, such as memory 804 including instructions executable by processor 820 of electronic device 800 to perform the above-described method. For example, the non-transitory computer readable storage medium may be ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.
In an exemplary embodiment, there is also provided a computer-readable storage medium having stored therein computer-executable instructions for performing the method of any one of the above embodiments by a processor.
In an exemplary embodiment, a computer program product is also provided, comprising a computer program for executing the method of any of the above embodiments by a processor.
It should be noted that, for simplicity of description, the foregoing method embodiments are all described as a series of acts, but it should be understood by those skilled in the art that the present application is not limited by the order of acts described, as some steps may be performed in other orders or concurrently in accordance with the present application. Further, those skilled in the art will also appreciate that the embodiments described in the specification are alternative embodiments, and that the acts and modules referred to are not necessarily required for the present application.
It should be further noted that, although the steps in the flowchart are sequentially shown as indicated by arrows, the steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least a portion of the steps in the flowcharts may include a plurality of sub-steps or stages that are not necessarily performed at the same time, but may be performed at different times, the order in which the sub-steps or stages are performed is not necessarily sequential, and may be performed in turn or alternately with at least a portion of the sub-steps or stages of other steps or other steps.
It will be appreciated that the device embodiments described above are merely illustrative and that the device of the application may be implemented in other ways. For example, the division of the units/modules in the above embodiments is merely a logic function division, and there may be another division manner in actual implementation. For example, multiple units, modules, or components may be combined, or may be integrated into another system, or some features may be omitted or not performed.
In addition, each functional unit/module in each embodiment of the present application may be integrated into one unit/module, or each unit/module may exist alone physically, or two or more units/modules may be integrated together, unless otherwise specified. The integrated units/modules described above may be implemented either in hardware or in software program modules.
The integrated units/modules, if implemented in hardware, may be digital circuits, analog circuits, etc. Physical implementations of hardware structures include, but are not limited to, transistors, memristors, and the like. The processor may be any suitable hardware processor, such as CPU, GPU, FPGA, DSP and ASIC, etc., unless otherwise specified. Unless otherwise indicated, the storage elements may be any suitable magnetic or magneto-optical storage medium, such as resistive Random Access Memory RRAM (Resistive Random Access Memory), dynamic Random Access Memory DRAM (Dynamic Random Access Memory), static Random Access Memory SRAM (Static Random-Access Memory), enhanced dynamic Random Access Memory EDRAM (Enhanced Dynamic Random Access Memory), high-Bandwidth Memory HBM (High-Bandwidth Memory), hybrid Memory cube HMC (Hybrid Memory Cube), etc.
The integrated units/modules may be stored in a computer readable memory if implemented in the form of software program modules and sold or used as a stand-alone product. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in whole or in part in the form of a software product stored in a memory, comprising several instructions for causing a computer device (which may be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method of the various embodiments of the present application. And the aforementioned memory includes: a U-disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a removable hard disk, a magnetic disk, or an optical disk, or other various media capable of storing program codes.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and for parts of one embodiment that are not described in detail, reference may be made to related descriptions of other embodiments. The technical features of the above embodiments may be combined in any way, and for brevity, all of the possible combinations of the technical features of the above embodiments are not described, but should be considered as the scope of the description
Other embodiments of the application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It is to be understood that the application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.
Claims (11)
1. A transaction playback processing method, the method comprising:
receiving a playback request sent by a terminal, analyzing the playback request, and acquiring transaction time and an application identifier;
acquiring actual transaction data corresponding to the application identifier and an actual transaction result corresponding to the actual transaction data based on the transaction time, wherein the actual transaction data comprises: log data and transaction environment data;
Preprocessing the log data to obtain log data to be played back, wherein the preprocessing comprises the following steps: screening, filtering and decrypting;
simulating an actual transaction environment based on the transaction environment data and a pre-configured test environment, and performing transaction playback processing in the simulated transaction environment by adopting a pre-configured MOCK tool based on the log data to be played back to obtain a simulation transaction result;
and analyzing the actual transaction result and the simulated transaction result to obtain corresponding analysis results, and sending the analysis results to the terminal.
2. The method of claim 1, wherein the obtaining actual transaction data corresponding to the application identifier and actual transaction results corresponding to the actual transaction data based on the transaction time comprises:
determining whether the application identifier is an application identifier corresponding to a local application;
if yes, searching actual transaction data matched with the transaction time and an actual transaction result corresponding to the actual transaction data in a local cache database, and acquiring the matched actual transaction data and the actual transaction result corresponding to the actual transaction data;
If not, acquiring actual transaction data matched with the transaction time and an actual transaction result corresponding to the actual transaction data from an external cache database corresponding to the external application.
3. The method of claim 1, wherein preprocessing the log data to obtain log data to be played back comprises:
acquiring a service type identifier and a key field corresponding to the service type identifier in the playback request, screening the log data based on the service type identifier, and acquiring first log data matched with the service type identifier;
filtering the matched first log data based on the key field to obtain second log data matched with the key field;
and decrypting the encrypted data in the matched second log data to obtain log data to be played back.
4. The method of claim 1, wherein the transaction context data comprises: bottom account data and snapshot data;
the simulating an actual transaction environment based on the transaction environment data and a pre-configured test environment, performing transaction playback processing in the simulated transaction environment by using a pre-configured MOCK tool based on the log data to be played back, and obtaining a simulated transaction result, including:
Importing the ledger data and the snapshot data into a pre-configured test environment to simulate an actual transaction environment;
performing transaction playback processing based on the log data by adopting a preconfigured playback tool in the simulated transaction environment;
in the process of transaction playback, for each transaction in the log data to be played back, acquiring actual transaction return information by adopting a pre-configured MOCK tool based on the transaction identifier corresponding to each transaction, determining a simulation transaction result of each transaction based on the actual transaction return information corresponding to each transaction and a matched pre-set business rule, and recording the transaction identifier corresponding to each transaction and the corresponding simulation transaction result in a data table until the transaction playback is completed, thereby acquiring a simulation transaction result table.
5. The method of claim 4, wherein the obtaining, for each transaction in the log data to be played back, actual transaction return information using a preconfigured MOCK tool based on a transaction identifier corresponding to the each transaction, comprises:
for each transaction in the log data to be replayed, reading actual transaction return information matched with the transaction identifier corresponding to the transaction in an actual transaction log in a local cache database by adopting a pre-configured MOCK tool based on the transaction identifier corresponding to the transaction;
The actual transaction log includes: the transaction identification corresponding to each transaction and the corresponding actual transaction return information.
6. The method of claim 4, wherein analyzing the actual transaction results and the simulated transaction results to obtain corresponding analysis results comprises:
comparing the simulated transaction result table with an actual transaction result table;
if the simulated transaction results in the simulated transaction result table are consistent with the corresponding actual transaction results in the actual transaction result table, the analysis result is successful in transaction playback;
and if any simulated transaction result in the simulated transaction result table is inconsistent with the corresponding actual transaction result in the actual transaction result table, the analysis result is that the transaction playback fails.
7. The method according to any one of claims 1 to 6, further comprising:
acquiring a playback processing type in the playback request, and determining a transaction playback processing mode based on the playback processing type;
if the playback processing type is partial link playback, performing transaction playback processing based on the log data in a simulated transaction environment by adopting a pre-configured MOCK tool;
And if the playback processing type is full-link playback, performing full-link transaction playback processing based on the log data in the simulated transaction environment.
8. A transaction playback processing device, the device comprising:
the receiving and transmitting unit is used for receiving a playback request sent by the terminal, analyzing the playback request and acquiring transaction time and application identification;
the acquiring unit is configured to acquire actual transaction data corresponding to the application identifier and an actual transaction result corresponding to the actual transaction data based on the transaction time, where the actual transaction data includes: log data and transaction environment data;
the processing unit is used for preprocessing the log data to obtain log data to be played back, and the preprocessing comprises the following steps: screening, filtering and decrypting;
the transaction playback unit is used for simulating an actual transaction environment based on the transaction environment data and a pre-configured test environment, and performing transaction playback processing in the simulated transaction environment by adopting a pre-configured MOCK tool based on the log data to be played back to obtain a simulation transaction result;
the processing unit is also used for analyzing the actual transaction result and the simulated transaction result to obtain a corresponding analysis result;
And the receiving and transmitting unit is also used for transmitting the analysis result to the terminal.
9. An electronic device, comprising: a processor, a memory, and a transceiver;
a processor, memory, and transceiver circuitry interconnect;
the memory stores computer-executable instructions;
a transceiver for transceiving data;
a processor executing computer-executable instructions stored in a memory, causing the processor to perform the method of any one of claims 1 to 7.
10. A computer readable storage medium having stored therein computer executable instructions which when executed by a processor are adapted to carry out the method of any one of claims 1 to 7.
11. A computer program product comprising a computer program which, when executed by a processor, implements the method of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311248218.4A CN117033246A (en) | 2023-09-26 | 2023-09-26 | Transaction playback processing method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311248218.4A CN117033246A (en) | 2023-09-26 | 2023-09-26 | Transaction playback processing method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117033246A true CN117033246A (en) | 2023-11-10 |
Family
ID=88624825
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311248218.4A Pending CN117033246A (en) | 2023-09-26 | 2023-09-26 | Transaction playback processing method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117033246A (en) |
-
2023
- 2023-09-26 CN CN202311248218.4A patent/CN117033246A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106170004A (en) | Process the method and device of identifying code | |
| RU2673401C2 (en) | Method and device for obtaining certification document | |
| CN115185717B (en) | Interface calling method and device, electronic equipment and storage medium | |
| CN106126592B (en) | Processing method and device for search data | |
| Tri et al. | Forensics acquisition and analysis method of imo messenger | |
| CN110809036B (en) | Resource updating method and device | |
| CN110213062B (en) | Method and device for processing message | |
| CN117033246A (en) | Transaction playback processing method, device, equipment and storage medium | |
| Silla | WeChat forensic artifacts: Android phone extraction and analysis | |
| CN114428737A (en) | Communication method, device, equipment and storage medium based on micro service system | |
| CN112667852B (en) | Video-based searching method and device, electronic equipment and storage medium | |
| CN106302002B (en) | Test method and device | |
| CN112463827B (en) | Query method, query device, electronic equipment and storage medium | |
| CN107256151A (en) | Processing method, device and the terminal of page rendering | |
| CN113378022A (en) | In-station search platform, search method and related device | |
| CN113362180B (en) | Customer information identification method, device and equipment for suspected nonstandard financial behavior | |
| CN113206772B (en) | Method, device, equipment, medium and product for judging correctness of response message | |
| Wang et al. | Integration of Mobile Forensic Tool Capabilities | |
| CN110119471B (en) | Method and device for checking consistency of search results | |
| CN117149649A (en) | Transaction testing method and device and electronic equipment | |
| CN116645052A (en) | Method, device, equipment and storage medium for auditing service information | |
| CN105976235A (en) | Information classification method and information classification device | |
| CN117493460A (en) | Data processing method, device and equipment applied to long-protection fund | |
| CN115455007A (en) | Data processing method, device, equipment and storage medium | |
| CN116009946A (en) | Git-based code statistics method and device |
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 |