Skip to content

Chris

← NCrunch Feature Suggestions

My feedback

2 results found

  1. Ignore Categories of tests

    24 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    3 comments  ·  Feature Requests  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    Chris supported this idea  · 

  2. Rerun flaky test

    5 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Feature Requests  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    Chris supported this idea  · 
    An error occurred while saving the comment
    Chris 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

(thinking…)