Feature Requests

  1. Support for C/C++

    It would be awsome if NCrunch could add support for C/C++ (or at least C++ CLI)

    37 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 →
  2. Add coverage aggregates to the xml report produced by the console runner

    The output of the console runner contains HTML and raw xml reports.

    The HTML report is nice, however the contents of the XML files is a bit too detailed to get statistics from it.

    It would be nice to have the same kind of data that is in the HTML file but in XML form (meaning, the % coverage per method/class/assembly/global). Something similar to the DotCover XML or JSON reports. In fact if the format was exactly the same as the dotcover reports we could leverage tools that can already process these files, like SonarQube.

    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

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. 39 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 →
  4. Make a license of NCrunch available for free to Open Source projects

    I can't justify paying for NCrunch to volunteer on a FOSS project.

    ReSharper does this.

    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

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  5. Create an option to enable NCrunch only when on A/C power

    I almost always develop on a laptop - but sometimes while travelling, and sometimes plugged in. I'd like NCrunch to automatically disable itself when I'm on battery power - it does suck energy like crazy - and then re-enable itself when I'm back on the grid.

    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

    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Copy engine mode

    I have fairly non trivial engine modes with test filters set. I want to create a new engine mode based on existing but only tweak e.g. a condition in the filter.
    It would help a lot if could copy an existing engine mode and tweak it instead of re-doing the entire filter.

    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 →
  7. SSL support for NCrunch Grid Node server

    Its a must for remote grid nodes

    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

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Edit entries in 'Additional Files to Include'

    Put an Edit button in the Additional Files to Include dialog which is opened from the NCrunch Configuration window.

    Would allow you to edit the path of an existing entry in the list, just now I have to remove and then re-add which is a little frustrating.

    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

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Add support for custom delegates with MSpec

    MSpec supports Custom delegates.

    https://github.com/machine/machine.specifications/blob/master/Source/Examples/Example.CustomDelegates/Delegates.cs

    Currently NCrunch seems hardcoded to "It", it would be great to support also custom delegates annotated with the AssertDelegate-Attribute

    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

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  10. Show indication that the build is failing

    Right now when the build is failing the line indication is that the test is failing. Technically, it is true. For the developer however, a failing running test, and a non compiling tests require different responses.

    The spinner shows when the build is failing, but is in a very inaccessible placement on the far bottom right. This is not a place that we're used to looking at.

    It would be much better, in my opinion, to have the line-dot color change to indicate build failure in addition to the spinner.

    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

    1 comment  ·  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

    8 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. Option to always start NCrunch disabled

    I frequently switch between working copies/branches and since I use an engine mode which is automatically running tests I would to manually enable NCrunch on startup. This since the test suite is very heavy and I might want to open solution without immediately running all tests and/or I need some changes to e.g. "Custom environment variables" so tests are running correctly.

    (Now I need to remember to disable NCrunch before closing project, which I most often do not remember. Also the now and then occasional vstudio crashes prevents me from setting this)

    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 →
  13. When showing coverage for specific tests show icon against them in 'NCrunch Tests' view

    When I show coverage for a specific test I trace through the code paths which are being executed using the per line coverage, however sometimes I then need to debug through that test, it would be nice if I could easily see which test is currently showing coverage so I can debug it

    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

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Doubleclicking a failing test should jump to the failing line

    If I doubleclick a test in the tests window the test, the file containing the test is opened in the IDE and the cursor jumps to the beginning of the test (Feature: Go to selected test").

    It would be nice to have a "Go to selected test at failing line" feature that can be accessed via right click a failing test and even being able to set this as default action for double click.

    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

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Display test output in text window (on button click)

    We use extensive logging information to analyze test failures.

    Currently the test output is only displayed in a split window of the tests window. This makes reading and analyzing long test outputs (especially with long lines) rather difficult.

    Therefore it would be nice to be able to display the test output with one button click in a separate (temporary) text window (similar to the Visual Studio test runner).

    Posted in response to: http://forum.ncrunch.net/yaf_postsm5490_Ability-to-display-test-output-in-text-window.aspx#post5490

    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

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Add a way (toolbar button ideally) to pin visible tests.

    Often I want to pin failing tests, then make a change so a large number pass, then I want to unpin the passing ones. I can unpin all, show only failing then would like to pin all visible.

    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

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Attribute to exclude specific tests from automatically running

    I have several unit tests and integration tests within the same project. It would be great to have an attribute to exclude the integration tests from automatic runs. These tests would only be trigger-able manually

    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 →
  18. Detect Microsoft.Net.Compilers references and automatically copy it to the workspace

    The Microsoft.Net.Compilers package allows projects to use a specific version of the compiler. When NCrunch attempts to build a project referencing that package it will fail by default with the error: "packages\Microsoft.Net.Compilers.2.4.0\build..\tools\csc.exe" is invalid." The current workaround is to add the tools directory for that package in the "Additional Files to Include" dialog.

    NCrunch should recognize that this package is unique and handle it automatically.

    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 →
  19. Add window showing slowest lines of code

    The slow hotspot markers were super useful in me rewriting portions of test / application code to speed them up.

    It would be useful to be able to see a list of the slowest lines of code so attention can be given to refactoring them.

    Bonus points if this can be sorted based on total time under test, and also average time under test

    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 →
  20. Allow to rerun all tests matching current engine mode

    If I have 2 engine modes "Manual" and "All Automatically except HttpTest", I must toggle between the 2 in order to re-execute all tests.

    I would want a way to execute all tests matching the active engine mode, without having to toggle between "Manual" and the one I would want to be re-executed.

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

Feature Requests

Categories

Feedback and Knowledge Base