Due to security restrictions on programs executing out of AppData at my company, they whitelist another directory where we can install development software. Because NCrunch does not allow an install directory outside of AppData, I am unable to get it to work under this security policy.

It is pretty common to allow custom install paths, so I am requesting that you support this feature for NCrunch as well.

[v3.22]
Today I can select a project in NCrunch Tests window and RMB and choose "Configure selected component" to easily find it in the NCrunch Configuration pane.
However for project warnings I cannot do this (e.g. for warning "NCrunch detected unusual behaviour around the resolution of referenced assemblies required by this project in its test environment"). and must manually navigate to the project in the configuration pane, which is tedious for large solutions.

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.

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

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.

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 :'( )

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

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.

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.

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.

Build an addin for Xamarin studio

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.