Skip to content

Feature Requests

55 results found

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    completed  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 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
    MCT

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 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 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    completed  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    41 comments  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. 7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. 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 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Support .NET framework 4.7.2

    Currently, NCrunch supports up to 4.7.1.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’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.

  20. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3
  • Don't see your idea?

Feature Requests

Categories

Feedback and Knowledge Base