Feature Requests

  1. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    completed  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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 DONT_INSTALL_NPM 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  8. Support .NET framework 4.7.2

    Currently, NCrunch supports up to 4.7.1.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    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.

  10. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. 0 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    completed  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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("&lt;div&gt;")</span>

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    41 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1
  • Don't see your idea?

Feature Requests

Feedback and Knowledge Base