Feature Requests
58 results found
-
Pin all test under the tests tree node
It would be nice to have ability to pin all tests inside specific node in the "Tests" window. Currently it only works for classes. It would be super convenient to have it working with other nodes (based on groupping) - namespaces, projects, ect.
7 votesIntroduced with NCrunch v4.9 (released today).
-
Make use of ExcludeFromCodeCoverage .net framework attribute
there is already this attribute in framework, most of code coverage tools make use of it, why not to use it.
0 votes -
Integrate with the upcoming project rider, similar to what WallabyJS does
Integrate with the upcoming IDE from jetbrains to support project rider. Project rider is already available for download. Based on intellij. NCrunch couldn't do exactly what WallabyJS is doing and providing a number of IDE integrations.
235 votesWe now have NCrunch in JetBrains Rider!
https://blog.ncrunch.net/post/NCrunch-V5-Now-Available.aspx
As of today, we're officially in a BETA state with our Rider support. Although we're sitting more or less at feature parity (compared with our VS plugin), our Rider plugin hasn't yet seen the sort of rigorous real-world testing as we have under VS, and there is still a lot of performance optimisation to be done.
Right now the plugin is only available for direct download in ZIP form. You'll need to install it by clicking on the cog icon in the Rider plugin settings. We'll be publishing it to the JetBrains market in a few weeks when we're confident that any critical issues have been ironed out.
Please take the time to report any issues you encounter so we can fix them.
Thanks everyone for your patience with us over the years while we've worked on this. It's been quite a…
-
HTML encode span text for AllResults.html file
So if you have a test case that contains an opening HTML tag and not a closing tag the AllResults report becomes mangled.
My TestCase: [TestCase("<div>")]
Generated HTML by the NCrunch console tool: <span class='name'>TestNCrunch.Class1.Test01("<div>")</span>
really it should be this: <span class='name'>TestNCrunch.Class1.Test01("<div>")</span>
1 voteIntroduced in 2.20 (Released today).
-
Disable conhost host
In process explorer you can see that every nCrunch.TextHost452.x86.exe load a conhost process, which isn't really needed, so it's just wasting performance and resources and fixing this would be really easy. (In Visual Studio for example just set project type of your exe to windows application)
1 voteIntroduced in 2.20 (Released today).
-
Support .NET Core
I'm new to NCrunch. I've just seen on Pluralsight and fell in love with it at first sight.
However, I'm working in a project platformed on .NET Core.
Do you plan to support it in the near future?
(Maybe if lots of us vote?)39 votesImplemented in V3.4.
-
Save to project/solution config which tests to run/ignore
We have a large number of tests. Sadly not all of them are true unit tests and require external systems to started prior to the test.
It seems if I Ignore all tests and then un-ignore a select few I want to run in Ncrunch there is no way to save this config and commit it to source control. This means each user on the dev team has to do something similar but there is no way to share what tests we want ncrunch to always run.
I am thinking something similar to what ReSharper allows you to do. It…
3 votes -
Ability to create global engine modes, and set default engine mode globally.
I've created a "Run all unit tests automatically" engine mode in multiple projects because I don't see how I can create a new global engine mode, and set a global default engine mode. This would be a time big time saver!
3 votesThis can now be done with the new configuration system in NCrunch V3.
http://blog.ncrunch.net/post/Announcing-NCrunch-Version-3!.aspx
-
Solution-level defaults for all projects
There are some settings that we need on every single project within our solution. Currently this means we need a .ncrunchproject file next to every single project with this setting.
It would be nice if we could set this once in the .ncrunchsolution file instead.
For bonus points, the individual projects could then override that new default value in their own .ncrunchproject file.
FYI - The existing value I need this for is UseBuildPlatform=x64, which is set globally in one of our msbuild rules, but not specifically set in every single .csproj file. I'd don't want to need to set…
3 votesNow available in V3 with the new configuration system.
http://blog.ncrunch.net/post/Announcing-NCrunch-Version-3!.aspx -
Turn off rosyln analyzers during NCrunch Build
Inspired by post http://forum.ncrunch.net/yaf_postsm7582_Build-fails-with-custom-analyzers.aspx
Rosyln analyzers in Visual studio 2015 get run during NCrunch Builds. Would it speed up compilation if analyzers were turned off in NCrunch?
I cant think of a reason why it is necessary - Visual studio gives you real time feedback in the editor and on manual compiles. I wouldn't watch the NCrunch output window for build warnings
6 votesSetting the ‘Allow code analysis’ NCrunch setting to False will now disable Roslyn analyzers.
-
7 votes
Implemented and released as part of NCrunch v4.5.
-
Store NCrunch configuration files as UTF-8
NCrunch stores its configuration settings in UTF-16. GIT sees that as binary file, and doesn’t show the text diff, even though, they’re just xml files.
I know you can configure GIT to show those changes (using, for example) the vimdiff tool, but that’s ugly).
I converted my files to UTF-8, but when you make changes through the NCrunch settings dialog, they’re converted back to UTF-16 :(
Could the settings of NCrunch be stored as UTF-8, or at least, maintain the encoding on disk?
1 voteImplemented in NCrunch 2.19
-
Warn when your licence won't be valid for the next version
When notifying a user when there is a new version of NCrunch to download, add a warning if their licence won't cover the new version.
This would be preferable compared to only finding out after upgrading and starting Visual Studio that you need to either uninstall and re-install your old version, or go through procurement to get a new licence and live without NCrunch in the interim.
1 voteThis feature was released in NCrunch v2.15 (May). Unfortunately, as there is no way to apply the feature retrospectively, everyone that is upgrading from older versions is still being hit by the bad UX.
-
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
-
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.
-
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 -
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.
-
Enable "Build Configuration" to be set at the global level
Hopefully the title of this is enough, but basically we have the following scenario:
Some of our Grid Node servers are on premises and have a "local" SQL instance. This fits in well with our test config as they all point to the local instance.
We also have some Grid Nodes running in Azure, and these do not have SQL Server installed but we'd like to point them to SQL Azure (so basically change the connection string).
We can do this on a "Project Level" currently, but we'd like it to be configurable on a per machine level.
2 votesNow available with the new V3 configuration system.
http://blog.ncrunch.net/post/Announcing-NCrunch-Version-3!.aspx -
make "First Time Crunch" Dialog for each new solution optional.
I, and I'm sure others as well, use a similar, if not identical, NCrunch configuration for each solution. So I would suggest making the "First Time Crunch" dialog optional for new solutions. If disabled, a default configuration could be applied to each new solution.
10 votesThere are some conflicting views about how this wizard should be improved. I’ve tried to tackle the underlying design issue with the new V3 release. I hope this should get rid of the frustration everyone is experiencing here.
http://blog.ncrunch.net/post/Announcing-NCrunch-Version-3!.aspx -
16 votes
- Don't see your idea?