CN114048145A - Transaction checking test method and device, electronic equipment and storage medium - Google Patents
Transaction checking test method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN114048145A CN114048145A CN202111422744.9A CN202111422744A CN114048145A CN 114048145 A CN114048145 A CN 114048145A CN 202111422744 A CN202111422744 A CN 202111422744A CN 114048145 A CN114048145 A CN 114048145A
- Authority
- CN
- China
- Prior art keywords
- reconciliation
- file
- report
- batch
- generating
- 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
- 238000010998 test method Methods 0.000 title claims abstract description 21
- 238000012360 testing method Methods 0.000 claims abstract description 70
- 238000012795 verification Methods 0.000 claims description 33
- 238000000034 method Methods 0.000 claims description 20
- 238000012544 monitoring process Methods 0.000 claims description 9
- 238000004590 computer program Methods 0.000 claims description 4
- 238000011144 upstream manufacturing Methods 0.000 description 11
- 238000010586 diagram Methods 0.000 description 9
- 230000006870 function Effects 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 238000004891 communication Methods 0.000 description 2
- 238000013479 data entry Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 238000002360 preparation method Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Prevention of errors by analysis, debugging or testing of software
- G06F11/3668—Testing of software
- G06F11/3696—Methods or tools to render software testable
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Prevention of errors by analysis, debugging or testing of software
- G06F11/3668—Testing of software
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application discloses a transaction checking test method and device, electronic equipment and a storage medium, which can be applied to the financial field or other fields, wherein the transaction checking test method comprises the following steps: generating account checking files of a requesting party and a serving party based on a predefined interface file; resetting the account checking scene to be in a batch running state; calling a pre-compiled batch reconciliation program to perform reconciliation based on the reconciliation file; acquiring reconciliation result information after batch reconciliation and a generated report file; and respectively comparing the reconciliation result information and the report file with a real reconciliation result to generate a test report.
Description
Technical Field
The present disclosure relates to the field of program testing, and in particular, to a transaction verification testing method and apparatus, an electronic device, and a storage medium.
Background
In order to improve efficiency and accuracy of transaction checking, namely account checking, enterprises in current needs start to adopt application systems to automatically check accounts. And in order to ensure the accuracy of account checking of the application system, a test is required.
The existing test method for checking account mainly receives the checking account files sent by the system of the requester and the server for transaction checking, and manually calls the batch checking account program of the system for checking account after manually checking the correct data. And finally, verifying whether the transactions of the two parties are matched and whether the generated report file is correct according to the generated reconciliation result file.
However, the mode needs to rely on the reconciliation file sent by the system of the upstream system, has high coupling degree with the upstream system, can test the reconciliation file after the reconciliation file is issued by the upstream system, and carries out matching verification of results through manual work, so that the efficiency of the existing mode is relatively low.
Disclosure of Invention
Based on the defects of the prior art, the application provides a transaction checking test method and device, electronic equipment and a storage medium, so as to solve the problem that the efficiency of the existing transaction checking test method is relatively low.
In order to achieve the above object, the present application provides the following technical solutions:
the first aspect of the present application provides a transaction verification testing method, including:
generating account checking files of a requesting party and a serving party based on a predefined interface file;
resetting the account checking scene to be in a batch running state;
calling a pre-compiled batch reconciliation program to perform reconciliation based on the reconciliation file;
acquiring reconciliation result information after batch reconciliation and a generated report file;
and respectively comparing the reconciliation result information and the report file with a real reconciliation result to generate a test report.
Optionally, in the transaction verification test method, after the calling a pre-compiled batch reconciliation program to perform reconciliation based on the reconciliation file, the method further includes:
monitoring whether the batch reconciliation program is executed in real time;
if the batch reconciliation program execution is monitored to be finished, judging whether reconciliation result information and a report file are generated or not;
and if the generated reconciliation result information and the report file are judged, executing the reconciliation result information after batch reconciliation and the generated report file.
Optionally, in the transaction verification testing method, the generating a reconciliation file of the requester and the server based on a predefined interface file includes:
generating a reconciliation file template based on a predefined interface file; the interface file is obtained by defining in advance according to the reconciliation agreement between the requester and the server;
and writing a plurality of transaction data into the account checking file template based on the interface file to obtain the account checking files of the requesting party and the service party.
Optionally, in the transaction verification testing method, the generating a test report by comparing the reconciliation result information and the report file with the real reconciliation result respectively includes:
analyzing target information in a target field from the account checking result information and the report file respectively;
comparing each target information with corresponding information in the real reconciliation result to obtain a comparison result;
and generating a test report by using the comparison result.
A second aspect of the present application provides a transaction verification testing apparatus, including:
the file generation unit is used for generating reconciliation files of the requester and the server based on a predefined interface file;
the resetting unit is used for resetting the account checking scene to be in a batch running state;
the calling unit is used for calling a pre-compiled batch reconciliation program so as to carry out reconciliation based on the reconciliation file;
the acquisition unit is used for acquiring reconciliation result information after batch reconciliation and the generated report file;
and the report generating unit is used for generating a test report by respectively comparing the reconciliation result information and the report file with a real reconciliation result.
Optionally, in the above transaction verification testing apparatus, further comprising:
the monitoring unit is used for monitoring whether the batch reconciliation program is executed in real time;
the judging unit is used for judging whether account checking result information and a report file are generated or not if the execution of the batch account checking program is monitored to be finished;
if the generated reconciliation result information and the generated report file are judged, the acquisition unit executes the reconciliation result information after batch reconciliation and the generated report file.
Optionally, in the above transaction verification testing apparatus, the file generating unit includes:
the template generating unit is used for generating a reconciliation file template based on a predefined interface file; the interface file is obtained by defining in advance according to the reconciliation agreement between the requester and the server;
and the filling unit is used for writing a plurality of transaction data into the account checking file template based on the interface file to obtain the account checking files of the requesting party and the service party.
Optionally, in the above transaction verification testing apparatus, the report generating unit includes:
the analysis unit is used for analyzing the target information in the target field from the account checking result information and the report file respectively;
the comparison unit is used for comparing each target information with corresponding information in the real reconciliation result to obtain a comparison result;
and the generating subunit is used for generating a test report by using the comparison result.
A third aspect of the present application provides an electronic device comprising:
a memory and a processor;
wherein the memory is used for storing programs;
the processor is configured to execute the program, which when executed is particularly configured to implement the transaction verification testing method as described in any of the above.
A fourth aspect of the present application provides a computer storage medium storing a computer program which, when executed, is operable to implement a transaction verification test method as claimed in any one of the preceding claims.
According to the transaction checking test method, the account checking files of the requesting party and the service party are generated based on the predefined interface file, so that the upstream system is simulated to generate the account checking files, the upstream system is not required to issue the account checking files, and the decoupling with the upstream system is realized. And then resetting the reconciliation scene to be in a non-batch running state, calling a pre-compiled batch reconciliation program to perform reconciliation based on the reconciliation file, finally acquiring reconciliation result information after batch reconciliation and a generated report file, and generating a test report by respectively comparing the reconciliation result information and the report file with a real reconciliation result. Therefore, manual calling of batch reconciliation programs is not needed, automatic comparison of the checking results and automatic generation of test reports are realized, and the efficiency of transaction checking tests is effectively improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
FIG. 1 is a block diagram of a transaction verification test system according to an embodiment of the present disclosure;
FIG. 2 is a flow chart of a transaction reconciliation test method according to an embodiment of the present application;
fig. 3 is a flowchart of a method for generating a reconciliation file according to an embodiment of the present application;
FIG. 4 is a flowchart of a method for generating a test report according to an embodiment of the present application;
FIG. 5 is a flow chart of another transaction reconciliation test method according to another embodiment of the present application;
FIG. 6 is a schematic diagram of a transaction verification testing apparatus according to another embodiment of the present application;
fig. 7 is a schematic structural diagram of a file generation unit according to another embodiment of the present application;
fig. 8 is a schematic structural diagram of a report generation unit according to another embodiment of the present application;
fig. 9 is a schematic structural diagram of an electronic device according to another embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, 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 application.
The term "include" and variations thereof as used herein are open-ended, i.e., "including but not limited to". The term "based on" is "based, at least in part, on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions for other terms will be given in the following description.
It should be noted that the terms "first", "second", and the like in the present disclosure are only used for distinguishing different devices, modules or units, and are not used for limiting the order or interdependence relationship of the functions performed by the devices, modules or units.
It is noted that references to "a", "an", and "the" modifications in this disclosure are intended to be illustrative rather than limiting, and that those skilled in the art will recognize that "one or more" may be used unless the context clearly dictates otherwise.
The application provides a transaction checking test method, which aims to solve the problem that the efficiency of the existing transaction checking test method is relatively low.
Optionally, in order to implement the transaction verification testing method provided by the present application, an embodiment of the present application provides a transaction verification testing system.
Optionally, the transaction verification test system provided in the embodiment of the present application may be implemented based on an automated test framework robotframe.
The robotframe is an automatic testing frame written based on python, adopts a keyword driving mode, uses a table to organize a testing process and testing data, and has good expandability. Basic functions such as organization and operation of test cases and generation of test reports are provided, so that robotframe is realized through an automatic test framework, and convenience is brought. This is of course only one option and other tools may be used.
In addition, the transaction verification test system provided in the embodiment of the present application may further use a SSHLibrary remote operation linux system as a test support library, and use a database library to operate a database.
As shown in fig. 1, the transaction verification testing system provided in the embodiment of the present application specifically includes:
a data layer, a communication layer and an analysis layer.
Wherein, the data layer is mainly used for data entry and accuracy before batching.
In the data entry process, the robotframe can be connected with a background server to automatically generate the account checking file. Specifically, according to an interface defined in a reconciliation file agreed by the transaction checking system, transaction data is written into the reconciliation file, and the reconciliation file of an upstream system is simulated, so that the decoupling with the upstream system is realized.
The preparation before batch can be realized by connecting a database through robotframe, resetting the account checking scene to be a non-batch running condition according to a preset batch running precondition, namely the precondition for executing the batch account checking program, and carrying out some precondition works of batch account checking layer program operation, such as switching of test environment and the like, before the batch account checking program is executed each time, so that the circular execution of the automatic case can be ensured.
The communication layer is mainly used for calling a pre-compiled batch account checking program to check accounts. The batch reconciliation program can be a shell script.
Optionally, the robotframe can be connected with a background server, and then the written shell script is called, so that the batch reconciliation program is automatically called to complete the reconciliation.
The analysis layer mainly analyzes and compares results and is used for generating a test report.
In the result analysis and comparison process, the checking result information after the batch checking program is executed and the generated report file are distributed, and the fields needing to be compared are analyzed. Then, the analyzed field is compared with an actual result, so that an automatic comparison effect is achieved.
When the test report is generated, the test report is automatically generated mainly according to the running condition of the program.
The tester can conveniently and quickly analyze the test result through the test report, and for the test failure case, the tester can visually check the comparison between the actual result and the expected result, so that the problem is analyzed, and the problem is quickly positioned.
Based on the transaction verification test system provided above, another embodiment of the present application provides a transaction verification test method, as shown in fig. 2, including the following steps:
s201, generating account checking files of the requesting party and the service party based on the predefined interface files.
The predefined interface file is a file defined in advance based on the reconciliation contract of the requester and the server. The result file may include information such as format and type of data.
The requestor and the server refer to both parties involved in the transaction check.
Optionally, in another embodiment of the present application, as shown in fig. 3, a specific implementation manner of step S201 includes:
s301, generating a reconciliation file template based on a predefined interface file.
The interface file is defined in advance according to the reconciliation agreement between the requesting party and the service party.
Specifically, a file template in which transaction data is not stored is generated according to a requirement for the control file in the predefined interface file, and then step S302 is executed.
S302, writing a plurality of transaction data into the reconciliation file template based on the interface file to obtain the reconciliation files of the requester and the server.
Specifically, based on the requirement for the transaction data in the interface file, a plurality of transaction data are generated, and the generated transaction data are filled into a comparison file template to obtain a comparison file.
It should be noted that, when generating transaction data, it is necessary to simulate the transaction data of the generation requesting party and the transaction data of the corresponding service party.
And S202, resetting the reconciliation scene to be in a batch running state.
It should be noted that, since the test is not performed only once, in order to ensure that the previous test does not affect the result of the current test, it is necessary to reset each parameter of the comparison scenario to a state of no batch running, that is, to reset the state back to the state when the multi-batch reconciliation program is not executed.
And S203, calling a pre-compiled batch reconciliation program to perform reconciliation based on the reconciliation file.
Alternatively, the pre-compiled match-and-compare program may be a shell script.
Specifically, a pre-compiled batch reconciliation program is called, and the batch reconciliation program is executed. When the batch account checking program is executed, the transaction data in the account checking file are compared, and the compared result information, namely the account checking result information, is output.
And S204, acquiring reconciliation result information after batch reconciliation and the generated report file.
It should be noted that, when the batch reconciliation program is executed, the reconciliation file is subjected to batch reconciliation, at this time, reconciliation result information, that is, whether the transaction data is successfully matched or not, is correspondingly generated, and according to the reconciliation condition, a report file is generated, which specifically includes parameters such as a matching rate, and which specifically can be set as required.
And S205, comparing the reconciliation result information and the report file with the real reconciliation result respectively to generate a test report.
It should be noted that the result obtained by executing the batch reconciliation file is not necessarily accurate, so that the result can be compared with the real reconciliation result, and a test report is generated based on the comparison result and fed back to the tester.
Optionally, in another embodiment of the present application, a specific implementation manner of step S205, as shown in fig. 4, includes the following steps:
s401, analyzing target information in the target field from the account checking result information and the report file respectively.
Wherein the target field refers to a pre-specified field. The target information refers to information in a target field.
Specifically, the reconciliation result information and the report file are analyzed, and the target information in the target field is extracted from the parsed reconciliation result information and the report file.
S402, comparing each target information with corresponding information in the real reconciliation result to obtain a comparison result.
And respectively comparing information which is associated with the target field where the target information is located in the real reconciliation result with the target information aiming at each target information, determining whether the two information are consistent or not, and obtaining a comparison result.
And S403, generating a test report by using the comparison result.
According to the transaction checking test method provided by the embodiment of the application, the account checking files of the requesting party and the service party are generated based on the predefined interface file, so that the upstream system is simulated to generate the account checking files, the account checking files do not need to be issued by the upstream system, and the decoupling with the upstream system is realized. And then resetting the reconciliation scene to be in a non-batch running state, calling a pre-compiled batch reconciliation program to perform reconciliation based on the reconciliation file, finally acquiring reconciliation result information after batch reconciliation and a generated report file, and generating a test report by respectively comparing the reconciliation result information and the report file with a real reconciliation result. Therefore, manual calling of batch reconciliation programs is not needed, automatic comparison of the checking results and automatic generation of test reports are realized, and the efficiency of transaction checking tests is effectively improved.
Another embodiment of the present application provides another transaction verification testing method, as shown in fig. 5, including the following steps:
s501, generating reconciliation files of the requester and the server based on the predefined interface files.
It should be noted that, for the specific implementation of step S501, reference may be made to step S201 in the foregoing method embodiment, and details are not described here again.
And S502, resetting the account checking scene to be in a batch running state.
It should be noted that, for the specific implementation of step S502, reference may be made to step S202 in the foregoing method embodiment, and details are not described here again.
S503, calling a pre-compiled batch reconciliation program to perform reconciliation based on the reconciliation file.
It should be noted that, in the specific implementation of step S503, reference may be made to step S203 in the foregoing method embodiment, which is not described herein again.
And S504, monitoring whether the batch reconciliation program is executed in real time.
It should be noted that the reconciliation result is continuously generated in the process of executing the batch reconciliation program, but the comparison needs to be performed after all results are obtained, so that in the embodiment of the present application, it is summarized to monitor whether the execution of the batch reconciliation program is finished in real time, and if it is monitored that the execution of the batch reconciliation program is finished, the step S505 is executed.
And S505, judging whether account checking result information and a report file are generated.
In the program execution process, the reconciliation result information and the report file may not be generated due to other reasons, and the subsequent steps cannot be executed, so that it is necessary to determine whether to generate the reconciliation result information and the report file. If the reconciliation result information and the report file are determined to be generated, step S506 is executed.
Optionally, if it is determined that the reconciliation result information or the report file is not generated, feeding back prompt information to the user to prompt the user that the reconciliation result information or the report file cannot be generated.
S506, obtaining the reconciliation result information after batch reconciliation and the generated report file.
And S507, analyzing the target information in the target field from the account checking result information and the report file respectively.
It should be noted that, for the specific implementation of step S507, reference may be made to step S401 in the foregoing method embodiment, and details are not described here again.
And S508, comparing each target information with corresponding information in the real reconciliation result to obtain a comparison result.
It should be noted that, in the specific implementation of step S508, reference may be made to step S402 in the foregoing method embodiment, and details are not described here again.
And S509, generating a test report by using the comparison result.
It should be noted that, in the specific implementation of step S509, reference may be made to step S403 in the foregoing method embodiment, and details are not described here again.
It is to be noted that the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Although the operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous.
Another embodiment of the present application provides a transaction verification testing apparatus, as shown in fig. 6, including the following units:
the file generating unit 601 is configured to generate reconciliation files of the requester and the server based on a predefined interface file.
A resetting unit 602, configured to reset the reconciliation scenario to a non-batched state.
And an invoking unit 603, configured to invoke a precompiled batch reconciliation program to perform reconciliation based on the reconciliation file.
An obtaining unit 604, configured to obtain reconciliation result information after batch reconciliation and the generated report file.
A report generating unit 605, configured to generate a test report by comparing the reconciliation result information and the report file with a real reconciliation result respectively.
Optionally, in a transaction verification testing apparatus provided in another embodiment of the present application, further includes:
and the monitoring unit is used for monitoring whether the batch reconciliation program is executed and finished in real time.
And the judging unit is used for judging whether account checking result information and a report file are generated or not if the execution of the batch account checking program is monitored to be finished.
If the generated reconciliation result information and the generated report file are judged, the acquisition unit executes the reconciliation result information after batch reconciliation and the generated report file.
Optionally, in a transaction verification testing apparatus provided in another embodiment of the present application, as shown in fig. 7, the file generating unit includes:
a template generating unit 701, configured to generate a reconciliation file template based on a predefined interface file.
And the interface file is obtained by defining in advance according to the reconciliation agreement between the requesting party and the service party.
And the filling unit 702 is configured to write multiple transaction data into the reconciliation file template based on the interface file, so as to obtain a reconciliation file of the requester and the server.
Optionally, in a transaction verification testing apparatus provided in another embodiment of the present application, the report generating unit, as shown in fig. 8, includes:
an analyzing unit 801, configured to analyze target information in the target field from the reconciliation result information and the report file, respectively.
A comparing unit 802, configured to compare each piece of target information with corresponding information in the real reconciliation result, so as to obtain a comparison result.
A generating subunit 803, configured to generate a test report by using the comparison result.
It should be noted that each unit provided in the foregoing embodiments of the present application may be a component in each layer of the transaction verification test system shown in fig. 1, and specific operations of each unit may refer to corresponding steps summarized in the foregoing method embodiments, which are not described herein again.
Another embodiment of the present application provides an electronic device, as shown in fig. 9, including:
a memory 901 and a processor 902.
The memory 901 is used for storing programs.
The processor 902 is configured to execute the program stored in the memory 901, and when the program is executed, the program is specifically configured to implement the transaction verification test method provided in any one of the above-mentioned embodiments.
Another embodiment of the present application provides a computer storage medium for storing a computer program, which when executed, is used to implement the transaction verification testing method provided in any one of the above embodiments.
Computer storage media, including permanent and non-permanent, removable and non-removable media, may implement the 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, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should be noted that the transaction verification test method and apparatus, the electronic device, and the storage medium provided by the present application may be used in the financial field. The above description is only an example, and does not limit the application fields of the transaction verification test method and apparatus, the electronic device, and the storage medium provided in the present application.
Those of skill would further appreciate that the various illustrative elements 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 various illustrative components and steps 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 implementation. 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 application.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A transaction reconciliation test method comprising:
generating account checking files of a requesting party and a serving party based on a predefined interface file;
resetting the account checking scene to be in a batch running state;
calling a pre-compiled batch reconciliation program to perform reconciliation based on the reconciliation file;
acquiring reconciliation result information after batch reconciliation and a generated report file;
and respectively comparing the reconciliation result information and the report file with a real reconciliation result to generate a test report.
2. The method of claim 1, wherein after invoking the pre-compiled batch reconciliation program to reconcile based on the reconciliation file, further comprising:
monitoring whether the batch reconciliation program is executed in real time;
if the batch reconciliation program execution is monitored to be finished, judging whether reconciliation result information and a report file are generated or not;
and if the generated reconciliation result information and the report file are judged, executing the reconciliation result information after batch reconciliation and the generated report file.
3. The method of claim 1, wherein generating reconciliation files for the requestor and the server based on the predefined interface file comprises:
generating a reconciliation file template based on a predefined interface file; the interface file is obtained by defining in advance according to the reconciliation agreement between the requester and the server;
and writing a plurality of transaction data into the account checking file template based on the interface file to obtain the account checking files of the requesting party and the service party.
4. The method of claim 1, wherein the generating a test report by comparing the reconciliation result information and the report file with the actual reconciliation result respectively comprises:
analyzing target information in a target field from the account checking result information and the report file respectively;
comparing each target information with corresponding information in the real reconciliation result to obtain a comparison result;
and generating a test report by using the comparison result.
5. A transaction verification test device, comprising:
the file generation unit is used for generating reconciliation files of the requester and the server based on a predefined interface file;
the resetting unit is used for resetting the account checking scene to be in a batch running state;
the calling unit is used for calling a pre-compiled batch reconciliation program so as to carry out reconciliation based on the reconciliation file;
the acquisition unit is used for acquiring reconciliation result information after batch reconciliation and the generated report file;
and the report generating unit is used for generating a test report by respectively comparing the reconciliation result information and the report file with a real reconciliation result.
6. The apparatus of claim 5, further comprising:
the monitoring unit is used for monitoring whether the batch reconciliation program is executed in real time;
the judging unit is used for judging whether account checking result information and a report file are generated or not if the execution of the batch account checking program is monitored to be finished; if the generated reconciliation result information and the generated report file are judged, the acquisition unit executes the reconciliation result information after batch reconciliation and the generated report file.
7. The apparatus of claim 5, wherein the file generation unit comprises:
the template generating unit is used for generating a reconciliation file template based on a predefined interface file; the interface file is obtained by defining in advance according to the reconciliation agreement between the requester and the server;
and the filling unit is used for writing a plurality of transaction data into the account checking file template based on the interface file to obtain the account checking files of the requesting party and the service party.
8. The apparatus of claim 5, wherein the report generating unit comprises:
the analysis unit is used for analyzing the target information in the target field from the account checking result information and the report file respectively;
the comparison unit is used for comparing each target information with corresponding information in the real reconciliation result to obtain a comparison result;
and the generating subunit is used for generating a test report by using the comparison result.
9. An electronic device, comprising:
a memory and a processor;
wherein the memory is used for storing programs;
the processor is adapted to execute the program, which when executed is particularly adapted to implement the transaction verification testing method of any one of claims 1 to 4.
10. A computer storage medium storing a computer program which, when executed, implements a transaction reconciliation test method according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111422744.9A CN114048145A (en) | 2021-11-26 | 2021-11-26 | Transaction checking test method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111422744.9A CN114048145A (en) | 2021-11-26 | 2021-11-26 | Transaction checking test method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114048145A true CN114048145A (en) | 2022-02-15 |
Family
ID=80211302
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111422744.9A Pending CN114048145A (en) | 2021-11-26 | 2021-11-26 | Transaction checking test method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114048145A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115082178A (en) * | 2022-06-28 | 2022-09-20 | 平安银行股份有限公司 | Reconciliation and settlement method, system, electronic device and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107797933A (en) * | 2017-11-22 | 2018-03-13 | 中国银行股份有限公司 | Generate the method and device of analog message |
| CN107943692A (en) * | 2017-11-17 | 2018-04-20 | 中国银行股份有限公司 | The automatic test approach and device that a kind of batch original table passes down |
| CN110716870A (en) * | 2019-09-23 | 2020-01-21 | 中国建设银行股份有限公司 | Automatic service testing method and device |
| CN111639028A (en) * | 2020-05-26 | 2020-09-08 | 深圳乐信软件技术有限公司 | Account checking rule script test method, device, engine and storage medium |
| US11030565B1 (en) * | 2020-05-18 | 2021-06-08 | Grant Thornton Llp | System and method for audit report generation from structured data |
-
2021
- 2021-11-26 CN CN202111422744.9A patent/CN114048145A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107943692A (en) * | 2017-11-17 | 2018-04-20 | 中国银行股份有限公司 | The automatic test approach and device that a kind of batch original table passes down |
| CN107797933A (en) * | 2017-11-22 | 2018-03-13 | 中国银行股份有限公司 | Generate the method and device of analog message |
| CN110716870A (en) * | 2019-09-23 | 2020-01-21 | 中国建设银行股份有限公司 | Automatic service testing method and device |
| US11030565B1 (en) * | 2020-05-18 | 2021-06-08 | Grant Thornton Llp | System and method for audit report generation from structured data |
| CN111639028A (en) * | 2020-05-26 | 2020-09-08 | 深圳乐信软件技术有限公司 | Account checking rule script test method, device, engine and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 余开华: "银联对账系统自动化测试的设计与实现", 《中国优秀硕士学位论文全文数据库 (信息科技辑)》, no. 6, 15 June 2015 (2015-06-15) * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115082178A (en) * | 2022-06-28 | 2022-09-20 | 平安银行股份有限公司 | Reconciliation and settlement method, system, electronic device and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107122258B (en) | Method and equipment for checking state code of test interface | |
| CN107122296B (en) | Method and apparatus for data assertion for test interface | |
| CN107480039B (en) | Small file read-write performance test method and device for distributed storage system | |
| CN107092535B (en) | Method and apparatus for data storage of test interface | |
| CN111209206B (en) | Automatic test method and system for software products | |
| CN111444093B (en) | Method and device for determining quality of project development process and computer equipment | |
| CN109388564B (en) | Test method and device and electronic equipment | |
| CN114048145A (en) | Transaction checking test method and device, electronic equipment and storage medium | |
| CN113238940B (en) | Interface test result comparison method, device, equipment and storage medium | |
| CN110147313B (en) | Log output method and device | |
| CN116662317A (en) | Data verification method and device, processor and electronic equipment | |
| CN107622013B (en) | Distributed system testing method and device | |
| CN113986764A (en) | Data checking test method and device, electronic equipment and storage medium | |
| CN116738091A (en) | Page monitoring method and device, electronic equipment and storage medium | |
| CN114490361A (en) | Test script quality obtaining method and device, computer equipment and storage medium | |
| CN113535841A (en) | Data verification method, device and equipment and computer readable storage medium | |
| CN114637685A (en) | Performance test method, device, equipment and medium of application program in bank system | |
| CN110765006A (en) | Flow testing method and device, computer readable storage medium and electronic device | |
| CN113722355A (en) | Test method and device for service data processing, electronic equipment and storage medium | |
| CN113515401B (en) | Positioning and debugging method, system, electronic equipment and medium for abnormal transaction | |
| CN112307131B (en) | Equipment inspection method, system, electronic equipment and storage medium | |
| CN119149435A (en) | Software testing method, device, electronic device and storage medium | |
| CN113743948A (en) | Method and device for generating transaction information file, electronic equipment and storage medium | |
| CN116089266A (en) | Method and device for detecting abnormal processing of application interface | |
| CN115098381A (en) | Message template generation method and device, electronic equipment and computer storage medium |
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 |