CN111881020B - Payment center interface testing method, device and system - Google Patents
Payment center interface testing method, device and system Download PDFInfo
- Publication number
- CN111881020B CN111881020B CN202010646584.5A CN202010646584A CN111881020B CN 111881020 B CN111881020 B CN 111881020B CN 202010646584 A CN202010646584 A CN 202010646584A CN 111881020 B CN111881020 B CN 111881020B
- Authority
- CN
- China
- Prior art keywords
- test
- interface
- database
- module
- scripts
- 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.)
- Active
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 341
- 238000013515 script Methods 0.000 claims abstract description 82
- 238000012795 verification Methods 0.000 claims abstract description 31
- 238000000034 method Methods 0.000 claims abstract description 22
- 230000004044 response Effects 0.000 claims description 17
- 238000011056 performance test Methods 0.000 claims description 16
- 238000004590 computer program Methods 0.000 claims description 7
- 238000010998 test method Methods 0.000 claims description 6
- 238000010276 construction Methods 0.000 claims description 5
- 238000010586 diagram Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 238000003491 array Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 238000012790 confirmation Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 210000001503 joint Anatomy 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/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
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 invention relates to a method, a device and a system for testing a payment center interface, which acquire case scripts of various test scenes by using test data objects; adding the annotation of the DataProvider class into various case scripts to obtain various test scripts; determining a test order identifier corresponding to each test script by utilizing a random number generation rule; according to the input interface parameters, carrying out interface test on the current interface document by utilizing each test script to obtain interface test data corresponding to each test order mark; verifying the service information corresponding to each test order identifier in the service database to obtain a verification result corresponding to each test order identifier; and generating an interface test report according to the verification results and the interface test data corresponding to all the test order identifications. According to the scheme, multiple test scene cases are obtained simultaneously, multiple tests are performed simultaneously, the test scenes do not need to be manually converted, the test labor cost is reduced, multiple tests are executed simultaneously, and the test efficiency is improved.
Description
Technical Field
The invention relates to the technical field of interface testing, in particular to a method, a device and a system for testing a payment center interface.
Background
The online payment is a form of electronic payment, and is an instant payment mode provided by a third party and provided by a payment interface between a bank and the bank, and the mode has the advantages that funds can be directly transferred from a bank card of a user to a website account, money transfer is carried out immediately, and manual confirmation is not needed. The customers and merchants can pay by adopting a plurality of electronic payment modes such as credit cards, electronic wallets, electronic checks, electronic cash and the like, and the cost of transactions is saved by adopting the mode of electronic payment on the internet.
Due to the gradual development of online payment, the security of the payment center interface is also more and more important, and the method is particularly important for testing the payment center interface. In the prior art, the flow test, the data driving test and other test scenes of the payment center interface are tested separately one by one, but in the test process, a tester is required to manually switch the test scenes, the execution time for completing all the tests is long, and the test labor cost of the payment center interface is high and the efficiency is low.
Disclosure of Invention
Accordingly, the present invention is directed to a method, an apparatus, and a system for testing a payment center interface, so as to solve the problems in the prior art that a tester needs to manually switch test scenes, and the execution time for completing all tests is long, so that the cost of labor for testing the payment center interface is high and the efficiency is low.
In order to achieve the above purpose, the invention adopts the following technical scheme:
a payment center interface testing method, comprising:
constructing a test data object;
acquiring case scripts of various test scenes from a test case database by using the test data object;
adding the annotation of the DataProvider class into various case scripts to obtain various test scripts;
determining a test order identifier corresponding to each test script by using a preset random number generation rule;
according to the pre-input interface parameters, carrying out interface test on the current interface document by utilizing each test script to obtain interface test data corresponding to each test order mark;
verifying service information corresponding to each test order identifier in a preset service database to obtain a verification result corresponding to each test order identifier;
and generating an interface test report according to the verification results and the interface test data corresponding to all the test order identifications.
Further, the payment center interface testing method further comprises the following steps:
transmitting a call request set comprising a plurality of call requests to the current interface document by using a preset interface performance test rule to obtain request response information corresponding to the current interface document;
and generating an interface performance test report corresponding to the current interface document according to the calling request set and the request response information.
Further, in the payment center interface testing method, after obtaining the case scripts of the various testing scenarios from the testing case database, the method further includes:
and adding all the case scripts into a preset management file so that the current interface document is modified, and performing regression testing on the modified current interface document by using all the case scripts in the management file.
Further, in the payment center interface testing method, the management file is a TestSuite test suite management file of a TestNG framework.
Further, in the above payment center interface testing method, before verifying the service information corresponding to each test order identifier in the preset service database, the method further includes:
and connecting each independent database by using a preset database management rule to obtain the service database.
Further, in the above payment center interface testing method, the independent database includes: at least one of a payment center database, a clearing house database, and a third party database.
The invention also provides a payment center interface testing device, which comprises:
a construction module for constructing a test data object;
the acquisition module is used for acquiring case scripts of various test scenes from the test case database by utilizing the test data object;
the adding module is used for adding the annotation of the DataProvider class into various case scripts to obtain various test scripts;
the determining module is used for determining the test order mark corresponding to each test script by utilizing a preset random number generation rule;
the test module is used for carrying out interface test on the current interface document by utilizing each test script according to the interface parameters input in advance to obtain interface test data corresponding to each test order mark;
the verification module is used for verifying the service information corresponding to each test order identifier in a preset service database to obtain a verification result corresponding to each test order identifier;
and the generating module is used for generating an interface test report according to the verification results and the interface test data corresponding to all the test order identifiers.
Further, the payment center interface testing device further includes: a transmitting module;
the sending module is used for sending a call request set comprising various call requests to the current interface document by utilizing a preset interface performance test rule to obtain request response information corresponding to the current interface document;
the generating module is further configured to generate an interface performance test report corresponding to the current interface document according to the call request set and the request response information.
Further, the payment center interface testing device further includes: a connection module;
and the connection module is used for connecting each independent database by utilizing a preset database management rule to obtain the service database.
The invention also provides a payment center interface test system, which comprises: a processor and a memory coupled to the processor;
the memory is used for storing a computer program, and the computer program is at least used for executing the payment center interface testing method;
the processor is used for calling and executing the computer program.
A payment center interface test method, device and system, utilize test data object constructed in advance, obtain the case script of various test scenes from the test case database; adding the annotation of the DataProvider class into various case scripts to obtain various test scripts; determining a test order identifier corresponding to each test script by using a preset random number generation rule; according to the interface parameters input in advance, carrying out interface test on the current interface document by utilizing each test script to obtain interface test data corresponding to each test order mark; verifying service information corresponding to each test order identifier in a preset service database to obtain a verification result corresponding to each test order identifier; and generating an interface test report according to the verification results and the interface test data corresponding to all the test order identifications. By adopting the technical scheme, the cases of multiple test scenes can be obtained simultaneously, multiple tests are performed simultaneously, and after the test is started, the multiple test cases can be executed completely without manually switching the test scenes by a tester, so that the test labor cost of the payment center interface is reduced, the time for completing all the tests is reduced by simultaneously executing the multiple tests, and the test efficiency is improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention as claimed.
Drawings
In order to more clearly illustrate the embodiments of the invention or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart provided by one embodiment of a payment center interface testing method of the present invention;
FIG. 2 is a schematic diagram of a configuration provided by an embodiment of a payment center interface testing device of the present invention;
fig. 3 is a schematic diagram of a payment center interface test system according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the technical solutions of the present invention will be described in detail below. It will be apparent that the described embodiments are only some, but not all, embodiments of the invention. All other embodiments, based on the examples herein, which are within the scope of the invention as defined by the claims, will be within the scope of the invention as defined by the claims.
Fig. 1 is a flowchart provided by an embodiment of a payment center interface testing method of the present invention, and as shown in fig. 1, the payment center interface testing method of the present embodiment specifically includes the following steps:
s101, constructing a test data object;
according to the payment center interface testing method of the embodiment, when a port is required to be constructed for testing, a test data object which needs to be input is firstly constructed, and a get method and a set method can be provided for the test data object, namely, the port can be called by utilizing the test data object, such as acquisition (inquiry), transmission (modification) and the like.
S102, acquiring case scripts of various test scenes from a test case database by using the test data object;
after the test data object is constructed, the test data object can be used for acquiring case scripts of various test scenes from a test case database, wherein the case scripts comprise front cases, back cases and the like. The test case database is preferably a DataProvider class; various test scenarios include: a digital signature test scene, a data encryption test scene, an interface full-flow test scene, a data driving test scene and the like. For example, the structured test data object is passed into a DataProvider class, which returns an object [ ] array containing values for various test scenarios, including case scripts such as front case and back case.
S103, adding the annotation of the DataProvider class into various case scripts to obtain various test scripts;
after various case scripts are obtained from the test case database, annotations of the DataProvider class can be added to the various case scripts, so that various test scripts are obtained. The annotation of the DataProvider class is added in the case script, so that the test and test data of the case script of the interface can be managed separately, and the test data can be reused in similar interface test scenes, such as a refund request interface of WeChat and a refund request interface of a payment bank.
S104, determining a test order identifier corresponding to each test script by using a preset random number generation rule;
after various test scripts are obtained, a preset random number generation rule can be utilized to determine the test order identification corresponding to each test script, so that the interface idempotency when the test scripts are executed can be ensured. Wherein, the generation rule of the preset random number is preferably used for calling the random number class in the basic tool layer.
S105, performing interface test on the current interface document by utilizing each test script according to the interface parameters input in advance to obtain interface test data corresponding to each test order mark;
when the interface test is carried out, a tester needs to input interface parameters corresponding to the current interface document in advance, and according to the interface parameters, each test script carrying the test order mark is used for carrying out the interface test on the current interface document, so that interface test data corresponding to each test order mark is obtained. And each interface document is provided with an assertion component, so that after the current interface document is called when the test script tests the current interface document, the assertion component in the current interface document generates and feeds back assertion information, and interface test data obtained in the step contains the assertion information.
S106, verifying service information corresponding to each test order identifier in a preset service database to obtain a verification result corresponding to each test order identifier;
and inquiring service information corresponding to each test order mark from a preset service database according to the test order mark carried by each test script, verifying whether the service information is consistent with the expected service information, and generating a verification result corresponding to each test order mark. The business information comprises money drawing table data, transaction table data and the like. For example, after the interface test is performed on the current interface document by using the test script, no matter which third party the current interface document is in butt joint with, business information such as a money drawing table and transaction table data is inserted, the business information such as the money drawing table data and the transaction table data is updated, at this time, the business information corresponding to the test order mark carried by the test script needs to be queried from a preset business database, whether the business information is successfully updated is verified, whether the state is consistent with the expected state, and a corresponding verification result is generated. And if the interface documents are inconsistent, the current interface documents are tested to have problems. In this embodiment, the parameter transmission and result verification in step S105 and step S106 may be implemented through the dependendson annotation of the TestNG framework, or may be implemented through means such as Java class design private fields and method references.
And S107, generating an interface test report according to the verification results and the interface test data corresponding to all the test order identifiers.
After the interface test data and the verification result corresponding to all the test order identifications are obtained, all the interface test data and the verification result can be analyzed and arranged, so that an interface test report corresponding to the current interface document is generated, and the interface test report contains test reports of various test scenes. The interface test report can include the passing condition of the test cases in each test script in various test scenes, so that the problem of the current interface document can be judged according to the test passing condition of the test cases, and the tester can revise the current interface document in time.
According to the payment center interface testing method, a pre-constructed test data object is utilized to obtain case scripts of various test scenes from a test case database; adding the annotation of the DataProvider class into various case scripts to obtain various test scripts; determining a test order identifier corresponding to each test script by using a preset random number generation rule; according to the interface parameters input in advance, carrying out interface test on the current interface document by utilizing each test script to obtain interface test data corresponding to each test order mark; verifying service information corresponding to each test order identifier in a preset service database to obtain a verification result corresponding to each test order identifier; and generating an interface test report according to the verification results and the interface test data corresponding to all the test order identifications. By adopting the technical scheme, the cases of multiple test scenes can be obtained simultaneously, multiple tests are performed simultaneously, and after the test is started, the multiple test cases can be executed completely without manually switching the test scenes by a tester, so that the test labor cost of the payment center interface is reduced, the time for completing all the tests is reduced by simultaneously executing the multiple tests, and the test efficiency is improved.
Further, in the payment center interface testing method of the present embodiment, after obtaining the case scripts of the various test scenarios from the test case database, the method further includes: and adding all the case scripts into a preset management file so that the current interface document is modified, and performing regression testing on the modified current interface document by using all the case scripts in the management file. Therefore, the multiplexing of all the case scripts can be ensured, when the regression test is carried out on the modified current interface document, all the case scripts are directly obtained from the management file, the test data object is not required to be reconstructed, the test data object is not required to be reused to access the test case database, the automatic management of the interface regression test can be realized, the regression test time is shortened, and the test efficiency of the payment center interface is improved. Wherein the management file is preferably a TestSuite test suite management file of a TestNG framework.
Further, in the payment center interface testing method of this embodiment, before verifying the service information corresponding to each test order identifier in the preset service database, the method further includes: and connecting each independent database by using a preset database management rule to obtain a service database. In this embodiment, the JdbcTemplate in the spring framework is preferably used to implement connection processing of multiple independent databases, uniformly manage connection string information of multiple databases, and directly operate the service database to implement operation on multiple independent databases, so as to enhance readability of codes in test cases, reduce time for verification of results, and improve efficiency of interface test. The independent database in this embodiment includes: at least one of a payment center database, a clearing house database, and a third party database.
Further, the payment center interface testing method of the embodiment further includes:
firstly, sending a call request set comprising a plurality of call requests to a current interface document by using a preset interface performance test rule to obtain request response information corresponding to the current interface document;
the embodiment can send various calling requests to the current interface document by using the performance test module in the java spring framework, and after the current interface document is called, corresponding information is fed back, and the information is used as request response information. Sending multiple call requests to the current interface document can test the acceptance of the call requests by the current interface document, i.e., at most, how many call requests can be accepted. And sending various call requests to the current interface document, and determining the call request with the slowest response of the current interface document according to the request response information corresponding to each call request, so that the current interface document can be conveniently modified by a tester.
Secondly, according to the calling request set and the request response information, generating an interface performance test report corresponding to the current interface document.
And generating an interface performance test report corresponding to the current interface document according to various calling requests sent to the current interface document and request response information fed back by the current interface document for various calling requests. The interface performance test report may include the call request bearing condition of the current interface document, the response efficiency of each call request, and the like. The tester can optimize the current interface document by looking at the interface performance test report.
The payment center interface testing method of the embodiment uses the java spring framework to call the dubbo service, and after the developed dubbo service is upgraded, the pon file version number in the spring framework can be updated, and a maven local warehouse is synchronized, so that the upgrading of the dependence of the testing version is realized.
In order to be more comprehensive, the application also provides a payment center interface testing device corresponding to the payment center interface testing method provided by the embodiment of the invention.
Fig. 2 is a schematic structural diagram provided by an embodiment of a payment center interface testing device according to the present invention, as shown in fig. 2, the payment center interface testing device of the present embodiment includes: the system comprises a construction module 101, an acquisition module 102, an addition module 103, a determination module 104, a test module 105, a verification module 106 and a generation module 107.
A construction module 101 for constructing a test data object;
an obtaining module 102, configured to obtain, from a test case database, case scripts of various test scenarios using the test data object;
an adding module 103, configured to add the annotation of the DataProvider class to various case scripts to obtain various test scripts;
the determining module 104 is configured to determine a test order identifier corresponding to each test script by using a preset random number generating rule;
the test module 105 is configured to perform an interface test on the current interface document by using each test script according to the interface parameters input in advance, so as to obtain interface test data corresponding to each test order identifier;
the verification module 106 is configured to verify the service information corresponding to each test order identifier in the preset service database, and obtain a verification result corresponding to each test order identifier;
and the generating module 107 is configured to generate an interface test report according to the verification results and the interface test data corresponding to all the test order identifiers.
In the payment center interface test device of the present embodiment, the acquisition module 102 acquires case scripts of various test scenarios from the test case database by using test data objects pre-constructed by the construction module 101; the adding module 103 adds the annotation of the DataProvider class into various case scripts to obtain various test scripts; the determining module 104 determines a test order identifier corresponding to each test script by using a preset random number generating rule; the test module 105 performs interface test on the current interface document by utilizing each test script according to the interface parameters input in advance to obtain interface test data corresponding to each test order mark; the verification module 106 verifies the service information corresponding to each test order identifier in the preset service database to obtain a verification result corresponding to each test order identifier; the generating module 107 generates an interface test report according to the verification results and the interface test data corresponding to all the test order identifications. By adopting the technical scheme, the cases of multiple test scenes can be obtained simultaneously, multiple tests are performed simultaneously, and after the test is started, the multiple test cases can be executed completely without manually switching the test scenes by a tester, so that the test labor cost of the payment center interface is reduced, the time for completing all the tests is reduced by simultaneously executing the multiple tests, and the test efficiency is improved.
Further, in the payment center interface testing device of the present embodiment, the adding module 103 is further configured to add all the case scripts to a preset management file, so that after the current interface document is modified, regression testing is performed on the modified current interface document by using all the case scripts in the management file.
Further, the payment center interface testing device of the present embodiment further includes: and connecting the modules.
And the connection module is used for connecting each independent database by utilizing a preset database management rule to obtain a service database.
Further, the payment center interface testing device of the present embodiment further includes: and a transmitting module.
The sending module is used for sending a calling request set comprising a plurality of calling requests to the current interface document by utilizing a preset interface performance test rule to obtain request response information corresponding to the current interface document;
the generating module 107 is further configured to generate an interface performance test report corresponding to the current interface document according to the call request set and the request response information.
The specific manner in which the various modules perform the operations in the apparatus of the above embodiments have been described in detail in connection with the embodiments of the method, and will not be described in detail herein.
Fig. 3 is a schematic structural diagram provided by an embodiment of a payment center interface test system according to the present invention, and as shown in fig. 3, the payment center interface test system of the present embodiment includes a processor 21 and a memory 22 connected to the processor 21;
the memory 22 is used for storing a computer program for performing at least the payment center interface test method of the above-described embodiment;
the processor 21 is used to call and execute a computer program stored in the memory 22.
According to the payment center interface test system of the embodiment, the processor 21 can acquire cases of multiple test scenes at the same time by calling the payment center interface test method stored in the memory 22, and perform multiple tests at the same time, so that after the test is started, the multiple test cases can be executed completely without manually switching the test scenes by a tester, the test labor cost of the payment center interface is reduced, the time for completing all the tests is reduced by performing multiple tests at the same time, and the test efficiency is improved.
It is to be understood that the same or similar parts in the above embodiments may be referred to each other, and that in some embodiments, the same or similar parts in other embodiments may be referred to.
It should be noted that in the description of the present invention, the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. Furthermore, in the description of the present invention, unless otherwise indicated, the meaning of "plurality" means at least two.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and further implementations are included within the scope of the preferred embodiment of the present invention in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present invention.
It is to be understood that portions of the present invention may be implemented in hardware, software, firmware, or a combination thereof. In the above-described embodiments, the various steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, may be implemented using any one or combination of the following techniques, as is well known in the art: discrete logic circuits having logic gates for implementing logic functions on data signals, application specific integrated circuits having suitable combinational logic gates, programmable Gate Arrays (PGAs), field Programmable Gate Arrays (FPGAs), and the like.
Those of ordinary skill in the art will appreciate that all or a portion of the steps carried out in the method of the above-described embodiments may be implemented by a program to instruct related hardware, and the program may be stored in a computer readable storage medium, where the program when executed includes one or a combination of the steps of the method embodiments.
In addition, each functional unit in the embodiments of the present invention may be integrated in one processing module, or each unit may exist alone physically, or two or more units may be integrated in one module. The integrated modules may be implemented in hardware or in software functional modules. The integrated modules may also be stored in a computer readable storage medium if implemented in the form of software functional modules and sold or used as a stand-alone product.
The above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, or the like.
In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present invention. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiments or examples. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
While embodiments of the present invention have been shown and described above, it will be understood that the above embodiments are illustrative and not to be construed as limiting the invention, and that variations, modifications, alternatives and variations may be made to the above embodiments by one of ordinary skill in the art within the scope of the invention.
Claims (7)
1. A payment center interface testing method, comprising:
constructing a test data object;
acquiring case scripts of various test scenes from a test case database by using the test data object;
adding the annotation of the DataProvider class into various case scripts to obtain various test scripts;
determining a test order identifier corresponding to each test script by using a preset random number generation rule;
according to the pre-input interface parameters, carrying out interface test on the current interface document by utilizing each test script to obtain interface test data corresponding to each test order mark;
verifying service information corresponding to each test order identifier in a preset service database to obtain a verification result corresponding to each test order identifier;
generating an interface test report according to the verification results and the interface test data corresponding to all the test order identifications;
transmitting a call request set comprising a plurality of call requests to the current interface document by using a preset interface performance test rule to obtain request response information corresponding to the current interface document;
generating an interface performance test report corresponding to the current interface document according to the call request set and the request response information;
after obtaining the case scripts of various test scenes from the test case database, the method further comprises the following steps:
and adding all the case scripts into a preset management file so that the current interface document is modified, and performing regression testing on the modified current interface document by using all the case scripts in the management file.
2. The payment center interface test method of claim 1, wherein the management file is a TestSuite test suite management file of a TestNG framework.
3. The method for testing a payment center interface according to claim 1, further comprising, before verifying the service information corresponding to each test order identifier in the preset service database:
and connecting each independent database by using a preset database management rule to obtain the service database.
4. A payment centre interface test method according to claim 3, wherein the separate database comprises: at least one of a payment center database, a clearing house database, and a third party database.
5. A payment center interface testing device, comprising:
a construction module for constructing a test data object;
the acquisition module is used for acquiring case scripts of various test scenes from the test case database by utilizing the test data object;
the adding module is used for adding the annotation of the DataProvider class into various case scripts to obtain various test scripts;
the determining module is used for determining the test order mark corresponding to each test script by utilizing a preset random number generation rule;
the test module is used for carrying out interface test on the current interface document by utilizing each test script according to the interface parameters input in advance to obtain interface test data corresponding to each test order mark;
the verification module is used for verifying the service information corresponding to each test order identifier in a preset service database to obtain a verification result corresponding to each test order identifier;
the generating module is used for generating an interface test report according to the verification results and the interface test data corresponding to all the test order identifications;
the sending module is used for sending a call request set comprising various call requests to the current interface document by utilizing a preset interface performance test rule to obtain request response information corresponding to the current interface document;
the generating module is further used for generating an interface performance test report corresponding to the current interface document according to the calling request set and the request response information;
and the adding module is also used for adding all the case scripts into a preset management file so that the current interface document is modified and then the regression test is carried out on the modified current interface document by utilizing all the case scripts in the management file.
6. The payment center interface test device of claim 5, further comprising: a connection module;
and the connection module is used for connecting each independent database by utilizing a preset database management rule to obtain the service database.
7. A payment center interface test system, comprising: a processor and a memory coupled to the processor;
the memory is used for storing a computer program at least for executing the payment center interface test method of any one of claims 1-4;
the processor is used for calling and executing the computer program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010646584.5A CN111881020B (en) | 2020-07-07 | 2020-07-07 | Payment center interface testing method, device and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010646584.5A CN111881020B (en) | 2020-07-07 | 2020-07-07 | Payment center interface testing method, device and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111881020A CN111881020A (en) | 2020-11-03 |
| CN111881020B true CN111881020B (en) | 2024-04-09 |
Family
ID=73150332
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010646584.5A Active CN111881020B (en) | 2020-07-07 | 2020-07-07 | Payment center interface testing method, device and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111881020B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112328481B (en) * | 2020-11-04 | 2024-08-09 | 中国平安人寿保险股份有限公司 | Automatic testing method, device, equipment and storage medium for multitasking scene |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107526676A (en) * | 2016-06-20 | 2017-12-29 | 苏宁云商集团股份有限公司 | A kind of cross-system method of testing and device |
| CN109298997A (en) * | 2018-08-08 | 2019-02-01 | 平安科技（深圳）有限公司 | Interface test method, system, computer equipment and storage medium |
| CN109542765A (en) * | 2018-10-18 | 2019-03-29 | 深圳壹账通智能科技有限公司 | Database script verification method, device, computer equipment and storage medium |
| CN109597753A (en) * | 2018-10-22 | 2019-04-09 | 平安科技（深圳）有限公司 | Method, apparatus, computer equipment and the storage medium of interface testing |
| CN110209575A (en) * | 2019-05-20 | 2019-09-06 | 深圳壹账通智能科技有限公司 | Test document generation method, device, electronic equipment and storage medium |
| CN111198813A (en) * | 2018-11-20 | 2020-05-26 | 北京京东尚科信息技术有限公司 | Interface testing method and device |
| CN111324540A (en) * | 2020-03-02 | 2020-06-23 | 北京同邦卓益科技有限公司 | Interface testing method and device |
-
2020
- 2020-07-07 CN CN202010646584.5A patent/CN111881020B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107526676A (en) * | 2016-06-20 | 2017-12-29 | 苏宁云商集团股份有限公司 | A kind of cross-system method of testing and device |
| CN109298997A (en) * | 2018-08-08 | 2019-02-01 | 平安科技（深圳）有限公司 | Interface test method, system, computer equipment and storage medium |
| CN109542765A (en) * | 2018-10-18 | 2019-03-29 | 深圳壹账通智能科技有限公司 | Database script verification method, device, computer equipment and storage medium |
| CN109597753A (en) * | 2018-10-22 | 2019-04-09 | 平安科技（深圳）有限公司 | Method, apparatus, computer equipment and the storage medium of interface testing |
| CN111198813A (en) * | 2018-11-20 | 2020-05-26 | 北京京东尚科信息技术有限公司 | Interface testing method and device |
| CN110209575A (en) * | 2019-05-20 | 2019-09-06 | 深圳壹账通智能科技有限公司 | Test document generation method, device, electronic equipment and storage medium |
| CN111324540A (en) * | 2020-03-02 | 2020-06-23 | 北京同邦卓益科技有限公司 | Interface testing method and device |
Non-Patent Citations (2)
| Title |
|---|
| BIM应用与软件研发一体化云平台设计与部署;龙潇;《中华建设》;20200131(第01期);全文 * |
| 虞砺琨 ; 左万娟 ; 于倩 ; 陈华南 ; 黄晨 ; .基于数据模型的接口用例自动生成.测控技术.(07),全文. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111881020A (en) | 2020-11-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110493007B (en) | Block chain based information verification method, device, equipment and storage medium | |
| CN108346028B (en) | Business approval processing method, device and system | |
| US11698774B2 (en) | Systems and methods for translating data read from proxy APIs into computing code | |
| CN112163946A (en) | Accounting processing method and device based on distributed transaction system | |
| CN108111364B (en) | Service system testing method and device | |
| JP7454052B2 (en) | Data processing methods, apparatus, devices and media | |
| CN112015651B (en) | Data processing method and device | |
| CN111666201A (en) | Regression testing method, device, medium and electronic equipment | |
| CN111881020B (en) | Payment center interface testing method, device and system | |
| CN111429139A (en) | Control method and device for dynamically matching user payment mode selection | |
| CN110378735A (en) | Resource information management system and method | |
| KR20090083621A (en) | Test automating system | |
| CN115495372A (en) | Analog data processing method, device, equipment and medium | |
| CN111865726B (en) | Service message testing method, device, computer system and storage medium | |
| CN114371866A (en) | Version reconfiguration test method, device and equipment of service system | |
| CN113609014A (en) | Interface field checking method and device, storage medium and electronic equipment | |
| CN113641570B (en) | Test method and terminal | |
| CN115129355B (en) | Page repair method, system and computer equipment thereof | |
| CN112749075B (en) | Service testing method, device, storage medium and equipment based on preset data | |
| CN113138999B (en) | Data processing method and device, computer storage medium and electronic equipment | |
| CN111144867B (en) | Method and device for generating region code mapping relation | |
| CN110007904B (en) | Data processing method, device and equipment | |
| CN115578081A (en) | Code flow visualization display method and device, electronic equipment and storage medium | |
| CN113157498A (en) | Disaster recovery system verification method and device | |
| CN116228396A (en) | Credit data 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |