03-08-2011, 09:46 PM
From your original question, I thought maybe you wanted to see the error conditions (by breaking when the error occurs) but then you would stop/exit that particular script. If you want to run the rest of the test after you get a chance to examine the condition of the app under test when the error occurs, you could use the Command tab of the Debug window to manually re-enable your recovery scenario, then run your test from where it stopped. Put the code that disables the recovery scenario into a function named something like "DisableRecoveryScenario" (name doesn't matter) that you can call and give it one parameter named something like "status" (the name doesn't matter) and make it a boolean.
Change the code to use the parameter value instead of hard-coded "disable=true" :
When you're ready to re-enable your recovery scenario, call this function manually by going to the Debug window,click on the Command tab, and type: call DisableRecoveryScenario(false)
This should call your function and re-enable your recovery scenario.
If you want to automatically re-enable your recovery scenario without any manual intervention, I'm not sure how to do that. I'd have to think about it awhile, but I thought that you wanted the script to pause until you could look at the problem and the state of the universe, then pick up your script from where it stopped and continue on with the test once you understand the cause of the error.
Change the code to use the parameter value instead of hard-coded "disable=true" :
Code:
TestRecovery.Item(intIndex).Disabled = Parameter("status")
When you're ready to re-enable your recovery scenario, call this function manually by going to the Debug window,click on the Command tab, and type: call DisableRecoveryScenario(false)
This should call your function and re-enable your recovery scenario.
If you want to automatically re-enable your recovery scenario without any manual intervention, I'm not sure how to do that. I'd have to think about it awhile, but I thought that you wanted the script to pause until you could look at the problem and the state of the universe, then pick up your script from where it stopped and continue on with the test once you understand the cause of the error.