Feature Requests

  1. Show source code in code coverage report

    In the code coverage report, we would like to be able to navigate into the source code files and see which lines are covered, much like OpenCover does. Here is a screenshot of that feature in OpenCover:

    https://www.dropbox.com/s/38kj2wr5bczbtls/OpenCover%20Source%20Code%20Coverage%20Example.PNG?dl=0

    Our developers love using NCrunch. We would like to use NCrunch for our CI process, especially because it would unify the development and CI environments. The organization is hesitant to use NCrunch for CI without the ability to drill down into the source code in the report to see what lines of code were covered when the CI job ran.

    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. Show impacted tests filter button

    When running only some tests (base on a custom filter) automatically, I would like to see impacted tests that are not in the filter appearing in the Test Window. Adding a filter button "Show impacted tests" will do the trick!

    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 →
  3. Fix up layout of custom engine modes test filter builder screen

    Currently the "Test Filter Builder" screen in custom engine modes renders very badly. (This is on my 4K laptop screen). See http://imgur.com/Vw5Q1qZ.

    This makes the feature barely usable - would be great (and hopefully simple) to fix it.

    1 vote
    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 →
  4. Build solution for execution

    It would be great to take advantage of NCrunch's ability to build a solution in the background with every change; to keep the solution bin's up to date and remove the need to build in visual studio.

    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 →
  5. Filter tests with build configuration

    I would like to add a new condition to the test filter builder, "Build Configuration" that would allow filtering tests based on the currently selected build configuration.

    My use case is for integration tests that take a long time to run. I want to run these when the "Release" build configuration is selected. Running all tests in the solution is not suitable as some tests are only for running manually.

    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 →
  6. Option to select Test Suites dynamically

    We run all our tests from CI server (Jenkins).

    Currently, we add category to each test case. The NCrunch Engines are predefined (which is a huge number), with "Has category" option. When the runs are triggered, the predefined NCrunch Engine is selected for execution (from Console tool)

    This limits our option to trigger different combination of Test Suites from CI server.

    Could you please add the option to be able to dynamically create NCrunch Engines or define the Test Suites.

    For e.g, all test cases has a unique ID. I would like to pass the test case ID's and NCrunch…

    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 →
  7. Make the test timeout depends on RepeatAttribute (NUnit)

    The default timeout is 60 sec. One can change that value but it would be nice if NCrunch could adapt timeout based on the number of repetitions of the same test (in respect of RepeatAttribute of NUnit).
    Today, if I specify a timeout of 120 sec, that timeout is applied no matter how much times the test is repeated in the same tests session.

    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. User custom performance metrics (displayed with performance metrics)

    My prime use case would be counting and measuring SQL queries (would make easier to monitor impact of changes by other developpers).

    Hovering the green/red marker next to a line would display the count and total time for each custom metric.

    This could be implemented with a simple attribute like NCrunch.MetricAttribute("SQL") that would be added on functions and/or with a IDisposable scope (using(NCrunch.Metric("SQL")).

    They would be noop when not compiled by NCrunch.

    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. enable debug on ignored tests

    Often I get to the end of a TDD run and create a total integration test. This test necessarily hits dev database and http endpoints. I want to carefully control the execution of this test, not have it run continually. Ergo, I ignore it. Right clicking on the now "ignored" tests, I see the options to debug, but they don't do anything.

    It would be perfect if I could step into and debug ignored tests.

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

    ...my favorite, fluent syntax mocking tool.

    1 vote
    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 →
  11. Make pending test colors configurable

    I find finished tests (solid color) difficult to distinguish from pending tests (semi-translucent). I suggest making this configurable, either by allowing the user to specify the alpha for pending tests, or by providing completely separate color choices for pending test states.

    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. Allow the NCrunch Tests window to nest/group by Class

    i have my tests setup like this:

    public class CalculatorTests{
    public class AddMethod{
    [Fact]
    public void DoesAdd() { /**/ }
    }
    }

    I'd like to be able to see the tests grouped by class so I can ignore (for example) all the 'AddMethod' tests. I appreciate I could do this by categories, but it'd be a nice addition.

    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. Hotkey to skip sliding build window

    I have a sliding build window turned on as my tests can be fairly intensive to run. Sometimes, however, I'm done making a change and don't want to wait for the sliding window to activate. It'd be nice to have a hotkey to bypass the sliding window on demand.

    I take advantage of all the other fantastic hotkeys around running tests immediately, so this isn't a very big deal. But it'd be nice to have. :)

    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 →
  14. Inline run configuration

    I'm a long time NCrunch user but I feel the feedback loop has worsened significantly over time,

    An incremental compile on my solution takes ~1s but I often have to wait between 20-40s for ncunch to do the same. (I have no clue if this is because of workspace copying or what).

    What I really want from NCrunch is an inline run mode that runs directly on my build output everytime I build (which I do very often)

    But currently I can not instruct NCrunch to run directly on my build output or only try to run (build) after a…

    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 →
  15. Separate test output to separate dockable window

    (Similar to https://ncrunch.uservoice.com/forums/245203-feature-requests/suggestions/5689966-display-test-output-in-text-window-on-button-clic )

    I sometimes work from home with 1 monitor and at work with 3 monitors. I also tend to like having test output in a less "important" place than the tests themselves.
    With vstudio2015 the split setting (bottom or right) is not restored via the windows layout feature.
    if test output was a separate window I can choose to place/dock it wherever I like (and also restore/save its position).

    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. 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 →
  17. 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 →
  18. 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 →
  19. 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 →
  20. 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 →
  • Don't see your idea?

Feature Requests

Feedback and Knowledge Base