From https://forum.ncrunch.net/yaf_postst2644_Incremental-build-with-NCrunch-console.aspx

I run NCrunch console on TeamCity with engine mode "run impacted tests only" (with switch -NCrunchCacheStoragePath) but the build/analyze phase is always restarting from scratch instead of utilizing "incremental build" functionality, which causes the session to run longer than needed even if no source files have been modified.

I would want, in some way, to have the console tool session behave as an "incremental build" with MsBuild would do, granted nothing has changed in source files and NCrunch cache folder is kept between sessions.

It would be nice if I could run ncrunch in memory only. That would extend the lifetime of SSDs and would be much faster. At the moment this is only possible with a ram drive.

I would like the "Search" window in NCrunch Tests also match test categories (and maybe other columns as well?).

(going "all in" the grid component could maybe be replaced with a component with filter-per-column possibilities)

I'd like to be able to check the code coverage on new code when one of my developper do a pull request using VSTS and Git.

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.

The console tool is cool to generate a report. If there would be a VSTS plugin to show the coverage absolut or over time this would be a great feature.

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

Today the "custom environment variables" are "all or nothing" between the layers, e.g. if you have 5 settings in "shared settings" and want a new one (or modify one) locally, you need to duplicate all 5 in "my settings" to avoid the other ones being "unset" in the test runner.

I would like "my settings" to only override the ones I specify, so I can keep the 5 ones in "shared settings" being "active", and only add (or modify) 1 specific in "my settings".

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.