CN114064488A - Transaction testing method, device, storage medium and equipment - Google Patents
Transaction testing method, device, storage medium and equipment Download PDFInfo
- Publication number
- CN114064488A CN114064488A CN202111370195.5A CN202111370195A CN114064488A CN 114064488 A CN114064488 A CN 114064488A CN 202111370195 A CN202111370195 A CN 202111370195A CN 114064488 A CN114064488 A CN 114064488A
- Authority
- CN
- China
- Prior art keywords
- transaction
- result
- input
- parameters
- test
- 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
- 238000012360 testing method Methods 0.000 title claims abstract description 132
- 238000012545 processing Methods 0.000 claims abstract description 21
- 238000000034 method Methods 0.000 claims description 15
- 238000012795 verification Methods 0.000 claims description 7
- 238000012423 maintenance Methods 0.000 claims description 5
- 238000011161 development Methods 0.000 abstract description 12
- 238000013500 data storage Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000005856 abnormality Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000002360 preparation method Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000010998 test method Methods 0.000 description 1
- 238000012546 transfer Methods 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—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- 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
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/166—Editing, e.g. inserting or deleting
- G06F40/177—Editing, e.g. inserting or deleting of tables; using ruled lines
- G06F40/18—Editing, e.g. inserting or deleting of tables; using ruled lines of spreadsheets
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Computer Hardware Design (AREA)
- Health & Medical Sciences (AREA)
- Artificial Intelligence (AREA)
- Audiology, Speech & Language Pathology (AREA)
- Computational Linguistics (AREA)
- General Health & Medical Sciences (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application discloses a transaction testing method, a transaction testing device, a storage medium and transaction testing equipment, which can be applied to the field of network security. And acquiring transaction input data from the input area, and processing the transaction input data to obtain a transaction message. And acquiring a transaction expected result from the output area, and processing the transaction expected result to obtain a standard transaction result. And sending the transaction message to a preset transaction system, triggering the preset transaction system to call transaction parameters in a database table, and executing a transaction service shown by the transaction message to obtain a transaction result. And under the condition that the transaction result is the same as the standard transaction result, sending a transaction test success prompt to the user. Based on the scheme shown in the application, the user can realize different transaction tests without modifying the test program, so that the development workload of the test program is effectively reduced.
Description
Technical Field
The present application relates to the field of network security, and in particular, to a transaction testing method, apparatus, storage medium, and device.
Background
In the project development process, transaction testing is required after a complete transaction is developed, the transaction testing generally analyzes various transaction scenes related to the transaction, different transaction parameters are prepared according to the difference of the transaction scenes, then specific transaction input data are input, and finally a transaction result is taken for verification, and the series of processes of preparing data and verifying the result are required to be manually written with additional testing programs. The transaction scenario of individual transaction test may be very complex, and different transaction scenarios need to be coded differently, which results in frequent modification of the test program, which not only results in a large development workload of the test program, but also results in program errors.
Therefore, how to reduce the development workload of the test program becomes an urgent problem to be solved in the field.
Disclosure of Invention
The application provides a transaction testing method, a transaction testing device, a storage medium and equipment, and aims to reduce the development workload of a testing program.
In order to achieve the above object, the present application provides the following technical solutions:
a transaction testing method, comprising:
generating an electronic form according to test data input by a user in advance; wherein the test data comprises transaction parameters, transaction input data and expected transaction results; the spreadsheet comprises a parameter area, an input area and an output area; the parameter area is used for recording the transaction parameters; the input area is used for recording the transaction input data; the output area is used for recording the expected result of the transaction;
under the condition that a test instruction input by the user is received, acquiring the transaction parameters from the parameter area, and writing the transaction parameters into a preset database table;
acquiring the transaction input data from the input area, and processing the transaction input data according to a preset transaction input message format to obtain a transaction message;
acquiring the expected transaction result from the output area, and processing the expected transaction result according to a preset transaction output message format to obtain a reference transaction result;
sending the transaction message to a preset transaction system, triggering the preset transaction system to call the transaction parameters shown in the database table, and executing the transaction service shown in the transaction message to obtain a transaction result;
and under the condition that the transaction result is the same as the benchmark transaction result, sending a transaction test success prompt to the user.
Optionally, the obtaining the transaction parameter from the parameter area and writing the transaction parameter into a preset database table when the test instruction input by the user is received includes:
and under the condition of receiving the test instruction input by the user, acquiring the transaction parameters containing the transaction codes shown by the test instruction from the parameter area, and writing the transaction parameters containing the transaction codes shown by the test instruction into a preset database table.
Optionally, the method further includes:
and sending a transaction test failure prompt to the user under the condition that the transaction result is different from the benchmark transaction result.
Optionally, the method further includes:
deleting the transaction parameters in the database table.
A transaction testing device comprising:
the data maintenance unit is used for generating an electronic form according to test data input by a user in advance; wherein the test data comprises transaction parameters, transaction input data and expected transaction results; the spreadsheet comprises a parameter area, an input area and an output area; the parameter area is used for recording the transaction parameters; the input area is used for recording the transaction input data; the output area is used for recording the expected result of the transaction;
the data loading unit is used for acquiring the transaction parameters from the parameter area under the condition of receiving the test instruction input by the user and writing the transaction parameters into a preset database table;
the data loading unit is further configured to: acquiring the transaction input data from the input area, and processing the transaction input data according to a preset transaction input message format to obtain a transaction message;
the data loading unit is further configured to: acquiring the expected transaction result from the output area, and processing the expected transaction result according to a preset transaction output message format to obtain a reference transaction result;
the transaction execution unit is used for sending the transaction message to a preset transaction system, triggering the preset transaction system to call the transaction parameters shown in the database table, and executing the transaction service shown in the transaction message to obtain a transaction result;
and the result verification unit is used for sending a transaction test success prompt to the user under the condition that the transaction result is the same as the standard transaction result.
Optionally, the data loading unit is specifically configured to:
and under the condition of receiving the test instruction input by the user, acquiring the transaction parameters containing the transaction codes shown by the test instruction from the parameter area, and writing the transaction parameters containing the transaction codes shown by the test instruction into a preset database table.
Optionally, the result verification unit is further configured to:
and sending a transaction test failure prompt to the user under the condition that the transaction result is different from the benchmark transaction result.
Optionally, the method further includes:
and the data clearing unit is used for deleting the transaction parameters in the database table.
A computer-readable storage medium comprising a stored program, wherein the program executes the transaction testing method.
A transaction testing device comprising: a processor, a memory, and a bus; the processor and the memory are connected through the bus;
the memory is used for storing a program, and the processor is used for executing the program, wherein the program executes the transaction testing method during running.
According to the technical scheme, the electronic form is generated according to the test data input by the user in advance. The electronic form comprises a parameter area, an input area and an output area, wherein the parameter area is used for recording transaction parameters, the input area is used for recording transaction input data, and the output area is used for recording transaction expected results. And under the condition of receiving a test instruction input by a user, acquiring transaction parameters from the parameter area, and writing the transaction parameters into a preset database table. And acquiring transaction input data from the input area, and processing the transaction input data according to a preset transaction input message format to obtain a transaction message. And acquiring a transaction expected result from the output area, and processing the transaction expected result according to a preset transaction output message format to obtain a reference transaction result. And sending the transaction message to a preset transaction system, triggering the preset transaction system to call the transaction parameters shown in the database table, and executing the transaction service shown in the transaction message to obtain a transaction result. And under the condition that the transaction result is the same as the standard transaction result, sending a transaction test success prompt to the user. Based on the scheme shown in the application, the user can realize different transaction tests without modifying the test program, so that the development workload of the test program is effectively reduced.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic flow chart of a transaction testing method according to an embodiment of the present application;
FIG. 2 is a schematic flow chart illustrating another transaction testing method according to an embodiment of the present disclosure;
FIG. 3 is a block diagram of a transaction testing device according to an embodiment of the present disclosure;
fig. 4 is a schematic structural diagram of a transaction testing device according to an embodiment of the present disclosure.
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 applicant found that: aiming at the data diversity of different transaction scenes, the transaction test program needs to be frequently modified, and the risk of program errors and the development workload are increased. Secondly, before the transaction is executed, the required test data (including transaction parameters and transaction input data) needs to be manually written into the database, and the risk of misoperation is increased by directly operating the database; the test data after each use still need be cleared up after transaction test procedure uses up, otherwise these data will become invalid data to pollute the database, simultaneously, manual operation often can't guarantee can in time clear up invalid data after the test is accomplished. In addition, for the same transaction test, because the processing logic is the same, the used test data sources are the same, but there are differences in different transaction scenarios, so that the test data preparation needs to be performed again for each different transaction scenario, and the data reuse rate is low. Finally, the transaction results output after the transaction is completed need to be checked manually, one is low in efficiency, and the other is that some differences which are difficult to be identified by naked eyes (data have distinguishing data types, such as 1 with a numerical type and 1 with a character type) are easy to ignore inconsistency in the transaction results, and the abnormality cannot be found in time.
Based on the findings of the applicant, the embodiment of the present application provides a transaction testing method, which is used for reducing the development workload of a testing program and avoiding the error risk caused by manual testing.
As shown in fig. 1, a schematic flow chart of a transaction testing method provided in the embodiment of the present application includes the following steps:
s101: and generating an electronic form (excel) according to the test data input by the user.
The test data comprises transaction parameters, transaction input data and expected transaction results. The electronic form comprises a parameter area, an input area and an output area, wherein the parameter area is used for recording transaction parameters, the input area is used for recording transaction input data, and the output area is used for recording expected results of transactions.
It should be noted that the data storage structure of the spreadsheet is pre-established according to the value range and the value rule of the data, and specifically, the data storage structure of the parameter area, the data storage structure of the input area, and the data storage structure of the output area are not necessarily the same.
S102: and under the condition of receiving a test instruction input by a user, acquiring transaction parameters from a parameter area of the electronic form, and writing the transaction parameters into a preset database table.
Optionally, under the condition that the test instruction input by the user is received, the transaction parameters including the transaction code shown in the test instruction are obtained from the parameter area of the spreadsheet, and the transaction parameters including the transaction code shown in the test instruction are written into a preset database table.
S103: and acquiring transaction input data from an input area of the electronic form, and processing the transaction input data according to a preset transaction input message format to obtain a transaction message.
S104: and acquiring a transaction expected result from an output area of the spreadsheet, and processing the transaction expected result according to a preset transaction output message format to obtain a reference transaction result.
S105: and sending the transaction message to a preset transaction system, triggering the preset transaction system to call the transaction parameters shown in the database table, and executing the transaction service shown in the transaction message to obtain a transaction result.
The preset transaction system invokes the transaction parameters to execute the transaction service corresponding to the transaction message to obtain the transaction result, which is common knowledge familiar to those skilled in the art and will not be described herein again.
S106: and receiving a transaction result sent by a preset transaction system.
S107: and judging whether the transaction result is the same as the standard transaction result.
If the transaction result is the same as the reference transaction result, executing S108, otherwise executing S109.
S108: and sending a transaction test success prompt to the user.
After execution of S108, execution continues with S110.
If the transaction result is the same as the standard transaction result, the transaction test is successful, and a transaction test success prompt is sent to the user.
S109: and sending a transaction test failure prompt to the user.
After execution of S109, execution continues with S110.
If the transaction result is different from the standard transaction result, the transaction test is failed, and a transaction test failure prompt is sent to the user.
S110: the transaction parameters in the database table are deleted.
Based on the above flow shown in S101-S110, the following beneficial effects can be achieved in the present embodiment:
1. by standardizing the data related to the transaction test flows of the transaction parameters, the transaction input data and the transaction expected results, the test program (namely a preset transaction system) is not required to be modified in the subsequent transaction test, the repeated development of the test program is avoided, and the secondary risk brought by the change of the test program is reduced.
2. Corresponding data storage structures are respectively designed in the electronic forms, test data which are frequently modified are transferred to the electronic forms for maintenance, and the utilization rate of the test data is improved based on the characteristic that the electronic forms are convenient for management and maintenance of a large amount of data.
3. The transaction parameters are automatically written into the database table, manual modification of the database table is replaced, and the risk of misoperation of the database table is reduced.
4. After the transaction test is finished, the parameter data in the database table is automatically cleared, so that the problem of data pollution caused by the parameter data inserted in the current transaction test to the subsequent transaction test can be solved.
In summary, with the solution shown in this embodiment, a user can realize different transaction tests without modifying the test program, thereby effectively reducing the development workload of the test program.
It should be noted that S109 shown in the above embodiment is an alternative implementation of the transaction testing method shown in this application. In addition, S110 mentioned in the above embodiments is also an optional implementation manner of the transaction testing method shown in the present application. For this reason, the flow mentioned in the above embodiment can be summarized as the method shown in fig. 2.
As shown in fig. 2, a schematic flow chart of another transaction testing method provided in the embodiment of the present application includes the following steps:
s201: and generating the electronic form according to the test data input by the user in advance.
The test data comprises transaction parameters, transaction input data and expected transaction results; the spreadsheet comprises a parameter area, an input area and an output area; the parameter area is used for recording transaction parameters; the input area is used for recording transaction input data; the output area is used for recording the expected result of the transaction.
S202: and under the condition of receiving a test instruction input by a user, acquiring transaction parameters from the parameter area, and writing the transaction parameters into a preset database table.
S203: and acquiring transaction input data from the input area, and processing the transaction input data according to a preset transaction input message format to obtain a transaction message.
S204: and acquiring a transaction expected result from the output area, and processing the transaction expected result according to a preset transaction output message format to obtain a reference transaction result.
S205: and sending the transaction message to a preset transaction system, triggering the preset transaction system to call the transaction parameters shown in the database table, and executing the transaction service shown in the transaction message to obtain a transaction result.
S206: and under the condition that the transaction result is the same as the standard transaction result, sending a transaction test success prompt to the user.
In summary, with the solution shown in this embodiment, a user can realize different transaction tests without modifying the test program, thereby effectively reducing the development workload of the test program.
It should be noted that the invention provides a transaction testing method. The method can be used in the field of network security or the field of finance. The above description is only an example, and does not limit the application field of the transaction testing method provided by the present invention.
The transaction testing method provided by the invention can be used in the financial field or other fields, for example, can be used in the application scenario of transfer transaction testing in the financial field. The other fields are arbitrary fields other than the financial field, for example, the big data field. The above description is only an example, and does not limit the application field of the transaction testing method provided by the present invention.
Corresponding to the transaction testing method provided by the embodiment of the application, the embodiment of the application also provides a transaction testing device.
As shown in fig. 3, a schematic diagram of an architecture of a transaction testing device according to an embodiment of the present application is provided, including:
a data maintenance unit 100 for generating an electronic form according to test data input by a user in advance; the test data comprises transaction parameters, transaction input data and expected transaction results; the spreadsheet comprises a parameter area, an input area and an output area; the parameter area is used for recording transaction parameters; the input area is used for recording transaction input data; the output area is used for recording the expected result of the transaction.
And the data loading unit 200 is configured to, in a case that a test instruction input by a user is received, obtain the transaction parameters from the parameter area, and write the transaction parameters into a preset database table.
The data loading unit 200 is further configured to: and acquiring transaction input data from the input area, and processing the transaction input data according to a preset transaction input message format to obtain a transaction message.
The data loading unit 200 is further configured to: and acquiring a transaction expected result from the output area, and processing the transaction expected result according to a preset transaction output message format to obtain a reference transaction result.
The data loading unit 200 is specifically configured to: and under the condition of receiving a test instruction input by a user, acquiring the transaction parameters containing the transaction codes shown by the test instruction from the parameter area, and writing the transaction parameters containing the transaction codes shown by the test instruction into a preset database table.
The transaction executing unit 300 is configured to send the transaction message to a preset transaction system, trigger the preset transaction system to call a transaction parameter shown in the database table, and execute a transaction service shown in the transaction message to obtain a transaction result.
And the result verification unit 400 is used for sending a transaction test success prompt to the user under the condition that the transaction result is the same as the benchmark transaction result.
Wherein, the result verification unit 400 is further configured to: and under the condition that the transaction result is different from the benchmark transaction result, sending a transaction test failure prompt to the user.
And the data clearing unit 500 is used for deleting the transaction parameters in the database table.
In summary, with the solution shown in this embodiment, a user can realize different transaction tests without modifying the test program, thereby effectively reducing the development workload of the test program.
The present application also provides a computer-readable storage medium comprising a stored program, wherein the program performs the transaction testing method provided herein above.
The present application also provides a transaction testing device, as shown in fig. 4, comprising: a processor 401, a memory 402, and a bus 403. The processor 401 is connected to the memory 402 through the bus 403, the memory 402 is used for storing programs, and the processor 401 is used for executing the programs, wherein the programs execute the transaction testing method provided by the present application when running, and the method includes the following steps:
generating an electronic form according to test data input by a user in advance; wherein the test data comprises transaction parameters, transaction input data and expected transaction results; the spreadsheet comprises a parameter area, an input area and an output area; the parameter area is used for recording the transaction parameters; the input area is used for recording the transaction input data; the output area is used for recording the expected result of the transaction;
under the condition that a test instruction input by the user is received, acquiring the transaction parameters from the parameter area, and writing the transaction parameters into a preset database table;
acquiring the transaction input data from the input area, and processing the transaction input data according to a preset transaction input message format to obtain a transaction message;
acquiring the expected transaction result from the output area, and processing the expected transaction result according to a preset transaction output message format to obtain a reference transaction result;
sending the transaction message to a preset transaction system, triggering the preset transaction system to call the transaction parameters shown in the database table, and executing the transaction service shown in the transaction message to obtain a transaction result;
and under the condition that the transaction result is the same as the benchmark transaction result, sending a transaction test success prompt to the user.
Specifically, on the basis of the above embodiment, in the case that the test instruction input by the user is received, acquiring the transaction parameter from the parameter area, and writing the transaction parameter into a preset database table includes:
and under the condition of receiving the test instruction input by the user, acquiring the transaction parameters containing the transaction codes shown by the test instruction from the parameter area, and writing the transaction parameters containing the transaction codes shown by the test instruction into a preset database table.
Specifically, on the basis of the above embodiment, the method further includes:
and sending a transaction test failure prompt to the user under the condition that the transaction result is different from the benchmark transaction result.
Specifically, on the basis of the above embodiment, the method further includes:
deleting the transaction parameters in the database table.
The functions described in the method of the embodiment of the present application, if implemented in the form of software functional units and sold or used as independent products, may be stored in a storage medium readable by a computing device. Based on such understanding, part of the contribution to the prior art of the embodiments of the present application or part of the technical solution may be embodied in the form of a software product stored in a storage medium and including several instructions for causing a computing device (which may be a personal computer, a server, a mobile computing device or a network device) to execute all or part of the steps of the method described in the embodiments of the present application. And the aforementioned storage medium includes: u disk, removable hard disk, read only memory, random access memory, magnetic or optical disk, etc. for storing program codes.
The embodiments are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same or similar parts among the embodiments are referred to each other.
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 testing method, comprising:
generating an electronic form according to test data input by a user in advance; wherein the test data comprises transaction parameters, transaction input data and expected transaction results; the spreadsheet comprises a parameter area, an input area and an output area; the parameter area is used for recording the transaction parameters; the input area is used for recording the transaction input data; the output area is used for recording the expected result of the transaction;
under the condition that a test instruction input by the user is received, acquiring the transaction parameters from the parameter area, and writing the transaction parameters into a preset database table;
acquiring the transaction input data from the input area, and processing the transaction input data according to a preset transaction input message format to obtain a transaction message;
acquiring the expected transaction result from the output area, and processing the expected transaction result according to a preset transaction output message format to obtain a reference transaction result;
sending the transaction message to a preset transaction system, triggering the preset transaction system to call the transaction parameters shown in the database table, and executing the transaction service shown in the transaction message to obtain a transaction result;
and under the condition that the transaction result is the same as the benchmark transaction result, sending a transaction test success prompt to the user.
2. The method according to claim 1, wherein the obtaining the transaction parameters from the parameter area and writing the transaction parameters into a preset database table in a case of receiving the test instruction input by the user comprises:
and under the condition of receiving the test instruction input by the user, acquiring the transaction parameters containing the transaction codes shown by the test instruction from the parameter area, and writing the transaction parameters containing the transaction codes shown by the test instruction into a preset database table.
3. The method of claim 1, further comprising:
and sending a transaction test failure prompt to the user under the condition that the transaction result is different from the benchmark transaction result.
4. The method of claim 1, further comprising:
deleting the transaction parameters in the database table.
5. A transaction testing device, comprising:
the data maintenance unit is used for generating an electronic form according to test data input by a user in advance; wherein the test data comprises transaction parameters, transaction input data and expected transaction results; the spreadsheet comprises a parameter area, an input area and an output area; the parameter area is used for recording the transaction parameters; the input area is used for recording the transaction input data; the output area is used for recording the expected result of the transaction;
the data loading unit is used for acquiring the transaction parameters from the parameter area under the condition of receiving the test instruction input by the user and writing the transaction parameters into a preset database table;
the data loading unit is further configured to: acquiring the transaction input data from the input area, and processing the transaction input data according to a preset transaction input message format to obtain a transaction message;
the data loading unit is further configured to: acquiring the expected transaction result from the output area, and processing the expected transaction result according to a preset transaction output message format to obtain a reference transaction result;
the transaction execution unit is used for sending the transaction message to a preset transaction system, triggering the preset transaction system to call the transaction parameters shown in the database table, and executing the transaction service shown in the transaction message to obtain a transaction result;
and the result verification unit is used for sending a transaction test success prompt to the user under the condition that the transaction result is the same as the standard transaction result.
6. The apparatus of claim 5, wherein the data loading unit is specifically configured to:
and under the condition of receiving the test instruction input by the user, acquiring the transaction parameters containing the transaction codes shown by the test instruction from the parameter area, and writing the transaction parameters containing the transaction codes shown by the test instruction into a preset database table.
7. The apparatus of claim 5, wherein the result verification unit is further configured to:
and sending a transaction test failure prompt to the user under the condition that the transaction result is different from the benchmark transaction result.
8. The apparatus of claim 5, further comprising:
and the data clearing unit is used for deleting the transaction parameters in the database table.
9. A computer-readable storage medium, comprising a stored program, wherein the program performs the transaction testing method of any of claims 1-4.
10. A transaction testing device, comprising: a processor, a memory, and a bus; the processor and the memory are connected through the bus;
the memory is used for storing a program and the processor is used for executing the program, wherein the program executes the transaction testing method of any one of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111370195.5A CN114064488A (en) | 2021-11-18 | 2021-11-18 | Transaction testing method, device, storage medium and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111370195.5A CN114064488A (en) | 2021-11-18 | 2021-11-18 | Transaction testing method, device, storage medium and equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114064488A true CN114064488A (en) | 2022-02-18 |
Family
ID=80277920
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111370195.5A Pending CN114064488A (en) | 2021-11-18 | 2021-11-18 | Transaction testing method, device, storage medium and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114064488A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116483689A (en) * | 2023-03-13 | 2023-07-25 | 深圳华锐分布式技术股份有限公司 | Method, device, equipment and medium for testing option brokerage quick trading system |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104182348A (en) * | 2014-09-15 | 2014-12-03 | 北京国双科技有限公司 | Software test method and device |
| CN109992506A (en) * | 2019-03-18 | 2019-07-09 | 平安科技（深圳）有限公司 | Scheduling tests method, apparatus, computer equipment and storage medium |
| CN110399293A (en) * | 2019-06-21 | 2019-11-01 | 平安科技（深圳）有限公司 | System detection method, device, computer equipment and storage medium |
| CN110413507A (en) * | 2019-06-21 | 2019-11-05 | 平安科技（深圳）有限公司 | System detection method, device, computer equipment and storage medium |
| CN112988558A (en) * | 2019-12-16 | 2021-06-18 | 迈普通信技术股份有限公司 | Test execution method and device, electronic equipment and storage medium |
-
2021
- 2021-11-18 CN CN202111370195.5A patent/CN114064488A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104182348A (en) * | 2014-09-15 | 2014-12-03 | 北京国双科技有限公司 | Software test method and device |
| CN109992506A (en) * | 2019-03-18 | 2019-07-09 | 平安科技（深圳）有限公司 | Scheduling tests method, apparatus, computer equipment and storage medium |
| CN110399293A (en) * | 2019-06-21 | 2019-11-01 | 平安科技（深圳）有限公司 | System detection method, device, computer equipment and storage medium |
| CN110413507A (en) * | 2019-06-21 | 2019-11-05 | 平安科技（深圳）有限公司 | System detection method, device, computer equipment and storage medium |
| CN112988558A (en) * | 2019-12-16 | 2021-06-18 | 迈普通信技术股份有限公司 | Test execution method and device, electronic equipment and storage medium |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116483689A (en) * | 2023-03-13 | 2023-07-25 | 深圳华锐分布式技术股份有限公司 | Method, device, equipment and medium for testing option brokerage quick trading system |
| CN116483689B (en) * | 2023-03-13 | 2024-01-05 | 深圳华锐分布式技术股份有限公司 | Method, device, equipment and medium for testing option brokerage quick trading system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113434396A (en) | Interface test method, device, equipment, storage medium and program product | |
| CN110766167A (en) | Interactive feature selection method, device and readable storage medium | |
| CN113064759A (en) | Block chain data rollback processing method and processing system thereof | |
| CN114064488A (en) | Transaction testing method, device, storage medium and equipment | |
| CN115061924A (en) | Automatic test case generation method and generation device | |
| CN112506802A (en) | Test data management method and system | |
| CN112416725A (en) | Pressure testing method and device | |
| CN111737351A (en) | Transaction management method and device for distributed management system | |
| CN111193631B (en) | Information processing method, system, and computer-readable storage medium | |
| CN111367934A (en) | Data consistency checking method, device, server and medium | |
| Jumnongsaksub et al. | Reducing smart contract runtime errors on ethereum | |
| CN112070470B (en) | Annual report reporting method and device, electronic equipment and storage medium | |
| CN114741162A (en) | Service arranging method, device, storage medium and equipment | |
| CN111984473B (en) | Memory snapshot data acquisition method and related device | |
| CN111930358B (en) | Operation and maintenance script generation and execution method and system | |
| CN112131180B (en) | Data reporting method, device and storage medium | |
| CN108874325B (en) | Data printing method and system | |
| CN113505017A (en) | Problem troubleshooting method, device, storage medium and equipment | |
| CN115269345A (en) | Database testing method, device, equipment and storage medium | |
| CN113724074A (en) | Credit credit risk early warning method and device | |
| CN110362464B (en) | Software analysis method and equipment | |
| CN114862401B (en) | Payment exception processing method, device, equipment and medium | |
| CN111552586A (en) | Application crash processing method and device | |
| CN113704131B (en) | Interface function test method, device, storage medium and equipment | |
| CN110896413A (en) | Message processing 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 |