Skip to content

Feature Requests

298 results found

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

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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

    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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Allow negative wildcard inclusions

    NCrunch allows you to add files and directory to include in the workspace using file globbing patterns. This is a great feature. However, this feature could be improved to also allow you to specify "negative inclusions", which would greatly benefit large solutions.

    My solution has 107 projects in it and one of the projects is a test project that runs some "solution-wide" tests using Roslyn Compiler Services. So this test project requires that the entire solution be in the workspace. However, what I don't need are all the {bin,obj}*. files, just the *.cs and *.csproj files.

    Currently, it's really difficult…

    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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Engine mode condition to allow distribute processing only of some tests

    Summary: I would like to specify an engine mode e.g. "Run db tests locally, all other distributed".
    Details: I would like to define grid nodes condition in the NCrunch engine mode settings. A first simple step would be to add setting similar to "Tests to execute on this machine", but under the Distributed Processing node. This way I can ensure no test with category [DbTest] is executed on grid nodes, but only on local (where I have the test db set up).

    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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Include Process Id in NCrunch Console Timeline report

    I would like to see when NCrunch starts up a new, or reuses existing, process in the NCrunch Console Timeline report, so I can find if long test run duration is due to process startup time or due to slow test run.

    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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Run same test with different configuration options (similar to NUnit's TestCase)

    Let's say I need to support 2 db providers (e.g. SqlServer and Sqlite) and I write the same (1) test for both but in the configuration file for the test project I define which db provider it should connect to.

    Currently the work process is something like:
    1) Run all tests with SqlServer provider setting set
    2) Change configuration file to use Sqlite provider.
    3) Re-run all tests to tests towards Sqlite provider.

    What I would like to have is something like:
    1) In a setting for a test project, define x number of "environment configurations" where I guess the…

    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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Option to hide NCrunch warnings per user

    I would like a solution setting so clicking "Click here to hide this warning" ends up in my .ncrunchproject.user instead of team shared .ncrunchproject file.

    Background:
    I have a lot of warnings in projects I am hiding, after validating they are valid to ignore. If I am not experienced with NCrunch I probably do not know what they mean, hide it and commit changes to .ncrunchproject files.
    The warnings also include grid nodes warnings, which might only be specific for my machine (if we e.g. do not share grid nodes for the team settings) and really makes no sense to…

    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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. improve indicators for explicit and ignored tests

    I use Nunit but I guess there are similar concepts for other test frameworks. Currently any explicit or ignored tests have white icons in the editor and show as unexecuted in the tests window.

    I would like the option to change these indicators. In particular to change the colour/shape for the ignored/explicit tests icon in the editor.

    I would also like a filter for both explicit and ignored tests in the tests window. This would help me to track these tests down quickly

    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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Allow AssemblyVersion to be ignored in order to prevent errors in NCrunch

    If the AssemblyVersion attribute contains an asterisk (eg "1.0.0.*") then NCrunch cannot reliably build the solution.

    Currently, there is no way to prevent NCrunch from resolving the AssemblyVersion of each project and this causes problems with inconsistencies and NCrunch reporting build errors because MSBuild is expecting a different version of the assembly to the one provided.

    The current alternative to this involves polluting non-test project files with NCrunch-related hacks, which is not very clean.

    In order to resolve this issue, I suggest that a setting feature be added to NCrunch which allows AssemblyVersion resolution to be disabled.

    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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Add 'Collapse All' and 'Expand All' buttons in the UI which would allow me to collapse all the test groupings with 1 click

    It's quite time consuming collapsing the test groupings. I often do this when I want to hone in on a specific project but without loosing complete visibility of the rest. At present I have to perform lots and lots of separate mouse clicks to condence the test groups down - and kind of loose the will to live in the process

    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

    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Endlessly Churn While Logged out

    I'd like to keep Visual Studio open, log out of my account while keeping the machine on, and have NCrunch run Endless Churn in the background.

    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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. White color for "lines covered by passing tests"

    I have tried using the color white for marking lines covered by passing tests, so that I only get highlights on lines of code needing my attention.

    However, when setting anything above 224 it switches back to black, probably some kind of contrast code that kicks in. Could I ask for an option to turn this behavior off, so that if I want white color, I can get white color?

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Add coverage markers to the Find Results Window

    When searching for something in the project file, it would be nice to be able to see whether or not the line in the find results window is covered by a test.

    For instance, I know the piece I'm currently testing is sensitive to the use of DateTime.Now so I need to search all places where DateTime.Now is called and then browse to the code to see if the failing test used that instance in the search results.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
1 2 6 8 10 14 15
  • Don't see your idea?

Feature Requests

Categories

Feedback and Knowledge Base