Official Visual Studio 2017 with Xamarin support would be nice. In the moment it does only work the you edit Xamarin.forms.Targets file, what is annoying.

Visual Studio 2019 Preview was just released yesterday. How soon can we get a compatible NCrunch installer for it?

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'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.

Please sign all the exe files installed and utilized during execution so that we can whitelist your exe files with security software.

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.

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).

I would like to see when NCrunch starts up a new, or reuses existing, process in the NCrunch Console Timeline report, so I can find if long test run duration is due to process startup time or due to slow test run.