If you were to have Runner.Stop() in OnStartTestCase(), I haven't tried it myself, but I think it will just stop the test execution without running the test case!
Also, if I remember correctly OnStartTestCase() will not be triggered if running tests from Azure DevOps.
You could create a project suite, with projects, and write simple tests that just outputs to the log, with the appropriate event handlers. Run the scripts either individually or using the execution plan, to see the behaviour of how TC runs the automation. Then do the same via your internal tool to see if you get the same behaviour as TC.
Hello rraghvani,
Thanks for the answer,
First of all, just to make sure we understand each other, our internal tool is just a "remote control" to generate a configuration file that will be read by the scripts I coded and that are interpreted by TestComplete. So the test execution is always done by TestComplete, and never by our tool.
Secondly, my concern is not with the running of the events but with the behaviour of the Runner.Stop(true) command when it is interpreted in the OnStartTestCase() event.
This command is supposed to just stop the execution of the current test and it works fine if interpreted in the function associated with the test.
However, when interpreted in the OnStartTestCase() event, it behaves differently by displaying a dialog box indicating that the current test has failed to run and asking whether or not to continue, thus blocking the execution of the project's test suite (similar behaviour to TestExecute).
Hence my original post : is there any way to avoid this blocking behaviour?
Thanks in advance for your help !
A little additional information: if I answer that I want to continue executing the tests in the dialog box that appears, the behaviour is good: the execution goes on to the next test without executing the ignored test by marking it as OK.
The problem is just the appearance of this dialog box...
