Feature Requests

I suggest you ...

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Show/Hide previously passing, but now out of date tests

    When using the engine mode of "Run impacted tests only, other tests manually", the Test Window provides a green question mark indicator next to tests that were previously passing, but are now out of date (at least that's what we believe the green question mark indicates).

    We would like to request an enhancement to the Test Window to show/hide the green question mark tests; this would be an icon next to the current four indicators that will toggle the visible tests: Passing (green check mark), Failing (red X), UnExecuted (blue question mark with an eyeball), and Ignored (yellowish circle with…

    17 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Support for NSpec

    I'd love to run my nspec.org tests via ncrunch.

    16 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Allow the console tool to be run continuously

    Im super happy with ncrunch console tool that was just released:

    http://www.ncrunch.net/documentation/tools_console-tool

    However i would also like it to be able to run as a deamon continuously watching a specified folder/solution using NCrunch excellent incremental build/test features.

    Ideally it would output a maximum of N failing tests:

    1: *. [NameSpace].Test failed | at line 12 of filename.
    2: ....

    Ideally it would also support verbose output in json/xml so that plugins for other editors can be written.

    16 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Clean up the noise when an AssertFailedException (or similar) is thrown

    When an assertion in a test fails, you get the full stack trace of the AssertFailedException, which is noisy. For instance:

    Microsoft.VisualStudio.TestTools.UnitTesting.AssertFailedException: Assert.AreEqual failed. Expected:<1200>. Actual:<900>.
    at Microsoft.VisualStudio.TestTools.UnitTesting.Assert.HandleFail(String assertionName, String message, Object[] parameters)
    at Microsoft.VisualStudio.TestTools.UnitTesting.Assert.AreEqual[T](T expected, T actual, String message, Object[] parameters)
    at Microsoft.VisualStudio.TestTools.UnitTesting.Assert.AreEqual[T](T expected, T actual)
    at TestInheritance.Tests.RectangleTests.AreaAfterSettingHeightWidth() in d:\[some likely really long path]\RectangleTests.cs:line 22

    Of all the above information, the only pertinent information is the message text of the exception and the bottom of the stack where the assertion failure happened. For instance:

    Assert.AreEqual failed. Expected:<1200>. Actual:<900>.
    at TestInheritance.Tests.RectangleTests.AreaAfterSettingHeightWidth() in d:\users\floyd.may\documents\visual studio 2012\Projects\TestInheritance\TestInheritance.Tests\RectangleTests.cs:line 22

    Ideally, for MSTest, NUnit,…

    14 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  5. Exclude from Metrics Aggregation by wildcard

    Allow user to exclude files from Metrics Aggregation by wildcard. As an example, I'd like to exclude all *Designer.cs files from being counted.

    14 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  6. Create an option to enable NCrunch only when on A/C power

    I almost always develop on a laptop - but sometimes while travelling, and sometimes plugged in. I'd like NCrunch to automatically disable itself when I'm on battery power - it does suck energy like crazy - and then re-enable itself when I'm back on the grid.

    13 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Show code coverage metric in the status bar next to "N"

    It would save a few clicks when code coverage would be displayed in the status bar next to "N" or instead of green "N".
    Besides, it would be a constant reminder of the current Code Coverage before the commits.

    12 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  8. Standalone UI which can be used with every other IDE

    Here are some feature requests for Visual Studio Code and Rider. But these require deep Integration.

    But since VS 2017 sucks so much these days. It would be nice if we can use another IDE.

    I propose a standalone Version with the NCrunch with the UI and Windows which are currently in Visual Studio. But without Visual Studio.

    Of course this is not such a tight integration with the IDEs (not jumping to the code, debug and break into failing tests etc.) but would be a good start. And of course, it is only running tests on save because of…

    11 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Support for expression body (one line tests)

    I would like support for one line tests that use expression body syntax, like the one below. When the test fails I would like to see the red cross with the assert information instead of the red arrow that doesn't give any information of why the test failed

    [Test]
    public void CanEditIsTrue() => Assert.IsTrue(Result.CanEdit);

    11 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Test Window Filter

    I would like a filter in the test window that "show only tests that should runs automatically due to configured Engine Mode"

    11 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Option to always start NCrunch disabled

    I frequently switch between working copies/branches and since I use an engine mode which is automatically running tests I would to manually enable NCrunch on startup. This since the test suite is very heavy and I might want to open solution without immediately running all tests and/or I need some changes to e.g. "Custom environment variables" so tests are running correctly.

    (Now I need to remember to disable NCrunch before closing project, which I most often do not remember. Also the now and then occasional vstudio crashes prevents me from setting this)

    11 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Using XBox as NCrunch Grid node server

    When i'm programming my xbox is idle. it would be awesome if I could run ncrunch builds and test on it.

    10 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  13. Mutation Testing

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

    9 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Stress-debug flaky tests

    Flaky tests are difficult to catch under a debugger due to the time it takes to start a new debugging session. It is frustrating to click the "Run the selected test(s) with debugger" button over and over again, waiting 5-15 seconds for each run.

    It would be wonderful if we could tell NCrunch to debug a given test 100 times in a row, giving the test a chance to fail with the debugger attached. The behavior should be similar to running multiple tests with debugger attached, though in actuality it would be the same test running again and again.

    9 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  15. Allow specflow scenario outline examples to have their own 'dot marker' in the margin

    currently if you have a scenario outline that has several examples there is no way to run a specific example as a test, I can only see the dots in the actual scenario outline and have to then run 'x' number of tests at once (where 'x' is the number of scenario examples)

    I'd like a 'dot' by each line in the examples so I could run a specific scenario example on its own or see which example is actually failing

    9 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Visual Studio (Mac)

    Now that Visual Studio is available on the Mac, it would be nice for tools like this to be available for Mac users too.

    8 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Support Expecto

    It would be great if NCrunch could integrate with Expecto (https://github.com/haf/expecto).

    8 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Increase startup speed in VS2017

    Please, increase the startup speed in Visual Studio 2017. Every now and then it shows me a window with extension-related startup delays, and asking to disable them.

    8 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. to support custom Xunit test cases

    As discussed on Twitter (https://twitter.com/remcomulder/status/782892104485703681), I'd like NCrunch to support custom test cases.

    xUnit has the support for custom test cases, as the STAExamples of the xUnit Samples demonstrate (https://github.com/xunit/samples.xunit/tree/master/STAExamples). That relies on using your own test discoverer, and specifying a custom test case. When you run that in NCrunch, it fails with a cast exception (https://gist.github.com/tiesmaster/5ecb8bf76aab6ee3cb2bfcc9d4f08e72#file-stacktrace-of-staexamples-on-stable-xunit-packages-downgraded-to-2-1-0).

    I think this is a niche feature, since this something that won't be used that often, but still a powerful feature, so it would be really nice to have this.

    8 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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.

    8 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feature Requests

Feedback and Knowledge Base