Actually, what I meant was using try/catch/finally in the keyword tests themselves. Build into the tests exception handling and such that they can cleanly exit out when desired so that your script code can continue.
Yeah that setting is set to False (most of those are). I'm currently in TestComplete 12.
Are Try/Catch/Finally valid operators in VBscript? I was under the impression that they were not. Although that would probably be the easiest option to catch the error if I could just do
Try
KeywordTests.TestName.Run
Catch
<error handling>
But I was under the impression that those were not valid operations for VBscript.
Or are you talking about enclosing the actions of the keyword test itself in a Try/Catch using the TestComplete Methods?
Actually, what I meant was using try/catch/finally in the keyword tests themselves. Build into the tests exception handling and such that they can cleanly exit out when desired so that your script code can continue.
i Ag3nt49
I've recently been looking into doing something quite similar. In some cases I find one KWT is a prerequisite for the next, but just because KWT 1 failed, doesn't mean I can't run KWT 3 - I just want to skip over KWT 2
The approach I'm using is to always have my KWTs themselves return a true/false
The entrie KWT is in a Try/Catch/Finally structure.
If it falls through to the catch, you will obviously return false
If it reaches finally you will have to figure out if you want to return a true or a false. Sometimes I use a KWT level boolean variable and if, say halfway through my KWT an object recognition fails, the variable is set to false and I insert a Go To Label. The Finally block can then return the value of the global variable.
When you call the KWT from a script, you should now be able to assign the output of the KWT.Run() to a variable.
e.g.
var kw1tpassed = KWT1.Run();
if(kwt1passed)
{
KWT2.Run();
}
else
{
Log.Warning("KWT1 failed. Check your logs");
}
KWT3.Run();
