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

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?

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.

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.

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

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.

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

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.

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 .

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.

It would be great if I could get multiple risk/progress bars pointed at different categories of tests. I would like to see (for instance) one risk/progress bar for acceptance, one for integration, and one for unit tests. It would be great if these were full parallel instances - like with their own configuration and everything. For instance, having acceptance tests farmed out to servers makes a lot of sense but all my unit tests should run locally because it takes longer to farm out a batch than to run it.

I often have failing tests in my test window that I want to re-run in existing process (if there is one), e.g. when modifying database the tests are hitting.
Today I must go via RMB->Advanced, rather than just clicking a toolbar button (similar what exists with "run test(s) in new process".

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.

I'd like to be able to see the history of my work session, meaning at the end of the day I'd like to see visually when my code was compiling, when my tests were all green.
The purpose is to be able to identify if I spend a lot of time in those states and try to reduce that time.
It would be useful for self-improvement or coaching.

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