Feature Requests

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

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

    13 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 →
  3. Exclude from Metrics Aggregation by wildcard

    Allow user to exclude files from Metrics Aggregation by wildcard. As an example, I'd like to exclude all *Designer.cs files from being counted.

    14 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 →
  4. Show number of lines uniquely covered by a test

    Today, the test fail/pass indicators on each line show which tests are executing that line.

    I would like to have an option (maybe in the Metrics window) which tells me the number of lines covered solely by one test.

    My goal behind is to identify code that is only run by few system/integration tests and clearly needs more tests. Such tests might start/run half of the system just to prepare a test so that - from the coverage point of view - the code looks like to be covered but - from the testing point of view - actually isn't…

    4 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. Force tests to run inside the same process

    NCrunch spins up multiple processes to run tests. This is great most of the time.

    But if a suite of tests has some expensive setup that only needs to happen once, that setup will run once for each process. Increasing the overall time it takes to run the whole test suite.

    Provide a mechanism to force (suggest) NCrunch to run 2 tests in the same process. Something like a [SharedContext("Name")] attribute. Then when 2 or more tests are queued that have the same shared context, NCrunch should run those in the same process.

    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 →
  6. Option to disable stylecop MSBuild integration

    Currently, FxCop Analysis can be switched off for Performance reasons. For the same reason it would be great to have a Setting where the StyleCop build Integration (http://www.nuget.org/packages/StyleCop.MSBuild/) can be switched off as well.

    An additional benefit would be that there is no need anymore to occasionally reset the NCrunch test pipeline because of build failures (it cannot copy the StyleCop NuGet package which is at that time in use by another NCrunch process).

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

    We’ll send you updates on this idea

    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Show risk information in code margin.

    Show colour indicator and number indicator. Number will show how many tests cover that method and colour will say if its enough tests to fill safe.

    2 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 →
  8. make grid nodes discoverable on the network

    I think it would be great to use zeroconf or some such to provide a way to find available grid nodes on the network. Having to know the name or ip of each machine is cumbersome.

    Would suggest requiring the user to assign trust to the nodes before they get used for any calculations though.

    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 →
  9. Risk/Progress window move to toolbar (status bar) with progress bar. Add text "xxx/yyy test pass"

    Risk/Progress window move to toolbar (status bar) with progress bar. Add text "xxx/yyy test pass"

    Reason: unable dock this windows in right position when clip/unclip (auto hide ) dock panels.

    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 →
  10. Ncrunch Metrics Filter

    The inclusion of a filter in the Metrics folder would be great. At the moment I have to export to excel and filter which doe snot give me a lot of options. Filtering by name and project and ability to exclude would be great

    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 →
  11. Provide an option to only enable grid node when machines has no active user sessions

    I'd love to make use of the latent power of all the locked desktops in my office but don't want to risk using nodes when someone is logged in.

    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 →
  12. 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 →
  13. 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 →
  14. Allow coverage marker colour to be defined for tests in progress

    When tests execute the colour of the coverage markers darken. This is very useful for determining when affected tests have completed. However, the contrast is too subtle. It would be good if this could be changed in the 'Coverage Markers' configuration section. Either with an absolute colour or at least to have control over the percentage of darkening.

    2 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. Remote server: Run test on all (connected) servers

    I have a test which is required to be run manually to reset the environment to a initial state.
    I would like the option to run the test on all servers at once. Now I have to select "run test on server X" for each server I have which is tedious.

    (This feature would also be good to ensure a particular test is passing on all servers).

    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. Support for C/C++

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

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

    We’ll send you updates on this idea

    9 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Support UITestMethod in Windows Store apps

    Posted in response to: forum.ncrunch.net/yaf_postsm5807_UITestMethod-not-recognized.aspx.

    Currently NCrunch ignores test methods with UITestMethod attribute which forces the test to run on the UI thread. This is required whenever the test needs to manipulate a UI element even if it's not a UI test in itself.

    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 →
  18. Remote server: Add some sort of performance index per server

    I would like to have some index indicating how well the grid node server performs related to other servers.
    For instance, if I run 2 grid servers on Azure and 2 on internal network, I want to know if it's worth adding more servers on Azure or on internal network (or if it helps out scaling Azure servers etc.).

    One idea might be to have an average processing time on tests, and check when test has been executed on different servers is above or below the average execution time and calculate some sort of performance index from those measurements and…

    4 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. Add Setting to Allow NCrunch to Output to Standard Console

    Add a way to force console output to appear in the regular 'Output' window rather than having to click the test itself and see the output.

    This would be extremely useful so i view my Console.WriteLine output in real time in the Output window rather than having to wait until the test finishes and have to click on it to see the output. Also when my tests fail by throwing exceptions when using FluentAssertions, the code hangs on that line and anything i wrote to the console is lost when i stop debugging the test.

    Basically we just need to…

    3 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. Test Window Filter

    I would like a filter in the test window that "show only tests that should runs automatically due to configured Engine Mode"

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

Feature Requests

Categories

Feedback and Knowledge Base