There is a capability to re-run failed tests - https://support.smartbear.com/testcomplete/docs/testing-with/running/control-test-flow/stop-and-rerun.html
nitinn Just curious - why rerun the test cases again immediately? Do you think they will pass the second time? Perhaps if we help you look at why they are failing the first time, we can help you catch those problems and you won't need the second pass.
nitinn Just curious - why rerun the test cases again immediately?
I can answer this :)
In our project we have a lot of long tests which run on unstable environments with complicated architecture. It takes about 15 hours to run them all.
We schedule runs at night on several PCs. After the 1st run only 50% of the tests pass. Most of the issues are not related to the AUT functionality, but either environment problems, or unstable script issues. Sometimes we are able to fix our own mistakes, sometimes we are not.
Now, when on the next day we simply rerun all failed tests, 50% of them usually pass. Other may require some tiny fixes. Some of them may fail on one PC, but pass on another. So in general, it is much easier to implement automatic rerun of the failed tests than to try to fix all possible issues :)
karkadil wrote:
nitinn Just curious - why rerun the test cases again immediately?
Now, when on the next day we simply rerun all failed tests, 50% of them usually pass. Other may require some tiny fixes. Some of them may fail on one PC, but pass on another. So in general, it is much easier to implement automatic rerun of the failed tests than to try to fix all possible issues :)
Question: You mention that "on the next day, we rerun all failed tests". Is this an automatic function of your code in TestComplete that, after the test run completes, it kicks off another run with the failed tests as an unattended execution? Or does one of your staff come in and run the batch file generated that contains the failed tests?
Question: You mention that "on the next day, we rerun all failed tests". Is this an automatic function of your code in TestComplete that, after the test run completes, it kicks off another run with the failed tests as an unattended execution? Or does one of your staff come in and run the batch file generated that contains the failed tests?
I am ashamed answering this question, but right now I rerun them... MANUALLY :(I haven't implemented my own solution in this project yet
