Feature Requests

  1. Mutation Testing

    Perform Mutation Testing on the test cases to identify incorrect test cases.

    11 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Coverage on If statements

    Ncrunch does not appear to check all conditions in an if statement for 100% coverage.
    i.e. if (x || y) only requires that x is tested, not y.

    27 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Support Gauge

    Please consider adding support for Gauge (http://getgauge.io). Gauge is an open source test platform, started by ThoughtWorks, for writing specification by example. It is similar to Gherkin, only it uses Markdown. Steps are bound to code using StepAttribute binding.

    26 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Expose MSpec's [Subject] details in the tests window

    MSpec uses a [Subject] attribute to nominate the unit-under-test and optionally allows a "concern" to be specified.

    In R# these items appear in the test runner window as part of the test name, however in NCrunch there doesn't seem to be any way to get at this information, which is unfortunate.

    There just seems to be a level of organization missing when working with MSpec tests. It would be really helpful to be able to group the tests either by the [Subject] attribute, or by the file name that the test is defined in.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Pin test class in test runner rather than pin each test separately

    Would be nice to have ability to pin test class to test runner, rather than pinning each newly added test separately. When adding a new feature, you tend to spam quite a few tests in new test class, or to some existing class. If solution is big, and you have many tests, the response time from NCrunch becomes poor. Of course you can pin each task separately when you add them, but when you spam many small tests, it becomes annoying. NCrunch could automatically detect newly added or modified tests in pinned class(es) and run them, ignoring the rest.

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Support the new Visual Studio Code IDE

    Support the new Visual Studio Code editor.
    While it doesn't yet provide extensibility for utils like NCrunch, it is apparently planned for upcoming development, so I wanted to get this on the NCrunch radar.

    145 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    20 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. ARM support

    Please compile / release for ARM as well as x86/x64.
    I am looking to run the NCrunch Grid on machines which use ARM chips and noticed there are only x86/x64 builds.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Build on line "commit" insead of each character typed

    I would like the ability to be able to set NCrunch to only build my solution and run my tests after a new line of code is entered or an existing line of code has been edited.
    I find the feedback I get from VS more than enough while writing my line of code and would much rather have NCrunch working on giving me feedback on my solution up to the point where I added/edited the last complete line of code while typing the next.
    This would allow me to run many more test (as NCrunch has the time between…

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Update CodeLens test stats

    In Visual Studio 2015, Code Lens shows me 0 passing tests, while NCrunch shows me all green markers.
    Maybe it is possible for NCrunch to update the CodeLens test statistics.

    59 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Filter to show running tests.

    Hi, I'd like to have a new filter option along side the "show passing/failing/unexecuted/ignored tests" buttons which would allow me to "show running tests". My use case would be to have show enabled for failing, unexecuted, and running tests -- so I can more clearly see what NCrunch is up to at any given moment.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 44 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Option to run all test in current .cs file

    I would be nice if I could tell NCrunch to run all tests in the current file.

    Often related tests are implemented in the same .cs file. Some of the projects I work on are too large to leave ncrunch running all the time, so an option to just run all tests in a certain file would be really helpful.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. ternary coverage

    Increase resolution of coverage so that a ternary expression shows code coverage if one branch is not covered. (Otherwise my team is going to make me always use 8-line ifs instead of 1-line ternaries just so we can see code coverage completely :'( )

    21 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. NCrunch Console Tools provide TeamCity Code Coverage Stats

    You can check TeamCity documentation here: https://confluence.jetbrains.com/display/TCD9/Custom+Chart#CustomChart-CustomBuildMetrics

    CodeCoverageB Block-level code coverage %

    •CodeCoverageC Class-level code coverage %

    •CodeCoverageL Line-level code coverage %

    •CodeCoverageM Method-level code coverage %

    •CodeCoverageAbsLCovered The number of covered lines int

    •CodeCoverageAbsMCovered The number of covered methods int

    •CodeCoverageAbsCCovered The number of covered classes int

    •CodeCoverageAbsLTotal The total number of lines int

    •CodeCoverageAbsMTotal The total number of methods int

    •CodeCoverageAbsCTotal The total number of classes int

    31 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Add button to enable/disable word wrap in test output window

    The test output window currently wraps text which can make it difficult to read stack traces. An option to disable word wrap would be helpful, especially if it could be toggled via a button on the window itself.

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Hide non test projects in the NCrunch Tests window

    I typically leave the 'Show Passing Tests' filter enabled. However, when it is enabled, non-test projects also show up in the list with a check next to them. It would be good if the non-test projects would not show up at all in the tests view since there are no tests in them.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Color the console output

    I really like the idea of separation of console outputs by test. But, the problem is, that with more logs the output becomes cluttered. There is an excellent plugin for Visual Studio called VSColorOuput that allows to specify regular expressions to color the console output in the output window.

    Would you consider:
    1. Add similar coloring preferences to console output
    or
    2. Output console to the output window, as requested in another feature request?

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Enable real time output of the test being run in "NCrunch Tests" window

    It would be nice to have real-time or at least "refreshed" every 5-10 seconds "Test output" console in NCrunch Tests" window.

    Right now the output is provided once test is completed, but it would be useful to have some kind of "refresh every N seconds" option for integration tests. They might take minutes to run, and sometimes it is extremely useful to see output in real time - either to kill the test or to see what's going on.

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Improve hover-over hints on tests indicators/icons in 'NCrunch Tests' window

    Oh boy, we still have absolutely no idea what do some icons mean. Really.

    All these alerts icons on the test/assembly row, then green or red clocks, then green question marks. That IS so much puzzling. Seems we lived in VS space too much, at least it was simple - not run, run and pass/failed :)

    Please add hints on hover-over providing an explanation and suggestion on what is going on with the current test or whole test set.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feature Requests

Categories

Feedback and Knowledge Base