I use Nunit but I guess there are similar concepts for other test frameworks. Currently any explicit or ignored tests have white icons in the editor and show as unexecuted in the tests window.

I would like the option to change these indicators. In particular to change the colour/shape for the ignored/explicit tests icon in the editor.

I would also like a filter for both explicit and ignored tests in the tests window. This would help me to track these tests down quickly

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.

If the AssemblyVersion attribute contains an asterisk (eg "1.0.0.*") then NCrunch cannot reliably build the solution.

Currently, there is no way to prevent NCrunch from resolving the AssemblyVersion of each project and this causes problems with inconsistencies and NCrunch reporting build errors because MSBuild is expecting a different version of the assembly to the one provided.

The current alternative to this involves polluting non-test project files with NCrunch-related hacks, which is not very clean.

In order to resolve this issue, I suggest that a setting feature be added to NCrunch which allows AssemblyVersion resolution to be disabled.

It's quite time consuming collapsing the test groupings. I often do this when I want to hone in on a specific project but without loosing complete visibility of the rest. At present I have to perform lots and lots of separate mouse clicks to condence the test groups down - and kind of loose the will to live in the process

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

I'd like to keep Visual Studio open, log out of my account while keeping the machine on, and have NCrunch run Endless Churn in the background.

I have tried using the color white for marking lines covered by passing tests, so that I only get highlights on lines of code needing my attention.

However, when setting anything above 224 it switches back to black, probably some kind of contrast code that kicks in. Could I ask for an option to turn this behavior off, so that if I *want* white color, I can *get* white color?

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.

When searching for something in the project file, it would be nice to be able to see whether or not the line in the find results window is covered by a test.

For instance, I know the piece I'm currently testing is sensitive to the use of DateTime.Now so I need to search all places where DateTime.Now is called and then browse to the code to see if the failing test used that instance in the search results.

It would be nice to be able to use the scroll wheel to zoom in/out when in a NCrunch window.

When running churn mode I am interested in "Total test executions" i,.e. how many time test has been run in current churn mode, and "Total execution time" i.e. how long the churn mode has been going on (i.e. has it spent 1 minute or 30 minutes).

This so I know, when I decide cancel, that I ran it for e.g. 10 000 iterations and/or in 10 minutes so next time I want to "churn it" I get a hint how long I need to churn it .

Set User Account for Grid Node Server on installation and/or Keep Log On Credentials an an Update.

For .NET Core Projects it is needed that the builds or not running under the SYSTEM Account

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

I would be nice if it was possible to opt-in to change behavior of the context menu "Go to selected test" in that way:

With NUnit, one can write:

public static IEnumerable<TestCaseData> MyTestCaseSourceMethodName()
{
// return test cases...
}

[TestCaseSource("MyTestCaseSourceMethodName")]
public void MyTest(int someArgument)
{
// do test...
}

The test case factory method can be an separate (static) class.
In my case, I have a test with several dozens of test cases.

When a test fails, I can easily go to the failing test implementation, but I cannot easily find the culprit test case.

Our development machines are built via PowerShell script, which is a very flexible and maintainable way of scaling to many developers. The scripts rely heavily on Chocolatey packages to install software, but unfortunately the unofficial Chocolatey package for the NCrunch Visual Studio plugin is not reliably updated and does not cope well with upgrades. Also, there is no command-line NCrunch package.

Given that Chocolatey packages are relatively simple wrappers around the existing product installers, it would be great if you could work with the existing package maintainer to improve the existing package, and create a package for the command-line application.

I would like to be able to Churn tests for x seconds/minutes and if it hasn't failed within that time stop churning.

This so after I have fixed a failing test, which I know fails in churn mode within x seconds, I don't want to run "Churn until it fails" but rather set a time period I know should be sufficient to reproduce it.

When I try to connect to an NCrunch grid node and get "NCrunch Client DIsabled" in red text, my first impulse is to troubleshoot. Is it a firewall problem? Bad password? Something else?

Then it clicks...*client*. I don't have NCrunch enabled in my current Visual Studio solution (or maybe I don't even have a solution loaded yet).

Well, obviously NCrunch won't send anything to the node if there's nothing to send. This isn't really an *error*, per se, so I don't think NCrunch should show the message in red in this case.