I have some tests requiring vs2013, these work fine with ncrunch.exe since I can use the /VS version.
However when I use vs2017 for local development the tests are failing (since the grid node uses vs2017 if that is available).
I would like the grid node configuration to be able to specifiy a vs version to use, so I can dedicate 1 grid node to run in vs2013 environment (in combination with capabilities to ensure such tests are run on that)

From https://forum.ncrunch.net/yaf_postst2618_NCrunch-Console-and-TeamCity-muted-tests.aspx

I want to be able to utilize TeamCity Test Muting (see https://confluence.jetbrains.com/display/TCD18/Muting+Test+Failures ) and therefore I need NCrunch to not report build failure via TC service message if a test fails.

I would like to use churn mode for a single test and make NCrunch enter the debugger as soon as churn mode was able to fail the test.

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

Integrate with the upcoming IDE from jetbrains to support project rider. Project rider is already available for download. Based on intellij. NCrunch couldn't do exactly what WallabyJS is doing and providing a number of IDE integrations.

Paket is an alternative package manager that support NuGet packages. Currently NCrunch will auto detect NuGet packages that have build targets in the csproj and copy the tools folder into the workspace for that package.

This does not work when using Paket and requires manual fixup of the additional files to include the tools folders.

Please add support for Paket based NuGet references in the same way as NuGet is supported.

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.

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.

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.

I have fairly non trivial engine modes with test filters set. I want to create a new engine mode based on existing but only tweak e.g. a condition in the filter.
It would help a lot if could copy an existing engine mode and tweak it instead of re-doing the entire filter.

When I show coverage for a specific test I trace through the code paths which are being executed using the per line coverage, however sometimes I then need to debug through that test, it would be nice if I could easily see which test is currently showing coverage so I can debug it

Often I want to pin failing tests, then make a change so a large number pass, then I want to unpin the passing ones. I can unpin all, show only failing then would like to pin all visible.

I have several unit tests and integration tests within the same project. It would be great to have an attribute to exclude the integration tests from automatic runs. These tests would only be trigger-able manually

The Microsoft.Net.Compilers package allows projects to use a specific version of the compiler. When NCrunch attempts to build a project referencing that package it will fail by default with the error: "packages\Microsoft.Net.Compilers.2.4.0\build\..\tools\csc.exe" is invalid." The current workaround is to add the tools directory for that package in the "Additional Files to Include" dialog.

NCrunch should recognize that this package is unique and handle it automatically.

The slow hotspot markers were super useful in me rewriting portions of test / application code to speed them up.

It would be useful to be able to see a list of the slowest lines of code so attention can be given to refactoring them.

Bonus points if this can be sorted based on total time under test, and also average time under test

It would be helpful to be able to be able to copy paste text from the exception details popup that displays when you click the X mark in the ncrunch gutter, e. g. stack trace, exception message, ...
Right now, the test has to actually be executed in debug mode in the task runner to be able to copy text from the standard visual studio exception popup window

If I have 2 engine modes "Manual" and "All Automatically except HttpTest", I must toggle between the 2 in order to re-execute all tests.

I would want a way to execute all tests matching the active engine mode, without having to toggle between "Manual" and the one I would want to be re-executed.

Summary: I would like to specify an engine mode e.g. "Run db tests locally, all other distributed".
Details: I would like to define grid nodes condition in the NCrunch engine mode settings. A first simple step would be to add setting similar to "Tests to execute on this machine", but under the Distributed Processing node. This way I can ensure no test with category [DbTest] is executed on grid nodes, but only on local (where I have the test db set up).