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.

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.

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

I would like to easy spot which tests in my test are included in current UI coverage filter.
Given I have a coverage filter set, I would like an icon on the test (e.g. red X with some small overlay icon for a failing test) so I easily can see which tests that are currently used in coverage filter (e.g. when have 20 pinned tests and showing coverage for only 5 of them).

Today the tests window states e.g. "No tests are queued for execution. Monitoring 150 tests (10 failing), with 20 tests ignored."
I would like that text to include how many tests I have pinned (easy to tell if a new one gets pinned or not for example via engine mode).

Similar to https://ncrunch.uservoice.com/forums/245203-feature-requests/suggestions/6363545-when-showing-coverage-for-specific-tests-show-icon , I have X pinned tests, and currently only show coverage for 1 test.
The code I am looking indicates uncovered (or filtered due to coverage filter).
I would like a link similar "Click to return to normal" that reveals the tests currently showing coverage for (easiest way I guess is to pin them).
This way I can easily navigate to the tests currently used in coverage filter, without currently having covered code under cursor.

I have an explicit test which resets database to a clean state. If for whatever reason the db state becomes invalid, I would like to run this test on all connected/enabled "servers" (local and grid nodes).

Today I must select one by one ("Run starting test on server>X ") to ensure db is reset within each grid node.

[v3.23.0.10]
Today compile warnings are hidden with NCrunch for successfully built projects, I must select to "show all tests" and then select each project to see them.

I would like a toolbar button or similar which toggles compile warnings, so I can always spot those before committing even if project builds without errors.

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)