Breakpoint resumption test methods, systems, devices, media, and program products

Abstract

The present disclosure provides a breakpoint retest method, which relates to software testing in the financial field or other related fields. The method comprises: obtaining a program to be tested and a business table; performing a first processing logic on the business table based on a preset breakpoint to obtain a first result and an actual breakpoint, wherein the first processing logic comprises breakpoint retest testing in the process of executing the program to be tested on the business table; checking the consistency of the preset breakpoint and the actual breakpoint to obtain a breakpoint checking result; executing a program logic on the business table to be checked through the program to be tested to obtain a second result, wherein the second processing logic comprises executing the program to be tested on the business table; checking the consistency of the first business table result and the second business table result to obtain an account checking result; and determining that the program to be tested passes the breakpoint retest testing under the condition that both the breakpoint checking result and the account checking result meet the consistency. The present disclosure also provides a breakpoint retest device, equipment, medium and program product.

Description

Technical Field

[0001] This disclosure relates to the field of software testing technology, specifically to software testing in the financial sector or other related fields, and more specifically to a breakpoint re-capture testing method, apparatus, equipment, medium, and program product. Background Technology

[0002] Currently, core business operations are still primarily deployed on mainframes. Besides daily online transactions and customer interactions, a significant amount of time-sensitive business is processed in batches through mainframe batch systems, such as interest calculation and accrual, account reconciliation, and reporting. While mainframe batch systems improve the overall efficiency of the bank's operations, batch processing itself presents some significant and difficult-to-test risks, especially the more complex testing of mainframe breakpoint reloading.

[0003] Therefore, how to test breakpoint re-capture is a technical problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0004] In view of the above problems, this disclosure provides breakpoint recovery methods, apparatus, devices, media, and program products to improve the accuracy of testing.

[0005] According to a first aspect of this disclosure, a breakpoint re-emergence testing method is provided, comprising: acquiring a program to be tested and a business table; acquiring the program to be tested and the business table; executing a first processing logic on the business table based on a preset breakpoint position to obtain a first business table result and an actual breakpoint position, wherein the first processing logic includes performing a breakpoint re-emergence test based on the preset breakpoint position during the execution of the program to be tested on the business table; verifying the consistency between the preset breakpoint position and the actual breakpoint position to obtain a breakpoint verification result; executing a second processing logic on the business table through the program to be tested to obtain a second business table result, wherein the second processing logic includes executing the program to be tested on the business table; verifying the consistency between the first business table result and the second business table result to obtain an accounting verification result; and determining that the program to be tested passes the breakpoint re-emergence test under the condition that both the breakpoint verification result and the accounting verification result satisfy the consistency requirement.

[0006] According to an embodiment of this disclosure, obtaining the program to be tested and the business table includes: obtaining the program to be tested, the program to be tested including program logic; and obtaining the business table involved in the program processing based on the decomposition of the program logic.

[0007] According to embodiments of this disclosure, the step of executing the first processing logic on the business table based on a preset breakpoint position to obtain the first business table result and the actual breakpoint position includes: obtaining preset index information, the preset index information including the mapping relationship between the business table and the database; performing a table locking operation on the business table at the preset breakpoint position based on the preset index information; recording the corresponding actual breakpoint position if an error alarm occurs after performing the table locking operation; and obtaining the first business table result after successfully executing the program to be tested.

[0008] According to an embodiment of this disclosure, the step of verifying the consistency between the results of the first business table and the results of the second business table to obtain the accounting reconciliation result includes: extracting each detailed calculation result from the results of the first business table and the results of the second business table respectively; verifying whether each detailed calculation result from the results of the first business table and the results of the second business table is consistent; and determining that the accounting reconciliation result is consistent if all detailed calculation results are consistent.

[0009] According to an embodiment of this disclosure, the step of verifying the consistency between the results of the first business table and the results of the second business table to obtain the accounting reconciliation result further includes: summing up each detailed calculation result in the results of the first business table and each detailed calculation result in the results of the second business table to obtain a first summary result and a second summary result; verifying whether the first summary result and the second summary result are consistent; and determining that the accounting reconciliation result is consistent if the first summary result and the second summary result are consistent.

[0010] According to embodiments of this disclosure, the method further includes: prioritizing the execution of a first processing logic; and ending the breakpoint re-release test when the first processing logic fails to execute, or when the first processing logic executes successfully but the breakpoint verification result fails.

[0011] A second aspect of this disclosure provides a breakpoint re-extraction testing apparatus, the apparatus comprising: an acquisition module, a first testing module, a first verification module, a second testing module, a second verification module, and a determination module, wherein the acquisition module is used to acquire a program to be tested and a business table; the first testing module is used to execute a first processing logic on the business table based on a preset breakpoint position to obtain a first business table result and an actual breakpoint position, the first processing logic including performing breakpoint re-extraction testing based on the preset breakpoint position during the execution of the program to be tested on the business table; the first verification module is used to verify the consistency between the preset breakpoint position and the actual breakpoint position to obtain a breakpoint verification result; the second testing module is used to execute a second processing logic on the business table through the program to be tested to obtain a second business table result, the second processing logic including executing the program to be tested on the business table; the second verification module is used to verify the consistency between the first business table result and the second business table result to obtain an accounting verification result; and the determination module is used to determine that the program to be tested passes the breakpoint re-extraction test if both the breakpoint verification result and the accounting verification result satisfy the consistency requirement.

[0012] A third aspect of this disclosure provides an electronic device comprising: one or more processors; and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors perform the breakpoint re-resume test method described above.

[0013] A fourth aspect of this disclosure also provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, cause the processor to perform the above-described breakpoint re-reserve test method.

[0014] A fifth aspect of this disclosure also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described breakpoint re-reserve test method. Attached Figure Description

[0015] The foregoing contents, as well as other objects, features, and advantages of this disclosure, will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0016] Figure 1 The diagram illustrates an application scenario of the breakpoint recovery test method, apparatus, device, medium, and program product according to embodiments of the present disclosure.

[0017] Figure 2 A flowchart illustrating a breakpoint re-retrieval test method according to an embodiment of the present disclosure is shown schematically.

[0018] Figure 3A flowchart illustrating another breakpoint re-retrieval test method according to an embodiment of the present disclosure is shown schematically.

[0019] Figure 4 A flowchart illustrating another breakpoint re-retrieval test method according to an embodiment of the present disclosure is shown schematically.

[0020] Figure 5 The diagram illustrates the entire process of a breakpoint re-retrieval test method according to an embodiment of the present disclosure.

[0021] Figure 6 A schematic block diagram of a breakpoint recovery test apparatus according to an embodiment of the present disclosure is shown.

[0022] Figure 7 A block diagram schematically illustrates an electronic device suitable for implementing a breakpoint re-retrieval test method according to an embodiment of the present disclosure. Detailed Implementation

[0023] The embodiments of the present disclosure will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the disclosure. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of the present disclosure for ease of explanation. However, it will be apparent that one or more embodiments may be practiced without these specific details. Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concepts of the present disclosure.

[0024] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. The terms “comprising,” “including,” etc., as used herein indicate the presence of the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0025] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.

[0026] When using expressions such as "at least one of A, B, and C", they should generally be interpreted in accordance with the meaning that is commonly understood by a person skilled in the art (e.g., "a system having at least one of A, B, and C" should include, but is not limited to, a system having A alone, a system having B alone, a system having C alone, a system having A and B, a system having A and C, a system having B and C, and / or a system having A, B, and C, etc.).

[0027] The following is a detailed description of the technical terms mentioned in the embodiments of this disclosure:

[0028] Breakpoint Reset: When a program uses database tables and data files to record the results of data processing, an exception may occur during the job due to environmental factors, data issues, or inherent defects. This exception will trigger the error reporting mechanism of the host batch application system, causing the running job or program to be interrupted and no longer running. In this case, it is necessary to reset the program to ensure its normal operation. It should be noted that a reset operation can be understood as a restart operation, a restart operation based on the breakpoint location.

[0029] Currently, the status quo of breakpoint re-resumption testing in batch systems is as follows: Breakpoint re-resumption trigger scenarios are complex, requiring targeted scenario testing based on the specific mechanisms implemented in the program. Furthermore, the information related to these mechanisms is at the code level, which adds difficulty to testing breakpoint re-resumption. Additionally, batch processing involves a large amount of bank accounting transactions. If a breakpoint is triggered and the program fails to complete the re-resumption function correctly, it poses a significant risk to the bank accounting system. The impact would be even greater on customer business scenarios. Therefore, the requirements for testing are high, and the accuracy of accounting verification during testing is also demanded. The breakpoint re-resumption testing process is quite cumbersome, often requiring the joint involvement of technical, business, and development personnel. It also necessitates comprehensive consideration of factors such as the selection of the testing environment, testing location, and test data. Therefore, the testing process is relatively long and consumes relatively high testing resources, posing a severe challenge to today's development model characterized by short testing cycles and rapid production deployment.

[0030] To address the technical problem of existing breakpoint retrieval testing struggling to balance accuracy and efficiency, embodiments of this disclosure provide a breakpoint retrieval testing method, including: acquiring the program to be tested and a business table;

[0031] Based on preset breakpoint positions, a first processing logic is executed on the business table to obtain a first business table result and an actual breakpoint position. The first processing logic includes performing breakpoint re-firing tests based on preset breakpoint positions during the execution of the test program on the business table; verifying the consistency between the preset breakpoint position and the actual breakpoint position to obtain a breakpoint verification result; executing a second processing logic on the business table through the test program to obtain a second business table result. The second processing logic includes executing the test program on the business table; verifying the consistency between the first business table result and the second business table result to obtain an accounting verification result; and determining that the test program passes the breakpoint re-firing test if both the breakpoint verification result and the accounting verification result are consistent.

[0032] In the embodiments of this disclosure, under the background of verifying and testing a large number of data tables by the program under test, the verification of accounting results is carried out simultaneously with the verification of program breakpoint re-emergence. This achieves accurate monitoring of breakpoint re-emergence of batch programs from both technical and business perspectives, effectively improving the accuracy and efficiency of breakpoint re-emergence testing. It effectively fills the gap in the field of host breakpoint re-emergence testing, providing an effective solution and testing model for host breakpoint re-emergence testing.

[0033] Figure 1 The diagram illustrates an application scenario of breakpoint re-retrieval testing according to an embodiment of the present disclosure.

[0034] like Figure 1 As shown, application scenario 100 according to this embodiment may include terminal devices 101, 102, and 103, network 104, and server 105. Network 104 is used as a medium to provide a communication link between terminal devices 101, 102, and 103 and server 105. Network 104 may include various connection types, such as wired or wireless communication links or fiber optic cables, etc.

[0035] Users can use terminal devices 101, 102, and 103 to interact with server 105 via network 104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 101, 102, and 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social media platform software, etc. (for example only).

[0036] Terminal devices 101, 102, and 103 can be various electronic devices with displays and web browsing capabilities, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0037] Server 105 can be a server that provides various services, such as a backend management server that supports websites browsed by users using terminal devices 101, 102, and 103 (for example only). The backend management server can analyze and process data such as received user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal devices.

[0038] It should be noted that the breakpoint re-extraction test method provided in this embodiment can generally be executed by server 105. Correspondingly, the breakpoint re-extraction test device provided in this embodiment can generally be located in server 105. The breakpoint re-extraction test method provided in this embodiment can also be executed by a server or server cluster that is different from server 105 and capable of communicating with terminal devices 101, 102, 103 and / or server 105. Correspondingly, the breakpoint re-extraction test device provided in this embodiment can also be located in a server or server cluster that is different from server 105 and capable of communicating with terminal devices 101, 102, 103 and / or server 105.

[0039] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0040] The following will be based on Figure 1 The described scene, through Figures 2-5 The breakpoint re-retrieval test method of the disclosed embodiments is described in detail.

[0041] Figure 2 A flowchart illustrating a breakpoint re-retrieval test method according to an embodiment of the present disclosure is shown schematically.

[0042] like Figure 2 As shown, the breakpoint re-release test in this embodiment includes operations S210 to S260, and this breakpoint re-release test method can be executed by server 105.

[0043] In operation S210, obtain the program to be tested and the business table.

[0044] According to embodiments of this disclosure, the acquisition of the program to be tested and the business table includes the following attributes: the program application, its English name, its Chinese name, whether it is customer-facing, its risk level, its region of use, its technical lead, its business product line, its business lead, its release date, and whether it has passed verification. The business table includes attributes such as its region code, transaction code, current system date, and timestamp. When selecting the program to be tested, globally unique programs can be found using these attributes, and the test status of the program can also be recorded. When calling the business table, globally unique business tables can be found by combining the region code, transaction code, current system date, and timestamp.

[0045] According to embodiments of this disclosure, the method for obtaining the program to be tested and the business tables includes: obtaining the program to be tested, which includes program logic; and obtaining the business tables involved in the program processing based on the decomposition of the program logic. Specifically, different programs target different businesses, and different businesses involve different business tables. This step establishes the relationship between the program to be tested and the business tables. Finding the business tables corresponding to the program for testing reduces the probability of errors.

[0046] It should be noted that the program under test can be a batch processing program for business operations with large data volumes and low timeliness requirements. Examples include interest calculation and adjustment, financial reconciliation, and reporting. These operations often involve massive amounts of detailed business data. By executing the corresponding program logic on this massive amount of detailed data, the desired business result is obtained. Batch processing ensures efficient processing of massive amounts of detailed data; however, the program itself often contains significant vulnerabilities that are difficult to detect using conventional testing methods, greatly increasing security risks after the program goes live. Since the program under test executes its own program logic for specific business operations, the business tables adapted to different programs under test vary. Generally, the program logic in the program under test maps to the actual business logic. By splitting the program logic, the mapped actual business logic is also split. The business logic usually contains the business tables required during its execution. Therefore, one or more corresponding business tables required by the program under test during business processing can be obtained.

[0047] In operation S220, the first processing logic is executed on the business table based on the preset breakpoint position to obtain the first business table result and the actual breakpoint position. The first processing logic includes performing breakpoint re-release test based on the preset breakpoint position during the execution of the test program on the business table.

[0048] It's important to note that among all the vulnerabilities in the tested program that can trigger interruptions, there is a special type: deadlock errors. For situations where deadlock errors occur, compatibility with existing host-based batch application systems needs to be considered during the design phase. The triggering principle of deadlock is as follows: when two concurrent applications lock data that each other needs, a deadlock condition is triggered; that is, both applications are waiting for the other application to release the lock, thus resulting in a deadlock. Therefore, to resolve this special vulnerability, appropriate technical measures are needed, and breakpoint re-preparation is an important one. Specifically, to ensure compatibility with the host batch system for this error scenario, the host batch application system calls a module with a breakpoint retrieval mechanism. When the program encounters the aforementioned deadlock, it returns error code 911, indicating a deadlock. The program does not actually interrupt; instead, it records the current breakpoint in the batch execution control table. After 30 seconds, the program will retrieve from the recorded breakpoint. This mechanism provides the program with three automatic retrieval opportunities, minimizing the need for manual intervention in such situations.

[0049] Specifically, the selection of the business tables can be done randomly, selecting any number of business tables for testing.

[0050] Figure 3 A flowchart illustrating another breakpoint re-retrieval test method according to an embodiment of the present disclosure is shown schematically.

[0051] like Figure 3 As shown, another breakpoint re-release test method in this embodiment corresponds to the preset breakpoint position and the actual breakpoint position in operation S220, that is, operation S220 includes operations S310 to S340, and this breakpoint re-release test method can be executed by server 105.

[0052] In operation S310, preset index information is obtained, which includes the mapping relationship between the business table and the database.

[0053] Specifically, the preset index information is automatically generated by the host's database in association with the business table.

[0054] In operation S320, based on preset index information, a table locking operation is performed at the preset breakpoint position of the business table through a preset breakpoint position.

[0055] Specifically, testers input specific values ​​for index conditions such as the test region. These index conditions include the attributes of the aforementioned business table. The location of the business table within the database is determined by these index conditions, thus enabling table locking operations. For example, based on a preset breakpoint, table locking operations can be performed on the corresponding portion of the business table using SQL table locking statements. It should be noted that SQL includes statements such as NOLOCK (no locking), HOLDLOCK (holding lock), UPDLOCK (modifying lock), TABLOCK (table lock), PAGLOCK (page lock), and TABLOCKX (exclusive table lock). The specific SQL table locking language can be selected according to the specific situation, which will not be elaborated upon here.

[0056] When operating S330, if an error alarm occurs after performing a table lock operation, record the actual breakpoint location.

[0057] In operation S340, after successfully executing the test program, the result of the first business table is obtained.

[0058] It should be noted that in the embodiments of this disclosure, a table locking operation is performed during the execution of program logic to simulate a breakpoint environment, and the first business table result is obtained after the breakpoint re-release test is completed. This integrates the execution side of the program under test and the breakpoint re-release side, which to some extent corresponds to the business table result and the actual breakpoint location, facilitating subsequent troubleshooting and analysis.

[0059] In operation S230, the consistency between the preset breakpoint position and the actual breakpoint position is checked to obtain the breakpoint check result.

[0060] Specifically, the preset breakpoint position is equivalent to a pre-defined breakpoint position, and the actual breakpoint position is equivalent to the actual breakpoint position, which is generally stored in a batch control table. When comparing the preset breakpoint position with the actual breakpoint position, the actual breakpoint position needs to be retrieved from the batch control table to complete the comparison.

[0061] In operation S240, the second processing logic is executed on the business table by the program to be tested to obtain the second business table result. The second processing logic includes executing the program to be tested on the business table.

[0062] Specifically, during breakpoint re-emergence testing, for the business table to be locked, both normal program logic execution and breakpoint re-emergence testing are required. For the business table to be verified, only normal program logic is executed. Therefore, the business table to be verified can be considered a control group of the business tables to be locked used in the breakpoint re-emergence test, used to complete the subsequent verification work. When a business table consistent with the business table to be locked is selected as the business table to be verified, the second business table result is obtained by executing program logic on the business table to be verified. When a business table inconsistent with the business table to be locked is selected as the business table to be verified, a preset second business table result is selected. The preset second business table result includes the accounting results already existing in the database required for testing. This second business table result directly corresponds to the business table. Therefore, to speed up the verification process, the pre-reserved second business table result in the database can be directly called.

[0063] In operation S250, the consistency between the results of the first business table and the results of the second business table is verified to obtain the accounting reconciliation result.

[0064] Figure 4 A flowchart illustrating another breakpoint re-retrieval test method according to an embodiment of the present disclosure is shown schematically.

[0065] like Figure 4 As shown, another breakpoint re-emergence test method in this embodiment corresponds to operation S250, that is, operation S250 includes operations S410 to S430, and this breakpoint re-emergence test method can be executed by server 105.

[0066] In operation S410, each detailed calculation result is extracted from the results of the first business table and the results of the second business table.

[0067] In operation S420, verify whether the detailed calculation results of each item in the results of the first business table and the second business table are consistent.

[0068] In operation S430, if all detailed calculation results are consistent, the accounting reconciliation result is determined to be consistent.

[0069] In the embodiments of this disclosure, a method of checking the business table item by item is adopted. This makes the check more accurate, and in the event of a failure, it can locate the breakpoint and resume the test to a greater extent, which is beneficial for troubleshooting and analysis.

[0070] According to an embodiment of this disclosure, the method for re-fractionating breakpoints further includes: summing up each detailed calculation result in the first business table result and each detailed calculation result in the second business table result to obtain a first summary result and a second summary result; verifying whether the first summary result and the second summary result are consistent; and determining that the accounting reconciliation result is consistent if the first summary result and the second summary result are consistent.

[0071] In embodiments of this disclosure, the method for verifying the business table also includes verifying the overall result. Verifying only the result improves the efficiency of the verification and is more suitable for large-volume data and / or breakpoint retrieval testing scenarios of the program under test.

[0072] It should be noted that there is no strict execution order restriction between the above operations S220 to S230 and operations S240 to S250. Operations S220 to S230 can be executed first, followed by operations S240 to S250, or operations S240 to S250 can be executed first, followed by operations S220 to S230. Of course, operations S220 to S230 and operations S240 to S250 can also be executed simultaneously.

[0073] According to embodiments of this disclosure, the method further includes: prioritizing the execution of a first processing logic; and ending the breakpoint re-release test when the first processing logic fails to execute, or when the first processing logic executes successfully but the breakpoint verification result fails.

[0074] Specifically, compared to the second processing logic, the first processing logic is executed first. If the first processing logic fails, or if the first processing logic succeeds but the breakpoint verification result fails, the current breakpoint re-test ends directly. That is, the second processing logic is not executed. This speeds up the entire breakpoint re-test process, especially when dealing with breakpoint re-testing of a large number of programs to be tested. In operation S260, if both the breakpoint verification result and the accounting verification result are consistent, the program to be tested is determined to have passed the breakpoint re-test.

[0075] In the embodiments of this disclosure, under the background of verifying and testing a large number of data tables by the program under test, the verification of accounting results is carried out simultaneously with the verification of program breakpoint re-emergence. This achieves accurate monitoring of breakpoint re-emergence of batch programs from both technical and business perspectives, effectively improving the accuracy and efficiency of breakpoint re-emergence testing. It effectively fills the gap in the field of host breakpoint re-emergence testing, providing an effective solution and testing model for host breakpoint re-emergence testing.

[0076] Figure 5A schematic diagram of the complete flowchart of the breakpoint re-retrieval test method according to an embodiment of the present disclosure is shown.

[0077] like Figure 5 The complete flowchart of the breakpoint re-retrieval test method in this embodiment includes:

[0078] In the S501 operation, select the program to be tested.

[0079] In operation S502, select the account to be locked.

[0080] In operation S503, the table is locked and the procedure is triggered.

[0081] In operation S504, record the interrupt information A for this table locking.

[0082] In the S505 operation, the actual interrupt information B recorded in the control table is obtained.

[0083] In operation S506, check if the interrupt information is consistent. If consistent, proceed to operation S507; otherwise, proceed to operation S514.

[0084] In operation S507, release the table and re-encode the procedure.

[0085] In operation S508, the accounting result Y is obtained.

[0086] In operation S509, select the accounts to be reconciled.

[0087] During S510 operation, the program is triggered.

[0088] In operation S511, the accounting result X is obtained.

[0089] In operation S512, verify whether the accounting results are consistent. If they are consistent, proceed to operation S513; otherwise, proceed to operation S514.

[0090] The verification was successful during the operation of S513.

[0091] Verification failed during S514 operation.

[0092] It should be noted that there is no temporal relationship between operations S509 to S511 and operations S502 to S512. They can be understood as two parallel tasks triggered by operation S501. Alternatively, it can be understood that operations S509 to S511 are triggered only when operation S506 is consistent.

[0093] Based on the above-described breakpoint recovery test method, this disclosure also provides a breakpoint recovery test apparatus. The following will be combined with... Figure 6 The device is described in detail.

[0094] Figure 6 A schematic block diagram of a breakpoint recovery test apparatus according to an embodiment of the present disclosure is shown.

[0095] like Figure 6 As shown, the breakpoint recovery test device 600 of this embodiment includes: an acquisition module 610, a first test module 620, a first verification module 630, a second test module 640, a second verification module 650, and a determination module 660.

[0096] The acquisition module 610 is used to acquire the program to be tested and the business table. In one embodiment, the acquisition module 610 can be used to perform the operation S210 described above, which will not be repeated here.

[0097] The first test module 620 is used to execute first processing logic on the business table based on a preset breakpoint position, to obtain a first business table result and the actual breakpoint position. The first processing logic includes performing breakpoint re-release testing based on the preset breakpoint position during the execution of the test program on the business table. In one embodiment, the first test module 620 can be used to execute the operation S220 described above, which will not be repeated here.

[0098] The first verification module 630 is used to verify the consistency between the preset breakpoint position and the actual breakpoint position to obtain a breakpoint verification result. In one embodiment, the first verification module 630 can be used to perform the operation S230 described above, which will not be repeated here.

[0099] The second test module 640 is used to execute a second processing logic on the business table through the program under test to obtain a second business table result. The second processing logic includes executing the program under test on the business table. In one embodiment, the second test module 640 can be used to execute the operation S240 described above, which will not be repeated here.

[0100] The second verification module 650 is used to verify the consistency between the results of the first business table and the results of the second business table to obtain the accounting verification result. In one embodiment, the second verification module 650 can be used to perform the operation S250 described above, which will not be repeated here.

[0101] The determination module 660 is used to determine whether the program under test passes the breakpoint re-test, provided that both the breakpoint verification result and the accounting verification result are consistent. In one embodiment, the determination module 660 can be used to execute the operation S260 described above, which will not be repeated here.

[0102] According to an embodiment of this disclosure, the acquisition module 610 is further configured to acquire a program to be tested, the program to be tested including program logic; and to obtain the business table involved in the program processing based on the decomposition of the program logic.

[0103] According to an embodiment of this disclosure, the first test module 620 includes an index acquisition unit, a table locking unit, an actual breakpoint acquisition unit, and a first business table result acquisition unit. The index acquisition unit is used to acquire preset index information, which includes the mapping relationship between the business table and the database. The table locking unit is used to perform a table locking operation on the business table at a preset breakpoint position based on the preset index information. The actual breakpoint acquisition unit is used to record the corresponding actual breakpoint position if an error alarm occurs after performing the table locking operation. The first business table result acquisition unit is used to obtain the first business table result after successfully executing the test program.

[0104] According to embodiments of this disclosure, any plurality of modules among the acquisition module 610, the first test module 620, the first verification module 630, the second test module 640, the second verification module 650, and the determination module 660 can be combined into one module, or any one of these modules can be split into multiple modules. Alternatively, at least part of the functionality of one or more of these modules can be combined with at least part of the functionality of other modules and implemented in one module. According to embodiments of this disclosure, at least one of the acquisition module 610, the first test module 620, the first verification module 630, the second test module 640, the second verification module 650, and the determination module 660 can be at least partially implemented as hardware circuitry, such as a field-programmable gate array (FPGA), a programmable logic array (PLA), a system-on-a-chip, a system-on-a-substrate, a system-on-package, an application-specific integrated circuit (ASIC), or implemented in hardware or firmware by any other reasonable means of integrating or packaging the circuitry, or implemented in any one of software, hardware, and firmware methods, or in a suitable combination of any of these methods. Alternatively, at least one of the acquisition module 610, the first test module 620, the first verification module 630, the second test module 640, the second verification module 650, and the determination module 660 can be at least partially implemented as a computer program module, which can perform corresponding functions when the computer program module is run.

[0105] Figure 7A block diagram schematically illustrates an electronic device suitable for implementing a breakpoint re-retrieval test method according to an embodiment of the present disclosure.

[0106] like Figure 7 As shown, an electronic device 700 according to an embodiment of the present disclosure includes a processor 701, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 702 or a program loaded from a storage portion 705 into a random access memory (RAM) 703. The processor 701 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 701 may also include onboard memory for caching purposes. The processor 701 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0107] RAM 703 stores various programs and data required for the operation of electronic device 700. Processor 701, ROM 702, and RAM 703 are interconnected via bus 704. Processor 701 performs various operations of the method flow according to embodiments of the present disclosure by executing programs in ROM 702 and / or RAM 703. It should be noted that the programs may also be stored in one or more memories other than ROM 702 and RAM 703. Processor 701 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in said one or more memories.

[0108] According to embodiments of this disclosure, the electronic device 700 may further include an input / output (I / O) interface 705, which is also connected to a bus 704. The electronic device 700 may also include one or more of the following components connected to the I / O interface 705: an input section 706 including a keyboard, mouse, etc.; an output section 707 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 708 including a hard disk, etc.; and a communication section 709 including a network interface card such as a LAN card, modem, etc. The communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the I / O interface 705 as needed. A removable medium 711, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 710 as needed so that computer programs read from it can be installed into the storage section 708 as needed.

[0109] This disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs that, when executed, implement the method according to the embodiments of this disclosure.

[0110] According to embodiments of this disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, such as, but not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this disclosure, the computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of this disclosure, the computer-readable storage medium may include ROM 702 and / or RAM 703 and / or one or more memories other than ROM 702 and RAM 703 described above.

[0111] Embodiments of this disclosure also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowchart. When the computer program product is run on a computer system, the program code is used to cause the computer system to implement the item recommendation method provided in the embodiments of this disclosure.

[0112] When the computer program is executed by the processor 701, it performs the functions defined in the system / apparatus of this disclosure embodiments. According to embodiments of this disclosure, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0113] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and may be downloaded and installed via the communication section 709, and / or installed from a removable medium 711. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0114] In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 709, and / or installed from the removable medium 711. When the computer program is executed by the processor 701, it performs the functions defined in the system of this disclosure embodiment. According to embodiments of this disclosure, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0115] According to embodiments of this disclosure, program code for executing the computer programs provided in embodiments of this disclosure can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, Python, "C", or similar programming languages. The program code can execute entirely on the user's computing device, partially on the user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0116] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0117] Those skilled in the art will understand that the features described in the various embodiments and / or claims of this disclosure can be combined or combined in various ways, even if such combinations or combinations are not explicitly described in this disclosure. In particular, the features described in the various embodiments and / or claims of this disclosure can be combined or combined in various ways without departing from the spirit and teachings of this disclosure. All such combinations and / or combinations fall within the scope of this disclosure.

[0118] The embodiments of this disclosure have been described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of this disclosure. Although various embodiments have been described above, this does not mean that the measures in the various embodiments cannot be used advantageously in combination. The scope of this disclosure is defined by the appended claims and their equivalents. Various substitutions and modifications can be made by those skilled in the art without departing from the scope of this disclosure, and all such substitutions and modifications should fall within the scope of this disclosure.

Claims

1. A breakpoint recovery test method, characterized in that, include: Obtain the program to be tested and the business table; The first processing logic is executed on the business table based on the preset breakpoint position to obtain the first business table result and the actual breakpoint position. The first processing logic includes performing breakpoint re-release test based on the preset breakpoint position during the execution of the test program on the business table. The first processing logic is executed on the business table based on the preset breakpoint position, which includes simulating the breakpoint scenario through table locking operation to trigger the breakpoint re-release mechanism of the test program. Verify the consistency between the preset breakpoint position and the actual breakpoint position to obtain the breakpoint verification result; The test program executes a second processing logic on the business table to obtain a second business table result. The second processing logic includes executing the test program on the business table. Verify the consistency between the results of the first business table and the results of the second business table to obtain the accounting reconciliation results; and If both the breakpoint verification result and the accounting verification result are consistent, the program under test is determined to have passed the breakpoint re-release test.

2. The method according to claim 1, characterized in that, The process of obtaining the program to be tested and the business table includes: Obtain the program to be tested, which includes program logic; The business tables involved in the program processing are obtained by breaking down the program logic.

3. The method according to claim 1, characterized in that, The step of executing the first processing logic on the business table based on the preset breakpoint position to obtain the first business table result and the actual breakpoint position includes: Obtain preset index information, which includes the mapping relationship between the business table and the database; Based on preset index information, a table locking operation is performed at the preset breakpoint position of the business table. If an error alert occurs after performing a table locking operation, record the actual breakpoint location; and After successfully executing the test program, the results of the first business table are obtained.

4. The method according to claim 1, characterized in that, The process of verifying the consistency between the results of the first business table and the results of the second business table to obtain the accounting reconciliation results includes: Extract the detailed calculation results of each item from the results of the first business table and the results of the second business table respectively; Verify that the detailed calculation results of each item in the results of the first business table and the second business table are consistent; If all detailed calculation results are consistent, the accounting reconciliation results are deemed to be consistent.

5. The method according to claim 4, characterized in that, The step of verifying the consistency between the results of the first business table and the results of the second business table to obtain the accounting reconciliation results also includes: The first summary result and the second summary result are obtained by summing the detailed calculation results of each item in the first business table result and the detailed calculation results of each item in the second business table result respectively. Verify that the first summary result and the second summary result are consistent; If the first summary result and the second summary result are consistent, the accounting reconciliation result is determined to be consistent.

6. The method according to claim 1, characterized in that, Also includes: The first processing logic will be executed first. If the first processing logic fails to execute, or If the first processing logic executes successfully but the breakpoint verification result fails, the breakpoint re-release test ends.

7. A breakpoint recovery test device, characterized in that, The device includes: an acquisition module, a first testing module, a first verification module, a second testing module, a second verification module, and a judgment module, wherein the acquisition module is used to acquire the program to be tested and the business table; The first test module is used to execute a first processing logic on the business table based on a preset breakpoint position to obtain a first business table result and the actual breakpoint position. The first processing logic includes performing a breakpoint re-release test based on the preset breakpoint position during the execution of the program to be tested on the business table. The first processing logic is used to execute the first processing logic on the business table based on the preset breakpoint position, which includes simulating a breakpoint scenario through a table locking operation to trigger the breakpoint re-release mechanism of the program to be tested. The first verification module is used to verify the consistency between the preset breakpoint position and the actual breakpoint position to obtain the breakpoint verification result; The second test module is used to execute a second processing logic on the business table through the program under test to obtain a second business table result. The second processing logic includes executing the program under test on the business table. The second verification module is used to verify the consistency between the results of the first business table and the results of the second business table, and to obtain the accounting verification result; and The determination module is used to determine whether the program under test passes the breakpoint re-release test, provided that both the breakpoint verification result and the accounting verification result are consistent.

8. An electronic device, comprising: One or more processors; Storage device for storing one or more programs. Wherein, when the one or more programs are executed by the one or more processors, the one or more processors perform the method according to any one of claims 1 to 6.

9. A computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to perform the method according to any one of claims 1 to 6.

10. A computer program product comprising a computer program that, when executed by a processor, implements the method according to any one of claims 1 to 6.

Images