CN102779094A - Terminal and software exception test method - Google Patents
Terminal and software exception test method Download PDFInfo
- Publication number
- CN102779094A CN102779094A CN2012102991052A CN201210299105A CN102779094A CN 102779094 A CN102779094 A CN 102779094A CN 2012102991052 A CN2012102991052 A CN 2012102991052A CN 201210299105 A CN201210299105 A CN 201210299105A CN 102779094 A CN102779094 A CN 102779094A
- Authority
- CN
- China
- Prior art keywords
- software
- virtual machine
- state
- fault
- testing
- 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.)
- Pending
Links
Images
Landscapes
- Stored Programmes (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention provides a terminal, comprising a running unit, a state detection unit, a state obtaining unit and a fault analysis unit. The running unit is used for running a specified test system through a virtual machine on the terminal, building the specified test environment in the test system, and running software required to be tested in the test environment; the state detection unit is used for detecting the running state of the software; the state obtaining unit is used for obtaining the state information corresponding to the fault when the state detection unit detects that the software has exceptions; and the fault analysis unit is used for analyzing the reason of fault based on the state information corresponding to the fault. Correspondingly, the invention further provides a software exception test method. By the technical scheme provided by the invention, the site of fault can be kept for real-time analysis when the software has exceptions, so that the test efficiency is improved.
Description
Technical field
The present invention relates to the software testing technology field, in particular to a kind of terminal and a kind of software unconventionality testing method.
Background technology
Test to software at present normally occurs on the physical machine, and for the general utility functions property testing, physical machine can satisfy the demands basically; But might cause the abnormality test of software crash, system in case of system halt, blue screen etc. for some, after the generation software and the system failure, fault in-situ can't keep; Need restart physical machine, build test environment again, or even the refitting system, be difficult to reappear once more fault and site environment; Location and solution failure ratio be difficulty, has a strong impact on work efficiency.
Therefore, need a kind of new software unconventionality testing technology, can take place when unusual at software, the retention fault scene is for instant analysis, thereby improved testing efficiency.
Summary of the invention
The present invention just is being based on the problems referred to above, has proposed a kind of new software unconventionality testing technology, can take place when unusual at software, and the retention fault scene is for instant analysis, thereby has improved testing efficiency.
In view of this; The present invention proposes a kind of terminal, comprising: the operation unit is used for the test macro through the operation of the virtual machine on said terminal appointment; In said test macro, build the test environment of appointment, and the software that operation need be tested in said test environment; State detection unit is used to detect the running status of said software; The state acquiring unit is used for detecting said software in said state detection unit status information when obtaining corresponding fault takes place under the unusual situation; The fault analysis unit, status information analyzing failure cause when being used to utilize said fault.
In this technical scheme; Virtual system and environment through using virtual machine to make up are tested software; When having avoided direct use physical machine, the instability of the physical machine that possibly cause, and the unusual or collapse of virtual machine etc.; Then can rebulid new test environment rapidly, thereby improve testing efficiency.Simultaneously, the obtaining of status information (fault in-situ) through to fault the time helps making in view of the above corresponding fault analysis, to confirm failure cause.
In technique scheme, preferably, the step that said state acquiring unit obtains said status information comprises: utilize said virtual machine creating virtual machine snapshot.
In this technical scheme,, can effectively preserve information such as the virtual machine of corresponding time point and test macro wherein, test environment, software operation state, thereby analyze after being convenient to directly analyze or return to corresponding state through creating virtual machine snapshot.
In technique scheme, preferably, said state acquiring unit also is used for: before said software takes place unusually, at least one time point, obtain the run time behaviour information of said virtual machine; And said fault analysis unit also comprises: the recovering state subelement, be used for taking place under the unusual situation at said software, and utilize said run time behaviour information that said virtual machine is returned to corresponding running status, to analyze said failure cause.
In this technical scheme, through obtaining run time behaviour information,, can in time return to corresponding running status such as setting up corresponding virtual machine snapshot, carry out analyzing failure cause thereby be convenient to the technician.
In technique scheme; Preferably, the said run time behaviour information obtained of said state acquiring unit comprise following one of at least or its combination: state, the operating state of said testing software before the original state of said test macro, the original state of said test environment, the operation of said testing software.
In technique scheme; Preferably; Said fault analysis unit also comprises: recover control sub unit, take place under the unusual situation at said software, according to the order of the acquisition time of a plurality of said run time behaviour information; Control said recovering state subelement and successively said virtual machine is returned to corresponding running status, take place once more unusually until said testing software.
In this technical scheme, through carrying out recovering state successively, then can dwindle gradually and scope that definite fault possibly exist, thereby in time find failure cause, solve fault, to improve software test efficient.
According to another aspect of the invention; Also proposed a kind of software unconventionality testing method, having comprised: step 202, through the test macro of the operation of the virtual machine on terminal appointment; In said test macro, build the test environment of appointment, and the software that operation need be tested in said test environment; Step 204, unusual if said software takes place, status information when then obtaining corresponding fault is for analyzing failure cause.
In this technical scheme; Virtual system and environment through using virtual machine to make up are tested software; When having avoided direct use physical machine, the instability of the physical machine that possibly cause, and the unusual or collapse of virtual machine etc.; Then can rebulid new test environment rapidly, thereby improve testing efficiency.Simultaneously, the obtaining of status information (fault in-situ) through to fault the time helps making in view of the above corresponding fault analysis, to confirm failure cause.
In technique scheme, preferably, the step of obtaining said status information comprises: utilize said virtual machine creating virtual machine snapshot.
In this technical scheme,, can effectively preserve information such as the virtual machine of corresponding time point and test macro wherein, test environment, software operation state, thereby analyze after being convenient to directly analyze or return to corresponding state through creating virtual machine snapshot.
In technique scheme, preferably, said step 204 also comprises: before said software takes place unusually, at least one time point, obtain the run time behaviour information of said virtual machine; And unusual if said software takes place, then utilize said run time behaviour information that said virtual machine is returned to corresponding running status, to analyze said failure cause.
In this technical scheme, through obtaining run time behaviour information,, can in time return to corresponding running status such as setting up corresponding virtual machine snapshot, carry out analyzing failure cause thereby be convenient to the technician.
In technique scheme; Preferably, said run time behaviour information comprise following one of at least or its combination: state, the operating state of said testing software before the original state of said test macro, the original state of said test environment, the operation of said testing software.
In technique scheme; Preferably, said step 204 also comprises: when said software takes place when unusual, according to the order of the acquisition time of a plurality of said run time behaviour information; Successively said virtual machine is returned to corresponding running status, take place once more unusually until said testing software.
In this technical scheme, through carrying out recovering state successively, then can dwindle gradually and scope that definite fault possibly exist, thereby in time find failure cause, solve fault, to improve software test efficient.
Through above technical scheme, can take place when unusual at software, the retention fault scene is for instant analysis, thereby improved testing efficiency.
Description of drawings
Fig. 1 shows the block diagram at terminal according to an embodiment of the invention;
Fig. 2 shows the process flow diagram of software unconventionality testing method according to an embodiment of the invention;
Fig. 3 shows the particular flow sheet of software unconventionality testing method according to an embodiment of the invention.
Embodiment
In order more to be expressly understood above-mentioned purpose of the present invention, feature and advantage, the present invention is further described in detail below in conjunction with accompanying drawing and embodiment.Need to prove that under the situation of not conflicting, the application's embodiment and the characteristic among the embodiment can make up each other.
A lot of details have been set forth in the following description so that make much of the present invention; But; The present invention can also adopt other to be different from other modes described here and implement, and therefore, protection scope of the present invention does not receive the restriction of following disclosed specific embodiment.
Fig. 1 shows the block diagram at terminal according to an embodiment of the invention.
As shown in Figure 1; The terminal 100 according to an embodiment of the invention, comprising: operation unit 102 is used for the test macro through the operation of the virtual machine on the said terminal 100 appointment; In said test macro, build the test environment of appointment, and the software that operation need be tested in said test environment; State detection unit 104 is used to detect the running status of said software; State acquiring unit 106 is used for detecting said software in said state detection unit 104 status information when obtaining corresponding fault takes place under the unusual situation; Fault analysis unit 108, status information analyzing failure cause when being used to utilize said fault.
In this technical scheme; Virtual system and environment through using virtual machine to make up are tested software; When having avoided direct use physical machine, the instability of the physical machine that possibly cause, and the unusual or collapse of virtual machine etc.; Then can rebulid new test environment rapidly, thereby improve testing efficiency.Simultaneously, the obtaining of status information (fault in-situ) through to fault the time helps making in view of the above corresponding fault analysis, to confirm failure cause.
In technique scheme, preferably, said state acquiring unit obtain 106 get said status information step comprise: utilize said virtual machine creating virtual machine snapshot.
In this technical scheme,, can effectively preserve information such as the virtual machine of corresponding time point and test macro wherein, test environment, software operation state, thereby analyze after being convenient to directly analyze or return to corresponding state through creating virtual machine snapshot.
In technique scheme, preferably, said state acquiring unit 106 also is used for: before said software takes place unusually, at least one time point, obtain the run time behaviour information of said virtual machine; And said fault analysis unit 108 also comprises: recovering state subelement 1080, be used for taking place under the unusual situation at said software, and utilize said run time behaviour information that said virtual machine is returned to corresponding running status, to analyze said failure cause.
In this technical scheme, through obtaining run time behaviour information,, can in time return to corresponding running status such as setting up corresponding virtual machine snapshot, carry out analyzing failure cause thereby be convenient to the technician.
In technique scheme; Preferably, the said run time behaviour information obtained of said state acquiring unit 106 comprise following one of at least or its combination: state, the operating state of said testing software before the original state of said test macro, the original state of said test environment, the operation of said testing software.
In technique scheme; Preferably; Said fault analysis unit 108 also comprises: recover control sub unit 1082, take place under the unusual situation at said software, according to the order of the acquisition time of a plurality of said run time behaviour information; Control said recovering state subelement 1080 and successively said virtual machine is returned to corresponding running status, take place once more unusually until said testing software.
In this technical scheme, through carrying out recovering state successively, then can dwindle gradually and scope that definite fault possibly exist, thereby in time find failure cause, solve fault, to improve software test efficient.
Fig. 2 shows the process flow diagram of software unconventionality testing method according to an embodiment of the invention.
As shown in Figure 2; Software unconventionality testing method according to an embodiment of the invention comprises: step 202, through the test macro of the operation of the virtual machine on terminal appointment; In said test macro, build the test environment of appointment, and the software that operation need be tested in said test environment; Step 204, unusual if said software takes place, status information when then obtaining corresponding fault is for analyzing failure cause.
In this technical scheme; Virtual system and environment through using virtual machine to make up are tested software; When having avoided direct use physical machine, the instability of the physical machine that possibly cause, and the unusual or collapse of virtual machine etc.; Then can rebulid new test environment rapidly, thereby improve testing efficiency.Simultaneously, the obtaining of status information (fault in-situ) through to fault the time helps making in view of the above corresponding fault analysis, to confirm failure cause.
In technique scheme, preferably, the step of obtaining said status information comprises: utilize said virtual machine creating virtual machine snapshot.
In this technical scheme,, can effectively preserve information such as the virtual machine of corresponding time point and test macro wherein, test environment, software operation state, thereby analyze after being convenient to directly analyze or return to corresponding state through creating virtual machine snapshot.
In technique scheme, preferably, said step 204 also comprises: before said software takes place unusually, at least one time point, obtain the run time behaviour information of said virtual machine; And unusual if said software takes place, then utilize said run time behaviour information that said virtual machine is returned to corresponding running status, to analyze said failure cause.
In this technical scheme, through obtaining run time behaviour information,, can in time return to corresponding running status such as setting up corresponding virtual machine snapshot, carry out analyzing failure cause thereby be convenient to the technician.
In technique scheme; Preferably, said run time behaviour information comprise following one of at least or its combination: state, the operating state of said testing software before the original state of said test macro, the original state of said test environment, the operation of said testing software.
In technique scheme; Preferably, said step 204 also comprises: when said software takes place when unusual, according to the order of the acquisition time of a plurality of said run time behaviour information; Successively said virtual machine is returned to corresponding running status, take place once more unusually until said testing software.
In this technical scheme, through carrying out recovering state successively, then can dwindle gradually and scope that definite fault possibly exist, thereby in time find failure cause, solve fault, to improve software test efficient.
Fig. 3 shows the particular flow sheet of software unconventionality testing method according to an embodiment of the invention.
As shown in Figure 3; According to an embodiment of the invention in the software unconventionality testing method, through virtual machine installation testing operating systems such as VMware Workstation or Microsoft Hyper, initialization test environment; Set up pure system and initial testing environment snapshot; Pressurize, abnormality test such as the limit, carry out snapshot after breaking down and keep on-the-spotly, and carry out fault analysis.
The idiographic flow of this method is following:
Step 302: install virtual machine, and on virtual machine installation testing operating system, set the size such as internal memory, CPU, hard disk of operating system according to the test needs;
Step 304: set up the test macro initial snapshot;
Step 306: build test environment;
Step 308: set up the test environment initial snapshot;
Step 310: dispose testing software;
Step 312: set up the testing software initial snapshot;
Step 314: start and copy screen software records test process;
Step 316: abnormality test is carried out in implementation of test cases;
Step 318: when software or system exception take place, set up the fault in-situ snapshot;
Step 320: judge whether the generation systems collapse,, otherwise get into step 324 if collapse then gets into step 322;
Step 322: get into necessary snapshot point, redeploy test, constantly carry out the convergence test, wherein, can return step 302, step 306, step 310, step 316 or other steps as required;
Step 324 if fault does not cause system crash, then directly utilizes fault in-situ snapshot analysis of failure on-the-spot, if find failure cause, then finishes, otherwise returns step 322, up to finding out the fault occurrence cause.
More than be described with reference to the accompanying drawings technical scheme of the present invention, considered in the correlation technique, owing to use physical machine directly to test; Testing efficiency is low; Therefore, the invention provides a kind of terminal and a kind of software unconventionality testing method, can take place when unusual at software; The retention fault scene is for instant analysis, thereby improved testing efficiency.
The above is merely the preferred embodiments of the present invention, is not limited to the present invention, and for a person skilled in the art, the present invention can have various changes and variation.All within spirit of the present invention and principle, any modification of being done, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (10)
1. a terminal is characterized in that, comprising:
The operation unit is used for the test macro through the operation of the virtual machine on said terminal appointment, in said test macro, builds the test environment of appointment, and the software that operation need be tested in said test environment;
State detection unit is used to detect the running status of said software;
The state acquiring unit is used for detecting said software in said state detection unit status information when obtaining corresponding fault takes place under the unusual situation;
The fault analysis unit, status information analyzing failure cause when being used to utilize said fault.
2. terminal according to claim 1 is characterized in that, the step that said state acquiring unit obtains said status information comprises: utilize said virtual machine creating virtual machine snapshot.
3. terminal according to claim 1 and 2 is characterized in that, said state acquiring unit also is used for: before said software takes place unusually, at least one time point, obtain the run time behaviour information of said virtual machine; And
Said fault analysis unit also comprises: the recovering state subelement, be used for taking place under the unusual situation at said software, and utilize said run time behaviour information that said virtual machine is returned to corresponding running status, to analyze said failure cause.
4. terminal according to claim 3 is characterized in that, the said run time behaviour information that said state acquiring unit obtains comprise following one of at least or its combination:
State, the operating state of said testing software before the original state of said test macro, the original state of said test environment, the operation of said testing software.
5. terminal according to claim 3 is characterized in that, said fault analysis unit also comprises:
Recover control sub unit; Take place under the unusual situation at said software; According to the order of the acquisition time of a plurality of said run time behaviour information, control said recovering state subelement and successively said virtual machine is returned to corresponding running status, take place once more unusually until said testing software.
6. a software unconventionality testing method is characterized in that, comprising:
Step 202 through the test macro of the operation of the virtual machine on terminal appointment, is built the test environment of appointment in said test macro, and the software that operation need be tested in said test environment;
Step 204, unusual if said software takes place, status information when then obtaining corresponding fault is for analyzing failure cause.
7. software unconventionality testing method according to claim 6 is characterized in that, the step of obtaining said status information comprises: utilize said virtual machine creating virtual machine snapshot.
8. according to claim 6 or 7 described software unconventionality testing methods, it is characterized in that said step 204 also comprises:
Before said software takes place unusually, at least one time point, obtain the run time behaviour information of said virtual machine; And
If said software takes place unusual, then utilize said run time behaviour information that said virtual machine is returned to corresponding running status, to analyze said failure cause.
9. software unconventionality testing method according to claim 8 is characterized in that, said run time behaviour information comprise following one of at least or its combination:
State, the operating state of said testing software before the original state of said test macro, the original state of said test environment, the operation of said testing software.
10. software unconventionality testing method according to claim 8 is characterized in that, said step 204 also comprises:
When said software takes place when unusual, the order according to the acquisition time of a plurality of said run time behaviour information returns to corresponding running status with said virtual machine successively, takes place once more unusually until said testing software.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2012102991052A CN102779094A (en) | 2012-08-21 | 2012-08-21 | Terminal and software exception test method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2012102991052A CN102779094A (en) | 2012-08-21 | 2012-08-21 | Terminal and software exception test method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102779094A true CN102779094A (en) | 2012-11-14 |
Family
ID=47124012
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2012102991052A Pending CN102779094A (en) | 2012-08-21 | 2012-08-21 | Terminal and software exception test method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102779094A (en) |
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103546341A (en) * | 2013-10-14 | 2014-01-29 | 广东电网公司信息中心 | Automatic setup method of test environment |
| CN103902351A (en) * | 2012-12-28 | 2014-07-02 | 鸿富锦精密工业（深圳）有限公司 | Virtual machine operation system and virtual machine operation method |
| CN104331372A (en) * | 2014-11-27 | 2015-02-04 | 北京奇艺世纪科技有限公司 | Method and device for performing remote problem positioning on application program |
| CN104503772A (en) * | 2014-11-21 | 2015-04-08 | 北京奇虎科技有限公司 | Operating system installation and test environment establishment method and device based on virtual machine |
| CN104614601A (en) * | 2014-12-26 | 2015-05-13 | 惠州Tcl移动通信有限公司 | Terminal fault positioning method, device and system |
| CN104750537A (en) * | 2013-12-31 | 2015-07-01 | 腾讯科技（深圳）有限公司 | Test case execution method and device |
| CN105117346A (en) * | 2015-09-24 | 2015-12-02 | 上海爱数软件有限公司 | Automatic testing method and system for distributed system of virtualization platform |
| WO2016061941A1 (en) * | 2014-10-24 | 2016-04-28 | 中兴通讯股份有限公司 | Exception handling method and device, and storage medium |
| CN106598594A (en) * | 2016-12-14 | 2017-04-26 | 捷开通讯(深圳)有限公司 | Test system and method for quickly restoring test program |
| CN107391358A (en) * | 2016-05-17 | 2017-11-24 | 大唐移动通信设备有限公司 | A kind of method for processing abnormal data and system |
| CN107577591A (en) * | 2016-07-05 | 2018-01-12 | 中兴通讯股份有限公司 | A kind of method, apparatus and system of automatic test abnormal protection |
| CN107844420A (en) * | 2017-10-27 | 2018-03-27 | 南京国电南自电网自动化有限公司 | A kind of dichotomy in-circuit emulation and error-checking method based on virtual machine snapshot |
| CN108920375A (en) * | 2018-07-11 | 2018-11-30 | 郑州云海信息技术有限公司 | A kind of software method for testing pressure, device, equipment and storage medium |
| CN111382079A (en) * | 2020-03-16 | 2020-07-07 | 北京云宽志业网络技术有限公司 | Method, device and equipment for restoring application program on site and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101458653A (en) * | 2009-01-06 | 2009-06-17 | 浪潮齐鲁软件产业有限公司 | Automatic test method for tax controller of cash register |
| CN102521128A (en) * | 2011-12-08 | 2012-06-27 | 华中科技大学 | Software fault tolerance method facing cloud platform |
| CN102637144A (en) * | 2012-03-31 | 2012-08-15 | 奇智软件（北京）有限公司 | System fault processing method and device |
-
2012
- 2012-08-21 CN CN2012102991052A patent/CN102779094A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101458653A (en) * | 2009-01-06 | 2009-06-17 | 浪潮齐鲁软件产业有限公司 | Automatic test method for tax controller of cash register |
| CN102521128A (en) * | 2011-12-08 | 2012-06-27 | 华中科技大学 | Software fault tolerance method facing cloud platform |
| CN102637144A (en) * | 2012-03-31 | 2012-08-15 | 奇智软件（北京）有限公司 | System fault processing method and device |
Cited By (22)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103902351A (en) * | 2012-12-28 | 2014-07-02 | 鸿富锦精密工业（深圳）有限公司 | Virtual machine operation system and virtual machine operation method |
| CN103546341A (en) * | 2013-10-14 | 2014-01-29 | 广东电网公司信息中心 | Automatic setup method of test environment |
| CN104750537B (en) * | 2013-12-31 | 2020-07-14 | 腾讯科技（深圳）有限公司 | Method and device for executing test case |
| CN104750537A (en) * | 2013-12-31 | 2015-07-01 | 腾讯科技（深圳）有限公司 | Test case execution method and device |
| WO2016061941A1 (en) * | 2014-10-24 | 2016-04-28 | 中兴通讯股份有限公司 | Exception handling method and device, and storage medium |
| CN104503772A (en) * | 2014-11-21 | 2015-04-08 | 北京奇虎科技有限公司 | Operating system installation and test environment establishment method and device based on virtual machine |
| CN104503772B (en) * | 2014-11-21 | 2018-10-12 | 北京奇虎科技有限公司 | The method and apparatus that operating system installation based on virtual machine, test environment are built |
| CN104331372B (en) * | 2014-11-27 | 2017-08-25 | 北京奇艺世纪科技有限公司 | A kind of method and device that long-range positioning problems are carried out to application program |
| CN104331372A (en) * | 2014-11-27 | 2015-02-04 | 北京奇艺世纪科技有限公司 | Method and device for performing remote problem positioning on application program |
| CN104614601B (en) * | 2014-12-26 | 2019-02-15 | 惠州Tcl移动通信有限公司 | A kind of terminal fault localization method, apparatus and system |
| CN104614601A (en) * | 2014-12-26 | 2015-05-13 | 惠州Tcl移动通信有限公司 | Terminal fault positioning method, device and system |
| CN105117346A (en) * | 2015-09-24 | 2015-12-02 | 上海爱数软件有限公司 | Automatic testing method and system for distributed system of virtualization platform |
| CN107391358A (en) * | 2016-05-17 | 2017-11-24 | 大唐移动通信设备有限公司 | A kind of method for processing abnormal data and system |
| CN107391358B (en) * | 2016-05-17 | 2020-08-28 | 大唐移动通信设备有限公司 | Abnormal data processing method and system |
| CN107577591A (en) * | 2016-07-05 | 2018-01-12 | 中兴通讯股份有限公司 | A kind of method, apparatus and system of automatic test abnormal protection |
| CN106598594A (en) * | 2016-12-14 | 2017-04-26 | 捷开通讯(深圳)有限公司 | Test system and method for quickly restoring test program |
| CN106598594B (en) * | 2016-12-14 | 2020-09-01 | 捷开通讯(深圳)有限公司 | Test system and method for rapidly recovering test program |
| CN107844420A (en) * | 2017-10-27 | 2018-03-27 | 南京国电南自电网自动化有限公司 | A kind of dichotomy in-circuit emulation and error-checking method based on virtual machine snapshot |
| CN107844420B (en) * | 2017-10-27 | 2020-08-28 | 南京国电南自电网自动化有限公司 | Binary online simulation and error checking method based on virtual machine snapshot |
| CN108920375A (en) * | 2018-07-11 | 2018-11-30 | 郑州云海信息技术有限公司 | A kind of software method for testing pressure, device, equipment and storage medium |
| CN111382079A (en) * | 2020-03-16 | 2020-07-07 | 北京云宽志业网络技术有限公司 | Method, device and equipment for restoring application program on site and storage medium |
| CN111382079B (en) * | 2020-03-16 | 2021-08-24 | 北京云宽志业网络技术有限公司 | Method, device and equipment for restoring application program on site and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102779094A (en) | Terminal and software exception test method | |
| EP3036633B1 (en) | Cloud deployment infrastructure validation engine | |
| CN106201892B (en) | Abnormal interrupt source position finding and detection method for embedded software | |
| CN104182288A (en) | Method for automatically testing power consumption of server cluster system | |
| CN102279787B (en) | Method and device for testing average fault-free time | |
| CN102571498B (en) | Fault injection control method and device | |
| CN103473162A (en) | Reliability evaluation system design method based on software fault injection | |
| CN102810073B (en) | Background real-time monitoring processing method for data | |
| CN102521098B (en) | Processing method and processing device for monitoring dead halt of CPU (Central Processing Unit) | |
| CN104572422A (en) | Memory monitoring achievement method based on startup and shutdown of Linux system | |
| CN102937932A (en) | Automated testing device and method of integrated heterogeneous testing tool | |
| CN101930308A (en) | Method and device for resetting drive circuit of touch input device | |
| CN113064762B (en) | Service self-recovery method based on various detection | |
| CN103294575A (en) | Test system and test method | |
| CN101216792A (en) | Real-time operating system tasks management process, device and real-time operating system | |
| CN104572428A (en) | Complicated control testing method based on windows operating system | |
| CN101192971B (en) | Detection method for master/slave data consistency | |
| CN105630664B (en) | Reverse debugging method and device and debugger | |
| CN103701651A (en) | Disaster recovery device and method for application service under domestic environment | |
| CN104750537B (en) | Method and device for executing test case | |
| JP4973205B2 (en) | Information processing apparatus, log acquisition method, and program | |
| CN101706752B (en) | Method and device for in-situ software error positioning | |
| CN112367186B (en) | Fault protection method and device based on 0penStack bare computer | |
| CN105786679A (en) | Automatic test monitoring system and method and mobile terminal | |
| JPH07311693A (en) | Debugging system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20121114 |