Re-running failed test cases

Question

Hello,I am running a set of 15 tests.I want to re-run the failed test cases at the end of test execution.Is there anyway through which I can identify the failed test cases and then re-run them at the end of execution.&nbsp;Thank you&nbsp;

prashantmohan · Accepted Answer

There is a capability to re-run failed tests -&nbsp;https://support.smartbear.com/testcomplete/docs/testing-with/running/control-test-flow/stop-and-rerun.html

tristaanogre · Answer

Short answer: no.&nbsp; There is no built in functionality in TestComplete to indicate that, if a test case is failed, to re-run it.
&nbsp;
In truth, this is a feature/functionality of Test Management software like QA Complete or Jenkins... to identify failed test cases and then, with a set of clicks or whatever, re-run them.&nbsp; TestComplete executes the tests and reports on them, other apps do the management of what needs to be re-run.
&nbsp;
Long answer: If you write enough code, you can do this.&nbsp; You would need to, somehow, write your tests in such a way that, if they "fail" (and you would need to clearly define a "failure" in code so as to make sure you properly identify it), you would somehow mark the test to be rerun (put the KeywordTest identifier or script routine reference into some sort of Array) and then write code to go through that list of tests and re-execute them.&nbsp; It can be done.&nbsp; As I'm fond of saying, you can automate ANYTHING given time, resource, energy and skill.&nbsp;&nbsp;

baxatob · Answer

Check this thread - https://community.smartbear.com/t5/TestComplete-General-Discussions/Run-failed-Tests-again/m-p/160709 - there is some workaround by&nbsp;karkadil

tristaanogre · Answer

baxatob wrote:
Check this thread - https://community.smartbear.com/t5/TestComplete-General-Discussions/Run-failed-Tests-again/m-p/160709 - there is some workaround by&nbsp;karkadil

Yes.&nbsp; This will work.
&nbsp;
But note... it's not something done completely within TestComplete.&nbsp; Both&nbsp;karkadil@&nbsp;and&nbsp;maxtester in another thread utilize an external tool to build something to be executed.&nbsp; In both cases, they needed to write code (event handlers, something internal to the test case itself, etc), to mark and store what test cases are "failed" and then pass that information off to something else to build a "retest" of some sort... In one case, there's a PowerShell script that executes... I didn't read the other one but I assume that there's something similar going on that alters/builds the batch file to be executed.&nbsp; Either way... you'll need to write custom code to do it.

karkadil · Answer

nitinn&nbsp;Just curious -&nbsp; why rerun the test cases again immediately?&nbsp;&nbsp;&nbsp;

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.
&nbsp;
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.
&nbsp;
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 :)

tristaanogre · Answer

Sure... manually... but not in code and not automatically as part of a test run.&nbsp; I'm sorry the answer doesn't help much... but that's the answer I have.&nbsp; Again, TestComplete executes tests... MANAGING what gets executed and when it gets executed is what a Test Management tool is for... and TestComplete is not a Test Management tool.
&nbsp;
As for moving test items around....
&nbsp;
One of the ways I like to explain how a "test run" works in TestComplete is that, when you start a test run, there's a "compile" process that happens at the beginning that initializes the "stuff" of the test run... stuff that is loaded into memory BEFORE the tests start executing that control and dictate the rules of execution (stop on error, iteration count, test item dependencies, etc).&nbsp; &nbsp;Part of that "compile" is the list of Test Items to be executed.&nbsp; These are "read only" during a test run because they are "compiled" as part of what you are executing.&nbsp; There are a number of things like this that are "initialized" when a test run starts which is why certain options, configuration settings, etc., are "read-only" at Run Time in TestComplete.&nbsp; So, no, you cannot "move" TestItems into separate folders via code during Run Time of your tests.&nbsp;&nbsp;
&nbsp;

Forum Discussion

Re-running failed test cases

12 Replies

Related Content

TestComplete Azure re-run failed tests

Access current re-run iteration from script (javascript)

Get test cases request through postman failing

Groovy Rerun Failed Test Case Execution Report

TestSuite Fails but all test cases are Passed

Recent Discussions

Floating window bleep overlapping window takes longer time (~10 min) to click the button on it.

Test case randomly fails with "parent object was not found"

Does TC have a .within() method similar to Cypress.io?

SessionCreator /Timeout option not firing EventControl_OnTimeout

testcomplete feature Intelligent Quality Add Ons