Feature Requests

  1. Standalone UI which can be used with every other IDE

    Here are some feature requests for Visual Studio Code and Rider. But these require deep Integration.

    But since VS 2017 sucks so much these days. It would be nice if we can use another IDE.

    I propose a standalone Version with the NCrunch with the UI and Windows which are currently in Visual Studio. But without Visual Studio.

    Of course this is not such a tight integration with the IDEs (not jumping to the code, debug and break into failing tests etc.) but would be a good start. And of course, it is only running tests on save because of…

    11 votes
    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 →
  2. 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
    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 →
  3. 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
    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 →
  4. Add "Title" field for simplified grid node management and identification

    As a NCrunch user, I would like to have an easy way to identify and manage my grid node while using distributing processing window.

    Currently, "server name" field is the only way to identify remote servers. With automated, disposable, DevOps-iified infrastructure, such identification is highly desiured. Out server names are random strings, such as this:

    MB-{RANDOM-8-CHARS}


    • MB-DMHJBDTDD

    • MB-THDRFBDF

    • MB-MKDHSVTD

    We don't really care or have control over this while scaling grid nodes infrastructure.

    It would be nice to have an additional field "Title" or "Display Title" for grid node so that we can have a human-readable name for randomly generated…

    0 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. An option to automatically pin *modified* tests

    Most of the time, I only want to automatically run tests that I'm working on.

    So I use engine mode "Run pinned tests automatically, others manually". And manually pin tests I'm working on.

    Would be nice if NCrunch could automatically pin modified tests (detect changes of test methods and test classes), and automatically pin modified tests.

    I know we already have an option "Automatically pin newly discovered tests". Would be nice if there was another option "Automatically pin modified tests".

    4 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. Attribute to identify type/methods that must have 100% code coverage

    It would be helpful to have NCrunch treat (or at least report) decreases in code coverage as "fail".

    For example, supporting an attribute that marks a project/class/method as "100% code coverage required".

    Or a larger flag such that any code coverage drop is a "failure". This would be a bit trickier to support as it may need to be include a way to identify a baseline. And it may be helpful to distinguish between coverage for old code vs coverage for new code.

    I think starting with a numeric attribute indicating the required coverage would give the biggest ROI --…

    2 votes
    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 →
  7. Add AlwaysImpactedAttribute for Run Impacted Tests Automatically mode

    It would be useful if there was an AlwaysImpactedAttribute that could be attached to a test method so that it always executes when a code change is made.

    The use case I am thinking of occurs with Automapper. We have a test that executes AssertConfigurationIsValid(), but when the engine mode is in "Run Impacted Tests Automatically" NCrunch will not detect that this test needs to be run whenever we make changes to the models in the solution.

    If I could put an attribute on that test method that says 'always run', I could continue to use the "impacted only" engine…

    2 votes
    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 →
  8. Integrate with the upcoming project rider, similar to what WallabyJS does

    Integrate with the upcoming IDE from jetbrains to support project rider. Project rider is already available for download. Based on intellij. NCrunch couldn't do exactly what WallabyJS is doing and providing a number of IDE integrations.

    178 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    21 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Support for Paket

    Paket is an alternative package manager that support NuGet packages. Currently NCrunch will auto detect NuGet packages that have build targets in the csproj and copy the tools folder into the workspace for that package.

    This does not work when using Paket and requires manual fixup of the additional files to include the tools folders.

    Please add support for Paket based NuGet references in the same way as NuGet is supported.

    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 →
  10. Coverage on If statements

    Ncrunch does not appear to check all conditions in an if statement for 100% coverage.
    i.e. if (x || y) only requires that x is tested, not y.

    24 votes
    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. Support Gauge

    Please consider adding support for Gauge (http://getgauge.io). Gauge is an open source test platform, started by ThoughtWorks, for writing specification by example. It is similar to Gherkin, only it uses Markdown. Steps are bound to code using StepAttribute binding.

    26 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 →
  12. Expose MSpec's [Subject] details in the tests window

    MSpec uses a [Subject] attribute to nominate the unit-under-test and optionally allows a "concern" to be specified.

    In R# these items appear in the test runner window as part of the test name, however in NCrunch there doesn't seem to be any way to get at this information, which is unfortunate.

    There just seems to be a level of organization missing when working with MSpec tests. It would be really helpful to be able to group the tests either by the [Subject] attribute, or by the file name that the test is defined in.

    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 →
  13. Build on line "commit" insead of each character typed

    I would like the ability to be able to set NCrunch to only build my solution and run my tests after a new line of code is entered or an existing line of code has been edited.
    I find the feedback I get from VS more than enough while writing my line of code and would much rather have NCrunch working on giving me feedback on my solution up to the point where I added/edited the last complete line of code while typing the next.
    This would allow me to run many more test (as NCrunch has the time between…

    5 votes
    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 →
  14. Support the new Visual Studio Code IDE

    Support the new Visual Studio Code editor.
    While it doesn't yet provide extensibility for utils like NCrunch, it is apparently planned for upcoming development, so I wanted to get this on the NCrunch radar.

    111 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    17 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. 41 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 →
  16. Option to run all test in current .cs file

    I would be nice if I could tell NCrunch to run all tests in the current file.

    Often related tests are implemented in the same .cs file. Some of the projects I work on are too large to leave ncrunch running all the time, so an option to just run all tests in a certain file would be really helpful.

    5 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. ternary coverage

    Increase resolution of coverage so that a ternary expression shows code coverage if one branch is not covered. (Otherwise my team is going to make me always use 8-line ifs instead of 1-line ternaries just so we can see code coverage completely :'( )

    21 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 →
  18. NCrunch Console Tools provide TeamCity Code Coverage Stats

    You can check TeamCity documentation here: https://confluence.jetbrains.com/display/TCD9/Custom+Chart#CustomChart-CustomBuildMetrics

    CodeCoverageB Block-level code coverage %

    •CodeCoverageC Class-level code coverage %

    •CodeCoverageL Line-level code coverage %

    •CodeCoverageM Method-level code coverage %

    •CodeCoverageAbsLCovered The number of covered lines int

    •CodeCoverageAbsMCovered The number of covered methods int

    •CodeCoverageAbsCCovered The number of covered classes int

    •CodeCoverageAbsLTotal The total number of lines int

    •CodeCoverageAbsMTotal The total number of methods int

    •CodeCoverageAbsCTotal The total number of classes int

    29 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 →
  19. Hide non test projects in the NCrunch Tests window

    I typically leave the 'Show Passing Tests' filter enabled. However, when it is enabled, non-test projects also show up in the list with a check next to them. It would be good if the non-test projects would not show up at all in the tests view since there are no tests in them.

    6 votes
    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 →
  20. Add button to enable/disable word wrap in test output window

    The test output window currently wraps text which can make it difficult to read stack traces. An option to disable word wrap would be helpful, especially if it could be toggled via a button on the window itself.

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

Feature Requests

Categories

Feedback and Knowledge Base