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...
- JuliaBernikova , yes it is correct that someone would need to press the "pause" button and then "resume".
- Yes, we have automation tools such as Jenkins to schdule jobs. All our automated tests are called by this tool.
- Yes we can rerun failed tests and do if needed.
- No we don't necessarily need the log to know that there is a problem.
I think that BenoitB put it very well, but I'll recap with more information. There are some instances where you know there is a problem with the environement or there is a scheduled maintenance. To add further to my above examples, there are some maintenances that you can't schedule around like an unplanned security patch. We know of these only a few hours before they happen. Also, sometimes as service will fail on an application and to mitigate the issse you have to reboot the entire server with multiple applications on it. Another example would be a known maintenance window, but you don't want to schedule all your tests around this window, so it would be easier just to pause what is running during that window and simply start it back up again after.