Skip to content

Feature Requests

300 results found

  1. Merge "custom environment variables" settings between shared/user settings.

    Today the "custom environment variables" are "all or nothing" between the layers, e.g. if you have 5 settings in "shared settings" and want a new one (or modify one) locally, you need to duplicate all 5 in "my settings" to avoid the other ones being "unset" in the test runner.

    I would like "my settings" to only override the ones I specify, so I can keep the 5 ones in "shared settings" being "active", and only add (or modify) 1 specific in "my settings".

    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)
  2. History of work session

    I'd like to be able to see the history of my work session, meaning at the end of the day I'd like to see visually when my code was compiling, when my tests were all green.
    The purpose is to be able to identify if I spend a lot of time in those states and try to reduce that time.
    It would be useful for self-improvement or coaching.

    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)
  3. Grid Node Serrvice Log On Credentials on Installation

    Set User Account for Grid Node Server on installation and/or Keep Log On Credentials an an Update.

    For .NET Core Projects it is needed that the builds or not running under the SYSTEM Account

    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)
  4. Extend line hit markers to include hit count and first hit order

    Two existing requests want hit count:

    https://ncrunch.uservoice.com/forums/245203-feature-requests/suggestions/15401490-hits-count-on-coverage-marker-circle

    https://ncrunch.uservoice.com/forums/245203-feature-requests/suggestions/6077791-show-number-of-lines-uniquely-covered-by-a-test

    , but I think that it would also be great if you could include a first hit order, then from a glance you could see the execution steps through the code (probably by thread in case multiple threads are used) and determine if line A was executed before line B

    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)
  5. Configuration option to completely remove the failing build message

    The message below is not necessary for users familiar with your product:

    NCrunch: If you are experiencing problems in getting this project to build, have a look at http://www.ncrunch.net/documentation/troubleshooting_project-build-issues

    It has 2 drawbacks:

    1) It contains a url which is easy to hit as there is no space between this url and the url for the first error in the build.

    2) It takes up screen space.

    So, a configuration option in General Settings to turn this off would be good. For those who wish to see the message, add a line between it and the first error message 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

    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)
  6. A more obvious colour of the coverage markers to show a build error

    When working in code, test or otherwise I would like more obvious feedback for when a build has failed as I often mistake the dull green of a previously passing test with a failed build for the normal passing green.

    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)
  7. Gated Check In Support

    It would be great if Ncrunch provided an optional gate for check-ins when there are failing unit tests. Check-ins to version control systems would fail and display failing tests.

    This would be helpful for long-running unit test builds, so that the work could be offloaded from a central build server to incremental runs on everyone's dev machine.

    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)
  8. Shortcut to run only failed tests

    Sometime I fix an issue for a failing test where NCrunch cannot detect the test is impacted.
    Instead of running all pinned tests I would like to bind a shortcut to only run failing tests (Similar to vstudio's TestExplorer.RunFailedTests) to verify the fix 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Show what it the currect engine mode on "NCrunch Test" screen or maybe via some icon in the VS status bar.

    Why?
    I often switch between modes like this:
    Run all tests automatically -> Run all tests manually or Run pinned test automatically -> Run all tests automatically
    This is due to make sure NCrunch does not get into the way by running tests that at the moment are doing more harm than good.

    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)
  10. Test Coverage Analysis by Specific Test Class

    I suggest to make possible to change the way code coverage is calculated.
    While I am developing I do not do much end-to-end testing. What I do is purely unit testing as part of my TDD process. I would like to have the code coverage calculated class by test class.
    Example case: Class "Car" being tested by class "CarUnitTests". I would like to have the code coverage of class "Car" being calculated exclusively by the tests present in "CarUnitTests".

    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)
  11. Client priority setting for use by node servers

    We're looking into setting up an NCrunch node farm. This would be used by developer machines but it would also be used by the build server. When the build server goes to run tests, we'd like to have those test tasks take execution priority over test tasks coming from dev machines. Is this possible?

    From Remco: Presently it isn't possible to control this. The grid nodes operate on a round-robin type request system that treats every connected client equally. The only way to ensure priority for the build server given NCrunch's current feature set would be to set aside nodes…

    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. Support for debugging with the 'Microsoft Child Process Debugging Power Tool'

    When debugging tests with NCrunch the 'Microsoft Child Process Debugging Power Tool' (https://marketplace.visualstudio.com/items?itemName=GreggMiskelly.MicrosoftChildProcessDebuggingPowerTool) does not work.

    Maybe this can be fixed.

    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. Introduce NCrunch.TestContext or similar to get info of current running test, e.g. attributes

    Original thread: http://forum.ncrunch.net/yaf_postst2127_NCrunch-attributes-on-interface.aspx

    I would like a way, in similar to NUnit\s TestContext, to read information about current running test.

    One piece of information I would like is attributes like [ExclusivelyUses]; In a complex test setup I might share test logic for multiple tests, and then it would be good to ensure that the proper attributes are applied on the tests to e.g. avoid deadlocks, or ensure an integration test has [ExclusivelyUeses("IntegrationTest")] attribute set etc.

    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. Allow "Build Successful" messages to be suppressed in Tests view separately from green tests.

    I usually organize my Test window by project. I sometimes want to see the green tests in the Tests window to keep a consistent view as tests alter between red and green, and to remind myself of which subset of tests I'm currently monitoring. However I almost never want to see all the Build Successful messages there for projects that don't contain any tests (in my case, that's dozens). If a build fails, I would still want to see it, but otherwise all that green is just a lot of noise to me.

    Is there a way to suppress those…

    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)
  15. keyboard shortcut to reset ncrunch (after build failure)

    I would love a keyboard shortcut to reset Ncrunch.
    I don't know if its possible to assign it myself, could not find it in customize keyboard.
    maybe the disable and (re)enable Ncrunch sequence is the same as a reset,...?

    Use case:
    - I open a solution in VS 215
    - ncrunch starts and reports green on risk/progress bar
    - I get latest version for a solution from sourcecontrol
    - build fails because there are not new nuget packages referenced.
    - I build the solution which does a nuget restore
    - then I have to open the ncrunch tests window (using…

    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 metrics to show method/function level coverage

    Currently the metrics allow the drilling down of coverage to the class level, but I'd like to be able to drill down into individual functions, and perhaps even properties.

    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. Support MoeIDE regards code coverage icon rendering

    After installing MoeIDE (
    https://marketplace.visualstudio.com/items?itemName=vs-publisher-593793.MoeIDE), for VS 2017, and configuring a background image, I noticed that NCrunch's code coverage icons are no longer visible.

    It seems that MoeIDE might be displaying the background image over the NCrunch icons. It would be awesome if NCrunch's icons could be adjusted in order to render on top of any images MoeIDE displays.

    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)
  18. Keyword highlight in test output window

    I have tons of log output during tests, however often I'm most interested in log output from test itself I am currently working with. Thus it would be helpful if I could highlights lines containing specific keyword (e.g. "*Test" to highlight test related log lines from test loggers).

    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)
  19. Command line argument for excluded test visibility in report

    User can hide excluded items in Visual Studio by setting MetricsTreeShowExcludedMetrics value to false. But if you use command line tool for CI it outputs all test and sets html class to "excluded childNode".
    It would be nice to have setting ShowExcludedMetrics argument in command line tool

    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)
  20. Code Coverage Suppression on Next Line Only

    On unit tests where you check for expected exceptions the end of the method can't be reached, so the line with the closing curly bracket keeps uncovered.

    Placing a no coverage comment directly after the closing curly bracket works.

    If you reorganize your code by using automated tools such like CodeMaid or ReSharper, the no coverage comment does not stay after the designated line and you have to adjust that by hand again (and again...).

    Introducing a suppression comment like
    "// ncrunch: no coverage next"
    which can be placed directly over the closing curly brackets would be moved as expected,…

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

Feature Requests

Categories

Feedback and Knowledge Base