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. 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
    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. 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
    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. 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
    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. Increase startup speed in VS2017

    Please, increase the startup speed in Visual Studio 2017. Every now and then it shows me a window with extension-related startup delays, and asking to disable them.

    8 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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
    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 →
  6. 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
    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. 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
    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. 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
    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. Do not automatically perform a build if tests are set to run manually

    We have some projects that are very expensive to build. Since I would like to see the output of the last test, I do not want to disable NCrunch completely, but the build engine keeps building the projects even when the tests are all set to run manually and I haven't yet started a test. I would like the option to defer the build until a test is scheduled for execution.

    3 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 →
  10. Use project loaded in VS

    Hi.

    I want to be able to mark that nCrunch only use/load the projects that are loaded in VS.
    Since our solution are becoming big, I use Funnel to load only the projects I need for my current task. But nCrunch still load all projects in my solution file.

    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 →
  11. 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
    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. to support custom Xunit test cases

    As discussed on Twitter (https://twitter.com/remcomulder/status/782892104485703681), I'd like NCrunch to support custom test cases.

    xUnit has the support for custom test cases, as the STAExamples of the xUnit Samples demonstrate (https://github.com/xunit/samples.xunit/tree/master/STAExamples). That relies on using your own test discoverer, and specifying a custom test case. When you run that in NCrunch, it fails with a cast exception (https://gist.github.com/tiesmaster/5ecb8bf76aab6ee3cb2bfcc9d4f08e72#file-stacktrace-of-staexamples-on-stable-xunit-packages-downgraded-to-2-1-0).

    I think this is a niche feature, since this something that won't be used that often, but still a powerful feature, so it would be really nice to have this.

    8 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 →
  13. 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 →
  14. 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 →
  15. 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 →
  16. 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 →
  17. 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 →
  18. 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 →
  19. 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 →
  20. 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 →
  • Don't see your idea?

Feature Requests

Feedback and Knowledge Base