Hi,
OnStopTest event (https://support.smartbear.com/testcomplete/docs/reference/events/onstoptest.html) seems to be what you are looking for...
Thanks!
I think try catch wasnt ideal because it doesn't guarantee that the test will end in the try block, so it can't reach catch/finally.
I can put the entire code inside a try block, but I feel that's a bigger sin. The event based solution seems perfect. Its just unfortunate it only works when you add "Events => GeneralEvents" onto the project itself.
On top of that I also had to add:
function GeneralEvents_OnStopTest(Sender)
{
Common.openUrl("http://localhost:1337/next")
}Wrapping all the code in a test case in a "try" block is actually not a bad idea... what happens if something unexpected happens during the execution of your test code? The "try" will catch anything unexpected... So, that's really a pretty good practice there.
As to your "unfortunate"... that's the way events work.... you want code to execute to "handle" an event, you first need to tell the project what events to "handle"... that's what the "GeneralEvents" does...
Yeah it'd be nice if they expose the event names so we can act upon it.
Can't I just tell it what events to handle inside the code ? It works like other frameworks out there where its like button.on('click') where click is just a built in event. So if I say onStopTest in the code, the code should just compile and add a listener for the stop event automatically...
I think the try block may be stylistic preference. Actually I'd be surprised if I manually stop the run manually if it will even run the 'finally' block at all, since the code executions just stops. But I can test that out for the curiosity.
I tested it. Finally does indeed run.
Now that I think more about it a try/catch/finally block may seem like better candidates than events since this is one of those 'if anything unexpected happen' situations.
Hrmmmm. Thanks everyone for the input! Ill ponder about it more.
