Azure functions are becoming more and more used. Unfortunatly NCrunch is not compatible with them. What's the plan to support them ?

We wanted to give all developers on my company an NCrunch licence but we all add some Azure functions to our projects, so people instead use Continuous Testing from Jetbrains. It does the work, but NCrunch is clearly ahead. Hope it will be supported soon.

Currently there are six hard-coded ways to display tests in the NCrunch Tests window.

My proposal is that in place of this hard-coded list, there be a way to specifically configure what I want to see:

* Category (on/off)
* Project (on/off)
* Namespaces (one level per dot, or all grouped in one level, or none)
* Fixture (on/off)
* Test (full namespace.class.name / just method name)

Usually except for large projects I'd prefer to just show the test name, but currently there's no way to do that. "Test" view shows namespace.class.testname.

I have a process that is being launched during the run of a test that I need to attach to. The current workflow of manually attaching to the test is slow and irritating. I believe since ncrunch is running as a VS extension ncrunch could provide a function to attach to a particular process by PID.

Sample code that implements this feature, with MIT license:
https://gist.github.com/xavierzwirtz/bd3dfcb5be4a0466cd4c106cc92f223e

Need to be able to instrument C#.Net webapi server deployed on Microsoft Azure Service Fabric Cluster? I am looking to get code coverage for the same, for the integration tests that are running against a Webapi server deployed on the SF host.

Save the Timeline report every 10 minutes in order to keep the history of a whole work session (a few hours). I could make visual reports based on the xml file.

I would need this for the training / coaching I do with team that are learning TDD.
I want to show them how NCrunch can be used to improve their practice and reduce their feedback loops. I don't know any other tool that could do it for Visual Studio and it would provide precious information.
We could even make it a game/competition with clear number objectives!

NCrunch supports crunching xUnit tests defined in an @code block of a razor file. It would be great if automatic inline code coverage were supported for those tests.

When you activate 'Show coverage on selected test only' while at the same time having 'Churn selected test until it fails' on, there is only a popup dialogue for turning off the 'Show coverage on selected test only'. It's probably more relevant to stop churning than to show coverage of all the tests in that particular situation, so It would be nice if the dialogue [also] offered the possibility to cancel the churning session.

With 3.25 NCrunch builds and test the complete solution even if a Solution filter is used. This is one side a good thing, so that if i break something in a filtered project, this will be detected pretty quickly.

But it may be nice in some more complicated case, only run and build the projects which are in the filter. Because the filter is used to explizit not build and test some projects.

The documentation (https://www.ncrunch.net/documentation/reference_project-configuration_autodetect-nuget-build-dependencies) describes that NCrunch is able to auto-detect NuGet package references.

It also states that it may happen that NCrunch workspaces might bloat significantly.

At least to work around some limitations it would be nice to have a filter that either excludes or includes specific files.

For example, I would like to exclude the .nupkg files and the .xml (documentation) files. In my specific scenario that would reduce the "bloat" from 16MB to 4MB as now I only include the DLLs I actually need.

With NUnit 3 I added [assembly:Apartment(ApartmentState.STA)] as an assembly-level attribute, thus applying to all tests in that assembly. Yet, NCrunch doesn't consider that for impacted tests. There are possibly also other assembly attributes that could impact all tests.

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.

Provide the ability to specify that certain tests should never run on the local machine and should always run on applicable Grid Node clients (e.g. if the Grid Node client meets whatever capabilities are specified, etc.).

All modern tools have possibility to check that updates available. I think good thing to have possibility check updates automatically or by the menu item, and inform user about new version available.

I have a large amount of tests but would like to see which tests are currently being executed or pending execution (without showing all passed tests/projects), even if test was previously passing.

This so I can get an overview of the "backlog" of the current work queue and easily utilize the Search filter/sorting etc.

The Processing Queue Window is good to know what is "happening" but I would like to have similar info in the Tests window (more focused on test itself versus all other info build/analyze/servers etc.)

I want to be able to download entire test output data in a file in order to search for keyword in any of the tests.

Scenario: I use NCrunch on TeamCity and have AllResults.html in a tab, since I also use "run impacted tests only" the TeamCity build log itself does not contain all test output so I have to resort to AllResults.html. I there want to find all tests with log output containing a substring, but have no way of searching output of all tests in one go.

From forum: https://forum.ncrunch.net/yaf_postst2641_Why-is-not-NCrunch-aborting-build-analysis-on-pending-grid-nodes-when-no-work-remains.aspx

If I have 1 slow grid node connected to NCrunch Console, and NCrunch engine has completed all tests for the engine mode, I want the slow grid node to abort its build/analyze processing since there are no more tests to execute anyhow.

Background: My NCrunchConsole runs on a fast server, one grid node might be very slow. So even though the console tool is completed building/analyzing/running tests within 3 minutes, it sits and wait for the slow grid node to complete building for another e.g. 15 minutes (see forum post for a timeline example).