I suggest you ...

Rerun flaky test

I'm using NCrunch for more than 2 years.
IMHO it's must-have extension.
When I come to new company that do not use NCrunch I need to fix/stabilize some test to run with NCruch engine.
But still I stay with few flaky test.
I need to rerun them few times to filter trully failing test.

It would be nice introduce option for my case with flanky test.
It could be rerun count before test is treated as failed
Other option to introduce 3rd test state: flanky.

9 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    PavelPavel shared this idea  ·   ·  Admin →

    1 comment

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • ChrisChris commented  · 

        I would like to add, normally I wouldn't find much value in something like this, but I recently ran into a situation that would greatly benefit from this type of behavior: Inconclusive Test runs.

        For instance, NUnit (among others) supports 'Inconclusive' test results, (ie. using the 'Assert.Inconclusive()' method). Dealing with specific test cases that validate concurrent behavior, sometimes it is necessary to gate the actual test logic behind a non-deterministic concurrency state validator; if that validation fails, then the test is marked "Inconclusive", but if it succeeds, then the test can continue execution in a known good state.

        I would add my vote for NCrunch to include first-class support for Inconclusive test results, and to allow for a configurable amount of retries in such a situation.

      Feedback and Knowledge Base