A service continuity test method and system, electronic equipment, and storage medium

Abstract

The application provides a business continuity test method and system, an electronic device and a storage medium. The method comprises the following steps: if a test request of a target test scenario of a system under test initiated by a target person is received, a continuous pressure test case corresponding to the target test scenario is executed to simulate, by a simulator, that a related system of the system under test continuously sends a request to the system under test and / or uploads a file under the target test scenario; after the system under test is stably operated, the system under test is switched from a production end to a backup end or from a multi-center to a specified center; after the system under test is successfully switched and stably operated, the system under test is switched from the backup end back to the production end or from the specified center back to the multi-center; after the system under test is successfully switched back and stably operated, a test report of the system under test is generated based on monitored test data; whether the service processing capacity of the system under test before and after the switching meets the requirements is judged based on the test report; and if yes, information that the test is successful is fed back.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a business continuity testing method and system, electronic device, and storage medium. Background Technology

[0002] With the rapid development of fintech strategies, commercial banks are incorporating business continuity management into their comprehensive risk management systems. Furthermore, the construction of business continuity for commercial bank information systems is a crucial component of building fundamental assurance capabilities. Therefore, before formal deployment, how to quickly and effectively verify their ability to respond to disasters and ensure business continuity has become an urgent issue to be addressed.

[0003] In existing technologies, functional testing is mainly used to verify business continuity. This usually requires setting up a test environment for multiple systems across the entire transaction line from end to end. Then, a certain number of functional cases of important business operations are selected. Next, relevant business personnel are organized to execute the functional cases through the interface. Finally, based on their work experience and the execution results of the functional cases, people judge whether the business continuity of the systems before and after meets the expected requirements.

[0004] However, since the functional test cases are executed manually through the interface, the manual input of data for interfaces with many input elements is time-consuming and prone to errors. Furthermore, due to the limitations and constraints of the manual test case execution method, the functional testing method can only determine whether the system can correctly handle business after the switch, but cannot determine the recovery level of the system's processing capacity after the switch. Summary of the Invention

[0005] In view of the shortcomings of the prior art, this application provides a business continuity testing method and system, electronic device and storage medium to solve the problem that the prior art cannot determine the recovery level of the system processing capacity after switching.

[0006] To achieve the above objectives, this application provides the following technical solution:

[0007] The first aspect of this application provides a business continuity testing method applied to a non-functional testing system. The non-functional testing system includes at least a business continuity management platform, a non-functional automated testing platform, a simulator, and a verification standard device. The business continuity testing method includes:

[0008] When the non-functional automated testing platform receives a test request for the target test scenario of the system under test initiated by the target personnel, it executes the continuous stress test case corresponding to the target test scenario, so as to simulate the related systems of the system under test continuously sending requests to the system under test, and / or uploading files to the system under test under the target test scenario through the simulator.

[0009] After the system under test is running stably, the business continuity management platform will switch the system under test from the production end to the disaster recovery end, or switch the system under test from multiple centers to a designated center.

[0010] After the system under test is switched from the production end to the disaster recovery end, or from the multi-center to the designated center and is running stably, the business continuity management platform will switch the system under test back from the disaster recovery end to the production end, or switch the system under test back from the designated center to the multi-center.

[0011] After the system under test switches from the disaster recovery terminal back to the production terminal, or from the designated center back to the multi-center and runs stably, the non-functional automated testing platform and the business continuity management platform respectively generate a test report for the system under test based on the test data monitored during the testing process.

[0012] The verification standard device, based on the test report of the system under test, determines whether the service processing capability of the system under test before and after the switchover meets the business continuity requirements.

[0013] If the verification standard device determines that the service processing capability of the system under test meets the business continuity requirements before and after the switchover, it will provide feedback that the business continuity test of the system under test is successful.

[0014] Optionally, in the above-described business continuity testing method, the test report of the system under test includes at least a handover plan execution report and a non-functional test report. The step of determining whether the service processing capability of the system under test before and after the handover meets the business continuity requirements based on the test report includes:

[0015] Extract the service recovery parameters from the non-functional test report and the effective indicators from the switching scheme execution report;

[0016] Each of the service recovery parameters of the system under test after the switchover is determined to meet the preset parameter requirements, and each of the effective indicators of the system under test after the switchover is determined to meet the validity requirements. If it is determined that each of the service parameters of the system under test before and after the switchover meets the preset parameter requirements, and if it is determined that each of the effective indicators of the system under test before and after the switchover meets the validity requirements, then it is determined that the service processing capability of the system under test before and after the switchover meets the business continuity requirements.

[0017] Optionally, the above-mentioned business continuity testing methods also include:

[0018] The non-functional automated testing platform monitors the various service data of the system under test in real time before and after the switchover.

[0019] When the non-functional automated testing platform detects that any of the service data does not meet the expected requirements, it feeds back the service data to the front end.

[0020] Optionally, in the above-described business continuity testing method, after the verification standard device determines whether the service processing capability of the system under test meets the business continuity requirements before and after the switchover based on the test report of the system under test, it further includes:

[0021] If the verification standard device determines that the service processing capability of the system under test does not meet the business continuity requirements before and after the switchover, it will provide feedback that the business continuity test of the system under test has failed.

[0022] A second aspect of this application provides a business continuity testing system, wherein the non-functional testing system includes at least a business continuity management platform, a non-functional automated testing platform, a simulator, and a verification standard device, comprising:

[0023] The non-functional automated testing platform is used to execute continuous stress test cases corresponding to the target test scenario when it receives a test request for the target test scenario of the system under test initiated by the target personnel. This is to simulate, through a simulator, the associated systems of the system under test continuously sending requests to the system under test, and / or uploading files, under the target test scenario. The platform is also used to generate a test report for the system under test based on the test data monitored during the test process.

[0024] The business continuity management platform is used to switch the system under test from the production end to the disaster recovery end or from the multi-center to the designated center after the system under test is running stably; and to switch the system under test from the disaster recovery end back to the production end or from the designated center back to the multi-center after the system under test has been switched from the production end to the disaster recovery end or from the multi-center to the designated center and is running stably. It is also used to generate a test report of the system under test based on the test data monitored during the test.

[0025] The verification standard device is used to determine, based on the test report of the system under test, whether the service processing capability of the system under test before and after the switch meets the business continuity requirements, and to provide feedback information indicating that the business continuity test of the system under test is successful if it is determined that the service processing capability of the system under test before and after the switch meets the business continuity requirements.

[0026] Optionally, in the aforementioned business continuity testing system, when the verification standard device executes the test report based on the system under test to determine whether the service processing capability of the system under test before and after the switchover meets the business continuity requirements, it is used for:

[0027] Extract the service recovery parameters from the non-functional test report and the effective indicators from the switching scheme execution report;

[0028] Each of the service recovery parameters of the system under test after the switchover is determined to meet the preset parameter requirements, and each of the effective indicators of the system under test after the switchover is determined to meet the validity requirements. If it is determined that each of the service parameters of the system under test before and after the switchover meets the preset parameter requirements, and if it is determined that each of the effective indicators of the system under test before and after the switchover meets the validity requirements, then it is determined that the service processing capability of the system under test before and after the switchover meets the business continuity requirements.

[0029] Optionally, the business continuity testing system described above is also used for:

[0030] The non-functional automated testing platform monitors the various service data of the system under test in real time before and after the switchover.

[0031] When the non-functional automated testing platform detects that any of the service data does not meet the expected requirements, it feeds back the service data to the front end.

[0032] Optionally, in the aforementioned business continuity testing system, after the verification standard device executes the test report based on the system under test and determines whether the service processing capability of the system under test meets the business continuity requirements before and after the switchover, it is further used to:

[0033] If the verification standard device determines that the service processing capability of the system under test does not meet the business continuity requirements before and after the switchover, it will provide feedback that the business continuity test of the system under test has failed.

[0034] A third aspect of this application provides an electronic device, comprising:

[0035] Memory and processor;

[0036] The memory is used to store programs;

[0037] The processor is used to execute the program, which, when executed, is specifically used to implement a business continuity testing method as described in any of the above.

[0038] A fourth aspect of this application provides a computer storage medium for storing a computer program, which, when executed, implements a business continuity testing method as described in any of the preceding claims.

[0039] This application provides a business continuity testing method. When a non-functional automated testing platform receives a test request from a target user for a target test scenario of the system under test (SUT), it executes a continuous stress test case corresponding to the target test scenario. This simulates, through a simulator, the continuous sending of requests and / or file uploads from related systems to the SUT under the target test scenario. After the SUT is running stably, the business continuity management platform switches the SUT from the production environment to a disaster recovery environment or from multiple data centers to a designated data center. The business continuity management platform then switches the SUT from the production environment to the disaster recovery environment or from multiple data centers to the designated data center and maintains stable operation. Afterwards, the system under test is switched from the disaster recovery site back to the production site or from the designated center back to multiple centers. Then, after the system under test has been switched back to the production site or from the designated center back to multiple centers and is running stably, the non-functional automated testing platform and the business continuity management platform generate test reports for the system under test based on the test data monitored during the testing process. Finally, the verification standard device uses the test reports of the system under test to determine whether the service processing capability of the system under test before and after the switch meets the business continuity requirements. If the verification standard device determines that the service processing capability of the system under test before and after the switch meets the business continuity requirements, it provides feedback that the business continuity test of the system under test is successful. This solves the problem that it is impossible to judge the recovery level of the system's processing capability after the switch manually, while reducing labor costs and greatly improving the efficiency of business continuity testing. Attached Figure Description

[0040] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0041] Figure 1 A schematic diagram of the structure of a business continuity testing system provided in another embodiment of this application;

[0042] Figure 2 A flowchart illustrating a business continuity testing method provided in this application embodiment;

[0043] Figure 3 This is a schematic diagram of the structure of an electronic device provided in another embodiment of this application. Detailed Implementation

[0044] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0045] In this application, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0046] This application provides a business continuity testing method to address the problem that existing technologies cannot determine the recovery level of system processing capacity after a switchover. Therefore, to implement the business continuity testing method provided in this application, specifically, embodiments of this application provide a non-functional testing system, such as... Figure 1 As shown, it includes: a non-functional automated testing platform 101, a simulator 102, a business continuity management platform 103, and a verification standard device 104.

[0047] The non-functional automated testing platform 101 is used to execute continuous stress test cases corresponding to the target test scenario when it receives a test request for the target test scenario of the system under test initiated by the target personnel. It simulates the related systems of the system under test continuously sending requests to the system under test and / or uploading files to the system under test under the target test scenario through the simulator 102, and generates a test report of the system under test based on the test data monitored during the test.

[0048] It's important to note that each system under test (SUT) has its corresponding test lab. From this lab, one can obtain information about the SUT's test scenarios, standard test cases, test execution, test data, script information, switchover plans, test reports, and which relevant data needs to be monitored during execution. Therefore, when performing business continuity testing on the SUT, one can use the SUT's test lab as a reference to determine whether the non-functional testing systems are correctly executing the relevant tests. Thus, the test lab is the primary operational space for business continuity non-functional testing. It should also be noted that when testers investigate and analyze the test scope and switchover plan for the system under test, they generally select typical business scenarios during peak business hours. In addition to covering the top 80% of transactions by volume, they should also supplement with transactions with attachments (verifying mirror storage switchover), maintenance transactions (verifying database switchover steps, changes in database status from read-only to read-write, and switching of data synchronization direction), and other supplementary transactions (not top transactions but requiring supplementary coverage of all deployment units involved in business continuity construction). Batch processing scenarios should include typical business batches as well as file transfer batch processing (verifying file transfer start / stop steps in the switchover plan). Therefore, the selection of test scenarios needs to follow two main principles: 1. Does it cover every process step in the switchover plan? 2. Does it cover all deployment units involved in the business continuity construction of the system under test?

[0049] Due to the varying scenarios and business continuity assurance solutions involved in failover, the standard non-functional test case set includes planned multi-active failover cases, unplanned multi-active failover cases, planned disaster recovery failover cases, and unplanned disaster recovery failover cases. The simulation of unplanned failures requires consideration of the system characteristics and the impact of the failover plan on different failure types. This necessitates simulating multiple failure types, such as system crashes, network outages, and service process anomalies. If the impacts differ, multiple unplanned test cases with different failure types need to be designed for verification.

[0050] It should also be noted that when testers apply for testing resources, the number of servers in the production and testing environments should be reduced proportionally, and their operating systems, middleware, and software versions should be consistent with the production environment. It is also necessary to ensure that the deployment region of the testing resources simulates the physical location of the production and disaster recovery ends, whether they are in the same city or different locations. Application servers and database servers on the same side (e.g., the production end) should avoid being deployed in different physical regions to simulate real-world production conditions as much as possible. If the limited testing resources prevent meeting the needs of different cities, and there is data and file synchronization between the production and disaster recovery ends, network latency techniques can be manually set to simulate the needs of different regions.

[0051] It should also be noted that when simulating the continuous sending of requests and / or file uploads from related systems of the system under test to the system under test in the target test scenario using simulator 102, the simulator can be divided into server-side and client-side simulators according to different functional usage scenarios. The server-side simulator is used to simulate the business-related systems of the system under test, and upstream or downstream systems for file transfer. By using simulators and message configuration technology to achieve the function of setting up numerous related systems of the system under test at once, the resource requirements for the test environment of related systems and the manpower requirements for version installation and deployment can be greatly reduced. At the same time, since the simulator does not need to perform real business logic processing (such as business rule verification), it decouples the strong consistency requirements of related systems for test data. Testers only need to focus on the correctness of request and response information configuration, allowing testers to focus more on the data logic of the system under test itself when preparing test data, while the data logic of related systems is shielded by the simulator. Here, related systems can refer to the common component platform, mainly including security components, file transfer components, service directory components, batch job configuration and scheduling components, DNS, network firewalls, image storage, etc. The batch job configuration and scheduling component primarily serves the configuration and scheduling of batch jobs on the system under test. The network firewall controls the opening and closing of the network and firewall. Under normal circumstances, for security reasons, network access to the disaster recovery server is not enabled. Network access to the disaster recovery server is only enabled when the production server switches to the disaster recovery server to ensure successful server registration.

[0052] The client simulator includes a service discovery simulator and a file transfer simulator. These two simulators are typically used as plugins in load testing tools, usually within load-generating scripts. The system under test normally registers the production server in the service directory. During a switchover, the production server is deregistered, and a disaster recovery server is registered. The service discovery simulator automatically retrieves the service address of the system under test from the service directory and requests the service from that address via a script. This allows for continuous load testing of the same scenario using the same script, simulating the seamless and transparent nature of the production service address for users. The file transfer simulator also retrieves the file transfer service address from the service directory and then uploads or downloads files to the system under test. The principle behind obtaining the file transfer service address is similar to that of the service discovery simulator; the difference is that the service discovery simulator is used for online transactions, while the file transfer simulator is used for file transfers.

[0053] It should be noted that when the non-functional automated testing platform receives a test request for the target test scenario of the system under test initiated by the target personnel, before executing the continuous stress test cases corresponding to the target test scenario, the specific target personnel will pre-write the stress test script for the target test scenario of the system under test, and then execute the stress test script through the non-functional automated testing platform to initiate the execution of the target test scenario to the system under test.

[0054] It should also be noted that the non-functional automated testing platform can monitor the execution status of stress test scenarios and the server resource usage of the system under test in real time. Therefore, when the non-functional automated testing platform detects that the continuous stress test cases corresponding to the target test scenario have been completed, it will automatically generate a test report of the system under test based on the test data monitored during the test. This effectively solves the problem of saving the manpower cost required to execute test cases and eliminates the dilemma of having to re-execute test cases when there are errors in the complex interface elements.

[0055] Optionally, during the execution of test cases, the non-functional automated testing platform can also monitor the execution status of service data at different stages of the system under test throughout the entire switchover process in real time. This allows for timely detection of any anomalies in the service data of the system under test during the switchover process. Therefore, the non-functional automated testing platform is also used for:

[0056] It monitors the service data of the system under test in real time before and after the switch, and provides feedback to the front end when any service data is found to be unsatisfactory.

[0057] Specifically, when the non-functional automated testing platform monitors the service data of the system under test in real time before and after the switchover, it can specifically monitor the execution status of each service data of the system under test before, during, and after the switchover, such as TPS, response time, transaction volume, transaction success and failure rate, as well as the server resource usage of each deployment unit. It can also observe the execution status of batch jobs processed by the system under test through the batch processing scheduling platform, and monitor the registration status of the system under test in the service directory, domain name switching status, batch processing registration status, service recovery level and duration, data loss duration, etc.

[0058] The business continuity management platform 103 is used to switch the system under test from the production end to the disaster recovery end or from multiple centers to a designated center after the system under test is running stably. It is also used to switch the system under test back from the disaster recovery end to the production end or from the designated center to the multiple centers after the system under test has been switched from the production end to the disaster recovery end or from multiple centers to the designated center and is running stably. It is also used to generate a test report for the system under test based on the test data monitored during the testing process.

[0059] It's important to note that the Business Continuity Management Platform is a management system for business continuity construction, capable of configuring switchover scheme templates and instances for different types of systems. Therefore, during test case execution, the platform can perform one-click forward or backward switching operations on a specific banking system. Specifically, after the tested system is running stably, the platform switches it from the production environment to the disaster recovery environment or from multiple data centers to a designated data center. Conversely, after the tested system has been switched from the production environment to the disaster recovery environment or from multiple data centers to the designated data center and is running stably, the platform switches it back from the disaster recovery environment to the production environment or from the designated data center back to the multiple data centers. Furthermore, it can simultaneously monitor the execution status of each process step during the switchover process. Finally, based on the test data monitored during the switchover, it automatically generates a switchover report, which can also be downloaded.

[0060] It should also be noted that the switching report of the business continuity management platform shows the execution status of each switching step as "execution successful". For systems that are required to support one-click switching, the execution status of each switching step should be "automatically executed successfully". Steps that are executed successfully but require manual operation or steps that fail and are skipped by the user are not allowed.

[0061] The verification standard device 104 is used to determine, based on the test report of the system under test, whether the service processing capability of the system under test before and after the switch meets the business continuity requirements, and to provide feedback on the successful business continuity test of the system under test if it is determined that the service processing capability of the system under test before and after the switch meets the business continuity requirements.

[0062] Optionally, in another embodiment of this application, the test report of the system under test may include a handover plan execution report and a non-functional test report. Therefore, the verification standard device 104 is used to determine, based on the test report of the system under test, whether the service processing capability of the system under test before and after the handover meets the business continuity requirements. A specific implementation of this method involves the following steps:

[0063] The verification standard device is used to extract various service recovery parameters from the non-functional test report and various valid indicators from the switchover execution report. It is also used to determine whether all service recovery parameters of the tested system after the switchover meet the preset parameter requirements, and whether all valid indicators of the tested system after the switchover meet the validity requirements. Furthermore, if it is determined that all service parameters of the tested system before and after the switchover meet the preset parameter requirements, and if it is determined that all valid indicators of the tested system before and after the switchover meet the validity requirements, then it is determined that the service processing capability of the tested system before and after the switchover meets the business continuity requirements.

[0064] It should be noted that if any data in the non-functional test report or the switchover execution report fails to meet the system's set requirements, it indicates that the service processing capacity of the tested system before and after the switchover does not meet the business continuity requirements. Continuous stress testing is then required until the service processing capacity of the tested system before and after the switchover meets the business continuity requirements. The service recovery parameters in the non-functional test report can include service processing capacity recovery level (%), service recovery time target, data recovery point-in-time target, batch processing time window, batch processing data volume, batch processing rerun or continuation effectiveness, and data recovery efficiency. Specifically, the service processing capacity recovery level (%) is the percentage of system processing capacity restored to before the switchover or failure. The required percentage of recovery level varies depending on the business level of the system. For example, for basic banking business systems, the service processing capacity recovery level requirement is 100%. The service recovery time target (RTO) is the time consumed from business interruption to system recovery to the target level. This does not include disaster declaration time or decision-making time, but includes the switchover operation time and the recovery time after the switchover is completed. Generally, technical recovery indicators are higher than the recovery requirements for each business level. The Service Recovery Time Objective (RTO) is calculated as follows: RTO = MAX(Switchover Operation End Time, Transaction Recovery Time) - Switchover Operation Start Time. The Data Recovery Point Objective (RPO) measures the amount of data that can be lost during business recovery, representing the time from the historical point in time to the point of disaster after a system disaster. RPO can be verified through a combination of business and technical methods. Alternatively, RPO can be checked from the application's business perspective: Select a transaction with newly added database records (such as an inbound transaction) and include it in the test scenario. Statistically analyze the total transaction volume and successful transaction volume of this transaction throughout the entire test scenario, and check the difference in data volume between the number of records in the database and the number of successful transactions. The business data recovery point objective is calculated as follows: RPO = (Successful Transaction Volume - Number of Records in Database) / TPS. For example, if the total transaction volume is 100,000, with 90,000 successful transactions, and the database records checked are 89,000 (expected 90,000), the TPS for this transaction is 10. The difference is 1,000 transactions / 10 TPS = 100 seconds. Batch processing includes three metrics: batch processing time window, batch processing data volume, and the effectiveness of batch processing reruns or continuations. The time window and data volume are used to compare batch processing efficiency before and after the switchover. Data recovery efficiency: the efficiency of data recovery to match the faulty node environment after fault recovery (data volume / time window).

[0065] The effective indicators in the switchover execution report can include the effectiveness of multi-active switchover, disaster recovery switchover, and one-click switchover. It should be noted that if transactions continue to report errors during the switchover process, and the reasons for failure are all related to the switchover, the verification standard device needs to further verify whether the effective indicators of the tested system meet the requirements after the switchover. Among them, multi-active switchover effectiveness verifies whether multi-active switchover is effective, disaster recovery switchover effectiveness verifies whether disaster recovery switchover is effective, and one-click switchover effectiveness enables one-click switchover on the business continuity management platform to determine whether the service processing capacity of the tested system also fails to meet the system's set requirements during the switchover process.

[0066] Optionally, in the application embodiment, after the verification standard device 104 determines whether the service processing capability of the system under test meets the business continuity requirements before and after the switchover based on the test report of the system under test, it is further used for:

[0067] If it is determined that the service processing capacity of the system under test does not meet the business continuity requirements before and after the switchover, then feedback will be provided that the business continuity test of the system under test has failed.

[0068] It should be noted that when the service processing capacity of the system under test does not meet the business continuity requirements before and after the switchover, the test failure information of the system under test needs to be promptly reported to the front end so that the testers can check and verify it, find the cause of the failure, and prevent the same problem from occurring in the next business continuity test, thereby effectively improving the efficiency of business continuity testing.

[0069] This application provides a business continuity testing system. Through a non-functional automated testing platform, it executes continuous stress test cases corresponding to the target test scenario when it receives a test request for the system under test (SUT) initiated by target personnel. This simulates, via a simulator, the continuous sending of requests and / or file uploads from related systems to the SUT under the target test scenario. The system also generates a test report for the SUT based on test data monitored during the testing process. A business continuity management platform is used to switch the SUT from the production environment to a disaster recovery environment or from multiple data centers to a designated data center after the SUT is running stably. Furthermore, after the SUT has been switched from the production environment to the disaster recovery environment or from multiple data centers to a designated data center and is running stably, it switches the SUT back from the disaster recovery environment to the production environment or from the designated data center back to multiple data centers. It also generates a test report for the SUT based on test data monitored during the testing process. The verification standard device is used to determine, based on the test report of the system under test, whether the service processing capacity of the system under test before and after the switchover meets the business continuity requirements. If the test results indicate that the service processing capacity of the system under test before and after the switchover meets the business continuity requirements, it provides feedback indicating that the business continuity test of the system under test has been successful. This eliminates the need to deal with the tedious process of re-executing test cases due to errors in the cumbersome input of interface elements. The non-functional testing system can automatically generate execution reports and accurately determine the recovery level of the system's processing capacity after the switchover, effectively ensuring the efficiency of business continuity testing.

[0070] Based on the aforementioned non-functional testing system, this application provides a business continuity testing method, such as... Figure 2 As shown, the specific steps include:

[0071] S201. When the non-functional automated testing platform receives a test request for the target test scenario of the system under test initiated by the target personnel, it executes the continuous stress test case corresponding to the target test scenario. This is done by simulating the related systems of the system under test continuously sending requests to the system under test and / or uploading files to the system under test in the target test scenario through a simulator.

[0072] S202. After the tested system is running stably, the business continuity management platform will switch the tested system from the production end to the disaster recovery end, or switch the tested system from multiple centers to a designated center.

[0073] S203. After the tested system is switched from the production end to the disaster recovery end or from multiple centers to a designated center and is running stably, the business continuity management platform will switch the tested system back from the disaster recovery end to the production end or from the designated center back to multiple centers.

[0074] After the tested system switches from the disaster recovery terminal back to the production terminal or from a designated center back to multiple centers and operates stably, the S204, non-functional automated testing platform, and business continuity management platform generate test reports for the tested system based on the test data monitored during the testing process.

[0075] S205. The verification standard device, based on the test report of the system under test, determines whether the service processing capability of the system under test before and after the switchover meets the business continuity requirements.

[0076] It should be noted that if the verification standard device determines that the service processing capability of the tested system before and after the switch meets the business continuity requirements, then step S206 is executed.

[0077] S206. The verification standard device provides feedback on the successful business continuity test of the tested system.

[0078] It should be noted that the specific working process of the above steps in the embodiments of this application can be referred to the non-functional automated test platform 101, business continuity management platform 102, simulator 103, and inspection standard device 104 in the above system embodiments, and will not be repeated here.

[0079] Optionally, in another embodiment of this application, a business continuity testing method includes a test report for the system under test that includes at least a handover plan execution report and a non-functional test report. Based on the test report, the method determines whether the service processing capability of the system under test before and after the handover meets the business continuity requirements, including:

[0080] Extract the service recovery parameters from the non-functional test report and the effective indicators from the switchover plan execution report.

[0081] Determine whether the recovery parameters of each service in the tested system after the switchover meet the preset parameter requirements, and whether each effective indicator of the tested system after the switchover meets the validity requirements.

[0082] If it is determined that all service parameters of the tested system before and after the switch meet the preset parameter requirements, and if it is determined that all effective indicators of the tested system before and after the switch meet the validity requirements, then it is determined that the service processing capability of the tested system before and after the switch meets the business continuity requirements.

[0083] It should be noted that the specific working process of each step provided in the above embodiments of this application can be referred to the corresponding inspection standard device in the above system embodiments, and will not be repeated here.

[0084] Optionally, another embodiment of this application provides a business continuity testing method that further includes:

[0085] The non-functional automated testing platform monitors the service data of the system under test in real time before and after the switchover.

[0086] When the non-functional automated testing platform detects that any service data does not meet the expected requirements, it sends the service data back to the front end.

[0087] It should be noted that the specific working process of each step provided in the above embodiments of this application can be referred to the corresponding non-functional automated test platform in the above system embodiments, and will not be repeated here.

[0088] Optionally, in another embodiment of this application, a business continuity testing method, after the verification standard device determines whether the service processing capability of the system under test meets the business continuity requirements before and after the handover based on the test report of the system under test, further includes:

[0089] If the verification standard device determines that the service processing capability of the system under test does not meet the business continuity requirements before and after the switchover, it will provide feedback that the business continuity test of the system under test has failed.

[0090] It should be noted that the specific working process of each step provided in the above embodiments of this application can be referred to the corresponding inspection standard device in the above system embodiments, and will not be repeated here.

[0091] This application provides a business continuity testing method. When a non-functional automated testing platform receives a test request from a target user for a target test scenario of the system under test (SUT), it executes a continuous stress test case corresponding to the target test scenario. This simulates, through a simulator, the continuous sending of requests and / or file uploads from related systems to the SUT under the target test scenario. After the SUT is running stably, the business continuity management platform switches the SUT from the production environment to a disaster recovery environment or from multiple data centers to a designated data center. The business continuity management platform then switches the SUT from the production environment to the disaster recovery environment or from multiple data centers to the designated data center and maintains stable operation. Afterwards, the system under test is switched from the disaster recovery site back to the production site or from the designated center back to multiple centers. Then, after the system under test has been switched back to the production site or from the designated center back to multiple centers and is running stably, the non-functional automated testing platform and the business continuity management platform generate test reports for the system under test based on the test data monitored during the testing process. Finally, the verification standard device uses the test reports of the system under test to determine whether the service processing capability of the system under test before and after the switch meets the business continuity requirements. If the verification standard device determines that the service processing capability of the system under test before and after the switch meets the business continuity requirements, it provides feedback that the business continuity test of the system under test is successful. This solves the problem that it is impossible to judge the recovery level of the system's processing capability after the switch manually, while reducing labor costs and greatly improving the efficiency of business continuity testing.

[0092] Another embodiment of this application provides an electronic device, such as... Figure 3 As shown, it includes:

[0093] Memory 301 and processor 302.

[0094] The memory 301 is used to store the program.

[0095] The processor 302 is used to execute a program, which, when executed, is specifically used to implement a business continuity testing method as provided in any of the above embodiments.

[0096] Another embodiment of this application provides a computer storage medium for storing a computer program, which, when executed, implements a business continuity testing method as provided in any of the above embodiments.

[0097] Computer storage media, including both permanent and non-permanent, removable and non-removable media, can store information using any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0098] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art 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 application.

[0099] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for testing business continuity, characterized in that, The method is applied to a non-functional testing system, which includes at least a business continuity management platform, a non-functional automated testing platform, a simulator, and a verification standard device. The business continuity testing method includes: When the non-functional automated testing platform receives a test request for the target test scenario of the system under test initiated by the target personnel, it executes the continuous stress test case corresponding to the target test scenario, so as to simulate the related system of the system under test continuously sending requests to the system under test, and / or uploading files to the system under test under the target test scenario through the simulator. After the system under test is running stably, the business continuity management platform will switch the system under test from the production end to the disaster recovery end, or switch the system under test from multiple centers to a designated center. After the system under test is switched from the production end to the disaster recovery end, or from the multi-center to the designated center and is running stably, the business continuity management platform will switch the system under test back from the disaster recovery end to the production end, or switch the system under test back from the designated center to the multi-center. After the system under test switches from the disaster recovery terminal back to the production terminal, or from the designated center back to the multi-center and runs stably, the non-functional automated testing platform and the business continuity management platform respectively generate a test report for the system under test based on the test data monitored during the testing process. The verification standard device, based on the test report of the system under test, determines whether the service processing capability of the system under test before and after the switchover meets the business continuity requirements. If the verification standard device determines that the service processing capability of the system under test meets the business continuity requirements before and after the switchover, it will provide feedback that the business continuity test of the system under test is successful.

2. The method according to claim 1, characterized in that, The test report of the system under test includes at least a handover plan execution report and a non-functional test report. The determination of whether the service processing capability of the system under test before and after the handover meets the business continuity requirements based on the test report includes: Extract the service recovery parameters from the non-functional test report and the effective indicators from the switching scheme execution report; Each of the service recovery parameters of the system under test after the switchover is determined to meet the preset parameter requirements, and each of the effective indicators of the system under test after the switchover is determined to meet the validity requirements. If it is determined that each of the service recovery parameters of the system under test before and after the switchover meets the preset parameter requirements, and if it is determined that each of the effective indicators of the system under test before and after the switchover meets the validity requirements, then it is determined that the service processing capability of the system under test before and after the switchover meets the business continuity requirements.

3. The method according to claim 1, characterized in that, Also includes: The non-functional automated testing platform monitors the various service data of the system under test in real time before and after the switchover. When the non-functional automated testing platform detects that any of the service data does not meet the expected requirements, it feeds back the service data to the front end.

4. The method according to claim 1, characterized in that, The verification standard device, based on the test report of the system under test, determines whether the service processing capability of the system under test meets the business continuity requirements before and after the switchover, and further includes: If the verification standard device determines that the service processing capability of the system under test does not meet the business continuity requirements before and after the switchover, it will provide feedback that the business continuity test of the system under test has failed.

5. A non-functional testing system for business continuity, characterized in that, The non-functional testing system includes at least a business continuity management platform, a non-functional automated testing platform, a simulator, and a verification standard device, including: The non-functional automated testing platform is used to execute continuous stress test cases corresponding to the target test scenario when it receives a test request for the target test scenario of the system under test initiated by the target personnel. This is to simulate, through a simulator, the associated systems of the system under test continuously sending requests to the system under test, and / or uploading files, under the target test scenario. The platform is also used to generate a test report for the system under test based on the test data monitored during the test process. The business continuity management platform is used to switch the system under test from the production end to the disaster recovery end or from the multi-center to the designated center after the system under test is running stably; and to switch the system under test from the disaster recovery end back to the production end or from the designated center back to the multi-center after the system under test has been switched from the production end to the disaster recovery end or from the multi-center to the designated center and is running stably. It is also used to generate a test report of the system under test based on the test data monitored during the test. The verification standard device is used to determine, based on the test report of the system under test, whether the service processing capability of the system under test before and after the switch meets the business continuity requirements, and to provide feedback information indicating that the business continuity test of the system under test is successful if it is determined that the service processing capability of the system under test before and after the switch meets the business continuity requirements.

6. The system according to claim 5, characterized in that, The test report of the system under test includes at least a handover plan execution report and a non-functional test report. When the verification standard device executes the test report based on the system under test to determine whether the service processing capability of the system under test meets the business continuity requirements before and after the handover, it is used for: Extract the service recovery parameters from the non-functional test report and the effective indicators from the switching scheme execution report; Each of the service recovery parameters of the system under test after the switchover is determined to meet the preset parameter requirements, and each of the effective indicators of the system under test after the switchover is determined to meet the validity requirements. If it is determined that each of the service recovery parameters of the system under test before and after the switchover meets the preset parameter requirements, and if it is determined that each of the effective indicators of the system under test before and after the switchover meets the validity requirements, then it is determined that the service processing capability of the system under test before and after the switchover meets the business continuity requirements.

7. The system according to claim 5, characterized in that, Also used for: The non-functional automated testing platform monitors the various service data of the system under test in real time before and after the switchover. When the non-functional automated testing platform detects that any of the service data does not meet the expected requirements, it feeds back the service data to the front end.

8. The system according to claim 5, characterized in that, The verification standard device, after executing the test report based on the system under test and determining whether the service processing capability of the system under test meets the business continuity requirements before and after the switchover, is further used for: If the verification standard device determines that the service processing capability of the system under test does not meet the business continuity requirements before and after the switchover, it will provide feedback that the business continuity test of the system under test has failed.

9. An electronic device, characterized in that, include: Memory and processor; The memory is used to store programs; The processor is used to execute the program, which, when executed, is specifically used to implement a business continuity testing method as described in any one of claims 1 to 4.

10. A computer storage medium, characterized in that, Used to store a computer program, which, when executed, is used to implement a business continuity testing method as described in any one of claims 1 to 4.

Images