转自：http://blog.csdn.net/Testing_is_believing/archive/2010/01/25/5255831.aspx
Tarun Lalwani在这篇文章归纳总结了5种QTP的恢复场景不会被触发的情况：
Why is my Recovery Scenario not getting fired?
http://knowledgeinbox.com/articles/qtp/recovery-scenario/why-is-my-recovery-scenario-not-getting-fired/
Debugging Recovery Scenario (RS) is always been a tough ask. But knowing situations where RS won’t work before hand can be of added
advantage. In this article we will explore various possible scenarios where RS is not fired. We will assume the RS to be fired is “Any Error”
Situation #1 - Script. Errors 脚本中没有涉及到测试对象的情况下，RS是不会被触发的！
Errors NOT involving any Test Object won’t fire any recovery scenario. All the code lines listed below will raise an error but not a RS
X = 2/0
Y = Left("Test", -2)
Situation #2 - Object Not in Object Repository (OR) 对象不在OR中这种错误也不会触发RS的执行！
If you try to access a object from the OR and it does not exist in the OR at all, then QTP will throw an error and RS won’t be fired. Object not
found in object repository error is treated as a Script. error by QTP and is raised directly.
Situation #3 - Modal dialog blocking execution 模式的对话框挡住了执行也不会触发RS的执行！
In case the operation you have performed causes a modal Dialog to appear, RS can’t get fired in such situations. The simplest example of this
the code shown below
Msgbox "You can't fire a Recovery scenario now"
The call to the Msgbox blocks execution in current thread and QTP get busy waiting for someone to close the message box. In such situations
no RS can get executed
Situation #4 - Associated Library is not found 找不到关联的函数库这种错误也不会触发RS的执行！
In case the RS action is to call a Function from a Library file and Library file is not found, the RS will not get triggered.
Situation #5 - Activate Recovery Scenario setting is not configured properly 如果Active Recovery Scenario被设置为“Never”也不会触发RS
Go to File->Settings…->Recovery (Tab)->Activate Recovery Scenario option. If the value is set to ‘Never’ no RS can get fired, in case value is
set to ‘On Error’ then the recovery scenario will only be fired when an error occurs. In case the scenario is not fired change this setting to ‘On Every Step’
