Feature Requests

  1. Create an NCrunch License Server

    It would be great to have a central management point for our NCrunch licenses.

    30 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 →
  2. 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)

    We’ll send you updates on this idea

    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Add possibility to expand/collapse multiple node levels in "NCRunch tests" window

    Problem: Today there is no way explode/collapse of tree nodes in the "NCrunch Tests" window (e.g. with +,-,* keys).

    Request: Add possibility to, in some way, expand/collapse multiple levels. It is very cumbersome today when you type something in filter and need to manually expand all test nodes one by one to see which tests are matching.

    36 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

    10 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Remote server: Remember service settings for Grid Node Service during upgrade.

    v2.7.0.5

    I have a non administrator account NCrunch Grid Node Service is running under as well as a service dependency on SQL Server express.

    When upgrading these settings are reset to default values (e.g. Local System as the account service is running under).

    I would like my customized settings windows service settings to be kept during upgrades.

    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  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. standalone executable version for builds etc.

    There should be a standalone executable version of NCrunch to allow for build integration with the NCrunch grid. This will make builds run faster where there are a lot of tests, and will make NCrunch much more compelling for large businesses.

    Ideally this would also offer XML & JSON versions of the coverage report, removing businesses' reliance on NCover and saving them money.

    19 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 →
  7. 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)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  8. Provide Debugging Support for Async/Await Methods

    Posted in response to: http://forum.ncrunch.net/yaf_postsm5589_does-not-exist-in-the-current-context.aspx#post5589

    It seems there are technical issues that limit the debugging experience of async/await methods when using NCrunch. Essentially the auto's, local's, and watch windows in visual studio cease to function properly when debugging async/await code when using NCrunch. Ideally, such technical issues could be overcome, but if that is not possible, the following would suffice:

    Add a debugging mode in NCrunch that does not add NCrunch instrumentation to the code. This would allow new debugging options such as 'Debug covering tests without instrumentation' and 'Break into first covering test without instrumentation'. This would allow the…

    31 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 →
  9. Separate ncrhunch project configuration from user setting for source control integration

    Currently there is *.NCrunchproject with both user settings and project configuration: what files are to deploy, what build configuration to use, etc...
    Once I set up and committed *.ncrunchproject files for 50+ projects, the files continued to change for my local environment: what tests to include, what warnings are disabled, etc...

    Idea is to separate Global Configuration from User settings, so we can add *.nchrunchconfig to repository, and *.ncrunchlocalsettings to ignore list.

    50 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 →
  10. Enhance "Impacted tests" filter

    The engine mode "Run impacted tests automatically, others manually" is a great idea, but nCrunch seems to think pretty much every test was impacted whenever I make any small change. This is most obviously wrong when I change one of the existing unit tests itself and then all other unit test run too. I realize that it is almost impossible to know for sure whether or not a given test has been impacted under all scenarios, but I would like a mode that has nCrunch error on the side of running less and thereby using fewer resources rather than erroring…

    13 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 →
  11. Make "Custom Environment Variables" solution specific

    I have different environment variable settings for different solutions, thus I would want the setting in "Custom Environment Variables" not to be stored globally on my machine but instead specific per solution so I don't need to manually change them depending on solution used.

    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 →
  12. 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)

    We’ll send you updates on this idea

    completed  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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)

    We’ll send you updates on this idea

    completed  ·  3 comments  ·  Flag idea as inappropriate…  ·  Admin →
1 3 Next →
  • Don't see your idea?

Feature Requests

Categories

Feedback and Knowledge Base