Skip to content

Feature Requests

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

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

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

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

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

    235 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)

    I'm happy to announce that we're a month away from releasing support for Jetbrains Rider in NCrunch.  It's been a very long difficult road.  I've included more details about this in the blog post at https://blog.ncrunch.net/post/Dotnet-build-support-Jetbrains-Rider-support-coming-soon!.aspx


    I apologise for not giving clearer communication on this feature request, and that we've already been working on it for some time.  I hope the details in the blog give some explanation for why we've been quiet about this work.  Rider support is coming.

  7. Allow Font Size Control Through Visual Studio's Standard Environment Font Target

    Font sizing for the output window is configurable in NCrunch, but font sizing for all other NCrunch windows is not. Please allow users to control NCrunch font sizing through the Visual Studio “Environment” font target. This font target, under "Tools-->Options-->Environment-->Fonts and Colors", is designed specifically for this purpose. See the section “Environment Font” under section “Show settings for” at: https://msdn.microsoft.com/en-us/library/kw7t0545.aspx

    Other tools, like JetBrains ReSharper, use this method and it works very well. For those of us who change our font sizes to minimize eye strain (especially when using multiple monitors), this would be a tremendous usability improvement.

    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

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

    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. Mutation Testing

    Perform Mutation Testing on the test cases to identify incorrect test cases.

    12 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)
  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.

    29 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)
  11. Rerun flaky test

    I'm using NCrunch for more than 2 years.
    IMHO it's must-have extension.
    When I come to new company that do not use NCrunch I need to fix/stabilize some test to run with NCruch engine.
    But still I stay with few flaky test.
    I need to rerun them few times to filter trully failing test.

    It would be nice introduce option for my case with flanky test.
    It could be rerun count before test is treated as failed
    Other option to introduce 3rd test state: flanky.

    5 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)
  12. 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

    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)
  13. ARM support

    Please compile / release for ARM as well as x86/x64.
    I am looking to run the NCrunch Grid on machines which use ARM chips and noticed there are only x86/x64 builds.

    5 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)
  14. 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

    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)
  15. Pin test class in test runner rather than pin each test separately

    Would be nice to have ability to pin test class to test runner, rather than pinning each newly added test separately. When adding a new feature, you tend to spam quite a few tests in new test class, or to some existing class. If solution is big, and you have many tests, the response time from NCrunch becomes poor. Of course you can pin each task separately when you add them, but when you spam many small tests, it becomes annoying. NCrunch could automatically detect newly added or modified tests in pinned class(es) and run them, ignoring the rest.

    9 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)
  16. 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.

    153 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)
  17. 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

    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)
  18. Update CodeLens test stats

    In Visual Studio 2015, Code Lens shows me 0 passing tests, while NCrunch shows me all green markers.
    Maybe it is possible for NCrunch to update the CodeLens test statistics.

    59 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)
  19. Filter to show running tests.

    Hi, I'd like to have a new filter option along side the "show passing/failing/unexecuted/ignored tests" buttons which would allow me to "show running tests". My use case would be to have show enabled for failing, unexecuted, and running tests -- so I can more clearly see what NCrunch is up to at any given moment.

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

Feature Requests

Categories

Feedback and Knowledge Base