Forum Discussion

johnmclaughlin's avatar
johnmclaughlin
Contributor
14 years ago

Accounting for errors during long test runs.

My project runs a series of tests that key on policies into a web based administration system. Each test is data driven and can take a few hours to finish so i usually leave the test to run over night. Because the administration system is still unfinished there are often a few problems that stop the running of the tests and leave it unfinished.



Is there a way that I can get the test to return to a familiar screen, if the test is stopped, and then continue with the next record in my data sheet.

1 Reply

  • AlexeyKolosov's avatar
    AlexeyKolosov
    Icon for Staff rankStaff
    14 years ago

    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.