Marsha_R wrote:
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.
That's actually a good question in general... This isn't the first question we've gotten here about automatically re-executing. And it probably won't be the last.
As a guess (because I don't bother with an automatic re-run myself) is that this is kind of a "sanity" check. A test case fails... was it a fluke? Let's check to make sure... that's the only reason I would do something like this.
But it is precisely this reason why I wouldn't... usually if it's a "fluke"... that means something in my code of the test in the first place was done incorrectly... something was off on the timing, there was an object identification that didn't happen in time, there was some pre-condition I didn't account for, etc. So... rather than just re-running it... I want to know what failed, then FIX it, THEN re-run it. A failure is a failure... Whether it's the application that failed or the test, I want to know about all failures and handle them before I run the test again.