Accounting for errors during long test runs.

Hi John,





There is no general solution for this, because the specific logic depends solely on your tests. The only thing I can recommend is to create a number of "checkpoints", that is, to store information on passed steps in a file on your disk. When your test is stopped and re-started, it will be possible to read the file and thus to find out which state of the application should be restored. However, implementing such logic can require much efforts. In addition, you'll need to find a way to track when TestComplete is stopped and re-start the tool. The most general solution for this is to use an external process to track TestComplete's process and to re-launch the tool if TestComplete is closed.