Feature Requests
290 results found
-
Add RMB menu "Run starting test on all enabled servers"
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.
1 vote -
Incremental build for console tool
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.
1 vote -
Allow to run in memory only
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.
6 votes -
Visual Studio (Mac)
Now that Visual Studio is available on the Mac, it would be nice for tools like this to be available for Mac users too.
18 votes -
Pin tests matching engine mode
Before selecting an engine mode (e.g. "Performance Tests") I would like to see which tests that would be executed for this mode, e.g. by pinning them. This way I can choose only to test run a single matching test for triage.
Ideas for implementation:
A) Create a sub menu on each engine mode "Pin matching tests" or similar, while the top menu item (engine mode name) still behaves as today.B) Add a NCrunch tests window toolbar button "Do not run tests automatically", then add a menu item "Pin test matching current engine mode". Then one can disable auto-execution, select…
1 vote -
Add window showing slowest lines of code
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
2 votes -
Support Install Directory Outside of AppData
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.
1 vote -
Add "Configure selected component" RMB menu on NCrunch project warnings
[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.1 vote -
Add "/VS" switch (vstudio version) to grid node server configuration
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)1 vote -
allow copy paste from exception details window
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 window2 votes -
Option to suppress TC service msg "NCrunch result: TestFailure" in console tool
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.
1 vote -
Look at working with Live Share
Visual Studio Live Share is a new collaborative sharing tool that is currently in development for both VS and VS Code.
We are currently evaluating it, and we noticed that annoyingly, there is currently no way to have the nice dots / coverage NCrunch provides to remote guests.
There is a task / issue logged with Live Share https://github.com/MicrosoftDocs/live-share/issues/125 which they seem interested in creating an API eventually.
I think you guys should look at trying to integrate with this... as I believe Live Share looks to be on the right track at the moment... and having NCrunch integrated into…
10 votes -
VSTS Plugin to show the Code Coverage over time
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.
3 votes -
Support Expecto
It would be great if NCrunch could integrate with Expecto (https://github.com/haf/expecto).
12 votes -
Standalone UI which can be used with every other IDE
Here are some feature requests for Visual Studio Code and Rider. But these require deep Integration.
But since VS 2017 sucks so much these days. It would be nice if we can use another IDE.
I propose a standalone Version with the NCrunch with the UI and Windows which are currently in Visual Studio. But without Visual Studio.
Of course this is not such a tight integration with the IDEs (not jumping to the code, debug and break into failing tests etc.) but would be a good start. And of course, it is only running tests on save because of…
19 votes -
Grid Node Serrvice Log On Credentials on Installation
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
1 vote -
Merge "custom environment variables" settings between shared/user settings.
Today the "custom environment variables" are "all or nothing" between the layers, e.g. if you have 5 settings in "shared settings" and want a new one (or modify one) locally, you need to duplicate all 5 in "my settings" to avoid the other ones being "unset" in the test runner.
I would like "my settings" to only override the ones I specify, so I can keep the 5 ones in "shared settings" being "active", and only add (or modify) 1 specific in "my settings".
1 vote -
Add "Title" field for simplified grid node management and identification
As a NCrunch user, I would like to have an easy way to identify and manage my grid node while using distributing processing window.
Currently, "server name" field is the only way to identify remote servers. With automated, disposable, DevOps-iified infrastructure, such identification is highly desiured. Out server names are random strings, such as this:
MB-{RANDOM-8-CHARS}
- MB-DMHJBDTDD
- MB-THDRFBDF
- MB-MKDHSVTD
We don't really care or have control over this while scaling grid nodes infrastructure.
It would be nice to have an additional field "Title" or "Display Title" for grid node so that we can have a human-readable name for randomly generated…
0 votes -
An option to automatically pin *modified* tests
Most of the time, I only want to automatically run tests that I'm working on.
So I use engine mode "Run pinned tests automatically, others manually". And manually pin tests I'm working on.
Would be nice if NCrunch could automatically pin modified tests (detect changes of test methods and test classes), and automatically pin modified tests.
I know we already have an option "Automatically pin newly discovered tests". Would be nice if there was another option "Automatically pin modified tests".
4 votes -
Attribute to identify type/methods that must have 100% code coverage
It would be helpful to have NCrunch treat (or at least report) decreases in code coverage as "fail".
For example, supporting an attribute that marks a project/class/method as "100% code coverage required".
Or a larger flag such that any code coverage drop is a "failure". This would be a bit trickier to support as it may need to be include a way to identify a baseline. And it may be helpful to distinguish between coverage for old code vs coverage for new code.
I think starting with a numeric attribute indicating the required coverage would give the biggest ROI --…
2 votes
- Don't see your idea?