Skip to content

Feature Requests

I suggest you ...

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

58 results found

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

    We’ll send you updates on this idea

    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  2. 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)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  4. Add support for exporting coverage in ndepend xml compatible format

    7 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    4 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  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 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  6. navigate to first compile failure

    reposting the original suggestion here as I'd love a keyboard shortcut that just went straight to the next compile error rather than having to click in the NCrunch test output window:

    Somewhat related to http://forum.ncrunch.net...keyboard-shortcuts.aspx .

    As above post states, ReSharper has a feature to navigate to next error in file, or next error in solution via keyboard shortcuts if that is enabled (resource intensive).

    Since NCrunch includes a continuous build runner, I would want to have a shortcut so I quickly can open the file which has the compile error.
    This way the "analyze errors in solution" can be…

    7 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  7. 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)
    Close
    Close

    We’ll send you updates on this idea

    completed  ·  1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  8. 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)
    Close
    Close

    We’ll send you updates on this idea

    3 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  10. The ability to mass-unpin tests

    NCrunch is great, but there is one annoying thing in the GUI - there is no option to unpin (and pin) tests by right-clicking on the whole namespace (or even root namespace). You can only pin/unpin individual test methods or test classes.

    6 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  11. No more notification for versions not covered by license.

    Stop continuously popping up notifications about (the same!) new versions if my license doesn't cover the new version. That's not helpful, it's basically sales spam.

    5 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    5 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  12. Add font configuration for output windows

    Allow configuration of the font used, specifically in the Test Results window, as the default is not the clearest for reading through stack traces in a test result output. This would either be built into the ncrunch config, or accessed via the Visual Studio fonts configuration section.

    5 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  13. 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)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  14. 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)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  15. Automatically resolve "lost project reference" when binary references are used

    When one project in a solution references an assembly that is the output of another project in the same solution (but does not use a Project Reference), NCrunch reports a "Possible 'lost' project reference" and is unable to trace unit test coverage in the referenced assembly.

    I would ask that NCrunch provide a means to "capture" that reference and allow NCrunch to see this as a project reference without having to modify the VS project files. Our build environment requires the use of direct assembly references and can't be modified to use project references, so the usefulness of NCrunch is…

    4 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    completed  ·  2 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  19. Change Configuration Wizard defaults

    In the configuration wizard I always change to "run my tests alongside each other" and "lets my tests run".
    I would really appreciate a way to set this as defaults instead of always changing those (it is very simple to change during the wizard, yes I know, but still a bit annoying...)

    3 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  20. Remote server: Remember disconnected servers when reopening solution.

    (Originally from http://forum.ncrunch.net/yaf_postst1180_Remote-server--Remember-disconnected-servers-when-reopening-solution.aspx )
    v2.6.0.3

    I would like my disconnected servers to stay disconnected until I tell NCrunch to connect, even if I am restarting vstudio etc. Currently disconnected servers are connected when reopening the solution and depending on engine mode start to run tests etc. which are not currently supported by that server.

    Which servers are enabled/disabled should preferably be saved in a solution user file config (versus global globalconfig.crunch.xml) so solution 1 may have server A and B enabled and solution 2 only server C etc.

    3 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    completed  ·  3 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
2
  • Don't see your idea?

Feature Requests

Categories

Feedback and Knowledge Base

(thinking…)