Verification method and system for system degradation, equipment and medium

Abstract

The embodiment of the invention provides a verification method and system for system degradation, equipment and a medium. A specific embodiment of the method comprises: in response to a degradation verification request of a user for a target system, starting a server to execute a corresponding target operation for the target system, and triggering a target event corresponding to the degradation verification request and for a verification server, event parameters comprising a test scene of the verification; in response to the target event, the verification server sends an event type and a test scene to the configuration server; the configuration server calls a test server to execute a function test task for the target system according to the event type and the test scene; the test server sends the execution result to a verification server for determining a verification result for the degraded verification request. By means of the method, the efficiency of degradation verification and the verification frequency in a specific verification period can be greatly improved, and then the capacity of discovering degradation faults of the system through degradation verification is improved.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and more particularly to a verification method, system, device, and medium for system degradation. Background Technology

[0002] Degradation, in this context, refers to the process of reducing specific functions or performance of a computer system or service to ensure its basic availability and stability when faced with load pressure, failures, or other abnormal conditions. Degradation verification involves intentionally triggering the system's degradation mechanism under preset conditions or specific scenarios to confirm whether the system can successfully degrade and whether its core functions can continue to operate normally after degradation. Existing conventional degradation verification schemes primarily involve users manually initiating degradation tasks and, after completion, manually initiating tasks such as functional testing to verify the effectiveness of the degraded system. However, this approach suffers from low verification efficiency and consequently, a low verification frequency for the system under test within a specific verification cycle. Summary of the Invention

[0003] This disclosure describes a verification method, system, device, and medium for system degradation.

[0004] Based on the first aspect, a verification method for system degradation is provided, including:

[0005] In response to a user's request for downgrade verification of a target system, the server is started to perform a target operation on the target system corresponding to the downgrade verification request, and a target event for the verification server corresponding to the downgrade verification request is triggered, wherein the parameters of the target event include the test scenario of this verification.

[0006] In response to the target event, the verification server sends the event type of the target event and the test scenario to the configuration server; the configuration server, based on the event type and the test scenario, instructs the test server to execute a functional test task for the target system, and the test server sends the execution result of the functional test task to the verification server; the verification server, based at least on the execution result, determines the verification result for the downgrade verification request.

[0007] According to the second aspect, a verification system for system degradation is provided, comprising:

[0008] The server is started and configured to, in response to a user’s downgrade verification request for the target system, perform a target operation corresponding to the downgrade verification request for the target system, and trigger a target event for the verification server corresponding to the downgrade verification request, wherein the parameters of the target event include the test scenario of this verification.

[0009] The verification server is configured to, in response to the target event, send the event type of the target event and the test scenario to the configuration server.

[0010] The configuration server is configured to, based on the event type and the test scenario, invoke the test server to execute functional test tasks for the target system;

[0011] The test server is configured to send the execution results of the functional test task to the verification server;

[0012] The verification server is further configured to determine the verification result for the downgrade verification request based at least on the execution result.

[0013] According to a third aspect, a computer-readable storage medium is provided, on which a computer program is stored, which, when executed in a computer, causes the computer to perform the method of the first aspect.

[0014] According to a fourth aspect, an electronic device is provided, including a memory and a processor, wherein the memory stores executable code, and the processor executes the executable code to implement the method of the first aspect.

[0015] This disclosure provides a method, system, device, and medium for verifying system degradation. First, a startup server receives a degradation verification request for a target system from a user. It then performs a target operation corresponding to the degradation verification request on the target system and triggers a target event for the verification server corresponding to the degradation verification request. The parameters of the target event include the test scenario for this verification. Next, in response to the target event, the verification server sends the event type of the target event and the test scenario to a configuration server. Then, based on the event type and test scenario, the configuration server instructs a test server to execute a functional test task for the application access interface of the target system that matches the test scenario and event type. The test server sends the execution result of the functional test task to the verification server to determine the verification result for the degradation verification request. This method significantly improves the efficiency of degradation verification and the verification frequency within a specific verification cycle, thereby enhancing the ability to detect system degradation faults through degradation verification. Attached Figure Description

[0016] Figure 1 A schematic diagram of a verification method for system degradation according to an embodiment of the present disclosure is shown;

[0017] Figure 2 A schematic diagram illustrating the determination of degradation verification results based on a combination of functional test results and indicator fluctuation trends according to an embodiment of this disclosure is shown.

[0018] Figure 3 A flowchart illustrating a verification method for system degradation according to an embodiment of this disclosure is shown.

[0019] Figure 4 A schematic diagram of post-downgrade verification according to an embodiment of this disclosure is shown;

[0020] Figure 5 A schematic diagram illustrating the downgrade recovery verification according to an embodiment of this disclosure is provided;

[0021] Figure 6 A schematic diagram illustrating pre-downgrade verification according to an embodiment of this disclosure is provided;

[0022] Figure 7 A schematic block diagram of a verification system for system degradation according to an embodiment of the present disclosure is shown;

[0023] Figure 8 A schematic diagram of the structure of an electronic device suitable for implementing the embodiments of the present disclosure is provided;

[0024] Figure 9 A schematic diagram of the structure of a storage medium suitable for implementing embodiments of the present disclosure is provided. Detailed Implementation

[0025] The technical solutions provided in this specification will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the relevant invention and not intended to limit the invention. Furthermore, it should be noted that, for ease of description, only the parts relevant to the invention are shown in the accompanying drawings. It should be noted that, unless otherwise specified, the embodiments and features described herein can be combined with each other.

[0026] In the description of the implementations disclosed herein, the term "comprising" and similar terms should be understood as open inclusion, i.e., "including but not limited to". The term "based on" should be understood as "at least partially based on". The term "one / an implementation" or "the implementation" should be understood as "at least one / an implementation". The term "some implementations" should be understood as "at least some implementations". Other explicit and implicit definitions may also be included below.

[0027] As mentioned earlier, degradation refers to reducing the specific functions or performance of a computer system or service to ensure its basic availability and stability when facing load pressure, failures, or other abnormal conditions. Degradation verification refers to verifying the effectiveness of degradation, such as intentionally triggering the system's degradation mechanism under preset conditions or specific scenarios to confirm whether the system can be successfully downgraded and whether the core functions of the system can continue to work normally after the degradation. Existing conventional degradation verification schemes mainly involve users manually initiating degradation tasks and, after the degradation tasks are completed, manually initiating tasks such as functional testing to verify the effectiveness of the downgraded system. However, this degradation verification scheme usually has the following problems: firstly, users need to perform degradation and verification operations separately, and after degradation recovery, it is usually necessary to manually perform a degradation rollback operation on the system and perform secondary verification to ensure that the system functions are truly restored, which is cumbersome for users. On the other hand, relying on manual methods makes it difficult to avoid operational oversights. For example, due to the cumbersome steps, users may forget to roll back the system to its pre-drill state after verifying the downgrade, which can easily lead to operational risks for the tested system. Thirdly, because the user operation steps are cumbersome and the efficiency of relying on manual methods to run downgrade verification is low, the verification frequency for the tested system is low within a specific verification cycle.

[0028] To address the aforementioned technical problems, this disclosure provides a verification method for system degradation. Figure 1 A schematic diagram of a verification method for system degradation according to an embodiment of this disclosure is shown. Figure 1 As shown, in some embodiments, a user may send a downgrade verification request to the startup server. Upon receiving the downgrade verification request, the startup server performs the target operation on the target system being verified and triggers a target event corresponding to the downgrade verification request for the verification server. Upon receiving the target event, the verification server can send the test scenario and event type included in the target event's parameters to the configuration server. The configuration server determines the functional test task based on the event type and test scenario, and executes the functional test task for the application interface of the target system through the test server. The test server sends the execution result of the functional test task to the verification server, which can determine the downgrade verification result based on the execution result and send it to the user. Figure 2 A schematic diagram illustrating the determination of degradation verification results based on a combination of functional test results and indicator fluctuation trends according to an embodiment of this disclosure is shown. Figure 2As shown, in some embodiments, the configuration server can also call the analysis server to determine the fluctuation trend of the target observation index in the target system after the target event. The analysis server can send the fluctuation trend of the target observation index to the verification server for use in conjunction with the execution results of the functional test task to determine the degradation verification result. The advantages of this method are: firstly, users can automatically complete the process from system degradation operation to system verification by sending a verification request. This not only greatly simplifies user operation but also reduces the operational risks caused by human error. Secondly, this method can greatly improve the efficiency of degradation verification and reduce the time consumed by a single degradation verification. Therefore, it increases the frequency of degradation verification within a specific verification cycle, greatly improving the ability to detect system degradation faults through degradation verification.

[0029] The following describes the detailed process of this method.

[0030] Figure 3 A flowchart illustrating a verification method for system degradation according to an embodiment of this disclosure is shown. Figure 3 As shown, the method includes at least the following steps:

[0031] Step S301: In response to the user's downgrade verification request for the target system, start the server to perform the target operation corresponding to the downgrade verification request on the target system, and trigger the target event corresponding to the downgrade verification request for the verification server. The parameters of the target event include the test scenario of this verification.

[0032] In step S303, in response to the target event, the verification server sends the event type of the target event and the test scenario to the configuration server; the configuration server, based on the event type and the test scenario, instructs the test server to execute a functional test task for the target system, and the test server sends the execution result of the functional test task to the verification server; the verification server determines the verification result for the downgrade verification request based at least on the execution result.

[0033] First, in step S301, in response to a user's downgrade verification request for the target system, the server is started to perform the target operation corresponding to the downgrade verification request on the target system, and a target event corresponding to the downgrade verification request is triggered for the verification server. The parameters of the target event include the test scenario for this verification. The server is a server that can receive user requests and initiate the verification process for the target system. In different embodiments, the server can specifically be a physical server, a logical server, or a cloud server, or a set of servers composed of the above types; this specification does not limit this.

[0034] In this step, after receiving a downgrade verification request for the target system from a user, the server can perform the target operation corresponding to the downgrade verification request on the target system, and trigger a target event for the verification server corresponding to the downgrade verification request. The target system refers to the application system for which the downgrade verification is targeted, and which implements application functions through or at least partially through software programs. In different embodiments, the target system can be an application system used for different specific businesses or purposes, and this specification does not limit this. The parameters of the target event can indicate the test scenario for this verification. In one embodiment, the test scenario for this verification, as well as other parameters (e.g., the identifier of the user sending the request), can also be determined based on the indication information in the downgrade verification request. In different embodiments, the specific test scenario indicated by the downgrade verification request can be different.

[0035] In different embodiments, the specific downgrade verification request sent by the user for the target system may differ. Figure 4 A schematic diagram of post-downgrade verification according to an embodiment of this disclosure is shown. Figure 4In the illustrated embodiment, the downgrade verification request may include a downgraded verification request. Therefore, after receiving the downgraded verification request sent by the user, the startup server can perform a downgrade operation on the target system and trigger a downgrade event for the verification server based on the downgraded verification request. A downgrade operation refers to an operation that reduces the specific functions or performance of a system. In different specific embodiments, the specific functions or performance targeted by the downgrade operation may differ depending on the target system, and this specification does not impose limitations on this. For example, in one specific embodiment, the target system may be a live video streaming system, and the downgrade operation includes a downgrade operation on the target live streaming room of the live video streaming system, which includes reducing the number of fields in the collected business messages of the target live streaming room. By reducing the number of fields in the business messages, the computational and network resources consumed in collecting and transmitting field information can be greatly reduced, reducing the operating pressure on the live video streaming system. Triggering a downgrade event for the verification server allows the verification server to initiate verification of the downgraded target system. In this embodiment, the room number of the target live streaming room may also be included in the downgrade verification request. The above methods allow users to send a verification request after downgrading, such as to confirm whether the downgrading operation has taken effect and whether the system functions normally.

[0036] Figure 5 A schematic diagram illustrating downgrade recovery verification according to embodiments of the present disclosure is provided. Figure 5 In the illustrated embodiment, the downgrade verification request may include a downgrade recovery verification request. Therefore, after receiving the downgrade recovery verification request sent by the user, the startup server can perform a downgrade rollback operation on the target system and trigger a rollback event for the verification server based on the downgrade recovery verification request. A downgrade rollback operation refers to the operation of restoring the target system from a downgraded state to a normal state. Triggering a rollback event for the verification server allows the verification server to initiate verification of the rolled-back target system. In this way, users can send downgrade rollback verification requests to confirm, for example, whether the downgrade rollback operation has taken effect and whether the rolled-back system functions normally.

[0037] Figure 6 A schematic diagram illustrating pre-downgrade verification according to an embodiment of this disclosure is shown. Figure 6In the illustrated embodiment, the downgrade verification request includes a pre-downgrade verification request. Therefore, after receiving the pre-downgrade verification request from the user, the startup server can perform a no-operation on the target system and trigger a configuration update event for the verification server based on the pre-downgrade verification request. Since in actual production scenarios, as the version or function of the target system iterates, the configuration for verifying the target system is often updated accordingly, triggering a configuration update event for the verification server allows the verification server to initiate verification of the target system before downgrade (i.e., the current version of the target system without the downgrade operation). In this way, users can send a pre-downgrade verification request to, for example, confirm whether the system functions normally before the downgrade operation.

[0038] Then, in step S303, in response to the target event, the verification server can send the event type of the target event and the test scenario to the configuration server. Specifically, the verification server can determine the event type of the target event and the test scenario based on the target event and its event parameters, and send them to the configuration server. To prompt the user that verification has begun, in one embodiment, the verification server can also send a verification trigger success message to the user in response to the target event, such as... Figure 2 As shown.

[0039] After receiving the event type and test scenario, the configuration server can, based on the event type and test scenario, instruct the test server to execute functional test tasks for the target system. Functional test tasks refer to test tasks used to verify whether the various functions of the application system operate as expected. In different embodiments, the functional test tasks for the target system can be different. In one embodiment, it can be a functional test task for the target system's application programming interface (API), or simply an interface test task. In another embodiment, it can be a functional test task for the target system's user interface, or simply a UI (User Interface) test task. In yet another embodiment, it can be a combination of interface test tasks and UI test tasks.

[0040] In different embodiments, the specific method by which the configuration server instructs the test server to execute functional test tasks based on the event type and test scenario can vary. In one embodiment, the configuration server can determine a target test task matching the event type and test scenario from multiple functional test tasks for the application access interface of the target system, and then instruct the test server to execute the target test task. For example, in a specific example, the target event might be a degradation event, and the test scenario might be a high-traffic live stream. The configuration server could determine the target test task matching the degradation event and the high-traffic live stream from multiple functional test tasks for the application access interface of the target system, based on a preset combination of event scenarios and the mapping relationship between them and test tasks. This method automatically matches and executes the test tasks corresponding to the target event and its test scenario, reducing the workload of manually matching test tasks before each verification.

[0041] After the functional test task is completed, the test server can send the execution result of the functional test task to the verification server. The verification server can determine the verification result for the downgrade verification request based at least on the execution result.

[0042] To make the verification results more accurate, in another embodiment, after receiving the event type and test scenario, the configuration server can also, based on the event type and test scenario, instruct the analysis server to determine the fluctuation trend of the target observation indicator for the target system after the target time. The analysis server then sends the fluctuation trend to the verification server. In a specific embodiment, the configuration server can, based on the event type and test scenario, determine the target observation indicator matching the event type and test scenario from multiple observation indicators for the target system, and instruct the analysis server to determine the fluctuation trend of the target observation indicator after the target event. Furthermore, the verification server can determine the verification result for the downgrade verification request based on the execution result and the fluctuation trend. Through these methods, the verification server can combine the test results of the application interfaces of the target system with the observation results of the data indicators of the target system to more accurately verify the operating status of the target system.

[0043] In different embodiments, the target observation metric can also be different specific observation metrics, and this specification does not limit this. In the above embodiment of the degraded field quantity, the target observation metric can be, for example, the total number of business fields collected by the system per unit time. In different embodiments, the specific method by which the verification server determines the verification result can be different. In one example, the verification result can be determined based on the pass rate of the execution result and whether the fluctuation trend is within a predetermined range.

[0044] In one embodiment, after confirming the verification result, the verification server can send the verification result to the user. By sending the verification result, the user can be informed of the result of the verification request, and the user can also initiate other requests related to the current verification request as desired. In another embodiment, the user may, for example, expect to send a pre-downgrade verification request, a post-downgrade verification request, and a downgrade rollback verification request in sequence. Furthermore, for example, after receiving the verification result of the post-downgrade verification request, the user can initiate the post-downgrade verification request.

[0045] Figure 7 A schematic block diagram of a verification system for system degradation according to an embodiment of this disclosure is shown. The system is used to perform, for example... Figure 3 The method shown. (As illustrated) Figure 7 As shown, the system 700 includes:

[0046] Start server 701 and configure it to respond to a user's downgrade verification request for the target system, perform a target operation corresponding to the downgrade verification request for the target system, and trigger a target event for the verification server corresponding to the downgrade verification request. The parameters of the target event include the test scenario of this verification.

[0047] The verification server 702 is configured to, in response to the target event, send the event type of the target event and the test scenario to the configuration server.

[0048] The configuration server 703 is configured to, based on the event type and the test scenario, invoke the test server to execute functional test tasks for the target system;

[0049] The test server 704 is configured to send the execution results of the functional test task to the verification server.

[0050] The verification server 704 is further configured to determine the verification result for the downgrade verification request based at least on the execution result.

[0051] This disclosure also provides an electronic device, including a memory and a processor. The memory stores executable code, and when the processor executes the executable code, it implements, for example... Figure 3 The method shown.

[0052] The following can also be referenced Figure 8 It shows a structural schematic diagram of an electronic device 800 suitable for implementing embodiments of the present application. Figure 8 The electronic device 800 shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0053] like Figure 8 As shown, the electronic device 800 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 801. The aforementioned processing device 801 may be a general-purpose processor, a digital signal processor (DSP), a microprocessor, or a microcontroller, and may further include an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can perform various appropriate actions and processes based on a program stored in read-only memory (ROM) 802 or a program loaded from storage device 808 into random access memory (RAM) 803. RAM 803 also stores various programs and data required for the operation of the electronic device 800. The processing device 801, ROM 802, and RAM 803 are interconnected via a bus 804. An input / output (I / O) interface 805 is also connected to the bus 804.

[0054] Typically, the following devices can be connected to I / O interface 805: input devices 806 including, for example, touchscreens, touchpads, keyboards, mice, etc.; output devices 807 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 808 including, for example, magnetic tapes, hard disks, etc.; and communication devices 809. Communication device 809 allows electronic device 800 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 8 An electronic device 800 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively. Figure 8 Each box shown can represent a device or multiple devices as needed.

[0055] Specifically, according to embodiments of this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device 809, or installed from a storage device 808, or installed from a ROM 802. When the computer program is executed by the processing device 801, it performs the functions defined in the verification method for system degradation provided in embodiments of this application.

[0056] This disclosure also provides a computer-readable storage medium storing a computer program thereon. When the computer program is executed in a computer, it causes the computer to perform the functions provided in the embodiments of this application. Figure 3 The image shows a verification method for system degradation. Figure 9 This is a schematic diagram illustrating a storage medium for implementing an embodiment of this application. For example, such as... Figure 9 As shown, the storage medium 900 can be a non-transitory computer-readable storage medium used to store non-transitory computer-executable instructions 901. When the non-transitory computer-executable instructions 901 are executed by a processor, a system degradation verification method provided in this application embodiment can be implemented. For example, when the non-transitory computer-executable instructions 901 are executed by a processor, one or more steps in the system degradation verification method provided in this application embodiment can be performed. For example, the storage medium 900 can be applied in the above-mentioned electronic device. For example, the storage medium 900 can include the memory in the electronic device. The description of the storage medium 900 can be found in the description of the memory in the embodiments of the electronic device; repeated descriptions will not be repeated here. The specific functions and technical effects of the storage medium 900 can be found in the description of the system degradation verification method provided in this application embodiment; repeated descriptions will not be repeated here.

[0057] It should be noted that the computer-readable medium in the embodiments of this disclosure may be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium may be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a memory card of a smartphone, a storage component of a tablet computer, a portable computer disk, a hard disk of a personal computer, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In the embodiments of this disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In the embodiments of this disclosure, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, wherein computer-readable program code is carried. The transmitted data signal can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. The computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0058] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device. The aforementioned computer-readable medium carries one or more programs, which, when executed by the server, cause the electronic device to implement the system degradation verification method provided in the embodiments of this application.

[0059] Computer program code for performing the operations of embodiments of this disclosure can be written in one or more programming languages ​​or a combination thereof. Programming languages ​​include object-oriented programming languages—such as Java, Smallport, and C++—and conventional procedural programming languages—such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0060] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions. The units described in the embodiments of the present disclosure may be implemented in software or hardware. The names of the units do not necessarily constitute a limitation on the unit itself. The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: Field Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application Standard Products (ASSPs), Systems-on-Chip (SOCs), Complex Programmable Logic Devices (CPLDs), and so on.

[0061] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the embodiments for storage media and computing devices are basically similar to the method embodiments, so they are described more simply; relevant parts can be referred to the descriptions of the method embodiments.

[0062] The above description is merely a preferred embodiment of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described concept. For example, technical solutions formed by substituting the above-described features with (but not limited to) technical features with similar functions disclosed in this disclosure. Furthermore, although the operations are described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in sequential order. In certain environments, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of this disclosure. Certain features described in the context of a single embodiment may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0063] The above detailed embodiments further illustrate the purpose, technical solution, and beneficial effects of the embodiments of the present invention. Although the subject matter has been described using language specific to structural features and / or methodological logic, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are merely illustrative forms of implementing the claims. It should be understood that the above are merely specific embodiments of the present invention and are not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made on the basis of the technical solutions of the present invention should be included within the scope of protection of the present invention.

Claims

1. A verification method for system degradation, comprising: In response to a user's request for downgrade verification of a target system, the server is started to perform a target operation on the target system corresponding to the downgrade verification request, and a target event for the verification server corresponding to the downgrade verification request is triggered, wherein the parameters of the target event include the test scenario of this verification. In response to the target event, the verification server sends the event type of the target event and the test scenario to the configuration server; The configuration server, based on the event type and the test scenario, instructs the test server to execute a functional test task for the target system, and the test server sends the execution result of the functional test task to the verification server. The verification server determines the verification result for the downgrade verification request based at least on the execution result.

2. The method according to claim 1, further comprising: The configuration server, based on the event type and the test scenario, activates the analysis server to determine the fluctuation trend of the target observation index for the target system after the target time, and the analysis server sends the fluctuation trend to the verification server. The verification server determines the verification result for the downgrade verification request based at least on the execution result, including: The verification server determines the verification result for the downgrade verification request based on the execution result and the fluctuation trend.

3. The method according to claim 2, wherein, The configuration server, based on the event type and the test scenario, invokes the analysis server to determine the fluctuation trend of the target observation indicators for the target system after the target event, including: Based on the event type and the test scenario, the configuration server determines the target observation indicator that matches the event type and the test scenario from multiple observation indicators for the target system, and then activates the analysis server to determine the fluctuation trend of the target observation indicator after the target event.

4. The method according to claim 1, wherein, The configuration server, based on the event type and the test scenario, instructs the test server to execute functional test tasks for the target system, including: Based on the event type and the test scenario, the configuration server determines the target test task that matches the event type and the test scenario from multiple functional test tasks for the application access interface of the target system, and then instructs the test server to execute the target test task.

5. The method according to claim 1, wherein, The downgrade verification request includes a downgraded verification request. Receiving a downgrade verification request sent by a user for a target system, performing a target operation corresponding to the downgrade verification request on the target system, and triggering a target event for the verification server corresponding to the downgrade verification request, including: receiving a downgrade verification request sent by a user, performing a downgrade operation on the target system, and triggering a downgrade event for the verification server based on the downgrade verification request.

6. The method according to claim 1, wherein, The downgrade verification request includes a downgrade recovery verification request. The system receives a downgrade verification request sent by a user for a target system, performs a target operation corresponding to the downgrade verification request for the target system, and triggers a target event for the verification server corresponding to the downgrade verification request, including: receiving a downgrade recovery verification request sent by a user, performing a downgrade rollback operation for the target system, and triggering a rollback event for the verification server based on the downgrade recovery verification request.

7. The method according to claim 1, wherein, The downgrade verification request includes a pre-downgrade verification request. The system receives a downgrade verification request sent by a user for a target system, performs a target operation corresponding to the downgrade verification request for the target system, and triggers a target event for the verification server corresponding to the downgrade verification request, including: receiving a pre-downgrade verification request sent by a user, performing a no-operation on the target system, and triggering a configuration update event for the verification server based on the pre-downgrade verification request.

8. The method according to claim 1, further comprising: After confirming the verification result, the verification server sends the verification result to the user.

9. The method according to claim 1, wherein, Invoking the test server to execute functional test tasks for the target system includes: invoking the test server to execute functional test tasks for the application access interface of the target system.

10. The method according to claim 1, wherein, The target system is a video live streaming system, and the degradation operation includes a degradation operation on the target live streaming room of the video live streaming system, which includes reducing the number of fields in the collected business messages of the target live streaming room.

11. A verification system for system degradation, comprising: The server is started and configured to, in response to a user’s downgrade verification request for the target system, perform a target operation corresponding to the downgrade verification request for the target system, and trigger a target event for the verification server corresponding to the downgrade verification request, wherein the parameters of the target event include the test scenario of this verification. The verification server is configured to, in response to the target event, send the event type of the target event and the test scenario to the configuration server. The configuration server is configured to, based on the event type and the test scenario, invoke the test server to execute functional test tasks for the target system; The test server is configured to send the execution results of the functional test task to the verification server; The verification server is further configured to determine the verification result for the downgrade verification request based at least on the execution result.

12. A computer-readable storage medium having a computer program stored thereon, which, when executed in a computer, causes the computer to perform the method of any one of claims 1-10.

13. An electronic device comprising a memory and a processor, wherein the memory stores executable code, and the processor, when executing the executable code, implements the method of any one of claims 1-10.

Images