Feature Requests
58 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).
-
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.
-
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
-
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.
-
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).
-
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.
-
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 -
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.
-
Support multiple Visual Studio 2017 Installations
If you install NCrunch to Visual Studio 2017 you cannot selected to which instance the installation should go.
NCrunch picks one, and install. As a Workaround it is possible to do manual Installation with is not that complicated, but needs several steps, which also needs administration rights.
This makes upgrading to newer Version a real pain point. Also it might not be a great first impression for new Users. If they don't find NCrunch after installation.
A Solution might be to switch from MSI to VSIX for VS2017 and following Version.
11 votesWe’ve found an unconventional but effective way to rope multi-instance support for VS2017 into the NCrunch MSI installer. The installer should now automatically install for up to 3 instances of VS2017. If you’re using more than 3 instances of VS2017, you can still install NCrunch using the manual installation option.
This has been released with v3.16.
-
Support the new PackageReference nodes in VS 2017 project files.
Currently NCrunch can't build projects that use the new PackageReference structure for NuGet packages as opposed to the "old" packages.config.
Workaround is to use the old method.
6 votesWe implemented this a few years ago, to avoid breaking the entire world under NCrunch (as these references are everywhere now).
Closing this task as I think we’re good here.
-
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’.
-
Increase startup speed in VS2017
Please, increase the startup speed in Visual Studio 2017. Every now and then it shows me a window with extension-related startup delays, and asking to disable them.
8 votesWe’ve done a bit of work in this area over the years. There have also been versions of VS that would often blame VS packages for slow startups unfairly (i.e. when the problem is actually in VS).
I haven’t seen any notifications of slow startups for a while, nor any recent complaints about this.
So I think we’re good here.
-
Add support for MSTest V2
Please add support for MSTest V2. This update to MSTest has been available from Microsoft for VS 2015 since June 2016: https://blogs.msdn.microsoft.com/visualstudioalm/2016/06/17/taking-the-mstest-framework-forward-with-mstest-v2/. Since this will be the default engine for VS15 you're going to have to support it at some point. Since it is already available for VS 2015 I'd like to get NCrunch support for that without waiting until VS15 is supported by NCrunch.
2 votes -
Support for Visual Studio 15
At the time of writing Visual Studio 15 is out in preview 5. When can we expect a NCrunch installer for VS 15?
10 votes
- Don't see your idea?