CN110377522B - Transaction scene testing method, device, computing equipment and medium - Google Patents

Transaction scene testing method, device, computing equipment and medium Download PDF

Info

Publication number
CN110377522B
CN110377522B CN201910665508.6A CN201910665508A CN110377522B CN 110377522 B CN110377522 B CN 110377522B CN 201910665508 A CN201910665508 A CN 201910665508A CN 110377522 B CN110377522 B CN 110377522B
Authority
CN
China
Prior art keywords
transaction data
historical transaction
target
transaction
historical
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
Application number
CN201910665508.6A
Other languages
Chinese (zh)
Other versions
CN110377522A (en
Inventor
薛存芳
白凯敏
杜宁宁
宛明晔
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Industrial and Commercial Bank of China Ltd ICBC
Original Assignee
Industrial and Commercial Bank of China Ltd ICBC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Industrial and Commercial Bank of China Ltd ICBC filed Critical Industrial and Commercial Bank of China Ltd ICBC
Priority to CN201910665508.6A priority Critical patent/CN110377522B/en
Publication of CN110377522A publication Critical patent/CN110377522A/en
Application granted granted Critical
Publication of CN110377522B publication Critical patent/CN110377522B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • G06F11/3672Test management
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • G06F11/3672Test management
    • G06F11/3676Test management for coverage analysis
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange

Abstract

The disclosure provides a method for testing a transaction scenario, comprising the following steps: acquiring a plurality of first historical transaction data, wherein the plurality of first historical transaction data comprises transaction data of a plurality of first transaction scenes; determining target historical transaction data based on the plurality of first historical transaction data, wherein the target historical transaction data comprises transaction data of a target transaction scenario of the plurality of first transaction scenarios; inputting the target historical transaction data into a test script for testing to obtain a test result; and determining whether the target transaction scene is normal or not according to the test result. The disclosure also provides a testing device, a computing device and a medium for the transaction scenario.

Description

Transaction scene testing method, device, computing equipment and medium
Technical Field
The present disclosure relates to the field of computer technology, and in particular, to a method for testing a transaction scenario, a device for testing a transaction scenario, a computing device, and a computer-readable storage medium.
Background
At present, in the process of testing a transaction scene, a tester generally selects corresponding fields from a plurality of service fields in a page input item by means of personal test experience to obtain a permutation and combination result of a plurality of transaction scenes, performs routine test on the transaction scenes, and then compares messages and accounting information manually. The transaction scenario includes, for example, SWIFT (Society for Worldwide Interbank Financial Telecommunication) remittance, industrial silver speed remittance, local clearing remittance, and the like. However, by manually selecting a transaction scenario, there are many problems with manually checking messages and accounting information. Among them, there are problems including, for example: (1) The transaction scenes are more, for example, the transaction scenes to be tested are quite more due to different remittance places, different commission charge modes, different remittance currencies and the like, so that the testing workload is high and the testing period is tension, and the one-by-one testing of a plurality of transaction scenes is not feasible; (2) The range of the coverage real scene is low, for example, the coverage ratio of the transaction scene selected by the tester according to experience to the transaction scene actually happening in production is low, so that the test cannot catch the key point and the actual effect is poor; (2) The accuracy of the test cannot be guaranteed, for example, because the assembly rules of various information in the message are different, the method of manually checking the message information item by item is time-consuming and labor-consuming, and the checking process is easy to miss, so that potential transaction hazards can be left behind after the operation.
Disclosure of Invention
One aspect of the present disclosure provides a method for testing a transaction scenario, including: acquiring a plurality of first historical transaction data, wherein the plurality of first historical transaction data comprise transaction data of a plurality of first transaction scenes, determining target historical transaction data based on the plurality of first historical transaction data, wherein the target historical transaction data comprise transaction data of target transaction scenes in the plurality of first transaction scenes, inputting the target historical transaction data into a test script for testing, obtaining a test result, and determining whether the target transaction scenes are normal or not according to the test result.
Optionally, the first historical transaction data includes transaction data generated by at least one user initiated transaction. The determining target historical transaction data based on the plurality of first historical transaction data includes: determining second historical transaction data based on the plurality of first historical transaction data, wherein the second historical transaction data is generated by a target user initiating transaction in the at least one user, and determining the target historical transaction data based on the second historical transaction data, wherein the number of the first historical transaction data is a first number, the number of the second historical transaction data is a second number, the number of the target historical transaction data is a third number, the ratio between the second number and the first number meets a first preset ratio, and the ratio between the third number and the second number meets a second preset ratio.
Optionally, determining the target transaction data history based on the second historical transaction data includes: determining at least one second transaction scene to which the second historical transaction data belongs, determining a target transaction scene in the at least one second transaction scene, and determining the transaction data belonging to the target transaction scene in the second historical transaction data as the target historical transaction data.
Optionally, the inputting the target historical transaction data into a test script for testing, to obtain a test result, includes: and executing updating operation on the target historical transaction data to obtain updated target historical transaction data, and testing based on the updated target historical transaction data to obtain the test result.
Optionally, the performing an updating operation on the target historical transaction data to obtain updated target historical transaction data includes: determining an initial transaction password and an initial transaction authentication mode of the target historical transaction data, acquiring a test password and a test authentication mode, updating the initial transaction password based on the test password, and updating the initial transaction authentication mode based on the test authentication mode.
Optionally, the inputting the target historical transaction data into a test script for testing, to obtain a test result, includes: testing the target historical transaction data to obtain a transaction result, obtaining a historical transaction message corresponding to the target historical transaction data, processing the historical transaction message to obtain a message rule of the target historical transaction data, and processing the transaction result based on the message rule to obtain the test result.
Optionally, the determining whether the target transaction scenario is normal according to the test result includes: comparing the target historical transaction data with the test result to obtain a comparison result, responding to the comparison result to represent that the target historical transaction data is inconsistent with the test result, determining that the target transaction scene is abnormal, and outputting prompt information.
Another aspect of the present disclosure provides a testing apparatus for a transaction scenario, including: the device comprises an acquisition module, a first determination module, a test module and a second determination module. The acquisition module acquires a plurality of first historical transaction data, the plurality of first historical transaction data comprise transaction data of a plurality of first transaction scenes, the first determination module determines target historical transaction data based on the plurality of first historical transaction data, the target historical transaction data comprise transaction data of target transaction scenes in the plurality of first transaction scenes, the test module inputs the target historical transaction data into the test script for testing, a test result is obtained, and the second determination module determines whether the target transaction scenes are normal or not according to the test result.
Another aspect of the present disclosure provides a computing device, comprising: one or more processors; and a memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method as described above.
Another aspect of the present disclosure provides a non-transitory readable storage medium storing computer executable instructions which, when executed, are configured to implement a method as described above.
Another aspect of the present disclosure provides a computer program comprising computer executable instructions which when executed are for implementing a method as described above.
Drawings
For a more complete understanding of the present disclosure and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:
FIG. 1 schematically illustrates a system architecture of a transaction scenario testing method and a transaction scenario testing device according to an embodiment of the present disclosure;
FIG. 2 schematically illustrates a flow chart of a method of testing a transaction scenario in accordance with an embodiment of the present disclosure;
FIG. 3 schematically illustrates a flow chart of determining targeted historical transaction data according to an embodiment of the present disclosure;
FIG. 4 schematically illustrates a flow chart of performing a test according to an embodiment of the disclosure;
FIG. 5 schematically illustrates a block diagram of a testing device of a transaction scenario according to an embodiment of the present disclosure;
FIG. 6 schematically illustrates a block diagram of a testing device of a transaction scenario according to another embodiment of the present disclosure;
FIG. 7 schematically illustrates a block diagram of a first determination module according to an embodiment of the disclosure;
FIG. 8 schematically illustrates a block diagram of a test module according to an embodiment of the disclosure; and
fig. 9 schematically illustrates a block diagram of a computer system for transaction scenario testing, according to an embodiment of the disclosure.
Detailed Description
Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is only exemplary and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the present disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. In addition, in the following description, descriptions of well-known structures and techniques are omitted so as not to unnecessarily obscure the concepts of the present disclosure.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and/or the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.
All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It should be noted that the terms used herein should be construed to have meanings consistent with the context of the present specification and should not be construed in an idealized or overly formal manner.
Where expressions like at least one of "A, B and C, etc. are used, the expressions should generally be interpreted in accordance with the meaning as commonly understood by those skilled in the art (e.g.," a system having at least one of A, B and C "shall include, but not be limited to, a system having a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.). Where a formulation similar to at least one of "A, B or C, etc." is used, in general such a formulation should be interpreted in accordance with the ordinary understanding of one skilled in the art (e.g. "a system with at least one of A, B or C" would include but not be limited to systems with a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).
Some of the block diagrams and/or flowchart illustrations are shown in the figures. It will be understood that some blocks of the block diagrams and/or flowchart illustrations, or combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable control apparatus, such that the instructions, when executed by the processor, create means for implementing the functions/acts specified in the block diagrams and/or flowchart.
Thus, the techniques of this disclosure may be implemented in hardware and/or software (including firmware, microcode, etc.). Additionally, the techniques of this disclosure may take the form of a computer program product on a computer-readable medium having instructions stored thereon, the computer program product being usable by or in connection with an instruction execution system. In the context of this disclosure, a computer-readable medium may be any medium that can contain, store, communicate, propagate, or transport the instructions. For example, a computer-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. Specific examples of the computer readable medium include: magnetic storage devices such as magnetic tape or hard disk (HDD); optical storage devices such as compact discs (CD-ROMs); a memory, such as a Random Access Memory (RAM) or a flash memory; and/or a wired/wireless communication link.
The embodiment of the disclosure provides a method for testing a transaction scenario, which comprises the following steps: the method comprises the steps of obtaining a plurality of first historical transaction data, wherein the plurality of first historical transaction data comprise transaction data of a plurality of first transaction scenes, determining target historical transaction data based on the plurality of first historical transaction data, wherein the target historical transaction data comprise transaction data of target transaction scenes in the plurality of first transaction scenes, inputting the target historical transaction data into a test script for testing, obtaining a test result, and determining whether the target transaction scenes are normal according to the test result.
Fig. 1 schematically illustrates a system architecture of a transaction scenario testing method and a transaction scenario testing apparatus according to an embodiment of the present disclosure. It should be noted that fig. 1 is only an example of a system architecture to which embodiments of the present disclosure may be applied to assist those skilled in the art in understanding the technical content of the present disclosure, but does not mean that embodiments of the present disclosure may not be used in other devices, systems, environments, or scenarios.
As shown in fig. 1, a system architecture 100 according to this embodiment may include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 is used as a medium to provide communication links between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
The user may interact with the server 105 via the network 104 using the terminal devices 101, 102, 103 to receive or send messages or the like. Various communication client applications, such as shopping class applications, web browser applications, search class applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only) may be installed on the terminal devices 101, 102, 103.
The terminal devices 101, 102, 103 may be a variety of electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.
The server 105 may be a server providing various services, such as a background management server (by way of example only) providing support for websites browsed by users using the terminal devices 101, 102, 103. The background management server may analyze and process the received data such as the user request, and feed back the processing result (e.g., the web page, information, or data obtained or generated according to the user request) to the terminal device.
It should be noted that the method for testing a transaction scenario provided by the embodiments of the present disclosure may be generally performed by the server 105. Accordingly, the testing device for the transaction scenario provided by the embodiments of the present disclosure may be generally disposed in the server 105. The method of testing a transaction scenario provided by embodiments of the present disclosure may also be performed by a server or cluster of servers other than server 105 and capable of communicating with terminal devices 101, 102, 103 and/or server 105. Accordingly, the testing apparatus of the transaction scenario provided by the embodiments of the present disclosure may also be provided in a server or a server cluster different from the server 105 and capable of communicating with the terminal devices 101, 102, 103 and/or the server 105.
It should be understood that the number of terminal devices, networks and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
A method of testing a transaction scenario according to an exemplary embodiment of the present disclosure is described below with reference to fig. 2-4 in conjunction with the system architecture of fig. 1. It should be noted that the above application scenario is only shown for the convenience of understanding the spirit and principles of the present disclosure, and the embodiments of the present disclosure are not limited in any way in this respect. Rather, embodiments of the present disclosure may be applied to any scenario where applicable.
Fig. 2 schematically illustrates a flow chart of a method of testing a transaction scenario in accordance with an embodiment of the present disclosure.
As shown in fig. 2, the method includes operations S210 to S240.
In operation S210, a plurality of first historical transaction data including transaction data of a plurality of first transaction scenarios is acquired.
According to an embodiment of the present disclosure, the first historical transaction data is, for example, transaction data generated by conducting a transaction in a real scene. The first historical transaction data includes a plurality of data under a first transaction scenario. For example, the tester may configure corresponding environmental zone information in the configuration interface to select first historical transaction data for the corresponding zone.
In operation S220, target historical transaction data is determined based on the plurality of first historical transaction data, wherein the target historical transaction data includes transaction data of a target transaction scenario of the plurality of first transaction scenarios.
According to an embodiment of the present disclosure, transaction data of a high frequency client, such as a high number of clients, is selected, for example, from a plurality of first historical transaction data. Further, the transaction data of the high-frequency business scenario can be selected from the transaction data of the high-frequency client as the target historical transaction data, wherein the high-frequency business transaction scenario is a transaction scenario with a larger transaction scenario proportion in the transaction data of the high-frequency client, namely, the transaction scenario with a larger proportion can be used as the target transaction scenario, and the transaction data in the target transaction scenario is the target historical transaction data.
In operation S230, the target historical transaction data is input into the test script for testing, and a test result is obtained.
For example, the target historical transaction data is input into a UFT (Unified Functional Testing) test script for testing, and a test result is obtained.
For example, taking a target historical transaction data as an example, when a target historical transaction data is: the customer A can transfer money to the customer B, the transfer money is C element, the currency is RMB, the afferent is China, and the commission charge mode is to pay commission charge for the sender. The target historical transaction data is input into the UFT test script for testing, for example, a test result obtained by executing a remittance instruction comprises a transaction result, the transaction result comprises remittance person information, payee information, currency information, remittance place information, commission fee collection mode information and the like, and the test result can be used for judging whether the target transaction scene is normal or not.
In operation S240, it is determined whether the target transaction scenario is normal according to the test result. For example, the target historical transaction data is compared with the test results to obtain a comparison result. And responding to the inconsistent comparison result characterization target historical transaction data and the test result, determining that the target transaction scene is abnormal and outputting prompt information.
For example, remitter information, payee information, currency information, remittance information, fee collection mode information and the like in the test result are compared with the target historical transaction data, if the remittance information, the payee information, the currency information, the remittance information, the fee collection mode information and the like are consistent, the target transaction scene is normal, and if the remittance information, the fee collection mode information and the like are inconsistent, the target transaction scene is abnormal. Under the condition that the target transaction scene is abnormal, prompt information can be output. The prompt information may include a portion where information in the test result and the target historical transaction data are inconsistent, for example, when a fee collection manner in the target historical transaction data is a fee payment manner for a sender, the fee collection manner in the test result is a fee payment manner for a receiver, the fee collection manner in the test result is abnormal, and the fee collection manner is marked as abnormal.
According to the embodiment of the disclosure, the high-frequency scene transaction data of the high-frequency client is extracted as the test data, so that the real transaction data can be effectively utilized, the test data do not need to be prepared by a tester according to experience, and the time for preparing the test data is greatly shortened. In addition, the real high-frequency service scene is extracted for carrying out the parallelization test, so that a larger range of real transaction scenes can be covered in a shorter time, the test efficiency is effectively improved, and the test workload is reduced.
FIG. 3 schematically illustrates a flow chart of determining targeted historical transaction data according to an embodiment of the present disclosure.
As shown in fig. 3, the operation S220 includes operations S221 to S222.
According to an embodiment of the present disclosure, the first historical transaction data includes transaction data generated by at least one user initiated transaction.
In operation S221, second historical transaction data is determined based on the plurality of first historical transaction data, wherein the second historical transaction data is generated by a target user-initiated transaction among the at least one user.
In operation S222, target historical transaction data is determined based on the second historical transaction data. The first historical transaction data are the first quantity, the second historical transaction data are the second quantity, and the ratio between the second quantity and the first quantity meets the first preset ratio.
For example, second historical transaction data generated by the target user initiating the transaction is selected from the plurality of first historical transaction data. For example, 300 users initiate transactions to generate 1000 first historical transaction data, for example, 2 users are selected from 300 users, the first historical transaction data of the 2 users is 600, the ratio of 600 to 1000 is 0.6, the ratio exceeds a first preset ratio (the first preset ratio is, for example, 0.5), then the 2 users are target users, and 600 first historical transaction data of the 2 users can be used as second historical transaction data.
According to an embodiment of the present disclosure, the above-mentioned operation S222 specifically includes the following steps (1) to (3).
(1) At least one second transaction scenario to which the second historical transaction data belongs is determined.
For example, the configuration interface includes a plurality of service fields, and the service fields include fields such as an importation place, a currency, a fee collection manner, and the like. Each field corresponds to at least one field value, for example, the field value corresponding to the location of the remittance includes china, the united states, and the like, the field value corresponding to the currency includes, for example, rmb, dollars, and the like, and the fee collection includes, for example, sender payment, receiver payment, and the like.
Wherein, after selecting 600 second historical transaction data of 2 users, a second transaction scenario of each of the 600 second historical transaction data may be determined. For example, a plurality of combinations are obtained by combining any of the field values in each service field, each combination representing one of the second transaction scenarios. Taking a second transaction scenario as an example, the second transaction scenario is, for example: the remittance area is China, the currency is RMB, and the charging mode of the commission fee is paid for remittance persons.
For example, the second historical transaction data may be extracted in terms of a business field. For example, any field value in each service field is used as a joint main key to traverse the second historical transaction data, the joint main key is the same and is regarded as a transaction record, duplicate removal is performed, and the number of the second historical transaction data corresponding to the joint main key is recorded, so that a plurality of second transaction scenes and the number of the second historical transaction data in each second transaction scene can be obtained.
(2) A target transaction scenario among the at least one second transaction scenario is determined. The second historical transaction data is a second quantity, the target historical transaction data is a third quantity, and the ratio between the third quantity and the second quantity meets a second preset ratio.
(3) And determining transaction data belonging to the target transaction scene in the second historical transaction data as target historical transaction data.
For example, in 600 second historical transaction data, the transaction scenario is: the transaction data which are paid for remittance persons by the remittance places of China, the currencies of the remittance places of the remittance persons are 300, and the transaction scene is as follows: the transaction data which is collected into the united states, the currency is dollar, and the payment method of the handling fee is 180 for remittance persons, the second historical transaction data corresponding to the two transaction scenes is 480, the ratio of 480 to 600 is 0.8, the ratio exceeds the second preset ratio (the second preset ratio is 0.6, for example), the 480 second historical transaction data can be used as target historical transaction data, the transaction scene corresponding to the target historical transaction data is used as target transaction scene, and the target transaction scene is the high-frequency transaction scene.
Fig. 4 schematically illustrates a flow chart of performing a test according to an embodiment of the present disclosure.
As shown in fig. 4, the operation S230 includes operations S231 to S232.
In operation S231, an update operation is performed on the target historical transaction data, resulting in updated target historical transaction data.
According to the embodiment of the disclosure, part of the information in the obtained target historical transaction data is not available for testing, for example, the initial transaction password and the initial transaction authentication mode in the target historical transaction data cannot be directly used, so that the initial transaction password in the target historical transaction data needs to be reset and the initial transaction authentication mode in the target historical transaction data needs to be replaced.
According to an embodiment of the present disclosure, the above-described operation S231 specifically includes the following steps (1) to (4).
(1) And determining an initial transaction password and an initial transaction authentication mode of the target historical transaction data. The initial transaction authentication mode comprises an initial transaction authentication medium, and the initial transaction authentication medium comprises a digital certificate, a dynamic password and the like.
(2) And obtaining a test password and a test authentication mode.
(3) The initial transaction password is updated based on the test password.
(4) And updating the initial transaction authentication mode based on the test authentication mode.
In operation S232, a test is performed based on the updated target historical transaction data, and a test result is obtained. For example, the updated target historical transaction data comprises available test passwords and test authentication media, and the updated target historical transaction data is input into the UFT test script for testing.
The above operation S230 may specifically further include: testing target historical transaction data to obtain a transaction result, acquiring a historical transaction message corresponding to the target historical transaction data, processing the historical transaction message to obtain a message rule of the target historical transaction data, and processing the transaction result based on the message rule to obtain a test result.
For example, the format of transaction messages varies from region to region. According to historical transaction messages reported in different regions, the transaction messages are assembled to form message rules corresponding to the regions, and the message rules can be input into UFT test scripts so that the obtained test results accord with the corresponding message rules.
According to the embodiment of the disclosure, the message rules of different areas are set so as to adapt to the testing of multiple overseas line differentiation, and the testing is performed based on the message rules, so that the checking accuracy of the testing result is improved, and the errors caused by manual checking are avoided. In addition, the embodiment of the disclosure realizes high-frequency service scene extraction by using the scripting language, and various operating systems can run the test scripts, so that the technical scheme of the embodiment of the disclosure can be better popularized and used.
Fig. 5 schematically illustrates a block diagram of a testing device of a transaction scenario according to an embodiment of the present disclosure.
As shown in fig. 5, the testing apparatus 500 of the transaction scenario includes a high frequency data configuration module 510, a script module 520, a message auto-checking module 530, and a communication module 540.
The high frequency data configuration module 510 is configured to configure the environmental region information and configure the critical service fields. The configuration environment area information is mainly used for configuring the test environment large area and the branch area code through the configuration interface. The key service field is mainly configured by a tester according to different transaction types, such as remittance, currency, commission fee collection mode and the like, and a high-frequency service scene model is established.
The script module 520 is configured to output high frequency client information, output a high frequency service scenario, and perform testing based on the UFT script. The method comprises the steps of outputting high-frequency client information, namely outputting a group number and a submitter ID with the largest transaction occurring in a certain time, and preparing for converting the medium type into test data. Outputting the high-frequency service scene comprises traversing the transaction type data table according to the key service field, removing duplication of the same record, and then ordering to generate an ordering table with the transaction amount from large to small. Testing based on the UFT script, including pre-recording the written reset password, replacing authentication medium and various types of remittance scripts, then importing high-frequency client information and high-frequency service data into the defined scripts, then carrying out parameterization processing, and completing automatic testing by data driving.
The message auto-checking module 530 is configured to assemble an expected message, extract an actual message, and compare the expected message with the actual message. The expected message comprises a message of target historical transaction data, and the actual message comprises a message of a test result obtained by testing the target historical transaction data. Assembling the expected message comprises assembling the expected message according to the message uploading rules of different regions and the high-frequency service data (target historical transaction data) in the script, and storing the expected message in the txt document. Extracting the actual message comprises running UFT automation script, completing the submission of the remittance instruction, and reading the host database to obtain the actual message. Comparing the expected message with the actual message comprises the step of comparing the actual message with the expected message item by item, if the same checking result is assigned to pass, if different checking results are assigned to fail, the comparison result is marked with red.
The communication module 540 is configured to output a result, for example, including outputting a comparison result of an actual result and an expected result, so that a check result of each item of the message can be checked. For example, outputting the checking result includes displaying an instruction list, a message state, a message checking result and a detail button, and by clicking the detail button, each item of matching result of the message can be checked. And when the check result is inquired later, the test result can be inquired according to the remittance instruction sequence number and the check result, so that the follow-up analysis and statistics are facilitated.
Fig. 6 schematically illustrates a block diagram of a testing device of a transaction scenario according to another embodiment of the present disclosure.
As shown in fig. 6, the testing apparatus 600 of the transaction scenario includes an acquisition module 610, a first determination module 620, a testing module 630, and a second determination module 640.
The acquisition module 610 may be configured to acquire a plurality of first historical transaction data including transaction data for a plurality of first transaction scenarios. The obtaining module 610 may, for example, perform operation S210 described above with reference to fig. 2 according to an embodiment of the present disclosure, which is not described herein.
The first determination module 620 may be configured to determine target historical transaction data based on the plurality of first historical transaction data, wherein the target historical transaction data includes transaction data for a target transaction scenario of the plurality of first transaction scenarios. According to an embodiment of the present disclosure, the first determining module 620 may perform, for example, operation S220 described above with reference to fig. 2, which is not described herein.
The test module 630 may be configured to input the target historical transaction data into a test script for testing, to obtain a test result. According to an embodiment of the present disclosure, the test module 630 may perform, for example, operation S230 described above with reference to fig. 2, which is not described herein.
According to an embodiment of the present disclosure, inputting target historical transaction data into a test script for testing, to obtain a test result, including: testing target historical transaction data to obtain a transaction result, acquiring a historical transaction message corresponding to the target historical transaction data, processing the historical transaction message to obtain a message rule of the target historical transaction data, and processing the transaction result based on the message rule to obtain a test result.
The second determining module 640 may be configured to determine whether the target transaction scenario is normal according to the test result. The second determining module 640 may, for example, perform operation S240 described above with reference to fig. 2 according to an embodiment of the present disclosure, which is not described herein.
According to an embodiment of the present disclosure, determining whether a target transaction scenario is normal according to a test result includes: comparing the target historical transaction data with the test result to obtain a comparison result, responding to the inconsistent comparison result characterization target historical transaction data and the test result, determining that the target transaction scene is abnormal, and outputting prompt information.
Fig. 7 schematically illustrates a block diagram of a first determination module according to an embodiment of the disclosure.
As shown in fig. 7, the first determination module 620 includes a first determination sub-module 621 and a second determination sub-module 622.
The first determination submodule 621 may be configured to determine second historical transaction data based on a plurality of first historical transaction data, wherein the first historical transaction data includes transaction data generated by at least one user-initiated transaction, and the second historical transaction data is generated by a target user-initiated transaction among the at least one user. The first determination sub-module 621 may perform, for example, operation S221 described above with reference to fig. 3 according to an embodiment of the present disclosure, which is not described herein.
The second determining sub-module 622 may be configured to determine target historical transaction data based on second historical transaction data, where the first historical transaction data is a first quantity, the second historical transaction data is a second quantity, the target historical transaction data is a third quantity, a ratio between the second quantity and the first quantity satisfies a first preset ratio, and a ratio between the third quantity and the second quantity satisfies a second preset ratio. The second determining sub-module 622 may, for example, perform operation S222 described above with reference to fig. 3, which is not described herein.
According to an embodiment of the present disclosure, determining target transaction data history data based on second history transaction data includes: determining at least one second transaction scene to which the second historical transaction data belongs, determining a target transaction scene in the at least one second transaction scene, and determining the transaction data belonging to the target transaction scene in the second historical transaction data as target historical transaction data.
Fig. 8 schematically illustrates a block diagram of a test module according to an embodiment of the disclosure.
As shown in fig. 8, the test module 630 includes an update sub-module 631 and a test sub-module 632.
The update sub-module 631 may be configured to perform an update operation on the target historical transaction data to obtain updated target historical transaction data. The update sub-module 631 may, for example, perform operation S231 described above with reference to fig. 4 according to an embodiment of the present disclosure, which is not described here again.
According to the embodiment of the disclosure, an updating operation is performed on target historical transaction data to obtain updated target historical transaction data, wherein the updating operation comprises determining an initial transaction password and an initial transaction authentication mode of the target historical transaction data, acquiring a test password and a test authentication mode, updating the initial transaction password based on the test password, and updating the initial transaction authentication mode based on the test authentication mode.
The test sub-module 632 may be configured to perform a test based on the updated target historical transaction data to obtain a test result. According to an embodiment of the present disclosure, the test sub-module 632 may perform, for example, operation S232 described above with reference to fig. 4, which is not described herein.
Any number of modules, sub-modules, units, sub-units, or at least some of the functionality of any number of the sub-units according to embodiments of the present disclosure may be implemented in one module. Any one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be implemented as split into multiple modules. Any one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be implemented at least in part as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system-on-chip, a system-on-substrate, a system-on-package, an Application Specific Integrated Circuit (ASIC), or in any other reasonable manner of hardware or firmware that integrates or encapsulates the circuit, or in any one of or a suitable combination of three of software, hardware, and firmware. Alternatively, one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be at least partially implemented as computer program modules, which when executed, may perform the corresponding functions.
For example, any of the acquisition module 610, the first determination module 620, the test module 630, the second determination module 640, the first determination sub-module 621, the second determination sub-module 622, the update sub-module 631, and the test sub-module 632 may be combined in one module to be implemented, or any one of the modules may be split into a plurality of modules. Alternatively, at least some of the functionality of one or more of the modules may be combined with at least some of the functionality of other modules and implemented in one module. According to embodiments of the present disclosure, at least one of the acquisition module 610, the first determination module 620, the test module 630, the second determination module 640, the first determination sub-module 621, the second determination sub-module 622, the update sub-module 631, and the test sub-module 632 may be implemented at least in part as hardware circuitry, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in hardware or firmware in any other reasonable manner of integrating or packaging circuitry, or in any one of or a suitable combination of three of software, hardware, and firmware implementations. Alternatively, at least one of the acquisition module 610, the first determination module 620, the test module 630, the second determination module 640, the first determination sub-module 621, the second determination sub-module 622, the update sub-module 631, and the test sub-module 632 may be at least partially implemented as computer program modules that, when executed, perform the respective functions.
Fig. 9 schematically illustrates a block diagram of a computer system for transaction scenario testing, according to an embodiment of the disclosure. The computer system illustrated in fig. 9 is merely an example, and should not be construed as limiting the functionality and scope of use of the embodiments of the present disclosure.
As shown in fig. 9, the computer system 900 includes a processor 901, a computer readable storage medium 902. The system 900 may perform methods according to embodiments of the present disclosure.
In particular, processor 901 may include, for example, a general purpose microprocessor, an instruction set processor and/or an associated chipset and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), or the like. Processor 901 may also include on-board memory for caching purposes. Processor 901 may be a single processing unit or multiple processing units for performing the different actions of the method flows according to embodiments of the disclosure.
The computer-readable storage medium 902 may be, for example, any medium that can contain, store, communicate, propagate, or transport the instructions. For example, a readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. Specific examples of the readable storage medium include: magnetic storage devices such as magnetic tape or hard disk (HDD); optical storage devices such as compact discs (CD-ROMs); a memory, such as a Random Access Memory (RAM) or a flash memory; and/or a wired/wireless communication link.
The computer-readable storage medium 902 may comprise a computer program 903, which computer program 903 may comprise code/computer executable instructions which, when executed by the processor 901, cause the processor 901 to perform a method according to an embodiment of the present disclosure or any variant thereof.
The computer program 903 may be configured with computer program code comprising, for example, computer program modules. For example, in an example embodiment, code in computer program 903 may include one or more program modules, including 903A, modules 903B, … …, for example. It should be noted that the division and number of modules is not fixed, and a person skilled in the art may use suitable program modules or combinations of program modules according to the actual situation, which when executed by the processor 901, enable the processor 901 to perform the method according to embodiments of the present disclosure or any variations thereof.
According to an embodiment of the present disclosure, at least one of the acquisition module 610, the first determination module 620, the test module 630, the second determination module 640, the first determination sub-module 621, the second determination sub-module 622, the update sub-module 631, and the test sub-module 632 may be implemented as a computer program module described with reference to fig. 9, which when executed by the processor 901, may implement the respective operations described above.
The present disclosure also provides a computer-readable medium that may be embodied in the apparatus/device/system described in the above embodiments; or may exist alone without being assembled into the apparatus/device/system. The computer readable medium carries one or more programs which, when executed, implement the methods described above.
According to embodiments of the present disclosure, the computer readable medium may be a computer readable signal medium or a computer readable storage medium or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this disclosure, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present disclosure, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, fiber optic cable, radio frequency signals, or the like, or any suitable combination of the foregoing.
Those skilled in the art will appreciate that the features recited in the various embodiments of the disclosure and/or in the claims may be combined in various combinations and/or combinations. While the present disclosure has been shown and described with reference to certain exemplary embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present disclosure as defined by the appended claims and their equivalents. The scope of the disclosure should, therefore, not be limited to the above-described embodiments, but should be determined not only by the following claims, but also by the equivalents of the following claims.

Claims (7)

1. A method for testing a transaction scenario, comprising:
acquiring a plurality of first historical transaction data, wherein the plurality of first historical transaction data comprises transaction data of a plurality of first transaction scenes;
determining target historical transaction data based on the plurality of first historical transaction data, wherein the target historical transaction data comprises transaction data of a target transaction scenario of the plurality of first transaction scenarios;
inputting the target historical transaction data into a test script for testing to obtain a test result; and
Determining whether the target transaction scene is normal according to the test result,
wherein the first historical transaction data comprises transaction data generated by at least one user initiating a transaction;
the determining target historical transaction data based on the plurality of first historical transaction data includes:
determining second historical transaction data based on the plurality of first historical transaction data, wherein the second historical transaction data is generated by a target user initiation transaction among the at least one user; and
determining the target historical transaction data based on the second historical transaction data specifically includes:
determining at least one second transaction scenario to which the second historical transaction data belongs;
determining a target transaction scenario among the at least one second transaction scenario; and
determining transaction data belonging to the target transaction scene in the second historical transaction data as the target historical transaction data;
wherein the first historical transaction data is a first quantity, the second historical transaction data is a second quantity, the target historical transaction data is a third quantity, the ratio between the second quantity and the first quantity satisfies a first preset ratio, the ratio between the third quantity and the second quantity satisfies a second preset ratio,
And inputting the target historical transaction data into a test script for testing to obtain a test result, wherein the method comprises the following steps:
testing the target historical transaction data to obtain a transaction result;
acquiring a historical transaction message corresponding to the target historical transaction data;
processing the historical transaction message to obtain a message rule of the target historical transaction data, which specifically comprises the following steps: processing historical transaction messages reported in different areas, and assembling the historical transaction messages reported in different areas to obtain message rules corresponding to the areas of the target historical transaction data; and
and processing the transaction result based on the message rule to obtain the test result.
2. The method of claim 1, wherein the inputting the target historical transaction data into a test script for testing, resulting in a test result, comprises:
performing updating operation on the target historical transaction data to obtain updated target historical transaction data; and
and testing based on the updated target historical transaction data to obtain the test result.
3. The method of claim 2, wherein the performing an update operation on the target historical transaction data to obtain updated target historical transaction data comprises:
Determining an initial transaction password and an initial transaction authentication mode of the target historical transaction data;
acquiring a test password and a test authentication mode;
updating the initial transaction password based on the test password; and
and updating the initial transaction authentication mode based on the test authentication mode.
4. The method of claim 1, wherein the determining whether the target transaction scenario is normal based on the test result comprises:
comparing the target historical transaction data with the test result to obtain a comparison result; and
and responding to the comparison result to represent that the target historical transaction data is inconsistent with the test result, determining that the target transaction scene is abnormal, and outputting prompt information.
5. A transaction scenario testing device, comprising:
the system comprises an acquisition module, a storage module and a display module, wherein the acquisition module acquires a plurality of first historical transaction data, and the plurality of first historical transaction data comprises transaction data of a plurality of first transaction scenes;
a first determination module that determines target historical transaction data based on the plurality of first historical transaction data, wherein the target historical transaction data includes transaction data of a target transaction scenario of the plurality of first transaction scenarios;
The test module inputs the target historical transaction data into a test script for testing to obtain a test result; and
a second determining module for determining whether the target transaction scene is normal according to the test result,
wherein the first historical transaction data comprises transaction data generated by at least one user initiating a transaction;
the determining target historical transaction data based on the plurality of first historical transaction data includes:
determining second historical transaction data based on the plurality of first historical transaction data, wherein the second historical transaction data is generated by a target user initiation transaction among the at least one user; and
determining the target historical transaction data based on the second historical transaction data specifically includes:
determining at least one second transaction scenario to which the second historical transaction data belongs;
determining a target transaction scenario among the at least one second transaction scenario; and
determining transaction data belonging to the target transaction scene in the second historical transaction data as the target historical transaction data;
wherein the first historical transaction data is a first quantity, the second historical transaction data is a second quantity, the target historical transaction data is a third quantity, the ratio between the second quantity and the first quantity satisfies a first preset ratio, the ratio between the third quantity and the second quantity satisfies a second preset ratio,
And inputting the target historical transaction data into a test script for testing to obtain a test result, wherein the method comprises the following steps:
testing the target historical transaction data to obtain a transaction result;
acquiring a historical transaction message corresponding to the target historical transaction data;
processing the historical transaction message to obtain a message rule of the target historical transaction data, which specifically comprises the following steps: processing historical transaction messages reported in different areas, and assembling the historical transaction messages reported in different areas to obtain message rules corresponding to the areas of the target historical transaction data; and
and processing the transaction result based on the message rule to obtain the test result.
6. A computing device, comprising:
one or more processors;
a memory for storing one or more programs,
wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method of any of claims 1-4.
7. A computer readable storage medium storing computer executable instructions which, when executed, are adapted to carry out the method of any one of claims 1 to 4.
CN201910665508.6A 2019-07-22 2019-07-22 Transaction scene testing method, device, computing equipment and medium Active CN110377522B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201910665508.6A CN110377522B (en) 2019-07-22 2019-07-22 Transaction scene testing method, device, computing equipment and medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910665508.6A CN110377522B (en) 2019-07-22 2019-07-22 Transaction scene testing method, device, computing equipment and medium

Publications (2)

Publication Number Publication Date
CN110377522A CN110377522A (en) 2019-10-25
CN110377522B true CN110377522B (en) 2023-10-03

Family

ID=68255004

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910665508.6A Active CN110377522B (en) 2019-07-22 2019-07-22 Transaction scene testing method, device, computing equipment and medium

Country Status (1)

Country Link
CN (1) CN110377522B (en)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111026665B (en) * 2019-12-09 2023-02-28 建信金融科技有限责任公司 Test range analysis method, device and equipment
CN112988552B (en) * 2019-12-12 2023-06-30 腾讯科技(深圳)有限公司 Application program testing method, device, equipment and storage medium
CN111414305B (en) * 2020-03-18 2023-03-28 中国工商银行股份有限公司 Test method, test device, test apparatus, and medium
CN111402057A (en) * 2020-03-31 2020-07-10 中国工商银行股份有限公司 Transaction message matching method, device, computing equipment and medium
CN111639022B (en) * 2020-05-16 2023-06-06 中信银行股份有限公司 Transaction testing method and device, storage medium and electronic device
CN111782540B (en) * 2020-07-10 2023-08-22 中国工商银行股份有限公司 Test processing method and device
CN112419052A (en) * 2020-09-30 2021-02-26 中信百信银行股份有限公司 Transaction testing method and device, electronic equipment and readable storage medium

Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9104815B1 (en) * 2011-05-08 2015-08-11 Panaya Ltd. Ranking runs of test scenarios based on unessential executed test steps
CN105930259A (en) * 2015-12-23 2016-09-07 中国银联股份有限公司 Method and apparatus for WEB regression testing
CN106157138A (en) * 2016-08-31 2016-11-23 中国银行股份有限公司 Group belonging to a kind of bank transaction data determines method and device
CN106803202A (en) * 2016-12-22 2017-06-06 中国银联股份有限公司 The extracting method and device of a kind of transaction record to be tested
CN107102947A (en) * 2017-05-12 2017-08-29 中国工商银行股份有限公司 ATM transaction flows test device and method
CN107229559A (en) * 2016-03-23 2017-10-03 阿里巴巴集团控股有限公司 For the detection method and device of the test integrity degree of operation system
CN107368428A (en) * 2017-09-07 2017-11-21 马上消费金融股份有限公司 A kind of method for testing software and software testing system
CN107391359A (en) * 2016-05-17 2017-11-24 腾讯科技(深圳)有限公司 A kind of service test method and device
CN108446222A (en) * 2018-03-05 2018-08-24 百度在线网络技术(北京)有限公司 Application testing method, device and equipment
CN109063920A (en) * 2018-08-20 2018-12-21 阿里巴巴集团控股有限公司 A kind of transaction risk recognition methods, device and computer equipment
CN109087138A (en) * 2018-07-26 2018-12-25 北京京东金融科技控股有限公司 Data processing method and system, computer system and readable storage medium storing program for executing
CN109376999A (en) * 2018-09-20 2019-02-22 阿里巴巴集团控股有限公司 A kind of management-control method of transaction, device and equipment
CN109783381A (en) * 2019-01-07 2019-05-21 中国银行股份有限公司 A kind of test data generating method, apparatus and system
CN109859028A (en) * 2019-01-03 2019-06-07 深圳壹账通智能科技有限公司 A kind of verification method, system, medium and the electronic equipment of repaying information

Patent Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9104815B1 (en) * 2011-05-08 2015-08-11 Panaya Ltd. Ranking runs of test scenarios based on unessential executed test steps
CN105930259A (en) * 2015-12-23 2016-09-07 中国银联股份有限公司 Method and apparatus for WEB regression testing
CN107229559A (en) * 2016-03-23 2017-10-03 阿里巴巴集团控股有限公司 For the detection method and device of the test integrity degree of operation system
CN107391359A (en) * 2016-05-17 2017-11-24 腾讯科技(深圳)有限公司 A kind of service test method and device
CN106157138A (en) * 2016-08-31 2016-11-23 中国银行股份有限公司 Group belonging to a kind of bank transaction data determines method and device
CN106803202A (en) * 2016-12-22 2017-06-06 中国银联股份有限公司 The extracting method and device of a kind of transaction record to be tested
CN107102947A (en) * 2017-05-12 2017-08-29 中国工商银行股份有限公司 ATM transaction flows test device and method
CN107368428A (en) * 2017-09-07 2017-11-21 马上消费金融股份有限公司 A kind of method for testing software and software testing system
CN108446222A (en) * 2018-03-05 2018-08-24 百度在线网络技术(北京)有限公司 Application testing method, device and equipment
CN109087138A (en) * 2018-07-26 2018-12-25 北京京东金融科技控股有限公司 Data processing method and system, computer system and readable storage medium storing program for executing
CN109063920A (en) * 2018-08-20 2018-12-21 阿里巴巴集团控股有限公司 A kind of transaction risk recognition methods, device and computer equipment
CN109376999A (en) * 2018-09-20 2019-02-22 阿里巴巴集团控股有限公司 A kind of management-control method of transaction, device and equipment
CN109859028A (en) * 2019-01-03 2019-06-07 深圳壹账通智能科技有限公司 A kind of verification method, system, medium and the electronic equipment of repaying information
CN109783381A (en) * 2019-01-07 2019-05-21 中国银行股份有限公司 A kind of test data generating method, apparatus and system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
一种跨业务场景的测试案例组构建方法;张丹阳等;《中国金融电脑》;20180907(第09期);全文 *

Also Published As

Publication number Publication date
CN110377522A (en) 2019-10-25

Similar Documents

Publication Publication Date Title
CN110377522B (en) Transaction scene testing method, device, computing equipment and medium
CN108346028B (en) Business approval processing method, device and system
US20230401555A1 (en) System and method for transaction account based micro-payments
CN109308266A (en) Construction method, test method, device, equipment and the medium of test case
US11087770B2 (en) Dispute initiation using artificial intelligence
US20220138705A1 (en) Search Engine with Automated Blockchain-Based Smart Contracts
CN105469502A (en) Intelligent oiling method and terminal
US11935068B1 (en) Methods and apparatus for mobile device messaging-based communications using custom-generated deeplinks and based on the hyper text transfer protocol (HTTP)
CN104376452A (en) System and method for managing payment success rate on basis of international card payment channel
US10949853B2 (en) Systems and methods for providing concurrent data loading and rules execution in risk evaluations
CN112288577B (en) Transaction processing method, device, electronic equipment and medium for distributed service
US11222270B2 (en) Using learned application flow to predict outcomes and identify trouble spots in network business transactions
US11227220B2 (en) Automatic discovery of data required by a rule engine
CN113205402A (en) Account checking method and device, electronic equipment and computer readable medium
CA3217578A1 (en) Payment processing method, device, medium and electronic device
US20150248673A1 (en) Methods and apparatus for a token management system for transactions
WO2023197917A1 (en) Payment security management method and apparatus and payment system
US20230222461A1 (en) System and method for payment processing telemetry
CN109345249B (en) Payment failure processing method and device
US20170249697A1 (en) System and method for machine learning based line assignment
CN112541765A (en) Method and apparatus for detecting suspicious transactions
US11030673B2 (en) Using learned application flow to assist users in network business transaction based apps
CN109542743A (en) Log method of calibration, device, electronic equipment and computer readable storage medium
CN115391343A (en) Bill data processing method and device, electronic equipment and storage medium
CN110569424A (en) Information recommendation 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