CN115952080B - Agent limit condition stability test method and device - Google Patents

Agent limit condition stability test method and device Download PDF

Info

Publication number
CN115952080B
CN115952080B CN202211550799.2A CN202211550799A CN115952080B CN 115952080 B CN115952080 B CN 115952080B CN 202211550799 A CN202211550799 A CN 202211550799A CN 115952080 B CN115952080 B CN 115952080B
Authority
CN
China
Prior art keywords
limit
test
environment
agent
operating systems
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202211550799.2A
Other languages
Chinese (zh)
Other versions
CN115952080A (en
Inventor
姜向前
耿兴龙
姚纪卫
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Anxin Wangdun Beijing Technology Co ltd
Original Assignee
Anxin Wangdun Beijing Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Anxin Wangdun Beijing Technology Co ltd filed Critical Anxin Wangdun Beijing Technology Co ltd
Priority to CN202211550799.2A priority Critical patent/CN115952080B/en
Publication of CN115952080A publication Critical patent/CN115952080A/en
Application granted granted Critical
Publication of CN115952080B publication Critical patent/CN115952080B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Landscapes

  • Automatic Analysis And Handling Materials Therefor (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The application discloses a method and a device for testing the stability of the limit condition of a reagent, wherein the method comprises the following steps: acquiring limit strategies of a plurality of operating systems, wherein the limit strategies comprise implementation scripts corresponding to a plurality of limit scenes; sequentially reducing a plurality of operating systems to a baseline environment respectively, and constructing the environment according to a limit strategy corresponding to the operating systems; testing the stability of the agent if the environment is constructed successfully; and if the environment construction fails, restoring the operating system to the baseline environment again, and carrying out environment construction again. The combination of different limit scenes and abnormal scenes is covered to the greatest extent, so that the test of the agent in different operating systems under the limit condition is realized, the function of the agent before delivery is more perfect, and the probability of the agent affecting the client computer system is further reduced.

Description

Agent limit condition stability test method and device
Technical Field
The application relates to the technical field of software testing, in particular to a method and a device for testing the stability of a reagent limit condition.
Background
On the client side, it is easy to trigger extreme scenarios under certain conditions, and some applications of part of the computer system may therefore be affected. If the testing stage fails to cover more extreme scenes, the potential problems of the agent itself are not exposed before the agent is delivered to the client, and the problem can be exploded at the client side, so that the agent itself has some function anomalies, the client computer system is possibly shut down or restarted, the web and other business anomalies on the computer system are possibly caused, and irreversible loss can be brought to the client due to the above results, so that the testing coverage of the agent extreme scenes and abnormal scenes is particularly important. The conventional test method comprises the following steps:
the method 1 is characterized in that the method is manually constructed, and all construction operations are manually executed for scenes such as excessively low CPU resource residues, excessively low memory resource residues, or network IO high concurrency scenes, sudden power failure and the like, wherein many scenes cannot be manually constructed, so that test coverage of extreme scenes is lacking, the method is insufficient from the aspect of test integrity, the scenes cannot be reused each time from the aspect of test cost, and the cost is high.
And 2, compiling corresponding environment construction scripts, executing different script construction scenes before each test, and then executing the test related to the agent. After each test, the operating system needs to be manually restored to perform the next time, and the specific execution strategies of different operating systems are lacking, and in addition, the extreme scenes are all the coverage of the main scene, so that the effectiveness and completeness of the test are required to be improved.
Based on the above facts, there is a need for an automated testing device that is novel, low-cost, and capable of maximally covering scenes to complete testing of agents under extreme conditions, and to satisfy the combination of different extreme, abnormal scenes in different operating systems,
disclosure of Invention
The embodiment of the application aims to provide a method and a device for testing the stability of the limit conditions of agents, which realize the testing of the agents in different operating systems under the limit conditions by covering the combinations of different limit scenes and abnormal scenes to the greatest extent, so that the functions of the agents before delivery are more perfect, and the probability of the agents affecting a client computer system is further reduced.
In order to solve the above technical problems, a first aspect of the embodiments of the present application provides a method for testing agent limit condition stability, including the following steps:
acquiring limit strategies of a plurality of operating systems, wherein the limit strategies comprise implementation scripts corresponding to a plurality of limit scenes;
sequentially restoring the operating systems to a baseline environment respectively, and constructing an environment according to the limit strategy corresponding to the operating systems;
testing the stability of the agent if the environment is constructed successfully;
and if the environment construction fails, restoring the operating system to the baseline environment again, and carrying out environment construction again.
Further, the agent stability test further includes:
sequentially testing a plurality of test cases of the agent, wherein the plurality of test cases comprise: the agent is provided with an installation test, an upgrading test, an unloading test and a risk reporting test;
if the test cases are tested successfully, judging that the operation system is tested completely, and constructing the environment of the next operation system according to a preset sequence;
if one of the test cases fails, creating a bug corresponding to the test case which fails, and correspondingly adjusting the limit strategy according to the bug.
Further, the adjusting the limit policy according to the bug includes:
and correspondingly adjusting the priority of the limit scene according to the bug, and increasing the test times of the limit scene.
Further, after the configuration fails to restore the operating system to the baseline environment, the method further includes:
and when the frequency of restoring the operating system to the baseline environment is greater than or equal to the preset frequency, sending alarm information.
Further, before the obtaining the limit policies of the operating systems, the method further includes:
writing an implementation script corresponding to a plurality of limit scenes according to the plurality of limit scenes;
the baseline environment for the multiple operating systems is created by python based on an api interface.
Accordingly, a second aspect of the embodiment of the present application provides a reagent limit condition stability testing device, including:
the system comprises a policy acquisition module, a policy generation module and a policy generation module, wherein the policy acquisition module is used for acquiring limit policies of a plurality of operating systems, and the limit policies comprise implementation scripts corresponding to a plurality of limit scenes;
the environment construction module is used for sequentially restoring the plurality of operating systems to a baseline environment respectively and carrying out environment construction according to the limit strategy corresponding to the operating systems;
the test control module is used for testing the stability of the agent when the environment is constructed successfully;
the test control module is also used for restoring the operating system to the baseline environment when the environment construction fails, and carrying out environment construction again.
Further, the test control module includes:
the test unit is used for sequentially testing a plurality of test cases of the agent, and the plurality of test cases comprise: the agent is provided with an installation test, an upgrading test, an unloading test and a risk reporting test;
the control unit is used for judging that the operation system is tested when the test cases are tested successfully, and carrying out environment construction on the next operation system according to a preset sequence;
the control unit is also used for creating a bug corresponding to the test case with the test failure when the test case fails, and correspondingly adjusting the limit strategy according to the bug.
Further, the control unit correspondingly adjusts the priority of the limit scene according to the bug, and increases the test times of the limit scene so as to adjust the limit strategy.
Further, the agent limit condition stability test device further includes:
and the restoration alarm module is used for sending alarm information when the frequency of restoring the operating system to the baseline environment is greater than or equal to the preset frequency.
Further, the agent limit condition stability test device further includes:
the script writing module is used for writing realization scripts corresponding to the plurality of limit scenes according to the plurality of limit scenes;
a baseline environment module for creating the baseline environments of the plurality of operating systems by python based on an api interface.
Accordingly, a third aspect of the embodiment of the present application provides an electronic device, including: at least one processor; and a memory coupled to the at least one processor; the memory stores instructions executable by the one processor, and the instructions are executed by the one processor, so that the at least one processor executes the agent limit condition stability testing method.
Accordingly, a fourth aspect of the embodiments of the present application provides a computer-readable storage medium having stored thereon computer instructions that, when executed by a processor, implement the agent limit case stability test method described above.
The technical scheme provided by the embodiment of the application has the following beneficial technical effects:
the combination of different limit scenes and abnormal scenes is covered to the greatest extent, so that the test of the agent in different operating systems under the limit condition is realized, the function of the agent before delivery is more perfect, and the probability of the agent affecting the client computer system is further reduced.
Drawings
FIG. 1 is a flow chart of a method for testing the stability of a reagent limit condition provided by an embodiment of the application;
FIG. 2 is a logic schematic diagram of a method for testing agent limit condition stability according to an embodiment of the present application;
FIG. 3 is a block diagram of a reagent limit condition stability test device according to an embodiment of the present application;
FIG. 4 is a block diagram of a test control module provided by an embodiment of the present application.
Reference numerals:
1. the system comprises a strategy acquisition module, an environment construction module, a test control module, a test unit, a control unit, a reduction alarm module, a script writing module, a base line environment module and a base line environment module, wherein the strategy acquisition module, the environment construction module, the test control module, the test unit, the control unit, the reduction alarm module, the script writing module and the base line environment module are respectively arranged in sequence.
Detailed Description
The objects, technical solutions and advantages of the present application will become more apparent by the following detailed description of the present application with reference to the accompanying drawings. It should be understood that the description is only illustrative and is not intended to limit the scope of the application. In addition, in the following description, descriptions of well-known structures and techniques are omitted so as not to unnecessarily obscure the present application.
Referring to fig. 1 and 2, a first aspect of the embodiment of the present application provides a method for testing agent limit condition stability, including the following steps:
step S300, obtaining limit strategies of a plurality of operating systems, wherein the limit strategies comprise implementation scripts corresponding to a plurality of limit scenes.
And step S400, sequentially respectively restoring the plurality of operating systems to a baseline environment, and constructing the environment according to a limit strategy corresponding to the operating systems.
Step S500, if the environment construction is successful, the stability of the agent is tested.
Step S600, if the environment construction fails, the operating system is restored to the baseline environment, and the environment construction is performed again.
The agent in the technical scheme is a client software in the operating system, and the client software is used for detecting and intercepting the attack behavior or the risk behavior in the memory of the operating system in real time. According to the technical scheme, the combination of different limit scenes and abnormal scenes is covered to the greatest extent, so that the test of the agent in different operating systems under the limit condition is realized, the function of the agent before delivery is more perfect, and the probability of the agent affecting the client computer system is further reduced. Specifically, the above limit conditions may be: the occupation rate of the host CPU of the operating system exceeds a preset proportion value (for example, 90%), the processes of the operating system exceed a preset number and the like, and the two types of the occupation rate and the processes of the operating system only use the limit condition for example, the limit condition in the technical scheme is not limited to the above-mentioned condition, and other conditions which can cause the operating system to run slowly, crash or restart all belong to the above-mentioned limit condition.
Specifically, the stability test of the agent in step S500 includes the following steps:
step S510, testing a plurality of test cases of the agent in sequence, where the plurality of test cases includes: the method comprises the steps of agent installation test, upgrade test, uninstall test and risk report test.
And step S520, if the test cases are tested successfully, judging that the operation system is tested completely, and constructing the environment of the next operation system according to a preset sequence.
In step S530, if a test case fails, a bug corresponding to the test case failing in the test is created, and the limit policy is adjusted accordingly according to the bug.
Further, in step S530, the limit policy is adjusted according to the bug, specifically: and correspondingly adjusting the priority of the limit scene according to the bug, and increasing the test times of the limit scene to adjust the limit strategy.
Specifically, after the configuration failure in step S520 restores the operating system to the baseline environment again, the method further includes:
in step S521, when the number of times of restoring the operating system to the baseline environment is greater than or equal to the preset number of times, the alarm information is sent.
Further, before acquiring the limit policies of the multiple operating systems in step S300, the method further includes:
and step S100, writing an implementation script corresponding to the plurality of limit scenes according to the plurality of limit scenes.
Step S200, based on the api interface, creating a baseline environment of a plurality of operating systems through python.
Referring to fig. 2, the following describes the agent limit stability test method in detail according to an embodiment of the present application:
firstly, writing an implementation script corresponding to the limit scene structure according to the limit scenes after carding and alignment.
Second, an api interface is written and a baseline environment for a plurality of different operating systems is created via python scripts based on the api interface.
Thirdly, pulling limit strategies (comprising a plurality of limit scenes) corresponding to a plurality of different systems and realization scripts corresponding to the limit scenes from a server; in addition, the priority of the limit scene is automatically adjusted according to the bug information found in the test process, and the execution times of the scene are increased to adjust the limit strategy.
And fourthly, restoring the operating system to the baseline environment by utilizing the api interface.
And fifthly, constructing the environment according to the baseline strategy, if the construction fails, re-executing the fourth step, and if the repeated execution fails for three times, sending alarm information to the testers. After the construction is successful, the installation test, the unloading test, the risk execution test and the reporting test of the agent can be executed, and when the use case fails to be executed, the bug is automatically created, and the warning information is automatically sent by utilizing enterprise WeChat and the like to inform the testers.
And sixthly, circularly traversing a plurality of limit scenes in the operating system, wherein each scene is executed according to the step 5.
And seventhly, after the operating system is executed, performing cycle traversal of other operating systems, and executing a sixth step each time of cycle until all the systems are subjected to cycle traversal test.
And eighth, after all scene structures are executed, recovering the system.
Accordingly, referring to fig. 3, a second aspect of the present application provides a reagent limit condition stability testing device, including:
the system comprises a strategy acquisition module 1, a control module and a control module, wherein the strategy acquisition module is used for acquiring limit strategies of a plurality of operating systems, and the limit strategies comprise implementation scripts corresponding to a plurality of limit scenes;
the environment construction module 2 is used for sequentially restoring the plurality of operating systems to a baseline environment respectively and constructing the environment according to a limit strategy corresponding to the operating systems;
a test control module 3 for testing the stability of the agent when the environment construction is successful;
the test control module 3 is also used to restore the operating system to the baseline environment when the environment construction fails, and to perform the environment construction again.
Further, referring to fig. 4, the test control module 3 includes:
a test unit 31, configured to test a plurality of test cases of the agent in sequence, where the plurality of test cases includes: the method comprises the steps of agent installation test, upgrade test, uninstall test and risk report test;
a control unit 32, configured to determine that the operating system is tested and perform environmental construction on the next operating system according to a preset sequence when all the plurality of test cases are tested successfully;
the control unit 32 is further configured to create a bug corresponding to a test case with a test failure when the test case fails, and adjust the limit policy according to the bug.
Further, the control unit 32 adjusts the priority of the limit scene according to the bug, and increases the number of tests of the limit scene to adjust the limit policy.
Further, the agent limit condition stability test device further includes:
and the restoration alarm module 4 is used for sending alarm information when the number of times of restoring the operating system to the baseline environment is greater than or equal to the preset number of times.
Further, the agent limit condition stability test device further includes:
the script writing module 5 is used for writing realization scripts corresponding to the plurality of limit scenes according to the plurality of limit scenes;
a baseline environment module 6 for creating a baseline environment for multiple operating systems via python based on the api interface.
According to the agent limit condition stability testing device, the combination of different limit scenes and abnormal scenes is covered to the greatest extent, so that the agent in different operating systems can be tested under the limit condition, the function of the agent before delivery is more perfect, and the probability of the agent affecting a client computer system is further reduced.
Accordingly, a third aspect of the embodiment of the present application provides an electronic device, including: at least one processor; and a memory coupled to the at least one processor; the memory stores instructions executable by one processor, and the instructions are executed by one processor, so that at least one processor executes the agent limit condition stability testing method.
Accordingly, a fourth aspect of the embodiments of the present application provides a computer-readable storage medium having stored thereon computer instructions that, when executed by a processor, implement the agent limit case stability test method described above.
The embodiment of the application aims to protect a method and a device for testing the stability of the limit condition of a agent, wherein the method comprises the following steps: acquiring limit strategies of a plurality of operating systems, wherein the limit strategies comprise implementation scripts corresponding to a plurality of limit scenes; sequentially reducing a plurality of operating systems to a baseline environment respectively, and constructing the environment according to a limit strategy corresponding to the operating systems; testing the stability of the agent if the environment is constructed successfully; and if the environment construction fails, restoring the operating system to the baseline environment again, and carrying out environment construction again. The technical scheme has the following effects:
the combination of different limit scenes and abnormal scenes is covered to the greatest extent, so that the test of the agent in different operating systems under the limit condition is realized, the function of the agent before delivery is more perfect, and the probability of the agent affecting the client computer system is further reduced.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Finally, it should be noted that: the above embodiments are only for illustrating the technical aspects of the present application and not for limiting the same, and although the present application has been described in detail with reference to the above embodiments, it should be understood by those of ordinary skill in the art that: modifications and equivalents may be made to the specific embodiments of the application without departing from the spirit and scope of the application, which is intended to be covered by the claims.

Claims (8)

1. The agent limit condition stability test method is characterized by comprising the following steps:
acquiring limit strategies of a plurality of operating systems, wherein the limit strategies comprise implementation scripts corresponding to a plurality of limit scenes;
sequentially restoring the operating systems to a baseline environment respectively, and constructing an environment according to the limit strategy corresponding to the operating systems;
testing the stability of the agent if the environment is constructed successfully;
restoring the operating system to the baseline environment if the environment construction fails, and constructing the environment again;
the agent stability test further comprises:
sequentially testing a plurality of test cases of the agent, wherein the plurality of test cases comprise: the agent is provided with an installation test, an upgrading test, an unloading test and a risk reporting test;
if the test cases are tested successfully, judging that the operation system is tested completely, and constructing the environment of the next operation system according to a preset sequence;
if one of the test cases fails, creating a bug corresponding to the test case which fails, and correspondingly adjusting the limit strategy according to the bug.
2. The agent limit case stability test method according to claim 1, wherein the adjusting the limit policy according to the bug comprises:
and correspondingly adjusting the priority of the limit scene according to the bug, and increasing the test times of the limit scene to adjust the limit strategy.
3. The agent limit case stability test method of claim 1, further comprising, after restoring the operating system to the baseline environment if the environment configuration fails:
and when the frequency of restoring the operating system to the baseline environment is greater than or equal to the preset frequency, sending alarm information.
4. The agent limit case stability test method according to any one of claims 1-3, further comprising, before the acquiring the limit policies of the plurality of operating systems:
writing an implementation script corresponding to a plurality of limit scenes according to the plurality of limit scenes;
the baseline environment for the multiple operating systems is created by python based on an api interface.
5. Agent limit condition stability testing arrangement, characterized in that includes:
the system comprises a policy acquisition module, a policy generation module and a policy generation module, wherein the policy acquisition module is used for acquiring limit policies of a plurality of operating systems, and the limit policies comprise implementation scripts corresponding to a plurality of limit scenes;
the environment construction module is used for sequentially restoring the plurality of operating systems to a baseline environment respectively and carrying out environment construction according to the limit strategy corresponding to the operating systems;
the test control module is used for testing the stability of the agent when the environment is constructed successfully;
the test control module is also used for restoring the operating system to the baseline environment when the environment construction fails, and carrying out environment construction again;
the test control module includes:
the test unit is used for sequentially testing a plurality of test cases of the agent, and the plurality of test cases comprise: the agent is provided with an installation test, an upgrading test, an unloading test and a risk reporting test;
the control unit is used for judging that the operation system is tested when the test cases are tested successfully, and carrying out environment construction on the next operation system according to a preset sequence;
the control unit is also used for creating a bug corresponding to the test case with the test failure when the test case fails, and correspondingly adjusting the limit strategy according to the bug.
6. The agent limit case stability test device of claim 5, wherein,
the control unit correspondingly adjusts the priority of the limit scene according to the bug, and increases the test times of the limit scene so as to adjust the limit strategy.
7. The agent limit case stability test device of claim 5, further comprising:
and the restoration alarm module is used for sending alarm information when the frequency of restoring the operating system to the baseline environment is greater than or equal to the preset frequency.
8. The agent limit case stability test device according to any one of claims 5 to 7, further comprising:
the script writing module is used for writing realization scripts corresponding to the plurality of limit scenes according to the plurality of limit scenes;
a baseline environment module for creating the baseline environments of the plurality of operating systems by python based on an api interface.
CN202211550799.2A 2022-12-05 2022-12-05 Agent limit condition stability test method and device Active CN115952080B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211550799.2A CN115952080B (en) 2022-12-05 2022-12-05 Agent limit condition stability test method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211550799.2A CN115952080B (en) 2022-12-05 2022-12-05 Agent limit condition stability test method and device

Publications (2)

Publication Number Publication Date
CN115952080A CN115952080A (en) 2023-04-11
CN115952080B true CN115952080B (en) 2023-08-29

Family

ID=87281541

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211550799.2A Active CN115952080B (en) 2022-12-05 2022-12-05 Agent limit condition stability test method and device

Country Status (1)

Country Link
CN (1) CN115952080B (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5475843A (en) * 1992-11-02 1995-12-12 Borland International, Inc. System and methods for improved program testing
CN104391780A (en) * 2014-10-23 2015-03-04 浪潮电子信息产业股份有限公司 Method for automatically checking stability of power supply redundancy function of server
CN106843965A (en) * 2017-01-20 2017-06-13 郑州云海信息技术有限公司 The system and installation method of a kind of automated installation of system testing tool
CN110471828A (en) * 2018-05-09 2019-11-19 阿里巴巴集团控股有限公司 A kind of operating system testing method, apparatus and its equipment
CN115221030A (en) * 2021-04-15 2022-10-21 网联清算有限公司 Application testing method and device, electronic equipment and storage medium

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5475843A (en) * 1992-11-02 1995-12-12 Borland International, Inc. System and methods for improved program testing
CN104391780A (en) * 2014-10-23 2015-03-04 浪潮电子信息产业股份有限公司 Method for automatically checking stability of power supply redundancy function of server
CN106843965A (en) * 2017-01-20 2017-06-13 郑州云海信息技术有限公司 The system and installation method of a kind of automated installation of system testing tool
CN110471828A (en) * 2018-05-09 2019-11-19 阿里巴巴集团控股有限公司 A kind of operating system testing method, apparatus and its equipment
CN115221030A (en) * 2021-04-15 2022-10-21 网联清算有限公司 Application testing method and device, electronic equipment and storage medium

Also Published As

Publication number Publication date
CN115952080A (en) 2023-04-11

Similar Documents

Publication Publication Date Title
US8806476B2 (en) Implementing a software installation process
US8978015B2 (en) Self validating applications
CN102736978A (en) Method and device for detecting installation status of application program
US7370233B1 (en) Verification of desired end-state using a virtual machine environment
US9411711B2 (en) Adopting an existing automation script to a new framework
US20090204946A1 (en) Intelligent software code updater
CN113094210B (en) Window platform process and file daemon method and system
CN112698846B (en) Method and system for automatically installing patches in Linux system
CN111949292B (en) Hot patch loading method and device, electronic equipment and storage medium
CN111813495A (en) Node testing method and device, storage medium and electronic device
CN113805925A (en) Online upgrading method, device, equipment and medium for distributed cluster management software
US20190147164A1 (en) Novel methodology, process and program for the repair of disabled, badly infected or slow windows computers
CN115952080B (en) Agent limit condition stability test method and device
CN115599645B (en) Method and device for testing stability of linux driving module
CN112579330A (en) Method, device and equipment for processing abnormal data of operating system
CN114116330B (en) Server performance testing method, system, terminal and storage medium
CN113590494B (en) Automatic testing method for cloud native environment vulnerability
CN112596750B (en) Application testing method and device, electronic equipment and computer readable storage medium
CN113986263A (en) Code automation test method, device, electronic equipment and storage medium
CN114546420A (en) Software remote installation protection uninstalling method
CN112560041A (en) Method, apparatus and computer storage medium for automated quality verification detection
CN109032955B (en) UI automation test method, device, equipment and readable storage medium
CN112947948B (en) Deployment method and device of application service
US20230126244A1 (en) Method, electronic device, and computer program product for managing operating system
US8316444B2 (en) Third-party software product certification

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant