Account following test method and device and electronic equipment
By determining the production request message of the automatic task and the business fields of the target outbound call transaction in the new system, the problem of automatic task Sino-foreign call transaction reading test is solved, and the complete accounting test of the automatic task is realized.
Patent Information
- Application Number
- CN202411492497.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-24
- Publication Date
- 2025-02-25
AI Technical Summary
The prior art cannot support the accounting test of automatic task Chinese and foreign call transactions, because the tracking number of outgoing call transactions generated by automatic task cannot match production packets.
By in response to the automatic task trigger in the new system, the production request message corresponding to the automatic task is determined, the target out-call transaction is determined based on the message, and the original message is determined from the target database according to the transaction's business field, thereby performing the automatic task and obtaining the accounting test results.
The accounting test of automatic task Chinese and foreign call transactions is realized, and the problem that the outgoing call transactions generated by automatic task cannot match the original message produced is solved, ensuring the integrity and correctness of the automatic task.
Smart Images
Figure CN119512934A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the fields of data processing, financial technology, and information technology industry technology, and in particular to an account tracking testing method, device, and electronic equipment. Background Art
[0002] When a financial business system switches between an old and new system, it is necessary to perform functional testing to verify the correctness of the new system. Based on this, the financial business system will introduce account tracking testing, that is, simulating transactions of the old system in the new system, performing automatic task testing, and then comparing the messages between the new and old systems to perform comprehensive functional verification of the automatic tasks in the new system.
[0003] In the prior art, outbound transactions rely on the baffle tool to match the production request message according to the transaction tracking number and return the corresponding production response message. However, the baffle tool in the above prior art only supports the online mode and matches the request message according to the transaction tracking number. However, since the outbound transaction tracking number initiated by the automatic task is actively generated, it cannot be matched with the production message, making the above prior art unable to support outbound transactions in the automatic task. Based on this, how to conduct account tracking test on the automatic task is an urgent problem to be solved. Summary of the invention
[0004] The present invention discloses an account tracking test method, device and electronic device, so as to propose an account tracking test method and realize the account tracking test of automatic tasks.
[0005] According to a first aspect of the present disclosure, there is provided an account tracking test method, the method comprising:
[0006] In response to the triggering of an automatic task in the new system, determining a production request message corresponding to the automatic task;
[0007] Based on the production request message, determining at least one corresponding target outbound call transaction;
[0008] Determine the service field corresponding to the target outbound call transaction, and determine the corresponding production original message based on the service field;
[0009] Executing the automatic task based on the production original message to obtain a test response message, wherein the test response message is used to indicate a test result of the automatic task in the new system;
[0010] A production response message of the automatic task is obtained, and based on the production response message and the test response message, an account tracking test result of the automatic task is determined.
[0011] According to a second aspect of the present disclosure, there is provided an account tracking test device, the device comprising:
[0012] A first determination module, configured to determine, in response to an automatic task trigger in the new system, a production request message corresponding to the automatic task;
[0013] A second determination module, configured to determine at least one corresponding target outbound call transaction based on the production request message;
[0014] A third determination module is used to determine the service field corresponding to the target outbound call transaction, and determine the corresponding production original message based on the service field;
[0015] An execution module, used for executing the automatic task based on the production original message to obtain a test response message, wherein the test response message is used to indicate a test result of the automatic task in the new system;
[0016] The comparison module is used to obtain the production response message of the automatic task, and determine the account tracking test result of the automatic task based on the production response message and the test response message.
[0017] According to a third aspect of the present disclosure, there is provided an electronic device, comprising: a processor; and a memory for storing instructions executable by the processor; wherein the processor is configured to execute the instructions to implement the account tracking test method as described in the first aspect embodiment above.
[0018] According to a fourth aspect of the present disclosure, a computer-readable storage medium is provided. When the instructions in the computer-readable storage medium are executed by a processor of a data management device / electronic device / server, the data management device / electronic device / server can execute the account tracking test method as described in the first aspect embodiment.
[0019] According to a fifth aspect of the present disclosure, a computer program product is provided, comprising a computer program / instruction, wherein when the computer program / instruction is executed by a processor, the account tracking test method of the first aspect embodiment is implemented.
[0020] The technical solution provided by the embodiments of the present disclosure brings at least the following beneficial effects:
[0021] In the account tracking test method, device and electronic device proposed in the present disclosure, in response to the triggering of an automatic task in the new system, a production request message corresponding to the automatic task is determined; based on the production request message, at least one corresponding target outbound call transaction is determined; the business field corresponding to the target outbound call transaction is determined, and the corresponding production original message is determined based on the business field; the automatic task is executed based on the production original message to obtain a test response message, wherein the test response message is used to indicate the test result of the automatic task in the new system; the production response message of the automatic task is obtained, and the account tracking test result of the automatic task is determined based on the production response message and the test response message. Therefore, in the account tracking test method proposed in the present disclosure, the corresponding production original message can be determined from the target database corresponding to the new system based on the business field corresponding to the target outbound call transaction, so that the outbound call transaction in the automatic task can be supported, which solves the problem that the outbound call transaction generated by the automatic task cannot match the production original message, and realizes the account tracking test of the automatic task.
[0022] Additional aspects and advantages of the present disclosure will be given in part in the following description and in part will be obvious from the following description or learned through practice of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0023] The drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the description are used to explain the principles of the present disclosure, and do not constitute improper limitations on the present disclosure.
[0024] Figure 1 A flowchart of an account tracking test method provided according to an embodiment of the present disclosure;
[0025] Figure 2 A flowchart of an account tracking test method provided according to another embodiment of the present disclosure;
[0026] Figure 3 A flowchart of an account tracking test method provided according to another embodiment of the present disclosure;
[0027] Figure 4 A schematic diagram of the structure of an account tracking test device provided according to an embodiment of the present disclosure;
[0028] Figure 5 The figure is a block diagram of an electronic device according to an exemplary embodiment. DETAILED DESCRIPTION
[0029] Embodiments of the present disclosure are described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present disclosure, and should not be construed as limiting the present disclosure.
[0030] It should be noted that the information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.) and signals involved in this application are all authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards of relevant countries and regions.
[0031] The acquisition, transmission, storage, use, and processing of data in the technical solution of this application comply with the relevant provisions of relevant laws and regulations.
[0032] In the embodiments of the present disclosure, some existing solutions in the industry, such as certain software, components, and models, may be mentioned. They should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.
[0033] The following describes the account tracking test method and device according to the embodiments of the present disclosure with reference to the accompanying drawings.
[0034] Figure 1 FIG. 1 is a flow chart of an account tracking test method provided according to another embodiment of the present disclosure, as shown in FIG. Figure 1 As shown, it may include:
[0035] Step 101: In response to the triggering of an automatic task in the new system, a production request message corresponding to the automatic task is determined.
[0036] The execution subject of the account tracking test method of this embodiment is an account tracking test device, which can be implemented by software and / or hardware, and can be configured in an electronic device.
[0037] In the disclosed embodiment, the automatic task may be a task that needs to be automatically executed periodically, for example, a bill repayment.
[0038] Furthermore, in the embodiment of the present disclosure, when an automatic task of the old system needs to be executed, the automatic task in the new system can be triggered at the same time, so that the old and new systems can execute the automatic task synchronously.
[0039] Further, in the embodiment of the present disclosure, in response to the triggering of an automatic task in the new system, a production request message corresponding to the automatic task may be determined.
[0040] Step 102: Based on the production request message, determine at least one corresponding target outbound call transaction.
[0041] Among them, in the embodiment of the present disclosure, after obtaining the production request message through the above steps, at least one corresponding target outbound call transaction can be determined.
[0042] In the disclosed embodiment, the production request message may include multiple transactions, wherein the multiple transactions may include outbound transactions and local transactions. In the disclosed embodiment, the local transaction requires local data; the outbound transaction requires data returned by the outbound call.
[0043] Furthermore, in the disclosed embodiment, at least one target outbound call transaction in the production request message can be determined according to the identifier of the outbound call transaction.
[0044] Step 103: Determine the business field corresponding to the target outbound call transaction, and determine the corresponding production original message based on the business field.
[0045] Among them, in the embodiment of the present disclosure, after obtaining the target outbound call transaction through the above steps, the business field corresponding to the target outbound call transaction can be determined, and the corresponding production original message can be determined based on the business field to solve the problem that the outbound transaction in the automatic task cannot match the production original message, so that the production original message of the target outbound call transaction in the automatic task can be obtained, and the account tracking test of the automatic task can be completed.
[0046] Specifically, in the disclosed embodiment, the method for determining the business field corresponding to the target outbound call transaction and determining the corresponding production original message based on the business field may include: determining the business field corresponding to the target outbound call transaction according to a mapping relationship table between the target outbound call transaction and the business field, and determining the corresponding production original message from the target database based on the business field. This part of the content will be described in detail in the subsequent embodiments.
[0047] Step 104: Execute the automatic task based on the original production message to obtain a test response message.
[0048] In the embodiment of the present disclosure, after the production original message is obtained through the above steps, the automatic task can be executed based on the production original message to obtain the test response message to complete the account tracking test of the automatic task. In the embodiment of the present disclosure, the above test response message is used to indicate the test result of the automatic task in the new system.
[0049] Specifically, in the embodiment of the present disclosure, the method for executing an automatic task based on generating an original message to obtain a test response message may include the following steps:
[0050] Step 1041, obtaining a dependency table of the automatic task;
[0051] Step 1042: Based on the dependency table, obtain dependency data of the automatic task;
[0052] Step 1043: Execute the automatic task according to the dependent data and the original production message to obtain a test response message.
[0053] In the embodiment of the present disclosure, the dependency table of the automatic task can be obtained from the database according to the identifier of the automatic task. In the embodiment of the present disclosure, the databases used by the new system and the old system can be the same or different. And, in the embodiment of the present disclosure, when the new system and the old system use different databases, the automatic task in the new system can obtain the dependency table of the automatic task from the database to which the new system belongs.
[0054] Among them, in the embodiment of the present disclosure, the above dependency table may include the execution order of each transaction in the automatic task to reflect the dependency relationship of each transaction. And, in the embodiment of the present disclosure, the above dependency table may also include the local data identifier in the database corresponding to the local transaction, so that the data of the local transaction can be obtained according to the local data identifier.
[0055] Furthermore, in the disclosed embodiment, after obtaining the dependent data and producing the original message through the above steps, the automatic task can be executed according to the sequence of transactions in the dependency table corresponding to the automatic task, so as to subsequently backtrack according to the account tracking test results of the automatic task and accurately locate the problematic part.
[0056] Step 105: Obtain a production response message of the automatic task, and determine an account tracking test result of the automatic task based on the production response message and the test response message.
[0057] Among them, in the embodiment of the present disclosure, after the production response message of the automatic task is obtained through the above steps, the account tracking test result of the automatic task can be determined based on the production response message and the test response message.
[0058] Specifically, in the embodiment of the present disclosure, the method for obtaining the production response message of the automatic task and determining the account tracking test result of the automatic task based on the production response message and the test response message may include the following steps:
[0059] Step 1051: extract first entity information corresponding to the target entity in the production response message;
[0060] Step 1052: extract the second entity information corresponding to the target entity in the test response message;
[0061] Step 1053: compare the first entity information with the second entity information. If the first entity information and the second entity information are identical, determine that the account tracking test result of the automatic task is successful.
[0062] Step 1054: If the first entity information and the second entity information are inconsistent with each other, the account tracking test result of the automatic task is determined to be an account tracking test failure.
[0063] In the disclosed embodiment, the first entity information and the second entity information, i.e., the ENTITY part of the message, can be extracted from the production response message and the test response message respectively by using the XML parsing method. The first entity information and / or the second entity information can store the corresponding multiple entity data in an array in sequence, and the first entity information and the second entity information compare the multiple entity data in sequence according to the sequence of the multiple entity data. During the comparison process, if there is an inconsistency in the comparison of one entity data, the account tracking test result of the automatic task is determined to be an account tracking test failure, and the comparison of other subsequent entity data is terminated to obtain the account tracking test result of the automatic task; if one entity data comparison is successful, the next entity data comparison is performed until all entity data are consistent, and the account tracking test result of the automatic task is determined to be an account tracking test success.
[0064] Among them, in the embodiment of the present disclosure, the method for comparing the results of the account tracking test of the above-mentioned production response message and the test response message can obtain the result of the account tracking test of the automatic task by comparing the messages, and can quickly realize the result comparison of the account tracking test of the automatic task, thereby improving the account tracking test rate of the new system.
[0065] Furthermore, in the disclosed embodiment, after determining through the above steps that the result of the account tracking test of the automatic task is a failure of the account tracking test, the above method may further include: determining all inconsistent third entity information between the first entity information and the second entity information, locating the code module in the automatic task corresponding to the third entity information according to the dependency table of the automatic task, and outputting the code module.
[0066] Among them, in the embodiment of the present disclosure, after determining that the account tracking test result of the automatic task is an account tracking test failure, the first entity information and the second entity information are traversed to determine all inconsistent third entity information in the first entity information and the second entity information, and then according to the dependency table of the automatic task, the code module in the automatic task corresponding to each third entity information is located, and the code module is output, thereby improving the accuracy of the new system account tracking test, allowing the code module to be modified in time, thereby improving the new system's account tracking test rate.
[0067] In the account tracking test method proposed in the present disclosure, in response to the triggering of an automatic task in the new system, a production request message corresponding to the automatic task is determined; based on the production request message, at least one corresponding target outbound call transaction is determined; the business field corresponding to the target outbound call transaction is determined, and the corresponding production original message is determined based on the business field; the automatic task is executed based on the production original message to obtain a test response message, wherein the test response message is used to indicate the test result of the automatic task in the new system; the production response message of the automatic task is obtained, and based on the production response message and the test response message, the account tracking test result of the automatic task is determined. Therefore, in the account tracking test method proposed in the present disclosure, the corresponding production original message can be determined from the target database corresponding to the new system based on the business field corresponding to the target outbound call transaction, so that the outbound call transaction in the automatic task can be supported, which solves the problem that the outbound call transaction generated by the automatic task cannot match the production original message, and realizes the account tracking test of the automatic task.
[0068] Figure 2 FIG. 1 is a flow chart of an account tracking test method provided according to another embodiment of the present disclosure, as shown in FIG. Figure 2 As shown, it may include:
[0069] Step 201: In response to the triggering of an automatic task in the new system, the execution configuration information of other automatic tasks in the new system is obtained.
[0070] In the disclosed embodiment, the execution configuration information is used to indicate whether the automatic task is automatically executed.
[0071] In the embodiment of the present disclosure, in response to the triggering of an automatic task in the new system, the execution configuration information of other automatic tasks in the new system may be obtained to determine whether there are automatic tasks that need to be executed at the same time.
[0072] And, in the embodiment of the present disclosure, the execution configuration information can be a first value or a second value. In the embodiment of the present disclosure, if the execution configuration information is the first value, it indicates that the automatic task is "on"; if the execution configuration information is the second value, it indicates that the automatic task is "off".
[0073] In the embodiment of the present disclosure, the first value may be 1, and the second value may be 0.
[0074] Step 202: In response to the execution configuration information being a first value, the execution configuration information is changed to a second value to disable automatic execution of other automatic tasks.
[0075] In an embodiment of the present disclosure, if the execution configuration information is a first value, it indicates that other automatic tasks are in the "on" state, indicating that they need to be executed simultaneously with the triggered automatic task at this time, and there may be a situation where the target data is overwritten due to repeated execution of the automatic task. Based on this, in response to the execution configuration information being the first value, the execution configuration information can be changed to a second value to turn off the automatic execution of other automatic tasks, so that no other automatic tasks are executed at the same time, thereby avoiding the situation where the target data is overwritten due to repeated execution of the automatic task; if the execution configuration information is the second value, it indicates that other automatic tasks are in the "off" state, indicating that there are no other automatic tasks executed simultaneously with the triggered automatic task at this time, and no adjustment is required.
[0076] Step 203: Determine the production request message corresponding to the automatic task.
[0077] Step 204: Based on the production request message, determine at least one corresponding target outbound call transaction.
[0078] For detailed description of steps 203 to 204, reference may be made to the relevant description in the above embodiment, which will not be elaborated in detail in the embodiment of the present disclosure.
[0079] Step 205: Determine the service field corresponding to the target outbound call transaction according to the mapping relationship table between the target outbound call transaction and the service field.
[0080] In the disclosed embodiment, the target outbound call transaction may correspond to at least one service field, and different target outbound call transactions may correspond to different service fields. Based on this, the service field corresponding to the target outbound call transaction may be determined according to a mapping relationship table between the outbound call transaction tracking number and the service field of the target outbound call transaction.
[0081] Furthermore, in the disclosed embodiment, a mapping relationship table between target outbound call transactions and business fields may be stored in advance.
[0082] Step 206: Determine the corresponding production original message from the target database based on the business field.
[0083] Among them, in the embodiment of the present disclosure, after determining the business field corresponding to the target outbound transaction through the above steps, the corresponding original production message can be determined from the target database corresponding to the new system based on the business field, so as to support outbound transactions in automatic tasks, solve the problem that the outbound transactions generated by the automatic tasks cannot match the original production messages, and realize the account tracking test of the automatic tasks.
[0084] Step 207: Execute the automatic task based on the original production message to obtain a test response message.
[0085] Step 208: Obtain a production response message of the automatic task, and determine an account tracking test result of the automatic task based on the production response message and the test response message.
[0086] For detailed description of steps 207 to 208, reference may be made to the relevant description in the above embodiment, which will not be elaborated in detail in the embodiment of the present disclosure.
[0087] In the account tracking test method proposed in the present disclosure, in response to the triggering of an automatic task in the new system, a production request message corresponding to the automatic task is determined; based on the production request message, at least one corresponding target outbound call transaction is determined; the business field corresponding to the target outbound call transaction is determined, and the corresponding production original message is determined based on the business field; the automatic task is executed based on the production original message to obtain a test response message, wherein the test response message is used to indicate the test result of the automatic task in the new system; the production response message of the automatic task is obtained, and based on the production response message and the test response message, the account tracking test result of the automatic task is determined. Therefore, in the account tracking test method proposed in the present disclosure, the corresponding production original message can be determined from the target database corresponding to the new system based on the business field corresponding to the target outbound call transaction, so that the outbound call transaction in the automatic task can be supported, which solves the problem that the outbound call transaction generated by the automatic task cannot match the production original message, and realizes the account tracking test of the automatic task.
[0088] Figure 3 FIG. 1 is a flow chart of an account tracking test method provided according to another embodiment of the present disclosure, as shown in FIG. Figure 3 As shown, it may include:
[0089] Step 301: In response to the triggering of an automatic task in the new system, a production request message corresponding to the automatic task is determined.
[0090] Step 302: Based on the production request message, determine at least one corresponding target outbound call transaction.
[0091] Step 303: Determine the business field corresponding to the target outbound call transaction, and determine the corresponding production original message based on the business field.
[0092] Step 304: Execute the automatic task based on the original production message to obtain a test response message.
[0093] Step 305: Obtain a production response message of the automatic task, and determine an account tracking test result of the automatic task based on the production response message and the test response message.
[0094] For a detailed description of steps 301 to 305 , reference may be made to the related description in the above embodiment, which will not be elaborated in detail in the embodiment of the present disclosure.
[0095] Step 306: Determine the account tracking test results of all automatic tasks in the new system.
[0096] Step 307: Determine the account tracking test results of the new system according to the account tracking test results of all automatic tasks.
[0097] Among them, in the embodiment of the present disclosure, the above steps can be used to determine the account tracking test results of all automatic tasks in the new system, and after determining the account tracking test results of all automatic tasks in the new system, the account tracking test results of the new system can be determined based on the account tracking test results of all automatic tasks.
[0098] In the embodiment of the present disclosure, if the account tracking test results of all automatic tasks are successful, the account tracking test result of the system is determined to be successful; if there is an automatic task whose account tracking test result is a failure, the account tracking test result of the system is determined to be a failure, thereby improving the account tracking test rate of the automatic tasks and further improving the account tracking test rate of the new system.
[0099] In the account tracking test method proposed in the present disclosure, in response to the triggering of an automatic task in the new system, a production request message corresponding to the automatic task is determined; based on the production request message, at least one corresponding target outbound call transaction is determined; the business field corresponding to the target outbound call transaction is determined, and the corresponding production original message is determined based on the business field; the automatic task is executed based on the production original message to obtain a test response message, wherein the test response message is used to indicate the test result of the automatic task in the new system; the production response message of the automatic task is obtained, and based on the production response message and the test response message, the account tracking test result of the automatic task is determined. Therefore, in the account tracking test method proposed in the present disclosure, the corresponding production original message can be determined from the target database corresponding to the new system based on the business field corresponding to the target outbound call transaction, so that the outbound call transaction in the automatic task can be supported, which solves the problem that the outbound call transaction generated by the automatic task cannot match the production original message, and realizes the account tracking test of the automatic task.
[0100] Figure 4 The figure is a block diagram of an account tracking testing device according to an exemplary embodiment.
[0101] like Figure 4 As shown, the account tracking test device 400 includes: a first determination module 401, a second determination module 402, a third determination module 403, an execution module 404, and a comparison module 405.
[0102] A first determination module 401 is used to determine a production request message corresponding to the automatic task in response to the automatic task triggering in the new system;
[0103] A second determination module 402 is used to determine at least one corresponding target outbound call transaction based on the production request message;
[0104] The third determination module 403 is used to determine the business field corresponding to the target outbound call transaction, and determine the corresponding production original message based on the business field;
[0105] An execution module 404 is used to execute the automatic task based on the production original message to obtain a test response message, wherein the test response message is used to indicate the test result of the automatic task in the new system;
[0106] The comparison module 405 is used to obtain the production response message of the automatic task, and determine the account tracking test result of the automatic task based on the production response message and the test response message.
[0107] In the account tracking test device proposed in the present disclosure, in response to the triggering of an automatic task in the new system, a production request message corresponding to the automatic task is determined; based on the production request message, at least one corresponding target outbound call transaction is determined; the business field corresponding to the target outbound call transaction is determined, and the corresponding production original message is determined based on the business field; the automatic task is executed based on the production original message to obtain a test response message, wherein the test response message is used to indicate the test result of the automatic task in the new system; the production response message of the automatic task is obtained, and the account tracking test result of the automatic task is determined based on the production response message and the test response message. Therefore, in the account tracking test method proposed in the present disclosure, the corresponding production original message can be determined from the target database corresponding to the new system based on the business field corresponding to the target outbound call transaction, so that the outbound call transaction in the automatic task can be supported, which solves the problem that the outbound call transaction generated by the automatic task cannot match the production original message, and realizes the account tracking test of the automatic task.
[0108] Among them, in the embodiments of the present disclosure, the above device is also used for:
[0109] Obtaining execution configuration information of other automatic tasks in the new system, wherein the execution configuration information is used to indicate whether the automatic task is automatically executed;
[0110] In response to the execution configuration information being a first value, the execution configuration information is changed to a second value to disable automatic execution of other automatic tasks.
[0111] Optionally, in an embodiment of the present disclosure, the third determining module 403 is specifically configured to:
[0112] Determine the business field corresponding to the target outbound call transaction according to the mapping relationship table between the target outbound call transaction and the business field;
[0113] The corresponding production original message is determined from the target database based on the business field.
[0114] Optionally, in an embodiment of the present disclosure, the execution module 404 is specifically used to:
[0115] Get the dependency table of the automatic task;
[0116] Based on the dependency table, obtain the dependency data of the automatic task;
[0117] Execute automatic tasks based on dependent data and production original messages to obtain test response messages.
[0118] Optionally, in an embodiment of the present disclosure, the comparison module 405 is specifically used to:
[0119] Extracting first entity information corresponding to the target entity in the production response message;
[0120] Extracting second entity information corresponding to the target entity in the test response message;
[0121] The first entity information and the second entity information are compared, and if the first entity information and the second entity information are the same, the account tracking test result of the automatic task is determined to be a success;
[0122] If the first entity information and the second entity information are inconsistent in entity information, it is determined that the account tracking test result of the automatic task is an account tracking test failure.
[0123] Optionally, in an embodiment of the present disclosure, the comparison module 405 is further used to:
[0124] Determine all third entity information that is inconsistent between the first entity information and the second entity information;
[0125] According to the dependency table of the automatic task, the code module in the automatic task corresponding to the third entity information is located, and the code module is output.
[0126] Optionally, in an embodiment of the present disclosure, the above device is further used for:
[0127] Determine the test results of all automated tasks in the new system;
[0128] Determine the new system's account tracking test results based on the account tracking test results of all automatic tasks.
[0129] Figure 5 It is a block diagram of an electronic device according to an exemplary embodiment.
[0130] like Figure 5 As shown, the electronic device 500 includes:
[0131] Processing component 502 , memory 504 , power component 506 , multimedia component 508 , audio component 510 , input / output (I / O) interface 512 , sensor component 514 , and communication component 516 .
[0132] The processing component 502 generally controls the overall operation of the electronic device 500, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 502 may include one or more processors 520 to execute instructions to complete all or part of the steps of the above-mentioned method. In addition, the processing component 502 may include one or more modules to facilitate the interaction between the processing component 502 and other components. For example, the processing component 502 may include a multimedia module to facilitate the interaction between the multimedia component 508 and the processing component 502.
[0133] The memory 504 is configured to store various types of data to support operations on the electronic device 500. Examples of such data include instructions for any application or method operating on the electronic device 500, contact data, phone book data, messages, pictures, videos, etc. The memory 504 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.
[0134] The power supply component 506 provides power to the various components of the electronic device 500. The power supply component 506 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the electronic device 500.
[0135] The multimedia component 508 includes a touch display screen that provides an output interface between the electronic device 500 and the user. In some embodiments, the touch display screen may include a liquid crystal display (LCD) and a touch panel (TP). The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor can not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 508 includes a front camera and / or a rear camera. When the electronic device 500 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera can receive external multimedia data. Each front camera and rear camera can be a fixed optical lens system or have a focal length and optical zoom capability.
[0136] The audio component 510 is configured to output and / or input audio signals. For example, the audio component 510 includes a microphone (MIC), and when the electronic device 500 is in an operation mode, such as a call mode, a recording mode, and a voice recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the memory 504 or sent via the communication component 516.
[0137] In some embodiments, the audio component 510 also includes a speaker for outputting audio signals.
[0138] I / O interface 512 provides an interface between processing component 502 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: a home button, a volume button, a start button, and a lock button.
[0139] The sensor assembly 514 includes one or more sensors for providing various aspects of status assessment for the electronic device 500. For example, the sensor assembly 514 can detect the open / closed state of the electronic device 500, the relative positioning of components, such as the display and keypad of the electronic device 500, and the sensor assembly 514 can also detect the position change of the electronic device 500 or a component of the electronic device 500, the presence or absence of user contact with the electronic device 500, the orientation or acceleration / deceleration of the electronic device 500, and the temperature change of the electronic device 500. The sensor assembly 514 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 514 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 514 may also include an accelerometer, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
[0140] The communication component 516 is configured to facilitate wired or wireless communication between the electronic device 500 and other devices. The electronic device 500 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 516 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 516 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.
[0141] In an exemplary embodiment, the electronic device 500 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic components to perform the above-mentioned data preheating cache method.
[0142] In an exemplary embodiment, a computer-readable storage medium including instructions is also provided, such as a memory 504 including instructions, and the instructions can be executed by a processor 520 of the electronic device 500 to perform the above method. Alternatively, the computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.
[0143] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the art that are not disclosed in the present application. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the following claims.
[0144] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.
[0145] It should be noted that the implementation process and technical principle of the electronic device of this embodiment refer to the above explanation of the account tracking test method of the embodiment of the present disclosure, which will not be repeated here.
[0146] In order to implement the above embodiments, the present disclosure also proposes a computer-readable storage medium.
[0147] When the instructions in the computer-readable storage medium are executed by the processor of the electronic device, the electronic device can execute the account tracking test method of the first aspect, the second aspect, or the third aspect of the above-mentioned embodiment. Optionally, the computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.
[0148] In order to implement the above embodiments, the present disclosure also provides a computer program product, including a computer program, characterized in that when the computer program is executed by a processor, the account tracking testing method of the first aspect, the second aspect, or the third aspect of the above embodiments is implemented.
[0149] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. The present disclosure is intended to cover any variations, uses or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The description and examples are to be considered exemplary only, and the true scope and spirit of the present disclosure are indicated by the following claims.
[0150] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
[0151] In an exemplary embodiment, a computer program product is also provided, including a computer program, characterized in that when the computer program is executed by a processor, the account tracking test method of the first aspect, the second aspect, or the third aspect of the above-mentioned embodiment is implemented.
[0152] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present disclosure are indicated by the following claims.
[0153] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims
1. A method for tracking account testing, characterized in that: The method comprises: In response to the triggering of an automatic task in the new system, determining a production request message corresponding to the automatic task; Based on the production request message, determining at least one corresponding target outbound call transaction; Determine the service field corresponding to the target outbound call transaction, and determine the corresponding production original message based on the service field; Executing the automatic task based on the production original message to obtain a test response message, wherein the test response message is used to indicate a test result of the automatic task in the new system; A production response message of the automatic task is obtained, and based on the production response message and the test response message, an account tracking test result of the automatic task is determined.
2. The method according to claim 1, characterized in that Before determining the production request message corresponding to the automatic task, the method includes: Acquire execution configuration information of other automatic tasks in the new system, wherein the execution configuration information is used to indicate whether the automatic task is automatically executed; In response to the execution configuration information being a first value, the execution configuration information is changed to a second value to disable automatic execution of the other automatic tasks.
3. The method according to claim 1, characterized in that The determining of the service field corresponding to the target outbound call transaction, and determining the corresponding production original message based on the service field, includes: Determine the service field corresponding to the target outbound call transaction according to the mapping relationship table between the target outbound call transaction and the service field; A corresponding production original message is determined from a target database based on the business field.
4. The method according to claim 1, characterized in that The step of executing the automatic task based on the production original message to obtain a test response message includes: Obtaining a dependency table of the automatic task; Based on the dependency table, obtaining dependency data of the automatic task; The automatic task is executed according to the dependent data and the production original message to obtain a test response message.
5. The method according to claim 1, characterized in that The obtaining of the production response message of the automatic task, and determining the account tracking test result of the automatic task based on the production response message and the test response message, includes: Extracting first entity information corresponding to the target entity in the production response message; Extracting second entity information corresponding to the target entity in the test response message; The first entity information and the second entity information are compared, and if the first entity information and the second entity information are the same, determining that the account tracking test result of the automatic task is a success of the account tracking test; If the first entity information and the second entity information are inconsistent in entity information, it is determined that the account tracking test result of the automatic task is an account tracking test failure.
6. The method as claimed in claim 5, characterized in that After determining that the account tracking test result of the automatic task is an account tracking test failure, the method further includes: Determine all third entity information that is inconsistent between the first entity information and the second entity information; According to the dependency table of the automatic task, the code module in the automatic task corresponding to the third entity information is located, and the code module is output.
7. The method according to claim 1, characterized in that The method further comprises: Determine the account tracking test results of all automatic tasks in the new system; The account tracking test results of the new system are determined based on the account tracking test results of all automatic tasks.
8. An account tracking test device, characterized in that: The device comprises: A first determination module, configured to determine, in response to an automatic task trigger in the new system, a production request message corresponding to the automatic task; A second determination module, configured to determine at least one corresponding target outbound call transaction based on the production request message; A third determination module is used to determine the service field corresponding to the target outbound call transaction, and determine the corresponding production original message based on the service field; An execution module, used for executing the automatic task based on the production original message to obtain a test response message, wherein the test response message is used to indicate a test result of the automatic task in the new system; The comparison module is used to obtain the production response message of the automatic task, and determine the account tracking test result of the automatic task based on the production response message and the test response message.
9. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; The processor is configured to execute the instructions to implement the method according to any one of claims 1 to 7.
10. A computer-readable storage medium, when instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the method according to any one of claims 1 to 7.
11. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.