Test data processing method and device, computer equipment and readable storage medium

By updating the identification and splicing test data of resource transfer requests in software testing, the problem of inaccurate test data processing in the prior art is solved, and more accurate and automated test data processing is achieved.

CN119440987APending Publication Date: 2025-02-14CHINA CONSTRUCTION BANK +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411432543.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-10-14
Publication Date
2025-02-14

AI Technical Summary

Technical Problem

The prior art test data processing is not accurate enough in software testing, making it difficult to effectively distinguish and process multiple resource transfer requests carrying the same resource transfer identifier.

Method used

By obtaining multiple resource transfer requests in the test scenario, the field column of the target resource transfer request is determined, and the resource transfer identification is updated based on the parameter values ​​in the field column within the preset offset range. Then, based on the resource transfer identifier of all resource transfer requests, the corresponding test branch type is spliced ​​and pushed to the application test end.

Benefits of technology

It realizes accurate distinction and processing of multiple resource transfer requests, improves the accuracy and automation of test data processing, and ensures accurate push of test data.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119440987A_ABST
    Figure CN119440987A_ABST
Patent Text Reader

Abstract

The invention relates to the field of data processing, and particularly discloses a test data processing method and device, computer equipment and a readable storage medium. The method comprises the steps of obtaining a plurality of resource transfer requests in a test scene, the resource transfer requests carrying resource transfer identifiers and resource transfer data; for a target resource transfer request carrying the same resource transfer identifier in the plurality of resource transfer requests, determining a field column corresponding to the target resource transfer request, and updating the resource transfer identifier of the target resource transfer request based on a parameter value within a preset offset range in the field column; and based on the test branch types corresponding to the resource transfer identifiers of all the resource transfer requests, splicing the resource transfer data of all the resource transfer requests, and pushing the spliced resource transfer data to the application test end. By adopting the method, the test data can be accurately processed.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a test data processing method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Art

[0002] With the development of science and technology, software testing has gradually become a hot topic. It is used to evaluate application performance and scalability, including response time and stress tolerance. By conducting software testing, the availability of applications can be improved.

[0003] In software testing, test data processing is an important part. At present, taking non-functional testing as an example, the test data processing process mainly includes obtaining the resource transfer identifier carried in the resource transfer request to trigger the resource transfer operation corresponding to the resource transfer identifier. For example, the resource transfer identifier can be a public identifier or a private identifier. In the case where the resource transfer identifier is a public identifier, the public resource transfer processing is triggered. In more detail, the resource transfer data of the resource transfer request is sent to the application test segment so that the application test end can perform public resource transfer processing on the resource transfer data. However, this test data processing method has the problem of inaccuracy. Summary of the invention

[0004] Based on this, it is necessary to provide an accurate test data processing method, device, computer equipment, computer readable storage medium and computer program product to address the above technical problems.

[0005] In a first aspect, the present application provides a test data processing method, comprising:

[0006] Acquire multiple resource transfer requests in the test scenario, wherein the resource transfer request carries a resource transfer identifier and resource transfer data;

[0007] For a target resource transfer request carrying the same resource transfer identifier among multiple resource transfer requests, determine a field column corresponding to the target resource transfer request, and update the resource transfer identifier of the target resource transfer request based on a parameter value in the field column within a preset offset range;

[0008] Based on the test branch types corresponding to the resource transfer identifiers of all resource transfer requests, the resource transfer data of all resource transfer requests are spliced, and the spliced ​​resource transfer data is pushed to the application test end.

[0009] In one embodiment, the method further comprises:

[0010] Determine the same resource transfer identifier carried by multiple resource transfer requests, and detect the target test branch types corresponding to all the same resource transfer identifiers;

[0011] Determine the type ratio of all target test branch types based on the actual resource amounts corresponding to all target test branch types;

[0012] Through type ratio, simulate the test scenario where all target test branch types exist.

[0013] In one embodiment, updating the resource transfer identifier of the target resource transfer request based on the parameter value in the field column within the preset offset range includes:

[0014] When there are multiple fields corresponding to the target resource transfer request, detecting a parameter value in each field within a preset offset range;

[0015] All detected parameter values ​​are concatenated, and the concatenated parameter values ​​are updated as the resource transfer identifier of the target resource transfer request.

[0016] In one embodiment, the method further comprises:

[0017] Based on the test branch type, generate a response message corresponding to the resource transfer request;

[0018] A response message is returned to the resource transfer requester corresponding to the resource transfer request, where the response message is used to return the object type of the resource transfer requester.

[0019] In one embodiment, returning a response message to the resource transfer requester corresponding to the target resource transfer request includes:

[0020] Determine whether there is a preset delimiter character in the response message;

[0021] In the case where there is a preset separation character in the response message, the response message is divided based on the preset separation character to obtain a first sub-response message and a second sub-response message, and the first sub-response message and the second sub-response message are returned in sequence, wherein the first sub-response message is used to verify whether the resource transfer request is received, and the second sub-response message is used to return the object type of the resource transfer requester;

[0022] When there is no preset separation character in the response message, the response message is returned to the resource transfer requester corresponding to the resource transfer request.

[0023] In one embodiment, the resource transfer data includes a resource transfer data header, actual resource transfer data, and a resource transfer data tail, and based on the test branch types of all resource transfer requests, the resource transfer data of all resource transfer requests are spliced, and further includes:

[0024] Acquire first repeated data corresponding to resource transfer data headers of all resource transfer requests and second repeated data corresponding to resource transfer data tails of all resource transfer requests;

[0025] Determine the first repeated data as a file header, determine the second repeated data as a file tail, and based on the test branch type corresponding to the resource transfer identifiers of all resource transfer requests, splice the actual resource transfer data of all resource transfer requests, and determine the spliced ​​actual resource transfer data as a file body;

[0026] Concatenate the file header, file body, and file footer.

[0027] In one embodiment, based on the test branch types of all resource transfer requests, actual resource transfer data of all resource transfer requests are spliced, including:

[0028] According to the number of rows of immutable data and the number of rows of variable data in the actual resource transfer data of each resource transfer request, splicing the immutable data and the variable data in the actual resource transfer data of each resource transfer request to obtain spliced ​​data of each resource transfer request;

[0029] Based on the test branch types corresponding to the resource transfer identifiers of all resource transfer requests, the splicing data corresponding to different test branch types are cross-spliced.

[0030] In a second aspect, the present application also provides a test data processing device, comprising:

[0031] A request acquisition module, used to acquire multiple resource transfer requests in a test scenario, wherein the resource transfer request carries a resource transfer identifier and resource transfer data;

[0032] A request analysis module, for determining, for a target resource transfer request carrying the same resource transfer identifier among multiple resource transfer requests, a field column corresponding to the target resource transfer request, and updating the resource transfer identifier of the target resource transfer request based on a parameter value in the field column within a preset offset range;

[0033] The test data processing module is used to splice the resource transfer data of all resource transfer requests based on the test branch types corresponding to the resource transfer identifiers of all resource transfer requests, and push the spliced ​​resource transfer data to the application test end.

[0034] In one of the embodiments, the test data processing device also includes a test scenario simulation module, which is used to: determine the same resource transfer identifier carried by multiple resource transfer requests, and detect the target test branch types corresponding to all the same resource transfer identifiers, determine the type ratio of all target test branch types based on the actual resource quantities corresponding to all target test branch types, and simulate the test scenario in which all target test branch types exist through the type ratio.

[0035] In one of the embodiments, the request analysis module is also used to detect the parameter value within a preset offset range in each field field when there are multiple field fields corresponding to the target resource transfer request, splice all the detected parameter values, and update the spliced ​​parameter value to the resource transfer identifier of the target resource transfer request.

[0036] In one of the embodiments, the test data processing device also includes a message return module, which is used to generate a response message corresponding to the resource transfer request based on the test branch type, and return the response message to the resource transfer requester corresponding to the resource transfer request, and the response message is used to return the object type of the resource transfer requester.

[0037] In one of the embodiments, the message return module is also used to determine whether there is a preset separation character in the response message; if there is a preset separation character in the response message, the response message is segmented based on the preset separation character to obtain a first sub-response message and a second sub-response message, and the first sub-response message and the second sub-response message are returned in sequence, wherein the first sub-response message is used to verify whether the resource transfer request is received, and the second sub-response message is used to return the object type of the resource transfer requester, and if there is no preset separation character in the response message, the response message is returned to the resource transfer requester corresponding to the resource transfer request.

[0038] In one of the embodiments, the resource transfer data includes a resource transfer data header, actual resource transfer data, and a resource transfer data tail. The test data processing module is also used to obtain the first repeated data corresponding to the resource transfer data header of all resource transfer requests and the second repeated data corresponding to the resource transfer data tail of all resource transfer requests, determine the first repeated data as the file header, determine the second repeated data as the file tail, and based on the test branch type corresponding to the resource transfer identifier of all resource transfer requests, splice the actual resource transfer data of all resource transfer requests, determine the spliced ​​actual resource transfer data as the file body, and splice the file header, file body, and file tail.

[0039] In one of the embodiments, the test data processing module is also used to splice the immutable data and the variable data in the actual resource transfer data of each resource transfer request according to the number of rows of immutable data and the number of rows of variable data in the actual resource transfer data of each resource transfer request to obtain the spliced ​​data of each resource transfer request, and based on the test branch types corresponding to the resource transfer identifiers of all resource transfer requests, cross-splice the spliced ​​data corresponding to different test branch types.

[0040] In a third aspect, the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0041] Acquire multiple resource transfer requests in a test scenario, wherein the resource transfer request carries a resource transfer identifier and resource transfer data;

[0042] For a target resource transfer request carrying the same resource transfer identifier among multiple resource transfer requests, determine a field column corresponding to the target resource transfer request, and update the resource transfer identifier of the target resource transfer request based on a parameter value in the field column within a preset offset range;

[0043] Based on the test branch types corresponding to the resource transfer identifiers of all resource transfer requests, the resource transfer data of all resource transfer requests are spliced, and the spliced ​​resource transfer data is pushed to the application test end.

[0044] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the following steps are implemented:

[0045] Acquire multiple resource transfer requests in a test scenario, wherein the resource transfer request carries a resource transfer identifier and resource transfer data;

[0046] For a target resource transfer request carrying the same resource transfer identifier among multiple resource transfer requests, determine a field column corresponding to the target resource transfer request, and update the resource transfer identifier of the target resource transfer request based on a parameter value in the field column within a preset offset range;

[0047] Based on the test branch types corresponding to the resource transfer identifiers of all resource transfer requests, the resource transfer data of all resource transfer requests are spliced, and the spliced ​​resource transfer data is pushed to the application test end.

[0048] In a fifth aspect, the present application further provides a computer program product, including a computer program, which implements the following steps when executed by a processor:

[0049] Acquire multiple resource transfer requests in the test scenario, wherein the resource transfer request carries a resource transfer identifier and resource transfer data;

[0050] For a target resource transfer request carrying the same resource transfer identifier among multiple resource transfer requests, determine a field column corresponding to the target resource transfer request, and update the resource transfer identifier of the target resource transfer request based on a parameter value in the field column within a preset offset range;

[0051] Based on the test branch types corresponding to the resource transfer identifiers of all resource transfer requests, the resource transfer data of all resource transfer requests are spliced, and the spliced ​​resource transfer data is pushed to the application test end.

[0052] The above-mentioned test data processing method, device, computer equipment, computer-readable storage medium and computer program product are different from executing data processing operations corresponding to the same resource transfer identifier when multiple resource transfer requests share a resource transfer identifier. In the present application, a more accurate test data processing method is proposed for target resource transfer requests in a test scenario where multiple resource transfer requests carry the same resource transfer identifier. Specifically, for each target resource transfer request, the field column corresponding to the target resource transfer request is determined, and the target resource transfer identifier is updated based on the parameter value in the field column within a preset offset range. That is to say, the present application can distinguish multiple target resource transfer requests that share a resource transfer identifier, and then accurately determine the test branch type corresponding to the resource transfer identifier of the target resource transfer request, and can automatically splice the resource transfer data carried by multiple resource transfer requests through the test branch type corresponding to the updated resource transfer identifier, without manually splicing them one by one, thereby improving the accuracy of splicing, and then pushing the spliced ​​resource transfer data to the application test end. The whole process is more accurate compared with the prior art. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the drawings required for use in the embodiments of the present application or the related technical descriptions will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying any creative work.

[0054] FIG1 is an application environment diagram of a test data processing method in one embodiment;

[0055] Figure 2 A schematic diagram of a flow chart of a test data processing method in one embodiment;

[0056] Figure 3A schematic diagram of a flow chart of a test data processing method in another embodiment;

[0057] Figure 4 A schematic diagram of a flow chart of a test data processing method in another embodiment;

[0058] Figure 5 is a structural block diagram of a test data processing device in one embodiment;

[0059] Figure 6 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0060] In order to make the purpose, technical solution and advantages of the present application clearer, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are used to explain the present application and are not used to limit the present application. It should be noted that in the embodiments of the present application, certain software, groups, models and other existing solutions in the industry may be mentioned, which should be considered as exemplary, and their purpose is to illustrate the feasibility of the implementation of the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0061] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations. The acquisition, storage, use, and processing of data in the technical solution of this application are in compliance with relevant provisions of national laws and regulations.

[0062] The test data processing method provided in the embodiment of the present application can be applied in the application environment shown in FIG1 . In which, the terminal 102 communicates with the server 104 through a network. The data storage system can store the data that the server 104 needs to process. The data storage system can be integrated on the server 104, or it can be placed on the cloud or other network servers.

[0063] The user interacts with the terminal 102 in the test scenario interface, uploads the resource transfer identifier and resource transfer data, and triggers the resource transfer button to upload a resource transfer request to the terminal 102, wherein the resource transfer request carries the resource transfer identifier and resource transfer data. The terminal 102 forwards the resource transfer request to the server 104.

[0064] Server 104 obtains multiple resource transfer requests in the test scenario, determines the field column corresponding to the target resource transfer request for the target resource transfer request carrying the same resource transfer identifier in the multiple resource transfer requests, and updates the resource transfer identifier of the target resource transfer request based on the parameter value in the field column within a preset offset range; splices the resource transfer data of all resource transfer requests based on the test branch type of the resource transfer identifier corresponding to all resource transfer requests, and pushes the spliced ​​resource transfer data to the application test end, so that the application test end receives the spliced ​​resource transfer data and performs subsequent processing on it.

[0065] The terminal 102 may be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, IoT devices, and portable wearable devices. The IoT devices may be smart speakers, smart TVs, smart air conditioners, smart car devices, projection devices, etc. Portable wearable devices may be smart watches, smart bracelets, head-mounted devices, etc. Head-mounted devices may be virtual reality (VR) devices, augmented reality (AR) devices, smart glasses, etc. The server 104 may be an independent physical server, a server cluster or distributed system consisting of multiple physical servers, or a cloud server that provides cloud computing services.

[0066] In an exemplary embodiment, Figure 2 As shown, a test data processing method is provided, and the method is applied to the server 104 in FIG. 1 as an example for description. In which:

[0067] S200, obtaining multiple resource transfer requests in a test scenario.

[0068] Among them, the test scenario in this application is generally a non-functional test scenario, and the resource transfer request carries a resource transfer identifier and resource transfer data.

[0069] Specifically, a plurality of resource transfer requests in a test scenario are obtained, where the resource transfer request is a resource transfer request uploaded by at least one terminal, and each resource transfer request carries a resource transfer identifier and resource transfer data.

[0070] Currently, the method for identifying resource transfer identifiers is relatively simple. For example, when using a baffle simulator to identify resource transfer identifiers, although multiple resource transfer requests have subdivided target test branches, such as some of the multiple resource transfer requests may be public test branch types, and some may be private test branch types, the called interfaces are all E0181S421, and the baffle simulator identifies that the resource transfer identifiers of the multiple resource transfer requests are all E0181S421. Therefore, the resource transfer identifiers in the multiple resource transfer requests may be the same or different. For resource transfer requests of multiple different test branch types, when the multiple resource transfer requests corresponding to the same resource transfer identifier are subsequently processed, the processing operations that match the same resource transfer identifier E0181S421 are also taken, and different processing operations are not taken for different test branch types. In other words, certain optimizations need to be made to the above process.

[0071] S400, for a target resource transfer request carrying the same resource transfer identifier among multiple resource transfer requests, determine the field column corresponding to the target resource transfer request, and update the resource transfer identifier of the target resource transfer request based on a parameter value in the field column within a preset offset range.

[0072] Specifically, the optimization method adopted by this application is to analyze the identification types and implementation methods supported in the baffle simulator jar (Java Archive, java archive) package, modify the baffle editing mode to directly modify on the server, so that the identification method of the resource transfer identifier is allowed to be edited, and the identification method of the resource transfer identifier is modified to the identification method of this application. In this application, the essence of the optimization method is to further subdivide the resource transfer identifier to update the resource transfer identifier carried in the request, and determine the real test branch based on the updated resource transfer identifier.

[0073] In detail, a target resource transfer request carrying the same resource transfer identifier is obtained from multiple resource transfer requests, and a method for updating the resource transfer identifier for the target resource transfer request carrying the same resource transfer identifier from multiple resource transfer requests includes: determining the field corresponding to the target resource transfer request, that is, determining the field related to the resource transfer process corresponding to the target resource transfer request, and updating the resource transfer identifier of the target resource transfer request based on the parameter value in the field within the preset offset range. For example, if the data in the field corresponding to the target resource transfer request is determined to be 1234567, and the preset offset range is the 3rd-4th bit, then the parameter value in the field at the 3rd-4th bit of the preset offset range is 34, and therefore, the parameter value 34 is determined as the resource transfer identifier of the updated target resource transfer request. Furthermore, there is more than one field, and therefore, the resource transfer identifier identification method can be modified to Join, that is, the resource transfer identifier identification method is changed from single identification to combined identification, and the resource transfer identifier of the updated target resource transfer request is obtained by combining the parameter values ​​identified by multiple field fields.

[0074] S600: based on the test branch types corresponding to the resource transfer identifiers of all resource transfer requests, concatenate the resource transfer data of all resource transfer requests, and push the concatenated resource transfer data to the application test end.

[0075] Specifically, based on the resource transfer identifier of the updated target resource transfer request, the test branch type of the target resource transfer request is determined. For example, the updated resource transfer identifiers identified are E10181S4213 and E0181S4216, and the corresponding test branch types are a public test branch type and a private test branch type, respectively. Then, based on the resource transfer identifiers of resource transfer requests other than the target resource transfer request, the test branch types of resource transfer requests other than the target resource transfer request are determined, that is, the test branch types of all resource transfer requests are obtained. Through the test branch types of all resource transfer requests, the resource transfer data of all resource transfer requests are spliced ​​according to a preset splicing method, wherein the preset splicing method is related to the test branch type. After splicing the resource transfer data of all resource transfer requests, the spliced ​​resource transfer data is pushed to the application test end.

[0076] In the above-mentioned test data processing method, different from executing the data processing operation corresponding to the same resource transfer identifier when multiple resource transfer requests share a resource transfer identifier, in the present application, a more accurate test data processing method is proposed for target resource transfer requests in test scenarios where multiple resource transfer requests carry the same resource transfer identifier. Specifically, for each target resource transfer request, the field column corresponding to the target resource transfer request is determined, and the target resource transfer identifier is updated based on the parameter value in the field column within a preset offset range. That is to say, the present application can distinguish multiple target resource transfer requests that share a resource transfer identifier, and then accurately determine the test branch type corresponding to the resource transfer identifier of the target resource transfer request, and can automatically splice the resource transfer data carried by multiple resource transfer requests through the test branch type corresponding to the updated resource transfer identifier, without the need for manual splicing one by one, thereby improving the accuracy of splicing, and then pushing the spliced ​​resource transfer data to the application test end. The entire process is more accurate compared to the prior art.

[0077] In an exemplary embodiment, the method further comprises:

[0078] Determine the same resource transfer identifier carried by multiple resource transfer requests, and detect the target test branch types corresponding to all the same resource transfer identifiers. According to the actual resource quantities corresponding to all target test branch types, determine the type ratio of all target test branch types. Through the type ratio, simulate the test scenario where all target test branch types exist.

[0079] Specifically, in the related art, the simulation test scenario is generally to obtain the resource transfer amount of multiple resource transfer identifiers through the three-level view in the application monitoring platform, and then simulate the proportion of the resource transfer process corresponding to each resource transfer identifier in the test scenario based on the resource transfer amount of multiple resource transfer identifiers. For example, the three-level view can be the overview view->deployment unit view->resource transfer identifier view, that is, it is necessary to select the deployment unit view included in the overview view, and then select the resource transfer identifier view included in the deployment unit view to obtain the resource transfer amount of multiple resource transfer identifiers. However, this method will result in a single test scenario and a large deviation from actual production, and the system pressure and test results will deviate from actual production.

[0080] Therefore, this application uses actual production monitoring data to refine the proportion of main test branch scenarios in the resource transfer process, and applies it to the test scenarios to make the test scenarios fit the actual production.

[0081] The specific optimization method includes: obtaining the resource transfer amount of the main test branches corresponding to each resource transfer identifier through the four-level view in the application monitoring platform, and subdividing the proportion of the test branches in the test scenario. For example, the four-level view includes but is not limited to the overview view -> deployment unit view -> resource transfer identifier view -> resource transfer amount, and the resource transfer amount includes the resource transfer amount of multiple test branches corresponding to the same resource transfer identifier.

[0082] That is to say, on the basis of obtaining multiple resource transfer requests, the same resource transfer identifiers carried by the multiple resource transfer requests are determined, and the target test branch types corresponding to all the same resource transfer identifiers are detected. If the target test branch types corresponding to all the same resource transfer identifiers are detected, the type proportions of all the target test branch types can be determined based on the actual amount of resources corresponding to all the target test branch types in the four-level view, and the test scenario with all the target test branch types can be simulated through the type proportions.

[0083] Furthermore, based on the actual resource quantities corresponding to all target test branch types in the four-level view, the type proportions of all target test branch types are determined, including: based on the ratio of the actual resource quantities corresponding to all target test branch types in the four-level view, the type proportions of all target test branch types are determined.

[0084] For example, let a resource transfer identifier be A0332R102, and the target test branch types include private type and public type. The private resource transfer amount of the private type is 5600, and the public resource transfer amount is 5400. According to the private resource transfer amount of the private type and the public resource transfer amount, the proportion of the simulated private type target test branch is 56%, and the proportion of the simulated public type target test branch is 54%. In actual applications, there may be other target test branch types. Generally, some target test branch types with less resource transfer amount can be ignored in the simulation of actual test scenarios, and no simulation is carried out. In addition, the proportion of each target test branch type can be allocated by setting throughput or transaction delay in the Jmeter test script scenario.

[0085] In an exemplary embodiment, the present application can also add new business scenarios corresponding to different test branch types, such as adding three business scenarios such as general credit remittance, simple remittance through non-counter channels, and general credit remittance. Based on the resource transfer amounts corresponding to the three newly added business scenarios, the resource transfer ratio of the test branch type is updated to make the entire hybrid test scenario closer to production.

[0086] In the above embodiment, by determining the type ratio of all target test branch types according to the actual resource amounts corresponding to all target test branch types, it is possible to simulate the ratio of resource transfer branch types in actual production, so as to obtain a target test branch type ratio similar to the ratio of resource transfer branch types in actual production life, so that the test data processing process is closer to reality and has high accuracy. Furthermore, by simulating test scenarios of different target test branch types, instead of simulating the test scenario of a single target test branch type, the response time is closely related to the single target test branch type, so that the response time of the test result is also closer to reality.

[0087] In an exemplary embodiment, Figure 3 As shown, S400 includes:

[0088] S420: For a target resource transfer request carrying the same resource transfer identifier among multiple resource transfer requests, determine a field column corresponding to the target resource transfer request.

[0089] S440 , when there are multiple fields corresponding to the target resource transfer request, detect a parameter value in each field within a preset offset range.

[0090] S460: Concatenate all detected parameter values, and update the concatenated parameter value as the resource transfer identifier of the target resource transfer request.

[0091] Specifically, for a target resource transfer request carrying the same resource transfer identifier in multiple resource transfer requests, there is more than one field field related to the resource transfer process corresponding to the target resource transfer request. When there are multiple field fields corresponding to the target resource transfer request, a parameter value within a preset offset range in each field field is detected, wherein the preset offset range corresponding to each field field is not necessarily the same. All detected parameter values ​​are spliced, and the spliced ​​parameter value is updated as the resource transfer identifier of the target resource transfer request.

[0092] For example, when the field fields corresponding to the target resource transfer request are field A and field B, the field data corresponding to field A is 123456789, and the field data corresponding to field B is 987654321. Let the preset offset range corresponding to field A be the first bit, and let the preset offset range corresponding to field B be the second bit. Then, the first parameter value 1 is extracted from the field data corresponding to field A, and the second parameter value 8 is extracted from the field data corresponding to field B. Parameter value 1 and parameter value 8 are concatenated into parameter value 18, and 18 is determined as the updated resource transfer identifier of the target resource transfer request.

[0093] In this embodiment, the resource transfer identifier of the target resource transfer request can be accurately updated by splicing the parameter values ​​in the multiple fields detected within the preset offset range, so that the resource transfer identifiers corresponding to the multiple resource transfer requests are different.

[0094] In an exemplary embodiment, the method further comprises:

[0095] Based on the test branch type, a response message corresponding to the resource transfer request is generated, and the response message is returned to the resource transfer requester corresponding to the resource transfer request, where the response message is used to return the object type of the resource transfer requester.

[0096] Specifically, for a target resource transfer request that carries the same resource transfer identifier in multiple resource transfer requests, since one response message is configured corresponding to one resource transfer identifier, and the test branch types corresponding to the multiple resource transfer requests may be the same or different. Therefore, for resource transfer requests of multiple different test branch types, the response message that matches the same resource transfer identifier is returned, and different response messages will not be returned for different test branch types.

[0097] In the present application, after the resource transfer identifier of the target resource transfer request is updated by the method of position offset, each resource transfer identifier is further subdivided, and then based on the test branch type corresponding to the resource transfer identifier of all resource transfer requests, a response message corresponding to the target resource transfer request is generated. For example, when the test branch type corresponding to the resource transfer identifier is a public test branch type, the response message corresponding to the target resource transfer request is a response message matching the public test branch type, and when the test branch type corresponding to the resource transfer identifier is a private test branch type, the response message corresponding to the target resource transfer request is a response message matching the private test branch type. Further, a corresponding response message is returned to the resource transfer requester corresponding to all resource transfer requests, and the response message includes the object type of the returned resource transfer requester, for example, whether the returned resource transfer requester is a public object type or a private object type. If it is a public object type, then for the resource transfer requester's resource transfer request, a public resource transfer processing operation is triggered, and if it is a private object type, then for the resource transfer requester's resource transfer request, a private resource transfer processing operation is triggered.

[0098] Furthermore, in the case where the object identifier of the resource transfer requester is an account number, the return message can also be used to verify whether the account number of the returned resource transfer requester is consistent with the account name. That is to say, the return message includes the account number of the resource transfer requester carried by the resource transfer request and the account name in the database, so that the user can verify whether the account number of the resource transfer requester is consistent with the account name.

[0099] In this embodiment, a response message corresponding to the resource transfer request is generated based on the test branch type, and the response message is returned to the resource transfer requester corresponding to the resource transfer request, instead of generating a response message corresponding to the resource transfer request based on the resource transfer identifier in the request, so that the response message feedback is more accurate.

[0100] In an exemplary embodiment, returning a response message to the resource transfer requester corresponding to the target resource transfer request includes:

[0101] Determine whether there is a preset separation character in the response message. If there is a preset separation character in the response message, split the response message based on the preset separation character to obtain a first sub-response message and a second sub-response message, and return the first sub-response message and the second sub-response message in sequence, wherein the first sub-response message is used to verify whether the resource transfer request is received, and the second sub-response message is used to return the object type of the resource transfer requester. If there is no preset separation character in the response message, return the response message to the resource transfer requester corresponding to the resource transfer request.

[0102] Specifically, for special scenarios where two response messages need to be returned, for example, when receiving a resource transfer request, in addition to returning the actual response message, a communication receipt needs to be returned first to indicate that the message has been received. For this situation where a request is received but two response messages need to be returned, the relevant technology currently cannot simulate the actual situation. In this application, it can be optimized as follows: the two response messages that need to be returned are returned in one response message, and a preset separation character, such as AAAA, is added between the messages that need to be returned twice to determine whether they need to be returned in two times.

[0103] In this case, the server determines whether there is a preset separation character in the response message. If there is a preset separation character in the response message, the server divides the response message into a first sub-response message and a second sub-response message based on the preset separation character, and returns the first sub-response message to confirm that the resource transfer request has been received, and then returns the second sub-response message to return the object type of the resource transfer requester. If there is no preset separation character in the response message, the response message is returned to the resource transfer requester corresponding to the resource transfer request at one time.

[0104] In this embodiment, by determining whether there is a preset separation character in the response message, the response message can be returned in two times to adapt to various different situations. In special scenarios where two response messages need to be returned, the response message is divided into a first sub-response message and a second sub-response message by using the preset separation character, so as to first return a response message confirming receipt of the resource transfer request, and then return a response message of the object type of the resource transfer requesting party.

[0105] In an exemplary embodiment, the resource transfer data includes a resource transfer data header, actual resource transfer data, and a resource transfer data footer, such as Figure 4 As shown, S600 also includes:

[0106] S620: Acquire first repeated data corresponding to resource transfer data headers of all resource transfer requests and second repeated data corresponding to resource transfer data tails of all resource transfer requests.

[0107] S640, determine the first repeated data as the file header, determine the second repeated data as the file tail, and based on the test branch type corresponding to the resource transfer identifier of all resource transfer requests, splice the actual resource transfer data of all resource transfer requests, and determine the spliced ​​actual resource transfer data as the file body.

[0108] S660, concatenate the file header, the file body, and the file tail.

[0109] S680: Push the spliced ​​resource transfer data to the application test end.

[0110] Specifically, the resource transfer data of all resource transfer requests are split into multiple segments, and the resource transfer data of all resource transfer requests are spliced ​​by writing an Excel macro code. In detail, the resource transfer data includes a resource transfer data header, actual resource transfer data, and a resource transfer data tail. Each resource transfer data is split into three segments: a resource transfer data header, actual resource transfer data, and a resource transfer data tail. Among them, the resource transfer data header is a repeated data header in all resource transfer data, and the resource transfer data tail is a repeated data tail in all resource transfer data.

[0111] Furthermore, the first repeated data in the resource transfer data header of all resource transfer requests and the second repeated data in the resource transfer data tail of all resource transfer requests are obtained, and the first repeated data is determined as the file header and the second repeated data is determined as the file tail.

[0112] Then, based on the test branch types corresponding to the resource transfer identifiers of all resource transfer requests, the actual resource transfer data of all resource transfer requests are spliced, and the spliced ​​actual resource transfer data is determined as the file body. The file header, file body and file tail are spliced ​​in sequence to obtain the spliced ​​resource transfer data.

[0113] In this embodiment, by determining the first repeated data as the file header and the second repeated data as the file tail, and based on the test branch type corresponding to the resource transfer identifier of all resource transfer requests, the actual resource transfer data of all resource transfer requests are spliced, and the spliced ​​actual resource transfer data is determined as the file body, instead of splicing multiple repeated resource transfer data headers and resource transfer data tails, the amount of spliced ​​repeated data is reduced, and then the resource transfer data of all resource transfer requests are spliced ​​without missing any resource transfer data, thereby taking into account both the accuracy and efficiency of test data processing.

[0114] In an exemplary embodiment, based on the test branch types corresponding to the resource transfer identifiers of all resource transfer requests, splicing the actual resource transfer data of all resource transfer requests includes:

[0115] According to the number of rows of immutable data and the number of rows of variable data in the actual resource transfer data of each resource transfer request, the immutable data and the variable data in the actual resource transfer data of each resource transfer request are spliced ​​to obtain the spliced ​​data of each resource transfer request; based on the test branch types corresponding to the resource transfer identifiers of all resource transfer requests, the spliced ​​data corresponding to different test branch types are cross-spliced.

[0116] The actual resource transfer data includes immutable data and variable data. Immutable data refers to fields that do not need to be parameterized, and variable data refers to fields that need to be parameterized, such as account numbers.

[0117] Specifically, the variable data is used as the variable segment, starting from the first row of the first actual resource transfer data, the first row of the first actual resource transfer data to the row above the row where the first variable segment of the first actual resource transfer data is located are spliced ​​into the file header, and then the row from the row where the first variable segment is located to the row above the row where the second variable segment is located is spliced, and the immutable data and variable data in the actual resource transfer data of each resource transfer request are spliced ​​cyclically to obtain the spliced ​​data of each resource transfer request. In the splicing process, the number of rows to be spliced ​​can be pre-written by the Excel macro code.

[0118] Furthermore, in order to be closer to actual production and life, the present application can simulate the actual resource transfer data of various test branch types in a message. For example, for the actual resource transfer data of the public test branch type, the starting account number is added with 3 at the beginning, and for the actual resource transfer data of the private test branch type, the starting account number is added with 6 at the beginning. And because the actual resource transfer data of different test branch types are processed by different threads, it is necessary to control the distribution ratio of the actual resource transfer data of different test branch types, and reduce the occurrence of splicing of multiple consecutive actual resource transfer data of the same test branch type in sequence, that is, cross-splicing the splicing data corresponding to different test branch types, so that the execution time of multiple threads is more balanced, that is, to reduce the situation where one thread is overloaded and the other thread is idle in the same time period.

[0119] Furthermore, when the splicing data corresponding to different test branch types are cross-spliced, the sequence number of each loop body will be increased, and finally the file tail will be spliced.

[0120] In this embodiment, by writing Excel macro code to automatically splice message details, the fields that need to be parameterized are maintained simply, and the actual resource transfer data of all resource transfer requests are spliced, so that the data in the simulated message reaches a certain amount, and the parameterized accounts of different business types are also proportional to actual production, so that the spliced ​​resource transfer data is close to actual production.

[0121] In an exemplary embodiment, taking the resource transfer request as a transaction request, the resource transfer identifier as a transaction code, and the resource transfer data as transaction data as an example, the present application optimizes various aspects of non-functional test data processing, including:

[0122] 1. Optimize non-functional testing scenarios.

[0123] The existing method is to obtain the transaction volume of each transaction code through the three-level views of Overview View -> Deployment Unit View -> Transaction Code View in the application monitoring platform, calculate the proportion of each transaction in the test scenario, and simulate the test scenario through the proportion of transactions with each transaction code;

[0124] The optimization method is to obtain the transaction volume of the main transaction branches in each transaction code through the four-level view of Overview View -> Deployment Unit View -> Transaction Code View -> Payment Resource in the application monitoring platform, and subdivide the proportion of branches in the test scenario. According to the proportion of transaction volume of each test branch, simulate the proportion of test branch types in the test scenario. For example, simulate that the proportion of private test branch types is 56%, and the proportion of public test branch types is 44%. Other scenarios with smaller proportions are not simulated.

[0125] 2. Optimize the baffle return function.

[0126] The existing method is to identify the transaction code commonly used by the standard XML (Extensible Markup Language) message baffle simulator by regular matching to identify the value of SYS_TX_CODE in the transaction request message. This field is a field that needs to be entered in the new generation of intra-bank messages. After identifying a certain transaction code, a response message corresponding to the transaction code is returned.

[0127] The optimization method is to analyze the identification types and implementation methods supported in the baffle simulator jar package, obtain parameter values ​​through multiple position offsets, and then splice them into a new transaction code. For example, the updated transaction codes recognized by the baffle are E10181S4213 and E0181S4216, representing the public test branch type and the private test branch type. Configure different response messages for each test branch type, and return different values ​​in the account type ACCT_DTL_TYPE field in the response message to trigger different subsequent transactions.

[0128] For special scenarios where two responses need to be returned, the two response messages that need to be returned are returned in one message body, and the special character AAAAA is added between the two responses to determine whether they need to be returned in two times.

[0129] 3. Optimize the transaction data corresponding to all transaction requests.

[0130] Split a transaction data into a data header, transaction details and data tail, and finally splice them into the final test message by writing Excel macro code. The relatively fixed parts of the transaction data, that is, the parts before and after the transaction details data, are used as the file header and file tail, and the transaction details data part is used as the file body. The splicing method is to splice the file header with the first line of the file body until the first variable segment in the file body. The variable segment is the field that needs to be parameterized. In the macro code, you can directly write it to the line of the file body, and add the variable end to change as needed. For example, the starting account number is added in a mixed way starting with 3 or 6, simulating that the details in a message have both public and private business, and then splice from the first variable segment to the second variable segment, and so on, until the last variable segment to the last line of the file body, so as to splice the required number of transaction details in a loop. The serial number of the variable body will increase each time the loop is repeated, and finally the file tail is spliced. Compress the spliced ​​transaction data and send the compressed data to the application test end.

[0131] In this application, by optimizing non-functional test scenarios, optimizing baffle return functions, and optimizing transaction data corresponding to all transaction requests, the transaction response time obtained by non-functional testing is made closer to production, and the results of gradient stress testing can more accurately obtain the system's stress resistance, which serves as a reference for subsequent operation and maintenance and parameter adjustment, making the non-functional test results more meaningful for reference.

[0132] Furthermore, the optimization methods for test data processing are not limited to the few items in the solution. For example, in non-functional testing, the database needs to have a certain amount of data as the test background, but most of the data in the test environment is artificially simulated, and the data distribution is quite different from that in production, resulting in transactions in the test being unable to reach the same index as in production. Different databases take time to result in different transaction response times, which makes the non-functional test results different from production. However, production data cannot be imported into the test environment due to confidentiality principles. How to solve the problem of making the data distribution in the test environment closer to production is also one of the methods for optimizing non-functional testing. For example, the non-functional test results can be integrated into online editing to greatly shorten the time for writing reports, which is also one of the methods for optimizing test data processing.

[0133] Furthermore, based on the above optimization content, the present application also provides a complete test data processing method, including:

[0134] Detect all target test branch types corresponding to the same transaction code, such as public test branch types and private test branch types. According to the ratio of the actual resource amounts corresponding to all target test branch types, determine the type ratio of all target test branch types. Through the type ratio, simulate the test scenario where all target test branch types exist.

[0135] For a target transaction request carrying the same transaction code among multiple transaction requests, the field column corresponding to the target transaction request is determined, and the transaction code of the target transaction request is updated based on the parameter value in the field column within a preset offset range. In the case where there are multiple field columns corresponding to the target transaction request, the parameter value in each field column detected within the preset offset range is spliced, and the spliced ​​parameter value is updated as the transaction code of the target transaction request.

[0136] Based on the test branch type corresponding to the transaction code of all transaction requests, a response message corresponding to the transaction request is generated. When a preset separation character exists in the response message, the response message is segmented based on the preset separation character to obtain a first sub-response message and a second sub-response message, and the first sub-response message and the second sub-response message are returned in sequence, wherein the first sub-response message is used to verify whether the transaction request is received, and the second sub-response message is used to return the object type of the transaction requester, such as whether the transaction requester is a public type or a private type. When there is no preset separation character in the response message, the response message is returned to the transaction requester corresponding to the resource transfer request at one time.

[0137] Each transaction data is split into a resource transfer data header, transaction details data, and transaction data tail. The transaction data header is determined as the file header, and the transaction data tail is determined as the file tail. According to the number of rows of immutable data and the number of rows of variable data in the transaction details data of each transaction request, the immutable data and the variable data in the transaction details data of each transaction request are spliced ​​to obtain the spliced ​​data of each transaction request. Based on the test branch types corresponding to the transaction codes of all transaction requests, the spliced ​​data corresponding to different test branch types are cross-spliced ​​to simulate various test branch types, and the distribution of various test branch types is close to real life. Splice the file header, file body, and file tail, and push the spliced ​​resource transfer data to the application test end.

[0138] It should be understood that, although the steps in the flowcharts involved in the above embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0139] Based on the same inventive concept, the embodiment of the present application also provides a test data processing device for implementing the test data processing method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more test data processing device embodiments provided below can refer to the limitations of the test data processing method above, and will not be repeated here.

[0140] In an exemplary embodiment, Figure 5As shown, a test data processing device 700 is provided, comprising: a request acquisition module 20, a request analysis module 400 and a test data processing module 600, wherein:

[0141] The request acquisition module 200 is used to acquire multiple resource transfer requests in the test scenario, wherein the resource transfer request carries a resource transfer identifier and resource transfer data;

[0142] The request analysis module 400 is used to determine the field column corresponding to the target resource transfer request carrying the same resource transfer identifier among multiple resource transfer requests, and update the resource transfer identifier of the target resource transfer request based on the parameter value in the field column within a preset offset range;

[0143] The test data processing module 600 is used to splice the resource transfer data of all resource transfer requests based on the test branch types corresponding to the resource transfer identifiers of all resource transfer requests, and push the spliced ​​resource transfer data to the application test end.

[0144] In one embodiment, the test data processing device 700 also includes a test scenario simulation module, which is used to: determine the same resource transfer identifier carried by multiple resource transfer requests, and detect the target test branch types corresponding to all the same resource transfer identifiers, determine the type ratio of all target test branch types based on the actual resource quantities corresponding to all target test branch types, and simulate the test scenario in which all target test branch types exist through the type ratio.

[0145] In one of the embodiments, the request analysis module is also used to detect the parameter value within a preset offset range in each field field when there are multiple field fields corresponding to the target resource transfer request, splice all the detected parameter values, and update the spliced ​​parameter value to the resource transfer identifier of the target resource transfer request.

[0146] In one embodiment, the test data processing device 700 also includes a message return module, which is used to generate a response message corresponding to the resource transfer request based on the test branch type, and return the response message to the resource transfer requester corresponding to the resource transfer request, and the response message is used to return the object type of the resource transfer requester.

[0147] In one of the embodiments, the message return module is also used to determine whether there is a preset separation character in the response message; if there is a preset separation character in the response message, the response message is segmented based on the preset separation character to obtain a first sub-response message and a second sub-response message, and the first sub-response message and the second sub-response message are returned in sequence, wherein the first sub-response message is used to verify whether the resource transfer request is received, and the second sub-response message is used to return the object type of the resource transfer requester, and if there is no preset separation character in the response message, the response message is returned to the resource transfer requester corresponding to the resource transfer request.

[0148] In one of the embodiments, the resource transfer data includes a resource transfer data header, actual resource transfer data, and a resource transfer data tail. The test data processing module is also used to obtain the first repeated data corresponding to the resource transfer data header of all resource transfer requests and the second repeated data corresponding to the resource transfer data tail of all resource transfer requests, determine the first repeated data as the file header, determine the second repeated data as the file tail, and based on the test branch type corresponding to the resource transfer identifier of all resource transfer requests, splice the actual resource transfer data of all resource transfer requests, determine the spliced ​​actual resource transfer data as the file body, and splice the file header, file body, and file tail.

[0149] In one of the embodiments, the test data processing module is also used to splice the immutable data and the variable data in the actual resource transfer data of each resource transfer request according to the number of rows of immutable data and the number of rows of variable data in the actual resource transfer data of each resource transfer request to obtain the spliced ​​data of each resource transfer request, and based on the test branch types corresponding to the resource transfer identifiers of all resource transfer requests, cross-splice the spliced ​​data corresponding to different test branch types.

[0150] Each module in the above test data processing device can be implemented in whole or in part by software, hardware or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module.

[0151] In an exemplary embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. Figure 6As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data such as resource transfer identification and resource transfer data. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a test data processing method is implemented.

[0152] Those skilled in the art will understand that Figure 6 The structure shown in the figure is a block diagram of a partial structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0153] In one embodiment, a computer device is further provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above method embodiments when executing the computer program.

[0154] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0155] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0156] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0157] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0158] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A test data processing method, characterized in that: The method comprises: Acquire multiple resource transfer requests in a test scenario, wherein the resource transfer request carries a resource transfer identifier and resource transfer data; For a target resource transfer request carrying the same resource transfer identifier among the multiple resource transfer requests, determine a field column corresponding to the target resource transfer request, and update the resource transfer identifier of the target resource transfer request based on a parameter value in the field column within a preset offset range; Based on the test branch types corresponding to the resource transfer identifiers of all resource transfer requests, the resource transfer data of all resource transfer requests are spliced, and the spliced ​​resource transfer data is pushed to the application test end.

2. The method according to claim 1, characterized in that The method further comprises: Determine the same resource transfer identifiers carried by the multiple resource transfer requests, and detect the target test branch types corresponding to all the same resource transfer identifiers; Determine the type ratio of all target test branch types according to the actual resource amounts corresponding to all target test branch types; Through the type proportions, a test scenario in which all the target test branch types exist is simulated.

3. The method according to claim 1, characterized in that The updating of the resource transfer identifier of the target resource transfer request based on the parameter value in the field column within the preset offset range includes: In the case where there are multiple fields corresponding to the target resource transfer request, detecting a parameter value in each field within a preset offset range; All detected parameter values ​​are concatenated, and the concatenated parameter values ​​are updated as the resource transfer identifier of the target resource transfer request.

4. The method according to claim 1, characterized in that: The method further comprises: Based on the test branch type, generating a response message corresponding to the resource transfer request; The response message is returned to the resource transfer requester corresponding to the resource transfer request, where the response message is used to return the object type of the resource transfer requester.

5. The method according to claim 4, characterized in that The returning the response message to the resource transfer requester corresponding to the target resource transfer request includes: Determine whether there is a preset separation character in the response message; In the case where the preset separation character exists in the response message, the response message is divided based on the preset separation character to obtain a first sub-response message and a second sub-response message, and the first sub-response message and the second sub-response message are returned in sequence, wherein the first sub-response message is used to verify whether the resource transfer request is received, and the second sub-response message is used to return the object type of the resource transfer requester; In a case where the preset separation character does not exist in the response message, the response message is returned to the resource transfer requesting party corresponding to the resource transfer request.

6. The method according to claim 1, characterized in that The resource transfer data includes a resource transfer data header, actual resource transfer data, and a resource transfer data tail. The test branch type corresponding to the resource transfer identifier based on all resource transfer requests is spliced ​​with the resource transfer data of all resource transfer requests, and further includes: Acquire first repeated data corresponding to resource transfer data headers of all resource transfer requests and second repeated data corresponding to resource transfer data tails of all resource transfer requests; Determine the first repeated data as a file header, determine the second repeated data as a file tail, and based on the test branch type corresponding to the resource transfer identifiers of all the resource transfer requests, splice the actual resource transfer data of all the resource transfer requests, and determine the spliced ​​actual resource transfer data as a file body; The file header, the file body and the file tail are concatenated.

7. The method according to claim 6, characterized in that The test branch type corresponding to the resource transfer identifier of all resource transfer requests, and splicing the actual resource transfer data of all resource transfer requests, includes: splicing the immutable data and the variable data in the actual resource transfer data of each resource transfer request according to the number of rows of immutable data and the number of rows of variable data in the actual resource transfer data of each resource transfer request to obtain spliced ​​data of each resource transfer request; Based on the test branch types corresponding to the resource transfer identifiers of all the resource transfer requests, the splicing data corresponding to the different test branch types are cross-spliced.

8. A test data processing device, characterized in that: The device comprises: A request acquisition module, used to acquire multiple resource transfer requests in a test scenario, wherein the resource transfer request carries a resource transfer identifier and resource transfer data; a request analysis module, configured to determine, for a target resource transfer request carrying the same resource transfer identifier among the multiple resource transfer requests, a field column corresponding to the target resource transfer request, and update the resource transfer identifier of the target resource transfer request based on a parameter value in the field column within a preset offset range; The test data processing module is used to splice the resource transfer data of all resource transfer requests based on the test branch types corresponding to the resource transfer identifiers of all resource transfer requests, and push the spliced ​​resource transfer data to the application test end.

9. The device according to claim 8, characterized in that The test data processing device also includes a test scenario simulation module, which is used to: determine the same resource transfer identifier carried by the multiple resource transfer requests, and detect the target test branch types corresponding to all the same resource transfer identifiers, determine the type ratio of all the target test branch types based on the actual resource quantities corresponding to all the target test branch types, and simulate the test scenario in which all the target test branch types exist through the type ratio.

10. The device according to claim 8, characterized in that The request analysis module is also used to detect the parameter value within a preset offset range in each field field when there are multiple field fields corresponding to the target resource transfer request, splice all detected parameter values, and update the spliced ​​parameter value to the resource transfer identifier of the target resource transfer request.

11. The device according to claim 8, characterized in that The test data processing device also includes a message return module, which is used to generate a response message corresponding to the resource transfer request based on the test branch type, and return the response message to the resource transfer requester corresponding to the resource transfer request, wherein the response message is used to return the object type of the resource transfer requester.

12. The device according to claim 11, characterized in that The message return module is also used to determine whether there is a preset separation character in the response message. If the preset separation character exists in the response message, the response message is divided based on the preset separation character to obtain a first sub-response message and a second sub-response message, and the first sub-response message and the second sub-response message are returned in sequence, wherein the first sub-response message is used to verify whether the resource transfer request is received, and the second sub-response message is used to return the object type of the resource transfer requester. If the preset separation character does not exist in the response message, the response message is returned to the resource transfer requester corresponding to the resource transfer request.

13. The device according to claim 8, characterized in that The resource transfer data includes a resource transfer data header, actual resource transfer data and a resource transfer data tail. The test data processing module is also used to obtain first repeated data corresponding to the resource transfer data header of all resource transfer requests and second repeated data corresponding to the resource transfer data tail of all resource transfer requests, determine the first repeated data as a file header, determine the second repeated data as a file tail, and based on the test branch type corresponding to the resource transfer identifier of all resource transfer requests, splice the actual resource transfer data of all resource transfer requests, determine the spliced ​​actual resource transfer data as a file body, and splice the file header, the file body and the file tail.

14. The device according to claim 13, characterized in that The test data processing module is also used to splice the immutable data and the variable data in the actual resource transfer data of each resource transfer request according to the number of rows of immutable data and the number of rows of variable data in the actual resource transfer data of each resource transfer request to obtain the spliced ​​data of each resource transfer request, and based on the test branch type corresponding to the resource transfer identifier of all the resource transfer requests, cross-splice the spliced ​​data corresponding to different test branch types.

15. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

16. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

17. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.