Feature Requests

  1. Pin test class in test runner rather than pin each test separately

    Would be nice to have ability to pin test class to test runner, rather than pinning each newly added test separately. When adding a new feature, you tend to spam quite a few tests in new test class, or to some existing class. If solution is big, and you have many tests, the response time from NCrunch becomes poor. Of course you can pin each task separately when you add them, but when you spam many small tests, it becomes annoying. NCrunch could automatically detect newly added or modified tests in pinned class(es) and run them, ignoring the rest.

    8 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Configurable list of custom ItemGroups to be copied over to workspace

    More details - http://forum.ncrunch.net/yaf_postsm7334_Custom-ItemGroups-to-be-copied-over-to-workspace.aspx#post7334

    The scenario is coming up with some shared logic to be used by other teams. They have the freedom to add build targets, so list of custom items used isn't fixed.

    Currently NCrunch just copies over None or Content or Compile items. Having a configurable list of such items will help avoiding workarounds like adding the item twice.

    8 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 →
  3. Cleanup of workspace

    For faster unit-testing, I am using a RAM-drive as workspace, with 4GB space.

    NCrunch keeps all old build artifacts around until they are no longer needed. In practice, this means that as I am working, the workspace keeps on filling up, since a change in one place which doesn't impact something else means both versions are kept in the workspace.

    As a result of this, the 4GB quickly get gobbled up, forcing me to cleanup by deactivating/activating NCrunch (which means everything gets rebuilt, even though this isn't necessary) or manually trying to delete as much as possible in the filesystem.

    8 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 →
  4. Look at working with Live Share

    Visual Studio Live Share is a new collaborative sharing tool that is currently in development for both VS and VS Code.

    We are currently evaluating it, and we noticed that annoyingly, there is currently no way to have the nice dots / coverage NCrunch provides to remote guests.

    There is a task / issue logged with Live Share https://github.com/MicrosoftDocs/live-share/issues/125 which they seem interested in creating an API eventually.

    I think you guys should look at trying to integrate with this... as I believe Live Share looks to be on the right track at the moment... and having NCrunch integrated into…

    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 →
  5. Support for Paket

    Paket is an alternative package manager that support NuGet packages. Currently NCrunch will auto detect NuGet packages that have build targets in the csproj and copy the tools folder into the workspace for that package.

    This does not work when using Paket and requires manual fixup of the additional files to include the tools folders.

    Please add support for Paket based NuGet references in the same way as NuGet is supported.

    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. 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
    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. Native support for xUnit Collection attributes

    Currently xUnit Collection attributes are not prohibiting nCrunch from running tests inside one collection in parallel. So developers require to decorate old tests with nCrunch-related attributes for those test not to be executed in parallel.

    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 →
  8. Create a 'Kill Currently Running Tests and Execute Selected Tests Immediately' button

    The existing 'Run selected test(s) in new process' button just gives the selected tests high priority. This is very irritating when longer running tests are clogging the queue. I often go to the Processing Queue to kill the tests I don't care about so that my test will start sooner. Worse, sometimes the test I want runs together with long tests I don't want, so I can't kill just the long tests without removing my requested test as well. Just run my test, right now! The others can wait.

    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 →
  9. Add a console runner nuget package

    A console runner package would make integration in build systems simpler.

    The would be no need to install the runner on each agent, just get the package from nuget and run 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 →
  10. Visual marker in far left margin when code is collapsed to definition

    For those developers who do code maintenance by collapsing code to definitions (use Outlining Collapse) we can't see which tests in the file are failing at a glance. To see that we have to expand all the code to see the red/green markers.
    All that would be needed is to promote a red or green top level marker to the far left margin to show us what test is failing in the file (when test method is collapsed).

    7 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Allow to temporarily ignore tests

    When some tests are failing for a known reason (eg: When making structural changes, or when developing to an interface which is not yet completed), it would be nice if there is a possibility to tell the NCrunch Tests window to ignore certain tests for a defined period of time.

    For example:
    right-click test in the list
    > Ignore..
    > Ignore for 10min
    > Ignore for 1hr
    ....
    > Ignore for today

    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 →
  12. Test pass/fail in Enhanced scroll bar or R# scroll margin.

    The ability to have NCrunch show the code coverage and test pass/fail in the enhanced scroll bar from power productivity tools or Resharpers scroll bar. Or something similar. That way can tell if tests that are not visible on screen change. Of course could have the tests window up...

    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 →
  13. Allow for easy command-line installation (e.g. Chocolatey)

    Our development machines are built via PowerShell script, which is a very flexible and maintainable way of scaling to many developers. The scripts rely heavily on Chocolatey packages to install software, but unfortunately the unofficial Chocolatey package for the NCrunch Visual Studio plugin is not reliably updated and does not cope well with upgrades. Also, there is no command-line NCrunch package.

    Given that Chocolatey packages are relatively simple wrappers around the existing product installers, it would be great if you could work with the existing package maintainer to improve the existing package, and create a package for the command-line application.

    6 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 →
  14. "first failing test"

    I suggest you include the option to highlight the first failing test in the "NCrunch Tests" window and display the details.

    Right now when there are no tests failing and a test fails, I have to click on it in order to see the details of why.

    Having it automatically show the details would be very helpful and save a few clicks.

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

    We’ll send you updates on this idea

    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Hide non test projects in the NCrunch Tests window

    I typically leave the 'Show Passing Tests' filter enabled. However, when it is enabled, non-test projects also show up in the list with a check next to them. It would be good if the non-test projects would not show up at all in the tests view since there are no tests in them.

    6 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 →
  17. 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
    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 →
  18. 6 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Enable real time output of the test being run in "NCrunch Tests" window

    It would be nice to have real-time or at least "refreshed" every 5-10 seconds "Test output" console in NCrunch Tests" window.

    Right now the output is provided once test is completed, but it would be useful to have some kind of "refresh every N seconds" option for integration tests. They might take minutes to run, and sometimes it is extremely useful to see output in real time - either to kill the test or to see what's going on.

    6 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 →
  20. ncrunch "absorb" solution folder structure to organize the tests

    Can we have ncrunch "absorb" solution folder structure to organise the tests in the test overview window? We currently have two folders (slow and fast) and resharper adheres to that struture (very convenient).

    I'd like ncrunch to do the same. Could you add that to the Tree structure option in the NCrunch Tests window?

    6 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 →
  • Don't see your idea?

Feature Requests

Feedback and Knowledge Base