A verification method, device, equipment and storage medium for a reconstruction system

Abstract

This article provides a verification method, device, equipment and storage medium for a reconstruction system, wherein the method includes receiving a business request sent by a verification system; generating a second call request to a service-side system according to the business request; obtaining baffle data fed back by the verification system according to the second call request, wherein the baffle data is the response data sent by the service-side system to the system before reconstruction; processing the business request according to the baffle data to obtain second output data; and feeding back the second output data to the verification system, so that the verification system verifies whether there are defects in the reconstructed system according to the second output data and the first output data, wherein the first output data is the response data of the system before reconstruction to the business request. This article can construct an isolated environment for the reconstructed system, and verify the reconstructed system with the business request, baffle data and first output data of the system before reconstruction, so that the verification of the reconstructed system does not need to rely on peripheral systems.

Description

Technical Field

[0001] The present invention relates to the technical field of automatic program design, and in particular to a verification method, device, equipment and storage medium for a reconstruction system. Background Art

[0002] With the continuous growth of the Internet market and the rapid expansion of business, the original system may not be compatible with the existing needs. However, considering many factors such as development cost and development cycle, sometimes a new system is not directly developed to replace the original system, but the original system is reconstructed. Reconstruction does not change the external functions of the system, but only readjusts the internal structure. After reconstruction, the integrity and robustness of the new system need to be verified. However, in the existing technology, the verification of the reconstructed system mainly adopts the method of manual full-process testing, that is, manual production request messages are used to verify whether the input and output of the system before reconstruction and the system after reconstruction are consistent. However, the above verification process often has many technical problems such as high verification cost, high error rate of manual data verification, and excessive dependence on peripheral systems. In view of this, this paper aims to provide a verification method for the reconstructed system to realize convenient, low-cost and accurate verification of the reconstructed system and overcome the dependence on peripheral systems. Summary of the invention

[0003] In view of the above problems in the prior art, the purpose of this article is to provide a verification method, device, equipment and storage medium for a reconstruction system to solve the problems of high cost, low reliability and dependence on peripheral systems in the prior art for verification of the reconstructed system.

[0004] In order to solve the above technical problems, the specific technical solutions of this article are as follows:

[0005] On the one hand, this paper provides a verification method for a reconstruction system, including:

[0006] Receive business requests sent by the verification system;

[0007] Generate a second call request according to the service request;

[0008] According to the second call request, the baffle data fed back by the verification system is obtained, wherein the baffle data is response data to the first call request sent by the service-side system to the pre-reconstruction system, and the first call request is obtained by the pre-reconstruction system according to the service request;

[0009] Processing the service request according to the baffle data to obtain second output data;

[0010] The second output data is fed back to the verification system so that the verification system verifies whether the reconstructed system has defects according to the second output data and the first output data, wherein the first output data is the response data of the system before reconstruction to the service request.

[0011] On the other hand, this article also provides a verification device for a reconstruction system, including:

[0012] A first receiving module, used for receiving a service request sent by a verification system;

[0013] A first generating module, used to generate a second calling request according to the service request;

[0014] A second acquisition module is used to acquire baffle data fed back by the verification system according to the second call request, wherein the baffle data is response data to the first call request sent by the service party system to the pre-reconstruction system, and the first call request is obtained by the pre-reconstruction system according to the business request;

[0015] A first processing module, configured to process the service request according to the baffle data to obtain second output data;

[0016] The first feedback module is used to feed back the second output data to the verification system, so that the verification system verifies whether there are defects in the reconstructed system based on the second output data and the first output data, and the first output data is the response data of the system before reconstruction to the business request.

[0017] On the other hand, this paper also provides a verification method for a reconstruction system, including:

[0018] Receive a service request sent by a requesting system;

[0019] Generate a first call request according to the business request and send it to the service party system;

[0020] Acquire baffle data corresponding to the first call request fed back by the service party system;

[0021] Processing the service request according to the baffle data to obtain first output data;

[0022] The service request, the baffle data and the first output data are stored and sent to a verification system, so that the verification system initiates verification of the reconstructed system.

[0023] On the other hand, this article also provides a verification device for a reconstruction system, including:

[0024] A second receiving module is used to receive a service request sent by a requesting system;

[0025] A second generating module, used to generate a first call request according to the business request and send the first call request to the service party system;

[0026] A third acquisition module, used to acquire the baffle data corresponding to the first call request fed back by the service party system;

[0027] A second processing module, configured to process the service request according to the baffle data to obtain the first output data;

[0028] The first sending module stores the service request, the baffle data and the first output data and sends them to a verification system, so that the verification system initiates verification of the reconstructed system.

[0029] On the other hand, this paper also provides a verification method for a reconstruction system, including:

[0030] Send business requests to the reconstructed system;

[0031] receiving a second call request to the service-side system sent by the reconstructed system;

[0032] According to the second call request, match the baffle data and send it to the reconstructed system, the baffle data being the response data to the first call request sent by the service-side system to the pre-reconstructed system, the first call request being obtained by the pre-reconstructed system according to the service request;

[0033] receiving second output data fed back by the reconstructed system, where the second output data is obtained by the reconstructed system processing the service request according to the baffle data;

[0034] Verify whether the reconstructed system has defects based on the second output data and the pre-stored first output data.

[0035] On the other hand, this article also provides a verification device for a reconstruction system, including:

[0036] A second sending module, used for sending a service request to the reconstructed system;

[0037] A third receiving module is used to receive a second call request to the service-side system sent by the reconstructed system;

[0038] a matching module, configured to match baffle data according to the second call request and send the baffle data to the reconstructed system, wherein the baffle data is response data to the first call request sent by the service-side system to the pre-reconstructed system, and the first call request is obtained by the pre-reconstructed system according to the service request;

[0039] A fourth receiving module, configured to receive second output data fed back by the reconstructed system, where the second output data is obtained by the reconstructed system processing the service request according to the baffle data;

[0040] A verification module is used to verify whether the reconstructed system has defects based on the second output data and the pre-stored first output data.

[0041] On the other hand, this document also provides a computer storage configuration, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the method steps described in the above technical solution are implemented.

[0042] On the other hand, this document also provides a storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method steps described in the above technical solution are implemented.

[0043] By adopting the above technical scheme, a reconstruction system, device, computer equipment and storage medium described in this article can build an isolated environment for the reconstructed system, and verify the reconstructed system with the system business request, the first call request, the baffle data and the first output data before the reconstruction, so that the verification of the reconstructed system does not need to rely on the peripheral system; it can reduce the interference of human factors, improve the sample nature and coverage of the data used to verify the reconstructed system, and improve the efficiency and reliability of the verification results.

[0044] In order to make the above and other purposes, features and advantages of this article more obvious and easy to understand, the following specifically cites preferred embodiments and describes them in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] In order to more clearly illustrate the technical solutions in the embodiments of this article or the prior art, the drawings required for use in the embodiments or the prior art descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments of this article. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0046] Figure 1 A first flow chart of a reconstruction system verification method provided by an embodiment of this invention is shown;

[0047] Figure 2 A schematic diagram showing an inter-system call architecture is shown;

[0048] Figure 3 The schematic diagram of the input and output principle of the system is shown;

[0049] Figure 4A first structural schematic diagram of a reconstruction system verification device provided by an embodiment of this invention is shown;

[0050] Figure 5 A second flow chart of a reconstruction system verification method provided by an embodiment of this invention is shown;

[0051] Figure 6 A second structural schematic diagram of a reconstruction system verification device provided by an embodiment of this invention is shown;

[0052] Figure 7 A third flow chart of a verification method for a reconstruction system provided in an embodiment of this invention is shown;

[0053] Figure 8 A third structural schematic diagram of a reconstruction system verification device provided by an embodiment of this invention is shown;

[0054] Fig. 9 A schematic diagram of the structure of a reconstruction system verification system is shown;

[0055] Fig.10 A schematic diagram of the overall process of a reconstruction system verification method is shown;

[0056] Fig.11 A schematic diagram of the structure of a computer device provided in an embodiment of this invention is shown.

[0057] Description of the accompanying symbols:

[0058] 41. A first receiving module;

[0059] 42. The first generation module;

[0060] 43. Second acquisition module;

[0061] 44. A first processing module;

[0062] 45. The first feedback module;

[0063] 61. A second receiving module;

[0064] 62. Second generation module;

[0065] 63. The third acquisition module;

[0066] 64. Second processing module;

[0067] 65. A first sending module;

[0068] 81. A second sending module;

[0069] 82. A third receiving module;

[0070] 83. Matching module;

[0071] 84. A fourth receiving module;

[0072] 85. Verification module;

[0073] 91. A first data acquisition module;

[0074] 92. Synchronization module;

[0075] 93. A second data acquisition module;

[0076] 94. Transaction playback module;

[0077] 95. Baffle service module;

[0078] 96. Comparison and verification module

[0079] 1102. Computer equipment;

[0080] 1104. Processor;

[0081] 1106. Memory;

[0082] 1108, driving mechanism;

[0083] 1110, input / output module;

[0084] 1112. Input device;

[0085] 1114. Output device;

[0086] 1116. Presentation equipment;

[0087] 1118. Graphical user interface;

[0088] 1120. Network interface;

[0089] 1122. Communication link;

[0090] 1124. Communication bus. DETAILED DESCRIPTION

[0091] The following will be combined with the drawings in the embodiments of this article to clearly and completely describe the technical solutions in the embodiments of this article. Obviously, the described embodiments are only part of the embodiments of this article, not all of the embodiments. Based on the embodiments of this article, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this article.

[0092] It should be noted that the terms "first", "second", etc. in the specification and claims of this article and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of this article described here can be implemented in an order other than those illustrated or described here. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, device, product or equipment that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or equipment.

[0093] Refactoring is to improve the quality and performance of software by adjusting the program code, making the design pattern and architecture of the program more reasonable, and improving the scalability and maintainability of the software.

[0094] With the rapid development of the Internet, customers' businesses are constantly changing. After the system is developed, some requirements may be relatively stable, some may change drastically, and some may have disappeared or transformed into other requirements. In this case, the system needs to be changed accordingly. However, considering factors such as cost and time, not all systems are directly abandoned and redeveloped. Instead, the original system is reconstructed, that is, the original external functions of the system are not changed, and only the internal structure of the system is reorganized. Through reconstruction, the structure of the system is constantly adjusted, so that the reconstructed system always has strong adaptability and support capabilities for business needs. Reconstruction can reduce the coupling degree of the system, make the system more modular, and help improve the development efficiency and subsequent maintenance of the system.

[0095] Of course, in order to make the reconstructed system have functional integrity and robustness, it is particularly important to verify the reconstructed system. The verification method used in the prior art is mainly to use manual full-process testing, that is, according to the transaction path and transaction process involved, through manual clicks, sending and other operations to trigger, let the test data run once in the reconstructed system and its associated peripheral systems (referring to the architecture of multiple system interactive calls, from the perspective of a certain system, all other systems associated with it, including the service requester system and the service provider system, collectively referred to as peripheral systems) for joint testing, and then perform manual comparison and analysis based on the test results to achieve the purpose of verification. As a result, it causes: excessive reliance on the cooperation of peripheral systems, especially involving complex scenarios that require the linkage of multiple peripheral systems. When the peripheral system is unstable or not supported in place, it leads to high coordination costs and slow testing progress; in addition, most of the test data comes from manual creation, system pre-embedded, system intervention, etc., resulting in single test data, reduced sample nature, incomplete coverage of cases, and unreliable verification structure of the reconstructed system; the comparison of verification output results mainly relies on manual comparison and review, which has high labor costs, high error rates and low testing efficiency.

[0096] In order to solve the above problems, the embodiments of this article provide a verification method for a reconstructed system, which can conveniently and accurately verify the reconstructed system, reduce costs, and overcome the dependence on peripheral systems. Figure 1 This is a first flow chart of a verification method for a reconstruction system provided in an embodiment of this invention. This specification provides method operation steps as described in the embodiment or flow chart, but may include more or fewer operation steps based on conventional or non-creative labor. The order of steps listed in the embodiment is only one way of executing the steps among many, and does not represent the only execution order. When the actual system or device product is executed, it can be executed in the order or in parallel according to the method shown in the embodiment or the accompanying drawings. Specifically, Figure 1 As shown, the method is applicable to a reconstructed system, and the method comprises:

[0097] S110: receiving a service request sent by a verification system;

[0098] S120: Generate a second call request according to the service request;

[0099] It should be noted that if Figure 2As shown, it is a schematic diagram of the inter-system call architecture. For a system, it can be used as a service system for other systems to call it, and it can also be used as a requesting system to initiate call requests to other systems. The same is true for the pre- / post-reconstruction system described in the embodiments of this specification. When the business request it receives requires the functional implementation of other systems to cooperate and complete, it can send a second call request to the service system. And the pre- / post-reconstruction system can make more than one call request to the same service system, and can also send call requests to multiple different service systems. That is, for one business request, the pre- / post-reconstruction system may require multiple and multiple functional cooperation of multiple service systems.

[0100] from Figure 2 It can be seen that for the pre-reconstruction / post-reconstruction system in the embodiment of this specification, there are two ways for data input, namely, the input request sent by the service requester system and the input response returned by the service provider system; there are also two ways for data output, namely, the output response returned by the reconstructed system to the service requester system and the output call request sent to the service provider system, that is, Figure 3 The system input and output principle diagram is shown.

[0101] according to Figure 2 and Figure 3 It can be seen that, under the premise of not affecting the associated systems and existing functions, to verify whether a reconstructed system has defects, it is only necessary to ensure that the same data is input to the reconstructed system and the system before reconstruction, and then compare and verify the output data generated by the two systems according to the preset comparison rules.

[0102] S130: According to the second call request, the baffle data fed back by the verification system is obtained, wherein the baffle data is a summary of the response data to the first call request sent by the service-side system to the pre-reconstruction system, and the baffle data is used to completely simulate the return of the service-side system, wherein the first call request is obtained by the pre-reconstruction system parsing the service request; in the embodiment of this specification, the post-reconstruction system is obtained by reconstructing the pre-reconstruction system;

[0103] S140: Processing the service request according to the baffle data to obtain second output data;

[0104] That is, the verification system uses the business requests processed by the system before reconstruction to realize playback in the reconstructed system. In the embodiments of this specification, playback (also called replay) means that according to the original functional process and transaction path before reconstruction, the verification system automatically simulates the operation of the requesting system initiating a business request to the reconstructed system and can simulate the service system returning the response data (i.e., baffle data).

[0105] S150: Feedback the second output data to the verification system, so that the verification system verifies whether the reconstructed system has defects according to the second output data and the first output data, wherein the first output data is the response data of the system before reconstruction to the business request.

[0106] A verification method for a reconstruction system provided in an embodiment of this specification can use the business request data, first output data and baffle data of the system before reconstruction to verify the function and performance of the reconstructed system, thereby overcoming the dependence on peripheral systems, reducing the influence of human factors, and facilitating improving verification accuracy.

[0107] Before generating the second call request, the method further includes:

[0108] According to the business request, determine whether the reconstructed system needs to call the service system; since the reconstructed system may have some improvements over the system before reconstruction, it may be possible to complete the processing of the business request without initiating a call to the service system.

[0109] If the service system needs to be called, the second calling request is generated, so that the verification system can match the baffle data according to the second calling request;

[0110] If there is no need to call the service system, the business request is directly processed to obtain the second output data.

[0111] Preferably, in the embodiment of this specification, before step S110: receiving the service request sent by the verification system, the method further includes:

[0112] S100: Sending a synchronization instruction to the verification system so that the verification system acquires the environment data and business data of the system before reconstruction, and then performs a synchronization operation on the system after reconstruction so that the system after reconstruction is synchronized with the system before reconstruction.

[0113] The post-reconstruction system is at the same level as the pre-reconstruction system, and the environmental data and business data of the two are kept consistent. This is a prerequisite for subsequent verification. The post-reconstruction system can be synchronized with the pre-reconstruction system through the following methods:

[0114] The system before reconstruction is subjected to daily batch processing on T-1 to collect static data of T-1 according to established rules. The collected data includes environmental data such as system date and directory structure, as well as business data such as business date, customer information, account information, and product information. The environmental data and business data may be the production environment data of the system before reconstruction. Of course, in some feasible embodiments, the test environment data of the system before reconstruction may also be obtained to enrich the data source and improve the verification efficiency of the reconstruction system. It should be noted that the production environment data is more real and accurate.

[0115] According to the design differences between the system before reconstruction and the system after reconstruction, the static data collected in the previous step is processed (for example, formatted so that the static data in the system before reconstruction has a format suitable for the system after reconstruction) to obtain initialization data for synchronizing the system after reconstruction;

[0116] The reconstructed system is initialized using the initialization data so that the system data of the reconstructed system is at the same level as that of the system before the reconstruction on day T-1 (for example, environmental data such as system time, business date, customer information, and business data are synchronized between the system after the reconstruction and the system before the reconstruction at a certain point in time).

[0117] In some feasible embodiments, the method further includes:

[0118] Feedback the second call request to the verification system, so that the verification system verifies whether there are defects in the reconstructed system according to the second call request and the first call request, and / or the second output data and the first output data. For the service-side system, if the second call request of the reconstructed system is inconsistent with the first call request of the system before reconstruction, the service-side system needs to be appropriately improved to adapt to the reconstructed system, which increases the burden of service-side system development and upgrade. The reconstruction system verification method provided in the embodiment of this specification can also verify the reconstructed system by the difference between the call requests of the system to the service-side system before and after reconstruction. The verification method is more diverse and is also conducive to improving the accuracy of verification.

[0119] In summary, the verification method for a reconstructed system provided in the embodiments of the present specification can build an isolated environment for the reconstructed system to eliminate the dependence on peripheral systems during verification; and use the static data collected from the system before reconstruction to initialize the reconstructed system in the isolated environment, and prepare for data leveling and baffle services; and use the business data of the system before reconstruction, the first output data, the baffle data, the first call request and other operating state data to replay and verify the reconstructed system to obtain a verification result.

[0120] like Figure 4FIG. 1 is a first structural diagram of a verification device for a reconstruction system provided in an embodiment of this specification, wherein the device includes:

[0121] A first receiving module 41, used to receive a service request sent by a verification system;

[0122] A first generating module 42, configured to generate a second calling request according to the service request;

[0123] A second acquisition module 43 is used to acquire baffle data fed back by the verification system according to the second call request, wherein the baffle data is response data to the first call request sent by the service party system to the pre-reconstruction system, and the first call request is obtained by the pre-reconstruction system parsing the service request;

[0124] A first processing module 44, configured to process the service request according to the baffle data to obtain second output data;

[0125] The first feedback module 45 is used to feed back the second output data to the verification system, so that the verification system verifies whether there are defects in the reconstructed system based on the second output data and the first output data, and the first output data is the response data of the system before reconstruction to the business request.

[0126] The beneficial effects achieved by the verification device for the reconstruction system provided in the embodiments of this specification are consistent with the beneficial effects achieved by the above method, and will not be described in detail here.

[0127] like Figure 5 As shown, the embodiment of this specification also provides a verification method for a reconstruction system, the method is applicable to a system before reconstruction, and the method includes:

[0128] S510: receiving a service request sent by a requesting system;

[0129] S520: Generate a first call request according to the business request and send it to the service party system;

[0130] S530: Obtain the baffle data corresponding to the first call request fed back by the service system; the baffle data here is essentially the response data sent by the service system to the pre-reconstruction system corresponding to the first call request, and the response data is stored as baffle data for feedback to the post-reconstruction system to meet its call requirements for the service system. S540: Process the service request according to the baffle data to obtain the first output data;

[0131] S550: Store the service request, the baffle data, and the first output data and send them to a verification system, so that the verification system initiates verification of the reconstructed system.

[0132] Also includes:

[0133] A first call request is sent to the verification system, so that the verification system initiates verification of the reconstructed system according to the first call request and / or the first output data.

[0134] The method further comprises:

[0135] The environmental data and the business data are sent to the verification system so that the verification system performs synchronization operations on the reconstructed system and the pre-reconstructed system.

[0136] A verification method provided in the embodiments of this specification is applicable to the pre-reconstruction system. The pre-reconstruction system sends the service request sent by the requesting system, the first call request to the service system, the baffle data fed back by the service system, and the first output data fed back to the requesting system as running state data to the verification system, so that the verification system verifies the reconstructed system according to the above running state data. Therefore, the reconstructed system does not need to rely on the peripheral system, nor does it need to interact with the pre-reconstruction system; nor will it affect the reconstruction operation of the pre-reconstruction system.

[0137] like Figure 6 As shown, the embodiment of this specification also provides a verification device for a reconstruction system, including:

[0138] The second receiving module 61 is used to receive a service request sent by a requesting system;

[0139] A second generating module 62, configured to generate a first call request according to the business request and send the first call request to the service system;

[0140] A third acquisition module 63 is used to acquire baffle data corresponding to the first call request fed back by the service side system, wherein the baffle data is substantially response data of the service side system to the first call request;

[0141] A second processing module 64, configured to process the service request according to the baffle data to obtain the first output data;

[0142] The first sending module 65 stores the service request, the baffle data and the first output data and sends them to a verification system, so that the verification system initiates verification of the reconstructed system.

[0143] The beneficial effects obtained by the device provided in the embodiments of this specification are consistent with the beneficial effects obtained by the above method and will not be repeated here.

[0144] like Figure 7As shown, the embodiment of this specification also provides a verification method of a reconstruction system, the method is applicable to a verification system, and the method includes:

[0145] S710: Sending a service request to the reconstructed system;

[0146] S720: Receive a second call request to the service-side system sent by the reconstructed system;

[0147] S730: According to the second call request, match the baffle data and send it to the reconstructed system, the baffle data being the response data to the first call request sent by the service-side system to the pre-reconstructed system, the first call request being obtained by the pre-reconstructed system according to the service request;

[0148] S740: receiving second output data fed back by the reconstructed system, where the second output data is obtained by the reconstructed system processing the service request according to the baffle data;

[0149] S750: Verify whether the reconstructed system has defects according to the second output data and the pre-stored first output data.

[0150] Furthermore, before step S710: sending the service request to the reconstructed system, the method further includes:

[0151] S700: Receive the service request fed back by the system before reconstruction, the baffle data and the first output data.

[0152] That is, the business request sent to the reconstructed system, the baffle data used to respond to the second call request of the reconstructed system, and the first output data used for comparison and verification with the second output data of the reconstructed system are all from the operating state data of the system before the reconstruction. The reconstructed system is verified using the operating state data of the system before the reconstruction, without the need to manually create verification data, or pre-embed or interfere with the associated peripheral systems, thereby reducing the verification cost and improving the verification efficiency; and the operating state data used for verification can be more comprehensive, avoiding the problems of low sample and poor coverage, thereby improving the reliability of the verification structure of the reconstructed system.

[0153] Furthermore, in step S750: after verifying whether the reconstructed system has defects according to the second output data and the pre-stored first output data, the method further includes:

[0154] S760: If it is verified that the reconstructed system has defects, the reconstructed system is repaired.

[0155] It should be noted that after repairing the reconstructed system, it is also possible to determine whether it is necessary to synchronize the data between the reconstructed system and the system before reconstruction based on actual conditions, and then perform verification (the verification system can repeatedly replay the collected static and dynamic data in the reconstructed system to verify whether the defect has been repaired or reproduced. This process does not require data rollback in the peripheral systems, which is conducive to improving the efficiency and accuracy of defect verification) until there are no defects in the reconstructed system.

[0156] In some feasible embodiments, step S730: matching baffle data according to the second call request and sending it to the reconstructed system may be specifically performed in the following manner:

[0157] Parse the second call request and obtain the transaction serial number;

[0158] The baffle data is matched according to the transaction serial number. The transaction serial number corresponds to the transaction business one by one, and the transaction serial number is the unique identifier of the transaction business on the transaction path. When the business requester sends a business request to the pre-reconstruction system, the transaction serial number of the business request will be carried; when the pre-reconstruction system feeds back the first output data, the transaction serial number will be carried.

[0159] When the system before reconstruction needs to call the service system, a first call request is generated and sent to the service system. In essence, the system before reconstruction also initiates a business request to the service system. Therefore, the first call request includes the transaction serial number corresponding to the first call request. When the service system feeds back the baffle data to the system before reconstruction, the transaction serial number will be fed back together with the baffle data.

[0160] It should be noted that the fields included in the service request (or the first call request) may be as shown in Table 1:

[0161] Table 1

[0162]

[0163] Accordingly, the fields included in the first output data (or baffle data) may be as shown in Table 2:

[0164] Table 2

[0165]

[0166] In some preferred embodiments, in addition to matching based on transaction serial number baffle data, matching can also be performed using a combination of one or more of the above fields such as transaction serial number, response system number, transaction code, sequence number and response status.

[0167] In some feasible embodiments, the method further includes:

[0168] Receiving a second call request fed back by the reconstructed system;

[0169] Verify whether the reconstructed system has defects based on the second call request and the pre-stored first call request, and / or the second output data and the first output data.

[0170] Preferably, the reconstructed system is verified from the perspectives of transaction line, data line, and accounting line respectively: data decoding and parsing of transaction messages, interactive files, and databases are performed, and comparative analysis is performed from multiple dimensions such as data format, structure, field, name, value range, and change process.

[0171] In some preferred embodiments, step S750: verifying whether the reconstructed system has defects according to the second output data and the pre-stored first output data, further comprises:

[0172] The first output data and the second output data are compared according to a preset comparison rule to verify whether the reconstructed system has defects, and the preset comparison rule includes one or a combination of difference filtering, difference mapping, difference shielding, and difference defects.

[0173] The difference filtering means: filtering each difference generated, identifying and grouping each difference according to the established rules, so that the difference groups and the proportion of the number of differences in the groups are clear. In practical applications, there are generally the following grouping dimensions: platform-level differences (such as system framework issues, etc.), module-level differences (issues such as system functional modules), environment-level differences (issues such as system permissions, middleware and other software, machine hardware stability factors, etc.), demand synchronization differences (when the reconstructed system and the pre-reconstructed system develop new requirements at the same time, the reconstructed system lags behind the pre-reconstructed system), explanatory differences, differences to be analyzed, other differences, etc. Different difference groups can be formulated according to the business characteristics and architectural form of the reconstructed system for difference filtering.

[0174] The difference mapping means: before the comparative analysis is run, mapping rules are formulated for the predicted differences to ambush, and when the differences generated by the comparative analysis are matched with these mapping rules, the matching is performed automatically, so that the matched differences are downgraded. The mapping rules generally include field name mapping (e.g., the field naming rules of the system before reconstruction and the system before reconstruction are different, including case sensitivity, camel case marking, etc.), for example: the system before reconstruction uses name to represent the user name, while the system after reconstruction uses Name, data dictionary mapping (e.g., the system before reconstruction uses "false-no true-yes" to represent, while the system after reconstruction uses "0-no 1-yes" to represent "yes or no" relationship, etc.), date format mapping (e.g., the system before reconstruction uses "yyyy / MM / dd" to represent "year, month, day", while the system after reconstruction uses "yyyy-MM-dd" to represent, etc.), file code mapping (e.g., the system before reconstruction uses GB18030, while the system after reconstruction uses UTF-8), etc.

[0175] The difference shielding means: according to the difference results analyzed in the previous round, shielding rules are formulated to shield the newly generated differences. In practical applications, when the difference in a certain link of the main process or key process causes the entire process to be unable to continue to execute, the difference in that link is shielded so that the subsequent steps that depend on it in the process can flow down. In addition, shielding the differences in the rules can speed up the verification of the reconstructed system.

[0176] Differential defects refer to: generating defect information corresponding to the difference according to the established rules. The defect information includes: defect time, defect version, defect severity (low, medium, high, etc.), module, assigned processing team, defect source (transaction line, data line, accounting line, etc.), priority, status, special scenarios, etc., so that the differences generated by comparative analysis can be seamlessly connected with commonly used defect management tools on the market (such as Mercury Quality Center) to facilitate the subsequent defect resolution, circulation, and tracking.

[0177] It should be noted that in the embodiments of this specification, the service request includes:

[0178] Functional verification request and performance verification request;

[0179] The performance verification request refers to sending a batch of business requests concurrently to the reconstructed system to be verified to verify the concurrent processing performance of the reconstructed system. This batch of business requests can have certain classification rules. For example, the system has multiple servers deployed in a cluster and achieves high availability through load balancing. In this way, performance verification can be achieved based on the server number of the receiving business request, the module to which it belongs, etc.

[0180] The function verification request is to send service requests one by one to the reconstructed system to be verified, so as to verify the function of the reconstructed system.

[0181] The functional verification request includes a full verification request and a partial verification request;

[0182] The full verification request verifies all transactions within a preset time period in chronological order; the partial verification request verifies transactions based on preset dimensions.

[0183] Optionally, the preset dimensions include: transaction channels (online banking, mobile banking, ATM machines, etc.), transaction objects (collective or individual, where individuals can be ordinary customers or VIP customers), transaction institutions (local banks involved in the transaction business), transaction categories (account opening, deposits and withdrawals, transfers, etc.) and one or a combination of several of the custom dimensions.

[0184] Therefore, a reconstruction system verification method provided in the embodiments of this specification can verify the reconstructed system through single business and batch business, reduce human interference, improve the sample nature of test data, verify the coverage of test cases, and improve the timeliness and accuracy of verification.

[0185] like Figure 8 As shown, the embodiment of this specification also provides a verification device for a reconstruction system, including:

[0186] A second sending module 81, used for sending a service request to the reconstructed system;

[0187] A third receiving module 82 is used to receive a second calling request to the service party system sent by the reconstructed system;

[0188] A matching module 83 is used to match the baffle data according to the second call request and send it to the reconstructed system, wherein the baffle data is the response data of the first call request sent by the service side system to the pre-reconstructed system, and the first call request is obtained by the pre-reconstructed system according to the service request;

[0189] A fourth receiving module 84, configured to receive second output data fed back by the reconstructed system, where the second output data is obtained by the reconstructed system processing the service request according to the baffle data;

[0190] The verification module 85 is used to verify whether the reconstructed system has defects based on the second output data and the pre-stored first output data.

[0191] like Fig. 9 As shown, the embodiment of this invention provides a verification system, which can be used to verify the reconstructed system, and the system includes:

[0192] The first data collection module 91 is used to collect static data of the system before reconstruction, wherein the static data includes environmental data such as system date and directory structure, and business data such as business date, customer information, account information, product information, etc.;

[0193] A synchronization module 92, configured to perform synchronization operations on the reconstructed system according to the static data collected by the first data collection module 91, so that the environment and data level of the reconstructed system are synchronized with the system before the reconstruction;

[0194] The second data collection module 93 is used to collect the running state data of the system before reconstruction, and the running state data includes the business request sent by the requesting system to the system before reconstruction and the first output data of the system before reconstruction in response to the requesting system; when the system before reconstruction needs to call the service system to process the business request, it also includes obtaining the first call request sent by the system before reconstruction to the service system and the response data corresponding to the first call request fed back by the service system (as the baffle data for subsequent transaction playback);

[0195] The data collected by the second data collection module 93 can be used not only for functional verification testing, but also for performance verification testing; global verification, local verification, single / batch verification, abnormal scenario reproduction, etc. can also be performed according to different verification strategies.

[0196] The transaction business playback module 94 is used to send the business request to the reconstructed system to initiate verification;

[0197] The baffle service module 95 is used to determine that when the reconstructed system needs to call the service system in response to the business request, obtain the second call request generated by the reconstructed system, and match the first call request and / or the business request according to the second call request, so as to match the corresponding baffle data;

[0198] and a comparison and verification module 96, which is used to obtain the second output data fed back by the reconstructed system according to the business request, or according to the business request and the baffle data; and verify the reconstructed system according to the first output data and the second output data. The comparison and verification module 96 is also used to verify the reconstructed system according to the first call request and the second call request, and / or the first output data and the second output data.

[0199] During the verification process of the reconstructed system, the cooperation of the system before reconstruction and the peripheral system is not required, which reduces the dependence and investment in the verification of the reconstructed system. In addition, the baffle data returned by the baffle service module is more accurate, thereby achieving autonomous and controllable verification process, reducing manpower and coordination costs, and improving verification accuracy and efficiency.

[0200] like Fig.10 As shown, it corresponds to Fig. 9 The reconstruction system verification system shown in also provides a verification method:

[0201] S101: The system before reconstruction processes the business request from the requesting system;

[0202] S102: When the service provider system needs to be called, the pre-reconstruction system sends a first call request corresponding to the business request to the service provider system;

[0203] S103: Acquire response data corresponding to the first call request fed back by the service party system (ie, baffle data used for transaction playback);

[0204] S104: Process the business request according to the aforementioned response data to obtain the first output data; feed back the first output data to the business requester; when the pre-reconstruction system does not need to call the service system to cooperate in completing the processing of the business request, directly process to obtain the first output data.

[0205] S105: storing the service request, the baffle data and the first output data and sending them to a verification system; in some feasible embodiments, the first call request may also be sent to a verification system;

[0206] S106: The verification system sends a service request to the reconstructed system;

[0207] S107: When the reconstructed system needs to call the service-side system, the verification system receives a second call request to the service-side system sent by the reconstructed system;

[0208] S108: The verification system matches the corresponding baffle data according to the second call request and simulates the service party system to feed back the data to the reconstructed system;

[0209] S109: The reconstructed system receives the baffle data, processes the business request based on the baffle data, obtains second output data and sends it to the verification system; when the reconstructed system does not need to call the service system to cooperate in completing the processing of the business request, it can directly process and obtain the second output data.

[0210] S1010: The verification system verifies whether the reconstructed system has defects based on the second output data and the first output data; in some feasible embodiments, the verification system can also verify whether the reconstructed system has defects based on the second output data and the first output data, and / or based on the first call request and the second call request.

[0211] Preferably, before step S106: the verification system sends the service request to the reconstructed system, it also includes:

[0212] Acquire static data sent by the system before reconstruction, wherein the static data includes environmental data and business data;

[0213] A synchronization instruction sent by the reconstructed system is received, so as to perform a synchronization operation corresponding to the system before the reconstruction on the reconstructed system through the static data.

[0214] It can be seen from this that the embodiment of this specification provides a verification method for a reconstructed system that is suitable for a verification system, which can verify the business request, first call request, baffle data and first output data of the system before reconstruction on the reconstructed system, so that the verification process does not need to rely on the peripheral system.

[0215] like Fig.11 As shown, a computer device provided in an embodiment of the present invention, the computer device 1102 may include one or more processors 1104, such as one or more central processing units (CPUs), each of which may implement one or more hardware threads. The computer device 1102 may also include any memory 1106, which is used to store any kind of information such as code, settings, data, etc. Non-restrictive, for example, the memory 1106 may include any one or more combinations of the following: any type of RAM, any type of ROM, flash memory device, hard disk, optical disk, etc. More generally, any memory may use any technology to store information. Further, any memory may provide volatile or non-volatile retention of information. Further, any memory may represent a fixed or removable component of the computer device 1102. In one case, when the processor 1104 executes an associated instruction stored in any memory or a combination of memories, the computer device 1102 may perform any operation of the associated instruction. The computer device 1102 also includes one or more drive mechanisms 1108 for interacting with any memory, such as a hard disk drive mechanism, an optical disk drive mechanism, etc.

[0216] The computer device 1102 may also include an input / output module 1110 (I / O) for receiving various inputs (via input devices 1112) and for providing various outputs (via output devices 1114). A specific output mechanism may include a presentation device 1116 and an associated graphical user interface (GUI) 1118. In other embodiments, the input / output module 1110 (I / O), the input device 1112, and the output device 1114 may not be included, and the computer device 1102 may be used as a computer device in a network. The computer device 1102 may also include one or more network interfaces 1120 for exchanging data with other devices via one or more communication links 1122. One or more communication buses 1124 couple the components described above together.

[0217] The communication link 1122 may be implemented in any manner, for example, through a local area network, a wide area network (e.g., the Internet), a point-to-point connection, etc., or any combination thereof. The communication link 1122 may include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc. governed by any protocol or combination of protocols.

[0218] Corresponds to Figures 1 to 3 , Figure 5 , Figure 7 or Fig.10 The method in this article also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the above method are executed.

[0219] The embodiment of the present invention also provides a computer readable instruction, wherein when the processor executes the instruction, the program therein causes the processor to execute the following Figures 1 to 3 , Figure 5 , Figure 7 or Fig.10 The method in .

[0220] It should be understood that in the various embodiments of this document, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this document.

[0221] It should also be understood that in the embodiments of this article, the term "and / or" is only a description of the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0222] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this article.

[0223] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0224] In the several embodiments provided herein, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of the units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, or can be electrical, mechanical or other forms of connection.

[0225] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiments of this article.

[0226] In addition, each functional unit in each embodiment of this invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit may be implemented in the form of hardware or in the form of software functional unit.

[0227] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this article is essentially or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of this article. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program code.

[0228] Specific embodiments are used in this article to illustrate the principles and implementation methods of this article. The description of the above embodiments is only used to help understand the methods and core ideas of this article. At the same time, for general technicians in this field, according to the ideas of this article, there will be changes in the specific implementation methods and application scopes. In summary, the content of this specification should not be understood as a limitation on this article.

Claims

1. A verification method for a reconstruction system, characterized in that: The method is applicable to a reconstructed system, and the method comprises: Receive business requests sent by the verification system; Generate a second call request according to the service request; According to the second call request, the baffle data fed back by the verification system is obtained, wherein the baffle data is response data to the first call request sent by the service-side system to the pre-reconstruction system, and the first call request is obtained by the pre-reconstruction system according to the service request; Processing the service request according to the baffle data to obtain second output data; The second output data is fed back to the verification system so that the verification system verifies whether the reconstructed system has defects according to the second output data and the first output data, wherein the first output data is the response data of the system before reconstruction to the service request.

2. The method according to claim 1, characterized in that Before generating the second call request, the method further includes: According to the business request, determining whether the reconstructed system needs to call a service provider system; If the service system needs to be called, the second calling request is obtained; If it is not necessary to call the service system, the business request is processed to obtain the second output data.

3. The method according to claim 1, characterized in that Before receiving the service request sent by the verification system, the method further includes: A synchronization instruction is sent to the verification system so that the verification system performs synchronization operations on the reconstructed system according to the environmental data and business data of the pre-reconstructed system.

4. The method according to claim 1, characterized in that: The method further comprises: The second call request is fed back to the verification system, so that the verification system verifies whether the reconstructed system has defects according to the second call request and the first call request, and / or the second output data and the first output data.

5. A verification device for a reconstruction system, characterized in that: include: A first receiving module, used for receiving a service request sent by a verification system; A first generating module, used to generate a second calling request according to the service request; A second acquisition module is used to acquire baffle data fed back by the verification system according to the second call request, wherein the baffle data is response data to the first call request sent by the service party system to the pre-reconstruction system, and the first call request is obtained by the pre-reconstruction system according to the business request; A first processing module, configured to process the service request according to the baffle data to obtain second output data; The first feedback module is used to feed back the second output data to the verification system, so that the verification system verifies whether there are defects in the reconstructed system based on the second output data and the first output data, and the first output data is the response data of the system before reconstruction to the business request.

6. A verification method for a reconstruction system, characterized in that: The method is applicable to a system before reconstruction, and the method comprises: Receive a service request sent by a requesting system; Generate a first call request according to the business request and send it to the service party system; Acquire baffle data corresponding to the first call request fed back by the service party system; Processing the service request according to the baffle data to obtain first output data; The service request, the baffle data and the first output data are stored and sent to a verification system, so that the verification system initiates verification of the reconstructed system.

7. The method according to claim 6, characterized in that The method further comprises: A first call request is sent to the verification system, so that the verification system initiates verification of the reconstructed system according to the first call request and / or the first output data.

8. The method according to claim 6, characterized in that The method further comprises: The environmental data and the business data are sent to the verification system so that the verification system performs synchronization operations on the reconstructed system and the pre-reconstructed system.

9. A verification device for a reconstruction system, characterized in that: include: A second receiving module is used to receive a service request sent by a requesting system; A second generating module, used to generate a first call request according to the business request and send it to the service party system; A third acquisition module, used to acquire the baffle data corresponding to the first call request fed back by the service party system; A second processing module, configured to process the service request according to the baffle data to obtain first output data; The first sending module stores the service request, the baffle data and the first output data and sends them to a verification system, so that the verification system initiates verification of the reconstructed system.

10. A verification method for a reconstruction system, characterized in that: The method is applicable to a verification system, and the method comprises: Send business requests to the reconstructed system; receiving a second call request to the service-side system sent by the reconstructed system; According to the second call request, match the baffle data and send it to the reconstructed system, the baffle data being the response data to the first call request sent by the service-side system to the pre-reconstructed system, the first call request being obtained by the pre-reconstructed system according to the service request; receiving second output data fed back by the reconstructed system, where the second output data is obtained by the reconstructed system processing the service request according to the baffle data; Verify whether the reconstructed system has defects based on the second output data and the pre-stored first output data.

11. The method according to claim 10, characterized in that After verifying whether the reconstructed system has defects according to the second output data and the pre-stored first output data, the method further includes: If it is verified that the reconstructed system has defects, the reconstructed system is repaired.

12. The method according to claim 10, characterized in that The verifying whether the reconstructed system has defects according to the second output data and the pre-stored first output data may further include: The first output data and the second output data are compared according to a preset comparison rule to verify whether the reconstructed system has defects, and the preset comparison rule includes one or a combination of difference filtering, difference mapping, difference shielding, and difference defects.

13. The method according to claim 10, characterized in that The business request includes: Functional verification requests and performance verification requests; The functional verification request includes a full verification request and a partial verification request; The full verification request is to verify all transaction businesses within a preset time period in chronological order; the partial verification request is to verify the transaction business in a preset dimension.

14. The method according to claim 13, characterized in that The preset dimensions include: transaction channels, transaction objects, transaction institutions, transaction categories and one or a combination of several of the custom dimensions.

15. The method according to claim 10, characterized in that The method further comprises: Receiving a second call request fed back by the reconstructed system; Verify whether the reconstructed system has defects based on the second call request and the pre-stored first call request, and / or the second output data and the first output data.

16. A verification device for a reconstruction system, characterized in that: include: A second sending module, used for sending a service request to the reconstructed system; A third receiving module, used for receiving a second call request sent by the reconstructed system; a matching module, configured to match baffle data according to the second call request and send the baffle data to the reconstructed system, wherein the baffle data is response data to the first call request sent by the service-side system to the pre-reconstructed system, and the first call request is obtained by the pre-reconstructed system according to the service request; A fourth receiving module, configured to receive second output data fed back by the reconstructed system, where the second output data is obtained by the reconstructed system processing the service request according to the baffle data; A verification module is used to verify whether the reconstructed system has defects based on the second output data and the pre-stored first output data.

17. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method according to any one of claims 1 to 4, claims 6 to 8, or claims 10 to 15 is implemented.

18. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 4, claims 6 to 8, or claims 10 to 15 is implemented.

Images