Feature Requests

I suggest you ...

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Let tests run continuously parallel but randomized - to find concurrency issues

    I had the problem that my test setup created some files and sometimes test would interfere because they moved some files. In general i would like to find out if there are concurrency issues in my code or in my tests. I know its not a safe way to find them, but if I could say "these 3 tests should run in parallel for a while" would ease debugging if I already know there is an issue

    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 →
  2. Add 'Clear search' button next to "Text to search on" in "NCrunch Tests" window

    It'd be useful to clean the search text in one click, similar to OOTB VS and other software experience.

    Right now we have to focus on the text within the search box, then double click and delete, or backspace a lot.

    Out of the box VS test window has that little button to clear the search, as well as other systems do.

    Matter of habit and efficiency while working with UI across various apps.

    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 →
  3. Better exception handing so that VS won't be crushed

    Please improve stability/exception handling, provide optional "Submit crash report" window so that we can feedback the exception and other details, and isolate NCrunch from the VS.

    We have been seeing unstable behaviour caused by NCrunch while intensively running 1000+ tests across dozens server nodes, all of them cause VS restarted.

    That's extremely annoying giving the fact that after the VS crash NCrunch "tries" to pick up tests from the very beginning. We can't complete the whole test suite having crashed somewhere along the way.

    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 →
  4. Shortened name should just be the test name when viewing with Tree Structure set to test

    Currently, when I want to view tests in flat list, I set the tree structure to "Test" but all the following columns display the same values

    Name, Shortened Name and Full Test Name !

    It would be helpful if the Shortened Name just displayed the test name rather than the full namespace.

    4 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 →
  5. Show/Hide previously passing, but now out of date tests

    When using the engine mode of "Run impacted tests only, other tests manually", the Test Window provides a green question mark indicator next to tests that were previously passing, but are now out of date (at least that's what we believe the green question mark indicates).

    We would like to request an enhancement to the Test Window to show/hide the green question mark tests; this would be an icon next to the current four indicators that will toggle the visible tests: Passing (green check mark), Failing (red X), UnExecuted (blue question mark with an eyeball), and Ignored (yellowish circle with…

    17 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. Mark tests using TestCaseSource as failed if an error in the method providing the TestCaseData fails

    Currently an NUnit test that uses a TestCaseSource attribute to provide the data will not show up at all if the method providing the TestCaseSource data has an exception.

    I often end up resorting to Resharper to run the offending test to find out what is going on.

    It would be nice if the tests that are failing because their TestCaseSource is not running can show up as failed tests the same way that they do in Resharper.

    4 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. Add 'Run tests on servers with capability(es)' ability

    So far we have two options to run tests:

    1) Run all/selected/whatever tests on all servers, so they would be run with per-capability match
    2) Run tests on a particular server

    That is not convenient once we want to run a test or set of the tests on a server with a particular capability.

    For instance, we'd like to run a test or a test suit against server with "WinXp" or "Win7" or "Win8".

    The things is that we can do that, but we either need to manually set the server, or we have to set the attributes on the…

    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 →
  8. Add 'Import/Export' NCrunch servers list from *.csv file

    So far it's is a bit time consuming and annoying to put up 20-30 servers in the server list.

    It'd be nice to have an ability to import server list from *.csv list.
    Server ip, port, password would be just about right.

    Same same goes with exporting - export current list into *.csv list, so that other people can use them as well, or so that we won't have to put them again and again.

    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 →
  9. Enhance 'NCrunch Distributed Processin -> Server Tasks' window with additional information

    It would be nice to enhance 'NCrunch Distributed Processin -> Server Tasks' window adding more context.

    Right now it shows 'Processing Taks: 1 test(s) in XXXXX.Test', so would be nice to expand on that and show what are the tests being run right now with that task.

    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. Enable columns grouping on both "NCrunch Distributed Processing'" and "NCrunch Tests" window

    Please enable grouping on "NCrunch Distributed Processing'" and "NCrunch Tests" window grids so that it would be possible to have extra dimension on grouping servers by capabilities, or tests by "Excecution status".

    With dozens servers we have to keep up with the name convention, naming the servers in a specific way. Grouping by capabilities would be a better choice.

    Same same with tests - grouping by excecution status, 'failed, being run, passed' would be just awesome to have - similar to out of the box Visual Studio tests window.

    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 →
  11. Optimize test status refresh between VS reloads on large amount of tests

    Once VS loads, NCrunch seems to refresh tests status.

    We noticed performance degradation on 500-1000+ tests.
    It takes about 10 minutes (1 test per second or somehting) to get the whole suit refreshed on the status.

    Always '500+' tests are queried for execution, 100 failing, no tests ignored. Hope that VS won't go down, as NCrunch will start that refresh process again from the very beginning.

    With current config we have ~1000 tests and 8 Azure VMs in the grid, 4CPU + 8G RAM.

    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. Add confirmation on deleting server node

    Please add a confirmation dialog "You sure you want to delete a node" while deleting a server node from the server nodes list.

    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 →
  13. Support for NSpec

    I'd love to run my nspec.org tests via ncrunch.

    16 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 →
  14. 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.

    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 →
  15. Add host spot detection.

    Add the ability to highlight risky code paths to help a developer focus their attention on un-covered code paths.

    Hot spots should be defined by areas of high cyclomatic complexity and low test coverage similar to the functionality found in JetBrains dotCover.

    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 →
  16. output window hyperlink for logging file and line number in standard visual studio format

    The output window currently requires the format "path: line number" which is not the format supported by visual studio. Visual studio windows require "path (line): message".

    Please add support for the visual studio standard format to allow hyperlinks to work in all windows.

    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 →
  17. Allow to run the tests on the grid node while the foreground solution is still compiling

    When working with large solutions, it would be great if the grid nodes would already compile/execute tests in parallel while the foreground solution is still compiling in Visual Studio.

    For the moment it seems that whenever I trigger a re-build, NCrunch is pausing to wait for completion. As the re-build takes several minutes (5-10), that seems to be a quite large delay to wait for the test results.

    My usage scenario is that I have several grid nodes with some RAM drives (having 2-4 GB capacity) and a large solution with around 160 projects. Thus, when executing, some of my…

    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 →
  18. Test Filter Builder: Enable filtering by Project Name via regular expressions

    Test Filter Builder already supports filtering by Full Name with Regular Expression, and it supports filtering by Project Name, but it doesn't appear that there's a way to filter by project name using wildcards/regex.

    I've got test projects containing pure unit tests, named *.UnitTests as a convention, but the test classes' namespaces are the same as their SUT (system under test) class (the namespaces don't have "*.UnitTests" in them).

    I'd like to trigger my (pure, fast) UnitTests to run when impacted, but not my integration tests (they're in separate projects named *.IntegrationTests).

    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 →
  19. Allow user to set color of code coverage marks while a test is executing.

    Currently it only goes a few shades light and it's difficult to see if this is in progress or if it's already passed/failed. Being able to set this color to something like orange gives a clear indication that the test is in progress.

    Changing the graphic would also work, instead of a green circle it could be a green question mark.

    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 →
  20. Add median, quartil, percentile or truncated mean to "Marker performance aggregation type"

    First run takes offen more time as following ones. Because of small count of runs in typical unittest scenario, the first outlier has too much weight. In this Case median, quartil, percentile or truncated mean are robust.

    Ps. It should be simple to implement this. )

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

Feature Requests

Feedback and Knowledge Base