Feature Requests
57 results found
-
Highlighting an important test to work on
I would like to "highlight" one or more tests as the most important ones at the moment. We have a little bit longer running tests and usually I work on a bug or a feature that is present on one or two of the tests. When I make a code change I don't want to wait for other tests to run. Usually I end up manually run the tests (from NCrunch list) or ignoring all the other tests and unignoring the important ones.
With this feature I could just highlight couple of tests so that they will be always run…
1 vote -
.NET 4.8.1
Support .NET 4.8.1
2 votes -
Support .NET 6.0
We started working with .NET 6.0 and now I see that I can no longer use NCrunch as it does not support .NET 6.0.
What are the plans for support of .NET 6.0?
6 votes -
Visual Studio 2022 Support
Add support for the preview versions of Visual Studio 2022. Really enjoying working with the VS Preview, but have to keep switching back to stable versions to get ncrunch results.
4 votesSetting this to completed as it looks like the big work is finished here now. We'll continue to maintain this as MS make incremental changes.
-
Add support for projects referencing Source Generators
When attempting to use NCrunch to test a project that has a source generator added, the project will not compile under NCrunch's build context because it excludes the Source Generator.
Please find the relevant thread here: https://forum.ncrunch.net/yaf_postsm15305_Support-for-C--source-generators.aspx#post15305
7 votesSupport for source generators introduced with NCrunch v4.9 (released today).
-
Option to exclude passing FIXTURE tests from Console runner
When using the NCrunch Console 4.3.0.13 with NUnit 3 and Team City we are seeing an extra "Fixture" unit test added to every class that has individual unit tests. This can significantly increase the number of tests reported by TeamCity compared to NCrunch in Visual Studio.
To be able to leverage NCrunch in a Continuous Delivery environment it is important that the build system test results & code coverage metrics match those in the development environment, and due to this reporting difference they currently do not.
I do understand the reason for the "Fixture" test appearing for diagnostic resolution, and…
12 votesImplemented in v4.4
-
Earlier Support for .Net 5.0
Currently, NCrunch supports up to .Net Core 3.1
.Net 5 is on "5.0.0-preview.7" (2020-07-21) now and will be released for 1st November.
My leading role leads me to develop often en preview and it has a burden to switch OFF NCrunch for those projets (when preview .Net Core 3 was the same burden).
My question is when the support is planned to be? And Can, principally can you change your workflow to have "Earlier support" for the new versions?
Thank you,
Christian P. Gyssels
MCT2 votesImplemented and released as part of NCrunch v4.5.
-
Support build of Azure functions
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.
47 votesSeems to be looking good as of the v4.9 release.
-
Support Visual Studio 2019 Preview!
Visual Studio 2019 Preview was just released yesterday. How soon can we get a compatible NCrunch installer for it?
7 votesVS2019 support has been introduced with NCrunch v3.24.
Be advised that support is currently experimental. VS2019 itself does not appear very stable for us yet.
-
Add "Check for Updates" menu item or do it automatically
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.
1 voteAlready implemented. NCrunch automatically checks for updates on a weekly basis and this can be disabled via config setting.
-
Filter settings in NCrunch Configuration window by name
Similar to the "Search" edit for tests I would like a "Search" edit for settings. This so I quickly can change setting I am looking for by typing e.g. "env" to find the custom enviornment variables settings (for the current settings layer I have selected)
1 voteIntroduced in NCrunch v3.24 (just released).
-
Sign all application exe files
Please sign all the exe files installed and utilized during execution so that we can whitelist your exe files with security software.
1 vote -
Add option to run test until failure
For tests with randomly generated inputs (e.g., FsCheck for F#), it would be great to have an NCrunch option that continues to run a single test until it fails, in order to catch rare edge cases.
Currently, the alternatives with NCrunch aren't so great:
1) If you set the maximum number of test runs to a large number, then when a failing case is found, it is necessary to run ALL the tests preceding the failing test in order to reproduce the failure, in order for the underlying random number generator to end up in the same state which generated…
4 votesLooks like we implemented this last year with ‘Churn mode’.
-
Support .NET Core, .NET Standard (previously known as DNX) projects
Surprised this hasn't already been requested.
Going to be necessary to implement.
224 votes -
7 votes
Implemented and released as part of NCrunch v4.5.
-
Add 'Import/Export' NCrunch configuration
Cause other guys want to run NCrunch with the same configurations.
It would be nice to have an export/import feature covering the following scenarios:
- Import/Export VS project settings
- Import/Export VS solution settings
- The whole NCrunch settings
Finally, the most interesting import/export feature is a set of the NCrunch server nodes. That would be just perfect - to save a list of the servers and then pass across the team.
7 votesThe new configuration system released in V3 has made it much easier to share configuration files. All settings are now in the XML, so it should be easy to just copy them between team members. This includes the list of NCrunch grid servers.
So I hope this feature can be considered delivered!
http://blog.ncrunch.net/post/Announcing-NCrunch-Version-3!.aspx
-
Stress-debug flaky tests
Flaky tests are difficult to catch under a debugger due to the time it takes to start a new debugging session. It is frustrating to click the "Run the selected test(s) with debugger" button over and over again, waiting 5-15 seconds for each run.
It would be wonderful if we could tell NCrunch to debug a given test 100 times in a row, giving the test a chance to fail with the debugger attached. The behavior should be similar to running multiple tests with debugger attached, though in actuality it would be the same test running again and again.
9 votesImplemented as NCrunch Churn Mode.
-
Custom environment variables per solution or per project
At the moment you can only custom environment variables can only be set globally (https://www.ncrunch.net/documentation/reference_global-configuration_custom-environment-variables). In particular, this means that they cannot be checked in to source control. It would be good to be able to set this per project or per solution, so that it could be shared across teams.
(For example, I would really like to be able to set a DONTINSTALLNPM environment variable to prevent this target from running in the Npm.js NuGet package: https://github.com/giggio/npm-nuget/blob/master/build/npm.js.targets)
2 votesThis is possible under the new configuration system released with V3.
-
Show Date as tooltip or suffix for Last Run/Build column
Last Run/Build only shows current time. When you have a session open for more then 1 day it becomes difficult to tell when it was last executed (and sorting does not work properly, but I assume this is a bug).
Adding the date as suffix in column (not prefix since IMHO the mostly the date is always today, thus saving screen estate if column can be narrow so date becomes truncated when needed) would help in determine if it was run today or not.
Alternative solutions:
A) Add the date (e.g. "2018-06-27") upon moseover.
B) Add date as separate column…1 voteThis was, actually, implemented a while ago. Sorry, I forgot to close the ticket.
-
Support .NET framework 4.7.2
Currently, NCrunch supports up to 4.7.1.
1 voteReleased with v3.16.
- Don't see your idea?