Feature Requests

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

    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 →
  2. Allow the console tool to be run continuously

    Im super happy with ncrunch console tool that was just released:

    http://www.ncrunch.net/documentation/tools_console-tool

    However i would also like it to be able to run as a deamon continuously watching a specified folder/solution using NCrunch excellent incremental build/test features.

    Ideally it would output a maximum of N failing tests:

    1: *. [NameSpace].Test failed | at line 12 of filename.
    2: ....

    Ideally it would also support verbose output in json/xml so that plugins for other editors can be written.

    16 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. Provide history of failed tests

    When working on a project where NCrunch is running (all) the tests automatically in the background, some tests occassionally fail and then suddenly pass.

    I would like to have some kind of history for failed tests so that I can even later on delve further into the failed tests to figure out what's going wrong.

    In addition it would be nice to be able to configure the time span (or number of tests runs) for that historical data to limit the memory consumed (I could imagine that using that feature on large projects will have a significant memory impact).

    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

    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Provide a smoother upgrade path for Grid Node Server - (backwards) compatability or run in parallel.

    At the moment, the grid node servers must be updated at the same time as all VS clients.

    Either allow mismatched versions of NCrunch in VS and distributed nodes, or allow multiple instances of the grid node server on the same machine.

    This is holding back our adoption of v2.8 - whether we install the server first or ask developers to upgrade their client first, we have a period where nobody has distributed processing.

    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

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Allow navigation to test in test window

    From the test status gutter or test name, I would like to be able to navigate to the test (right click or hotkey) in the test status window so that I can quickly ignore/unignore all tests in a test class easily.

    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

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Attribute to enable tests with "shared resource" to run on same server within same "session".

    Original thread: http://forum.ncrunch.net/yaf_postst1368_Restrict-multiple-tests-to-run-within-same-grid-node-in-console-runner.aspx

    This is primarily for the console test runner (or e.g engine mode "run all tests within automatically").

    Scenario: I have some integration tests using large test data. This test data is created once and then reused between these tests. When using grid nodes tests using same "test data resource" might end up running in different grid nodes, causing each test creating new test data (which makes the tests slower than if they were run in serial).

    It would be nice to have an attribute e.g. [SharedResource("TestBlob")] making all tests with same "shared resource" to be run within…

    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 →
  7. Allow specflow scenario outline examples to have their own 'dot marker' in the margin

    currently if you have a scenario outline that has several examples there is no way to run a specific example as a test, I can only see the dots in the actual scenario outline and have to then run 'x' number of tests at once (where 'x' is the number of scenario examples)

    I'd like a 'dot' by each line in the examples so I could run a specific scenario example on its own or see which example is actually failing

    9 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

    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Show the PID of process in which a test is running

    I whish to be able to see the PID of the currently running test when I break in it. Thus to allow to attach a performance analyzer.

    See also:
    http://forum.ncrunch.net/yaf_postst1362_How-to-identify-the-ProcessId--PID--in-which-a-test-is-running.aspx

    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 →
  9. Using XBox as NCrunch Grid node server

    When i'm programming my xbox is idle. it would be awesome if I could run ncrunch builds and test on it.

    10 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. Clean up the noise when an AssertFailedException (or similar) is thrown

    When an assertion in a test fails, you get the full stack trace of the AssertFailedException, which is noisy. For instance:

    Microsoft.VisualStudio.TestTools.UnitTesting.AssertFailedException: Assert.AreEqual failed. Expected:<1200>. Actual:<900>.
    at Microsoft.VisualStudio.TestTools.UnitTesting.Assert.HandleFail(String assertionName, String message, Object[] parameters)
    at Microsoft.VisualStudio.TestTools.UnitTesting.Assert.AreEqual[T](T expected, T actual, String message, Object[] parameters)
    at Microsoft.VisualStudio.TestTools.UnitTesting.Assert.AreEqual[T](T expected, T actual)
    at TestInheritance.Tests.RectangleTests.AreaAfterSettingHeightWidth() in d:[some likely really long path]\RectangleTests.cs:line 22

    Of all the above information, the only pertinent information is the message text of the exception and the bottom of the stack where the assertion failure happened. For instance:

    Assert.AreEqual failed. Expected:<1200>. Actual:<900>.
    at TestInheritance.Tests.RectangleTests.AreaAfterSettingHeightWidth() in d:\users\floyd.may\documents\visual studio 2012\Projects\TestInheritance\TestInheritance.Tests\RectangleTests.cs:line 22

    Ideally, for MSTest, NUnit,…

    14 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. Use consistent wording in settings

    When you describe the Spinner colours you use inconsistent language:
    For example,
    Outer circle colour on build failure
    AND
    Text colour when the build has failed

    Should be:
    Text colour on build failure

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

    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 →
  13. Reorganize settings based on events, not entities

    E.g.,
    On build Failure:
    Outer Circle Colour – Dark Brown
    Text Colour – Green
    Line Marker Colour – Brown
    Background music – Ride of the Valkyries

    On Test Failure
    Outer Circle Colour – Red
    Text Colour – Black
    Line Marker Colour – Red
    Background music – God Defend Visual Studio
    ….

    The reason is that humans are conditioned to think in terms of events. When “this” happens, I want “That”.
    I.e., instead of thinking of
    an entity, and all the events that can affect it,
    we human like to consider
    an event, and all the entities that are affected by…

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

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

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

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

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

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

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

    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