A method and device for constructing a chaotic test fault case library

Abstract

The application discloses a method and device for constructing a chaos test fault case library, whether the system technology library, the system business library, the fault scene library and the fault means library have system technology assets, system business assets, fault scene assets and fault means assets required for testing is judged in sequence, if not, new assets are added in the corresponding library, if yes, appropriate assets are selected from the corresponding library, finally, chaos testing is carried out based on the fault scene assets and the fault means assets, and the test case assets corresponding to this test are stored in the implementation record library. Therefore, the assets generated during chaos testing can be managed by the above asset library, so that the assets can be flexibly reused during each chaos testing, and the test efficiency is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of chaos testing, and in particular to a method and device for constructing a chaos testing fault case library. BACKGROUND

[0002] In today's digital world, the complexity and criticality of software systems are growing rapidly. For large-scale software systems and cloud infrastructures, it is particularly important to maintain high availability and stability. However, traditional testing methods and operation methods often cannot fully simulate complex scenarios and potential failures in real-world environments.

[0003] Chaos engineering, as a new method and concept, aims to test and evaluate the robustness and reliability of systems by actively introducing various failures, anomalies and uncertainty factors. Its concept is derived from complex system science and chaos theory, aiming to discover and solve potential problems in the system by simulating chaotic environments, and to improve the resilience of the system. The basic principle of chaos engineering is to intentionally create and introduce various anomalies and failure conditions to observe the behavior and response of the system in unstable and abnormal environments. This method can help developers better understand the weaknesses, bottlenecks and potential failure points of the system, so as to take appropriate measures to improve the design and performance of the system.

[0004] Chaos engineering has a wide range of applications in software development and system operation. It can help development teams discover and fix vulnerabilities and failures in software early, improving system stability and maintainability. For cloud infrastructures and distributed systems, chaos engineering can simulate network failures, resource bottlenecks and other conditions to evaluate the resilience and fault tolerance of the system. In addition, chaos engineering can also help operation teams plan for disaster recovery and test the system's recovery capabilities to ensure that the system can quickly recover and respond in the face of unexpected situations.

[0005] However, based on the principle of chaos engineering, chaos testing of the system involves system analysis, fault scenario design, fault design, fault injection implementation and other work links, and each work link requires a large amount of time and resources to handle the corresponding work tasks, resulting in low efficiency of chaos testing. SUMMARY

[0006] Therefore, the present application discloses the following technical solutions:

[0007] The first aspect of the present application provides a method for constructing a chaos testing fault case library, comprising:

[0008] determining whether the system technology library has system technology assets corresponding to the target system;

[0009] If the system technology library does not have a system technology asset corresponding to the target system, a system technology asset is generated to update the system technology library, and the step of determining whether the system technology library has a system technology asset corresponding to the target system is returned to be executed;

[0010] If the system technology library has a system technology asset corresponding to the target system, the system technology asset corresponding to the target system is selected;

[0011] Determine whether the system business library corresponding to the system technology asset has a system business asset corresponding to the target business;

[0012] If the system business library does not have a system business asset corresponding to the target business, a system business asset is generated to update the system business library, and the step of determining whether the system business library corresponding to the system technology asset has a system business asset corresponding to the target business is returned to be executed;

[0013] If the system business library has a system business asset corresponding to the target business, the system business asset corresponding to the target business is selected;

[0014] Determine whether the fault scenario library corresponding to the system business asset has a fault scenario asset corresponding to the target scenario;

[0015] If the fault scenario library does not have a fault scenario asset corresponding to the target scenario, a fault scenario asset is generated to update the fault scenario library, and the step of determining whether the fault scenario library corresponding to the system business asset has a fault scenario asset corresponding to the target scenario is returned to be executed;

[0016] If the fault scenario library has a fault scenario asset corresponding to the target scenario, the fault scenario asset corresponding to the target scenario is selected;

[0017] Determine whether the fault means library has a fault means asset corresponding to the fault scenario asset;

[0018] If the fault means library does not have a fault means asset corresponding to the fault scenario asset, a fault means asset is generated to update the fault means library, and the step of determining whether the fault means library has a fault means asset corresponding to the fault scenario asset is returned to be executed;

[0019] If the fault means library has a fault means asset corresponding to the fault scenario asset, the fault means asset corresponding to the fault scenario asset is selected;

[0020] According to the selected fault scenario asset and the fault means asset, the target business of the target system is subjected to a chaos test;

[0021] At the end of the test, a test case asset corresponding to this test is obtained and stored in an implementation record library.

[0022] The second aspect of the application provides a construction device of a chaotic test fault case library, comprising:

[0023] a system technology unit, configured to:

[0024] determine whether a system technology library has a system technology asset corresponding to a target system;

[0025] if the system technology library does not have the system technology asset corresponding to the target system, generate the system technology asset to update the system technology library, and return to execute the step of determining whether the system technology library has the system technology asset corresponding to the target system;

[0026] if the system technology library has the system technology asset corresponding to the target system, select the system technology asset corresponding to the target system;

[0027] a system business unit, configured to:

[0028] determine whether a system business library corresponding to the system technology asset has a system business asset corresponding to a target business;

[0029] if the system business library does not have the system business asset corresponding to the target business, generate the system business asset to update the system business library, and return to execute the step of determining whether the system business library corresponding to the system technology asset has the system business asset corresponding to the target business;

[0030] if the system business library has the system business asset corresponding to the target business, select the system business asset corresponding to the target business;

[0031] a fault scenario unit, configured to:

[0032] determine whether a fault scenario library corresponding to the system business asset has a fault scenario asset corresponding to a target scenario;

[0033] if the fault scenario library does not have the fault scenario asset corresponding to the target scenario, generate the fault scenario asset to update the fault scenario library, and return to execute the step of determining whether the fault scenario library corresponding to the system business asset has the fault scenario asset corresponding to the target scenario;

[0034] if the fault scenario library has the fault scenario asset corresponding to the target scenario, select the fault scenario asset corresponding to the target scenario;

[0035] a fault means unit, configured to:

[0036] determine whether a fault means library has a fault means asset corresponding to the fault scenario asset;

[0037] If the fault means library does not have the fault means asset corresponding to the fault scene asset, a fault means asset is generated to update the fault means library, and the step of judging whether the fault means library has the fault means asset corresponding to the fault scene asset is returned to be executed;

[0038] If the fault means library has the fault means asset corresponding to the fault scene asset, the fault means asset corresponding to the fault scene asset is selected;

[0039] The test unit is configured to:

[0040] The target system is subjected to the chaos test according to the selected fault scene asset and the fault means asset;

[0041] The implementation record unit is configured to, at the end of the test, obtain the test case asset corresponding to the test and store the test case asset in an implementation record library.

[0042] The scheme has the following beneficial effects:

[0043] The embodiment can store the system technology asset, the system business asset, the fault scene asset, the fault means asset and the test case asset generated in each link of the chaos test in the corresponding system technology library, the system business library, the fault scene library, the fault means library and the implementation record library, and update the asset libraries in real time. The asset libraries carry the implementation of the entire chaos test from the beginning to the end, and the embodiment can manage the assets generated in the chaos test through the asset libraries, so that the assets can be flexibly reused in each chaos test, and the test efficiency is improved. BRIEF DESCRIPTION OF DRAWINGS

[0044] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or the prior art description. Obviously, the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained without creative labor on the basis of the provided drawings.

[0045] Figure 1 is a structural schematic diagram of a chaos test fault case library provided by the embodiment of the present application;

[0046] Figure 2 is a flowchart of a construction method of a chaos test fault case library provided by the embodiment of the present application;

[0047] Figure 3 is a flowchart of generating a system technology asset to update a system technology library provided by the embodiment of the present application;

[0048] Figure 4is a flowchart provided by an embodiment of the present application for generating system business assets to update a system business library;

[0049] Figure 5 is a flowchart provided by an embodiment of the present application for generating fault scenario assets to update a fault scenario library;

[0050] Figure 6 is a flowchart provided by an embodiment of the present application for generating fault means assets to update a fault means library;

[0051] Figure 7 is a flowchart provided by an embodiment of the present application for conducting chaos testing;

[0052] Figure 8 is a structural schematic diagram of a chaos testing fault case library construction device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0053] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative labor fall within the scope of protection of the present application.

[0054] First, some terms that may be involved in the present application will be described.

[0055] Chaos engineering aims to test and evaluate the robustness and reliability of a system by actively introducing various faults, anomalies and uncertainty factors.

[0056] Chaos testing is the main way to land chaos engineering. By injecting faults into the system, it tests whether the system's fault handling and recovery capabilities meet expectations. By analyzing phenomena and test data, the reliability of the system is evaluated.

[0057] SRE team, simply put, is a team responsible for system stability. Compared with traditional system operation and maintenance, it pays more attention to the stability and reliability of the system, breaking the situation in which development, operation and maintenance, testing and security are independent of each other in IT organizations, and is a concrete practice of DevOps culture.

[0058] Fault case is an asset that records and summarizes information such as fault scenario analysis, fault design, fault implementation records, etc. in fault injection implementation work, which is used to provide effective reference information for subsequent fault injection of target systems and has the ability of reuse.

[0059] The chaos testing fault case library construction method provided by the embodiment can be used to construct and maintain a chaos testing fault case libraryFigure 1 The chaos test fault case library is shown, and then the work assets of the chaos test full-process analysis, design, execution and other links are aggregated and classified through the chaos test fault case library, so that each asset in the library can be flexibly reused during chaos testing.

[0060] As shown in Figure 1 The chaos test fault case library can include a system technology library, a system business library, a fault scenario library, a fault means library and an implementation record library.

[0061] System technology library. Carrying the technical assets of chaos test system analysis, the technical analysis results of the system are converted into technical analysis assets, and the test personnel can quickly master the technical properties of the system through the system library, including system architecture, resource deployment, technical characteristics, etc.

[0062] System business library. Carrying the business analysis assets for the system, the chaos test team converts the system business analysis content into business analysis assets, and the test personnel can quickly understand which type of business the system runs through the business assets, and how the scale and sensitivity of the business.

[0063] Fault scenario library. Carrying the assets of the fault scenario analysis and design by the chaos test team, the system fault scenario design is converted into fault scenario design assets, which supports the test personnel to face the same fault scenario test without repeating the fault scenario design.

[0064] Fault means library. Carrying the work output of fault injection method design, for the target fault scenario, what kind of fault means should be taken, and asset management is carried out.

[0065] Implementation record library. Asset management of asset combination and implementation configuration of chaos test, asset management of specific implementation record, convenient for test personnel to quickly retrieve various asset combinations and implementation configuration parameters of chaos test record, and support test personnel to carry out implementation playback of the same configuration.

[0066] Figure 1 In the system technology library, the system business library, the fault scenario library, the relationship is cascading, that is, a system technology asset is associated with multiple system business assets, and a system business asset is associated with multiple fault scenario assets. The fault means library includes organizational level fault means and multiple fault means corresponding to the fault scenario library. The implementation record library includes multiple test case assets, each test case asset can be used for a chaos test, and the test case asset can include the fault scenario, the fault means and the implementation parameters used in the chaos test.

[0067] The addition and update of assets in each of the above asset libraries need to be approved by an administrator before the assets can be completed and updated, and the implementation of chaos testing can be initiated by replaying (reusing) test case assets in the record library or by sequentially selecting assets through system technology, system business, fault scenario, and fault means.

[0068] Based on the above chaos testing fault case library, the embodiment provides a method for constructing a chaos testing fault case library, please refer to Figure 2 The method can include the following steps.

[0069] S201, determining whether the system technology library has system technology assets corresponding to the target system.

[0070] If the system technology library does not have system technology assets corresponding to the target system, step S202 is performed, and if the system technology library has system technology assets corresponding to the target system, step S203 is performed.

[0071] The target system refers to the system that needs to be tested at present.

[0072] The system technology library can store a plurality of system technology assets, and each system technology asset can correspond to a specific system under test. The system technology asset can include various system information and system technology attribute data required for chaos testing of the system under test.

[0073] In the embodiment, each system technology asset in the system technology library can have a system identifier, which represents the system under test corresponding to the asset. In S201, it can be determined whether each system technology asset in the system technology library has a system identifier of the target system. If it does, it means that the system technology library has corresponding system technology assets, and S203 is executed. If none of the assets in the library has the system identifier of the target system, it means that the system technology library does not have corresponding system technology assets, and S202 is executed.

[0074] S202, generating system technology assets to update the system technology library.

[0075] Updating the system technology library can specifically mean adding new system technology assets to the system technology library.

[0076] In step S202, system technology analysis can be performed on the target system to obtain new system technology assets corresponding to the target system, and then the new system technology assets are applied to join the system technology library. After the administrator of the system technology library approves, the asset addition is completed.

[0077] After updating the system technology library, return to execute the step of judging whether the system technology library has the system technology asset corresponding to the target system. Since the newly added system technology asset corresponding to the target system has been added to the system technology library in step S202, when S201 is executed again, the system technology asset corresponding to the target system can be found in the system technology library, and then S203 is executed.

[0078] S203, select the system technology asset corresponding to the target system.

[0079] As described above, each system technology asset corresponds to a system identifier, in S203, the system technology asset with the system identifier of the target system can be read from the system technology library, and the asset is taken as the system technology asset corresponding to the target system, and S203 is executed.

[0080] S204, judge whether the system business library corresponding to the system technology asset has the system business asset corresponding to the target business.

[0081] If the system business library does not have the system business asset corresponding to the target business, execute step S205, and if the system business library has the system business asset corresponding to the target business, execute step S206.

[0082] A system can include multiple businesses, and the target business can refer to any one or more of the businesses currently in need of chaos testing among the multiple businesses corresponding to the target system.

[0083] Each system business asset corresponds to a specific business, and the system business asset can include various business attributes of the corresponding business.

[0084] In step S204, the system business library corresponding to the target system can be determined first, and then it is checked whether the system business asset corresponding to the target business is included in the multiple system business assets in the system business library. If yes, step S206 is executed, and if not, step S205 is executed.

[0085] S205, generate a system business asset to update the system business library.

[0086] After updating the system business library, return to execute the step of judging whether the system business library corresponding to the system technology asset has the system business asset corresponding to the target business.

[0087] Updating the system business library can specifically refer to adding the newly added system business asset corresponding to the target business to the system business library.

[0088] In step S205, in the case where there is no system business asset corresponding to the target business, business analysis can be carried out and asset storage can be applied, and the system business asset can be newly added to the system business library after the administrator of the system business library approves.

[0089] After the system service library is updated, step S204 can be executed again, at this time, the newly added system service asset corresponding to the target service has been added to the system service library through step S205, so the system service asset corresponding to the target service can be found in the system service library, and then step S206 is executed.

[0090] S206, selecting the system service asset corresponding to the target service.

[0091] In step S206, the service identifiers of the system service assets contained in the system service library can be identified, and the system service asset whose service identifier matches the target service is determined as the system service asset corresponding to the target service and is read out from the system service library.

[0092] S207, judging whether the fault scenario library corresponding to the system service asset has a fault scenario asset corresponding to the target scenario.

[0093] If the fault scenario library does not have a fault scenario asset corresponding to the target scenario, step S208 is executed, and if the fault scenario library has a fault scenario asset corresponding to the target scenario, step S209 is executed.

[0094] The target scenario can be a fault scenario required for testing the target service of the target system, in step S207, the target scenario required for chaos testing can be determined according to the system technology asset of the target system and the system service asset of the target service, and then it is checked whether there is a fault scenario asset corresponding to the target scenario in the fault scenario library.

[0095] Each fault scenario asset corresponds to a fault scenario, and the fault scenario asset can include fault scenario data of the corresponding fault scenario, including but not limited to numerical values of various parameters constituting the fault scenario, input data and output data, etc.

[0096] If there is a fault scenario asset corresponding to the target scenario, step S209 is executed, and if there is no fault scenario asset corresponding to the target scenario, step S208 is executed.

[0097] S208, generating a fault scenario asset to update the fault scenario library.

[0098] After updating the fault scenario library, the step of judging whether the fault scenario library corresponding to the system service asset has a fault scenario asset corresponding to the target scenario is returned.

[0099] Updating the fault scenario library is equivalent to adding the newly added fault scenario asset corresponding to the target scenario to the fault scenario library (i.e., asset warehousing).

[0100] If there is no fault scene asset corresponding to the target scene in the fault scene library, the fault scene analysis can be carried out in step S208 and the asset can be applied for storage. After the administrator of the fault scene library approves, the asset can be stored and the new asset is added.

[0101] After updating the fault scene library, step S207 can be executed again. At this time, the new fault scene asset corresponding to the target scene has been added to the fault scene library through step S208, so the new fault scene asset corresponding to the target scene can be found in the fault scene library, and then S209 is executed.

[0102] S209, selecting the fault scene asset corresponding to the target scene.

[0103] In step S209, the fault scene asset with the scene identifier of the target scene in the fault scene library can be identified, and the fault scene asset is read out as the fault scene asset corresponding to the target scene.

[0104] S210, determining whether the fault means library has the fault means asset corresponding to the fault scene asset.

[0105] If the fault means library does not have the fault means asset corresponding to the fault scene asset, step S211 is executed, and if the fault means library has the fault means asset corresponding to the fault scene asset, step S212 is executed.

[0106] In S210, the fault means suitable for use in this test can be determined according to the system technology asset of the target system, the system business asset of the target business and the fault scene asset of the target scene, and then it is determined whether there is a fault means asset corresponding to the required fault means in the fault means library.

[0107] If yes, step S212 is executed, and if no, step S211 is executed.

[0108] Each fault means asset can correspond to one fault means, and the fault means asset can include various data for describing the corresponding fault means.

[0109] S211, generating a fault means asset to update the fault means library.

[0110] After updating the fault means library, the step of determining whether the fault means library has the fault means asset corresponding to the fault scene asset is returned.

[0111] Updating the fault means library means adding the fault means asset of the required fault means to the fault means library.

[0112] In step S211, the passed failure means can be added to the failure means library in the form of failure means assets through user-defined failure means and administrator review.

[0113] S212, selecting the failure means assets corresponding to the failure scenario assets.

[0114] In S212, if it is determined that the failure means library already has the failure means assets of the required failure means, the failure means assets can be directly read out, and then S213 is executed.

[0115] S213, performing chaos test on the target business of the target system according to the selected failure scenario assets and failure means assets.

[0116] After the failure means is determined and the corresponding failure means assets are obtained in step S212, in step S213, the implementation parameters of the chaos test can be configured, and then based on the implementation parameters, the failure scenario assets and the failure means assets, the chaos test on the target business of the target system is performed.

[0117] The specific method of the chaos test can refer to the related prior art, which is not described herein.

[0118] S214, obtaining the test case assets corresponding to the test and storing them in the implementation record library at the end of the test.

[0119] During the implementation of the chaos test, various data of the target system and the target business in the test process can be recorded in real time to obtain the test records of the test.

[0120] After the chaos test is completed, if it is planned to record the assets of the implementation, the above test records of the test are converted into corresponding test case assets and applied for asset storage, and after the administrator reviews, the implementation record library can be added.

[0121] The beneficial effects of the embodiment are as follows:

[0122] Some prior art will take various fault injection means of chaos testing as case management, support flexible reuse of multiple injection means when injecting faults in chaos testing, and select from the list of fault injection means after the target system enters the implementation link of fault injection. Managing fault injection means as cases does not actually reflect the whole process of chaos testing assets. Chaos testing is one of the multiple work links, and the main link of chaos testing is still in system analysis and fault scenario design, etc. These links require a lot of manual communication, analysis, and confirmation work. Therefore, only managing fault injection capability as assets can only achieve the effect of reusing fault injection tool capability level, and cannot flexibly reuse system assets for multiple chaos tests, reducing manual costs and repeated energy consumption.

[0123] In the embodiment, the system technology assets, system business assets, fault scenario assets, fault means assets and test case assets generated in each link of chaos testing are stored in the corresponding system technology library, system business library, fault scenario library, fault means library and implementation record library, and the above asset libraries are updated in real time. These asset libraries carry the whole process of chaos testing from beginning to end, and the embodiment can manage the assets generated during chaos testing through the above asset libraries, so as to flexibly reuse the assets during each chaos test and improve the test efficiency.

[0124] In summary, the application proposes a construction method and device of a chaos testing fault case library, which effectively organizes and manages the whole process assets of chaos testing through the design method of the fault case library, and realizes the whole process of asset management through the automatic device, fully utilizes the flexible reuse capability, and improves the work implementation efficiency of chaos testing.

[0125] In some optional embodiments, the step S201 can be performed before the following steps:

[0126] Determine whether the implementation record library has reusable test case assets;

[0127] If the implementation record library has reusable test case assets, perform chaos testing according to the test case assets;

[0128] If the implementation record library does not have reusable test case assets, perform the step of determining whether the system technology library has system technology assets corresponding to the target system.

[0129] The implementation record library can store multiple previous test case assets, and each test case asset corresponds to a previous chaos test.

[0130] In this embodiment, when preparing the chaos test, it can be analyzed whether the implementation record library has reusable test case assets. If the implementation record library has reusable test case assets and it is planned to reuse the assets for the test, the chaos test can be started directly according to the reusable test case assets.

[0131] If the implementation record library does not have reusable test case assets, or has reusable test case assets but does not plan to reuse the assets for the test, the system technology library can be screened, that is, step S201 is performed.

[0132] The method for determining whether the implementation record library has reusable test case assets can be that, for each test case asset of the implementation record library, it is determined whether the measured system, measured business, fault scene and fault means corresponding to the test case asset meet the requirements of the chaos test. If yes, it is determined that the test case asset is a reusable test case asset. If no, it is determined that the test case asset is not a reusable test case asset.

[0133] Whether to plan to reuse the reusable test case assets for the test can be determined by the relevant test personnel, that is, the reusable test case assets can be screened and displayed to the relevant test personnel, and then it is determined whether to plan to reuse the reusable test case assets for the test according to the operation of the test personnel.

[0134] Optionally, please refer to Figure 3 The process of generating system technology assets to update the system technology library (that is, the process of carrying out system technology analysis) can include:

[0135] Synchronizing the enterprise system service directory to update the system information;

[0136] Verifying and completing the system technology attribute data;

[0137] After the system technology attribute data and the updated system information pass the audit, the system technology attribute data and the system information are assembled according to the asset standard to obtain new system technology assets;

[0138] The new system technology assets are added to the system technology library.

[0139] In this embodiment, the enterprise system service directory can be synchronized first, and the latest system information of the target system, that is, the updated system information, can be read from the directory. Then, the system technical attribute data can be read from the target system according to the updated system information, and the system technical attribute data can be pushed to the terminal of the related operation and maintenance personnel, so that the related operation and maintenance personnel can check and complete the system technical attribute data. Then, the checked and completed system technical attribute data and the updated system information are pushed to the administrator responsible for managing the system technical assets, and the administrator performs an audit. If the administrator passes the audit, the checked and completed system technical attribute data and the updated system information can be standardized and assembled to obtain the newly added system technical assets corresponding to the target system, and finally the newly added system technical assets of the target system are added to the system technical library.

[0140] If the administrator does not pass the audit, the administrator's audit opinion can be obtained, and the synchronization directory step and the checking and completing step can be performed again, and the audit can be performed again.

[0141] The specific process of asset standardization assembly can be referred to related prior art, which is not described herein.

[0142] Optionally, please refer to Figure 4 The process of generating system business assets to update the system business library can include:

[0143] Analyzing system business attributes to obtain system business analysis results;

[0144] Checking and completing the system business analysis results;

[0145] After the system business analysis results pass the audit, the system business analysis results are standardized and assembled to obtain newly added system business assets;

[0146] The newly added system business assets are added to the system business library.

[0147] In this embodiment, the business attribute data of the target business of the target system can be collected first, and the data is pushed to the related operation and maintenance personnel for analysis to obtain system business analysis results. Then, the operation and maintenance personnel check and complete the system business analysis results, and push the checked and completed system business analysis results to the administrator of the system business library for audit. If the audit passes, the system business analysis results are standardized and assembled to obtain newly added system business assets corresponding to the target business and added to the system business library. If the audit does not pass, the analysis, checking and completing steps can be repeated based on the audit opinion to obtain new system business analysis results.

[0148] Optionally, please refer to Figure 5 The process of generating fault scenario assets to update the fault scenario library can include:

[0149] determining fault scenario design data;

[0150] verifying and completing the fault scenario design data;

[0151] After the fault scenario design data passes the review, the fault scenario design data is assembled into assets in a standardized manner to obtain new fault scenario assets;

[0152] The new fault scenario assets are added to the fault scenario library.

[0153] In this embodiment, a user responsible for designing fault scenarios can design the fault scenarios required for this test based on the system technical assets corresponding to the target system, the system business assets corresponding to the target business, and the test requirements of this test, to obtain fault scenario design data.

[0154] After obtaining the fault scenario design data, the data can be pushed to an operation and maintenance personnel responsible for verifying the data, so as to verify and complete the fault scenario design data, and then the verified and completed fault scenario design data can be sent to an administrator of the fault scenario library for review. If the review is passed, the fault scenario design data can be assembled into assets in a standardized manner to obtain new fault scenario assets, and the new fault scenario assets are added to the fault scenario library.

[0155] If the review is not passed, the fault scenario design and the verification and completion of the fault scenario design data can be re-performed according to the review opinions.

[0156] Optionally, please refer to Figure 6 The process of generating fault means assets to update the fault means library can include:

[0157] designing a custom fault means;

[0158] arranging the custom fault means and performing an explosion radius setting check;

[0159] After the custom fault means passes the review, the custom fault means is assembled into assets in a standardized manner to obtain new fault means assets;

[0160] The new fault means assets are added to the fault means library.

[0161] In the above embodiments, a user responsible for designing the fault means can design a custom fault means according to the target system, target business and target scenario, and test requirements of this test, and then a user responsible for arrangement and checking can arrange the custom fault means and perform explosion radius setting checking, and finally an administrator of the fault means library can review the custom fault means, if the review is not passed, the custom fault means can be redesigned, arranged and checked again to obtain a new custom fault means, if the review is passed, the custom fault means can be standardized assembled to obtain a new fault means asset corresponding to the custom fault means, and then the new fault means asset is added to the fault means library.

[0162] Optionally, referring to Figure 7 , the process of performing the chaos test on the target business of the target system according to the selected fault scenario asset and the fault means asset can include:

[0163] The user configures the chaos test implementation parameters;

[0164] Start the chaos test;

[0165] Complete the chaos test review;

[0166] Implement record carding;

[0167] The relevant operation and maintenance personnel determine whether to assemble into a test case asset;

[0168] If not assembled into a test case asset, the current chaos test ends;

[0169] If assembled into a test case asset, the foregoing step S214 can be executed.

[0170] In step S214, the carded implementation record and various data collected during the chaos test can be pushed to a system asset administrator for review, if the review is not passed, step S214 ends and a new test case asset is not added, if the review is passed, the carded implementation record and various data collected during the chaos test can be standardized assembled to obtain a test case asset corresponding to this test, and then the test case asset is added to the implementation record library for subsequent test reuse.

[0171] After starting the chaos test, the system can automatically perform the chaos test based on the foregoing technical assets of the target system, system business assets of the target business, fault scenario assets of the target scenario and selected fault means assets, combined with the configured implementation parameters.

[0172] In the test based on the reusable test case asset, the step of configuring the chaos test implementation parameters in the above embodiments can be performed, and the step of starting the chaos test is directly entered.

[0173] The embodiment of the application further provides a device for constructing a chaotic test fault case library, please refer to Figure 8 The device can include the following units.

[0174] The system technology unit 801 is configured to:

[0175] determine whether the system technology library has a system technology asset corresponding to the target system;

[0176] If the system technology library does not have a system technology asset corresponding to the target system, generate a system technology asset to update the system technology library, and return to the step of determining whether the system technology library has a system technology asset corresponding to the target system;

[0177] If the system technology library has a system technology asset corresponding to the target system, select the system technology asset corresponding to the target system;

[0178] The system business unit 802 is configured to:

[0179] determine whether the system business library corresponding to the system technology asset has a system business asset corresponding to the target business;

[0180] If the system business library does not have a system business asset corresponding to the target business, generate a system business asset to update the system business library, and return to the step of determining whether the system business library corresponding to the system technology asset has a system business asset corresponding to the target business;

[0181] If the system business library has a system business asset corresponding to the target business, select the system business asset corresponding to the target business;

[0182] The fault scenario unit 803 is configured to:

[0183] determine whether the fault scenario library corresponding to the system business asset has a fault scenario asset corresponding to the target scenario;

[0184] If the fault scenario library does not have a fault scenario asset corresponding to the target scenario, generate a fault scenario asset to update the fault scenario library, and return to the step of determining whether the fault scenario library corresponding to the system business asset has a fault scenario asset corresponding to the target scenario;

[0185] If the fault scenario library has a fault scenario asset corresponding to the target scenario, select the fault scenario asset corresponding to the target scenario;

[0186] The fault means unit 804 is configured to:

[0187] determine whether the fault means library has a fault means asset corresponding to the fault scenario asset;

[0188] If the fault means library does not have the fault means asset corresponding to the fault scene asset, a fault means asset is generated to update the fault means library, and the step of judging whether the fault means library has the fault means asset corresponding to the fault scene asset is returned to be executed;

[0189] If the fault means library has the fault means asset corresponding to the fault scene asset, the fault means asset corresponding to the fault scene asset is selected;

[0190] The test unit 805 is configured to:

[0191] According to the selected fault scene asset and the fault means asset, a target service of a target system is subjected to the chaos test;

[0192] The implementation record unit 806 is configured to, when the test is completed, obtain a test case asset corresponding to the test and store the test case asset in an implementation record library.

[0193] Optionally, the implementation record unit 806 is further configured to:

[0194] Judge whether the implementation record library has a reusable test case asset;

[0195] If the implementation record library has the reusable test case asset, the chaos test is performed according to the test case asset;

[0196] If the implementation record library does not have the reusable test case asset, the step of judging whether the system technology library has a system technology asset corresponding to the target system is executed.

[0197] Optionally, when the system technology unit 801 generates the system technology asset to update the system technology library, the system technology unit 801 is specifically configured to:

[0198] Synchronize an enterprise system service directory to update system information;

[0199] Verify and complete system technology attribute data;

[0200] After the system technology attribute data and the updated system information pass the audit, the system technology attribute data and the system information are subjected to asset standardization assembly to obtain a new system technology asset;

[0201] The new system technology asset is added to the system technology library.

[0202] Optionally, when the system business unit 802 generates the system business asset to update the system business library, the system business unit 802 is specifically configured to:

[0203] Analyze system business attributes to obtain a system business analysis result;

[0204] Verify and complete the system business analysis result;

[0205] After the system business analysis result passes the audit, the system business analysis result is standardized assembled to obtain the new system business asset;

[0206] The new system business asset is added to the system business library.

[0207] Optionally, when the fault scenario unit 803 generates the fault scenario asset to update the fault scenario library, the fault scenario asset is specifically used for:

[0208] determining fault scenario design data;

[0209] verifying and completing the fault scenario design data;

[0210] After the fault scenario design data passes the audit, the fault scenario design data is standardized assembled to obtain the new fault scenario asset;

[0211] The new fault scenario asset is added to the fault scenario library.

[0212] The working principle of the construction device of the chaos test fault case library of the embodiment can be referred to the related steps of the construction method of the chaos test fault case library provided by any embodiment of the present application, and will not be described again.

[0213] It should be noted that each embodiment in the present specification adopts a progressive manner for description, and each embodiment focuses on the different places from other embodiments. The same and similar parts between the embodiments can be referred to each other.

[0214] For the convenience of description, the above system or device is described as various modules or units respectively described by functions. Of course, the functions of each unit can be realized in the same or multiple software and / or hardware in the implementation of the present application.

[0215] From the description of the above embodiments, those skilled in the art can clearly understand that the present application can be realized by means of software and necessary general hardware platform. Based on such understanding, the technical solutions of the present application can be embodied in the form of software product, which can be stored in a storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., including a plurality of instructions to make a computer device (which can be a personal computer, server, or network device, etc.) execute the methods described in various embodiments or some parts of the embodiments of the present application.

[0216] Finally, it needs to be pointed out that, in this document, relational terms such as first, second, third, and fourth and the like can only be used to distinguish one entity or action from another entity or action, without necessarily requiring or implying any actual relationship or order between or among such entities or actions. Moreover, the terms "comprises", "comprising", or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but can include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by "comprises... a" does not, without more constraints, exclude the existence of additional identical elements in the process, method, article, or apparatus that comprises the element.

[0217] The above description is merely preferred embodiments of the present application, and it is obvious to those skilled in the art that, without departing from the principles of the present application, a number of improvements and refinements can be made, and these improvements and refinements should also be considered as falling within the scope of the present application.

Claims

1. A method for constructing a chaotic test fault case library, characterized by, The method comprises the following steps: determining whether the system technology library has system technology assets corresponding to the target system; if the system technology library does not have system technology assets corresponding to the target system, generating system technology assets to update the system technology library, and returning to the step of determining whether the system technology library has system technology assets corresponding to the target system; if the system technology library has system technology assets corresponding to the target system, selecting the system technology assets corresponding to the target system; determining whether the system business library corresponding to the system technology assets has system business assets corresponding to the target business; if the system business library does not have system business assets corresponding to the target business, generating system business assets to update the system business library, and returning to the step of determining whether the system business library corresponding to the system technology assets has system business assets corresponding to the target business; if the system business library has system business assets corresponding to the target business, selecting the system business assets corresponding to the target business; determining whether the fault scenario library corresponding to the system business assets has fault scenario assets corresponding to the target scenario; if the fault scenario library does not have fault scenario assets corresponding to the target scenario, generating fault scenario assets to update the fault scenario library, and returning to the step of determining whether the fault scenario library corresponding to the system business assets has fault scenario assets corresponding to the target scenario; if the fault scenario library has fault scenario assets corresponding to the target scenario, selecting the fault scenario assets corresponding to the target scenario; determining whether the fault means library has fault means assets corresponding to the fault scenario assets; if the fault means library does not have fault means assets corresponding to the fault scenario assets, generating fault means assets to update the fault means library, and returning to the step of determining whether the fault means library has fault means assets corresponding to the fault scenario assets; if the fault means library has fault means assets corresponding to the fault scenario assets, selecting the fault means assets corresponding to the fault scenario assets; performing a chaos test on the target business of the target system according to the selected fault scenario assets and fault means assets; at the end of the test, obtaining test case assets corresponding to this test and storing them in the implementation record library.

2. The method of claim 1, wherein, The method further comprises the following steps: determining whether the implementation record library has reusable test case assets; if the implementation record library has reusable test case assets, performing a chaos test according to the test case assets; if the implementation record library does not have reusable test case assets, performing the step of determining whether the system technology library has system technology assets corresponding to the target system.

3. The method of claim 1, wherein, The step of generating system technology assets to update the system technology library comprises the following steps: synchronizing the enterprise system service directory to update system information; verifying and completing system technology attribute data; after the system technology attribute data and the updated system information pass the audit, performing asset standardization assembly on the system technology attribute data and the system information to obtain new system technology assets; adding the new system technology assets to the system technology library.

4. The method of claim 1, wherein, The step of generating system business assets to update the system business library comprises the following steps: Analyzing system business attributes to obtain system business analysis results; Verifying and completing the system business analysis results; After the system business analysis results pass the verification, performing asset standardization assembly on the system business analysis results to obtain new system business assets; Adding the new system business assets to the system business library.

5. The method of claim 1, wherein, The generating fault scenario assets to update the fault scenario library comprises: Determining fault scenario design data; Verifying and completing the fault scenario design data; After the fault scenario design data pass the verification, performing asset standardization assembly on the fault scenario design data to obtain new fault scenario assets; Adding the new fault scenario assets to the fault scenario library.

6. A construction device of a chaos test failure case library, characterized by, Comprises: A system technology unit for: Determining whether the system technology library has system technology assets corresponding to a target system; If the system technology library does not have system technology assets corresponding to the target system, generating system technology assets to update the system technology library, and returning to execute the step of determining whether the system technology library has system technology assets corresponding to the target system; If the system technology library has system technology assets corresponding to the target system, selecting the system technology assets corresponding to the target system; A system business unit for: Determining whether the system business library corresponding to the system technology assets has system business assets corresponding to a target business; If the system business library does not have system business assets corresponding to the target business, generating system business assets to update the system business library, and returning to execute the step of determining whether the system business library corresponding to the system technology assets has system business assets corresponding to the target business; If the system business library has system business assets corresponding to the target business, selecting the system business assets corresponding to the target business; A fault scenario unit for: Determining whether the fault scenario library corresponding to the system business assets has fault scenario assets corresponding to a target scenario; If the fault scenario library does not have fault scenario assets corresponding to the target scenario, generating fault scenario assets to update the fault scenario library, and returning to execute the step of determining whether the fault scenario library corresponding to the system business assets has fault scenario assets corresponding to the target scenario; If the fault scenario library has fault scenario assets corresponding to the target scenario, selecting the fault scenario assets corresponding to the target scenario; A fault means unit for: Determining whether the fault means library has fault means assets corresponding to the fault scenario assets; If the fault means library does not have fault means assets corresponding to the fault scenario assets, generating fault means assets to update the fault means library, and returning to execute the step of determining whether the fault means library has fault means assets corresponding to the fault scenario assets; If the fault means library has fault means assets corresponding to the fault scenario assets, selecting the fault means assets corresponding to the fault scenario assets; A test unit for: Performing a chaos test on the target business of the target system according to the selected fault scenario assets and fault means assets; An implementation record unit is configured to obtain the test case asset corresponding to the current test and store it in the implementation record library at the end of the test.

7. The apparatus of claim 6, wherein, The implementation record unit is further configured to: determine whether the implementation record library has reusable test case assets; if the implementation record library has reusable test case assets, perform chaotic testing according to the test case assets; if the implementation record library does not have reusable test case assets, perform the step of determining whether the system technology library has system technology assets corresponding to the target system.

8. The apparatus of claim 6, wherein, When the system technology unit generates system technology assets to update the system technology library, it is specifically configured to: synchronize the enterprise system service directory to update system information; check and complete system technology attribute data; after the system technology attribute data and the updated system information pass the audit, perform asset standardization assembly on the system technology attribute data and the system information to obtain new system technology assets; add the new system technology assets to the system technology library.

9. The apparatus of claim 6, wherein, When the system business unit generates system business assets to update the system business library, it is specifically configured to: analyze system business attributes to obtain system business analysis results; check and complete the system business analysis results; after the system business analysis results pass the audit, perform asset standardization assembly on the system business analysis results to obtain new system business assets; add the new system business assets to the system business library.

10. The apparatus of claim 6, wherein, When the fault scenario unit generates fault scenario assets to update the fault scenario library, it is specifically configured to: determine fault scenario design data; check and complete the fault scenario design data; after the fault scenario design data pass the audit, perform asset standardization assembly on the fault scenario design data to obtain new fault scenario assets; add the new fault scenario assets to the fault scenario library.

Images