The idea is quite simple, being able to pause a test that is running in TestExecute. I know that you're supposed to be debugging in Testcomplete and that it's so people don't get licenses of TestExec...
Dmitry_Nikolaev. I posted this a long time ago and of course there are ways around this. But it's was a productivity issue. We run our tests on virtual machines, they should all be the same, but Windows being Windows, they are not, so debugging environments is something that has to be done. When you want to run a diagnostic on an environment in the middle of a regression test that lasts hours, you either lose your test run or wait... Hitting a pause button would be so simple I can't believe you think it's not an issue.
Also, all our tests are designed to reset the environment to it's original state (even the tested application). So if you find a bug and want to see details about the environment at at a certain point, you can't pause the test to do so. You have to go install TestComplete on those machines or try to rerun the steps manually which can be very long.
Another one, is when random messages appear for things like Windows updates, Java updates, Adobe updates or any other random crap that can happen. You want to be able to dismiss these and clear out any open windows so that the test run can continue. Again, you either stop the test and start over you have the tests fail because of overlapping stuff. Normally not such of an issue, but when it's the last line of tests on release dates, this is time consuming on an already overbooked date.
I can find more, but I'm not the one that deals daily with this anymore.