Feature Requests

I suggest you ...

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. 2 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 →
  2. 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 →
  3. Support [TestProperty]

    MSTest allows us to tag tests with [TestProperty] attributes and their values are then available as this.TestContext.Properties.
    However, ncrunch is not populating this dictionary, so a test using these attributes works in mstest/resharper, but fails in ncrunch.

    2 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 →
  4. Mutation Testing

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

    9 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 →
  5. 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.

    4 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 →
  6. Enable "hotspots" indicators also for awaited asynchronous method calls.

    I would like NCrunch to display the actual time taken for an async method to have been called, when using await, instead of showing 0ms, just like they do for ordinary synchronous calls.
    See http://screencast.com/t/1mwMqiK0bi

    Example code:
    [TestFixture]
    internal class TestFixture
    {
    private async Task FooAsync()
    {
    await Task.Delay(1000);
    }
    [Test]
    public async Task AsyncTest()
    {
    await FooAsync(); //Coverage marker indicates 0ms duration.
    }
    [Test]
    public void NonAsyncTest()
    {
    FooAsync().Wait(); //Coverage marker indicates 1s duration.
    }

    }

    2 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 →
  7. Display Reason for ignored tests

    I use Nunit, with ExplicitAttribute(string reason) on TestFixture class.
    The tests are correctly ignored but there no reason visible in NCrunch Tests window.

    It would be nice to have the reason, when I select an ignored test. Perhaps in Trace Output (which is empty for ignored tests).

    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 →
  8. Provide parallelized execution time on Performance markers

    Today, NCrunch shows the execution time across all threads on its performance markers.

    If code is run in parallel, e.g.

    Parallel.For(0, 100000, DoSomething);

    the execution time is somehow misleading as it is not the real execution time (eg. 5 seconds) but instead the overall time (eg. 1 minute).

    It would be nice if NCrunch would show both times, the actual time needed for the loop as well as the overall time accross all threads.

    2 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 →
  9. 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 →
  10. Hits count on coverage marker circle

    When I click on a coverage marker circle, a windows pops up with Test name and execution time information.
    It would be nice to have also a third column indicating how much times the test hit the current line

    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 →
  11. Be able to specify which class(es) a test is covering

    I've noticed that in our test suite, various classes are showing as having code coverage through implict usage i.e. I'm testing class A, which is using class B within a tested method, and so lines of class B show as covered, when there's no dedicated tests for class B.

    Technically class B is getting tested there, but it would be nice if we had an attribute we could optionally use (multiple times per class/method), which specifies which class(es) the class/method is testing.

    [Tests<A>]

    Then the code analysis will only calculate the LoC coverage for classes specified by the attribute(s) on…

    2 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. Make the columns resizable without reducing the width of the next colum.

    Currently, if you want to make the Name column larger and drag the column separator, it reduces the width of the Status column. I'd rather have the width of the other columns unchanged (with a scrollbar to see the columns that are now outside the window).

    In order to reduce the size of the column, simply drag the right column separator to the left.

    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 →
  13. 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 →
  14. Pin all test under the tests tree node

    It would be nice to have ability to pin all tests inside specific node in the "Tests" window. Currently it only works for classes. It would be super convenient to have it working with other nodes (based on groupping) - namespaces, projects, ect.

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

    2 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. Support for expression body (one line tests)

    I would like support for one line tests that use expression body syntax, like the one below. When the test fails I would like to see the red cross with the assert information instead of the red arrow that doesn't give any information of why the test failed

    [Test]
    public void CanEditIsTrue() => Assert.IsTrue(Result.CanEdit);

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

    8 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 →
  18. 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 →
  19. 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…

    4 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. 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 →
1 2 5 7 9 12 13
  • Don't see your idea?

Feature Requests

Feedback and Knowledge Base