Feature Requests

  1. 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 →
  2. 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.

    6 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 →
  3. Mutation Testing

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

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

    We’ll send you updates on this idea

    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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 →
  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.

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

    131 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 →
  10. 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 →
  11. 44 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 →
  12. 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 →
  13. 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 →
  14. 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

    30 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 →
  15. 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 →
  16. 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 →
  17. Enable real time output of the test being run in "NCrunch Tests" window

    It would be nice to have real-time or at least "refreshed" every 5-10 seconds "Test output" console in NCrunch Tests" window.

    Right now the output is provided once test is completed, but it would be useful to have some kind of "refresh every N seconds" option for integration tests. They might take minutes to run, and sometimes it is extremely useful to see output in real time - either to kill the test or to see what's going on.

    7 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 →
  18. Improve hover-over hints on tests indicators/icons in 'NCrunch Tests' window

    Oh boy, we still have absolutely no idea what do some icons mean. Really.

    All these alerts icons on the test/assembly row, then green or red clocks, then green question marks. That IS so much puzzling. Seems we lived in VS space too much, at least it was simple - not run, run and pass/failed :)

    Please add hints on hover-over providing an explanation and suggestion on what is going on with the current test or whole test set.

    5 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 →
  19. Mark tests using TestCaseSource as failed if an error in the method providing the TestCaseData fails

    Currently an NUnit test that uses a TestCaseSource attribute to provide the data will not show up at all if the method providing the TestCaseSource data has an exception.

    I often end up resorting to Resharper to run the offending test to find out what is going on.

    It would be nice if the tests that are failing because their TestCaseSource is not running can show up as failed tests the same way that they do in Resharper.

    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 →
  20. Stress-debug flaky tests

    Flaky tests are difficult to catch under a debugger due to the time it takes to start a new debugging session. It is frustrating to click the "Run the selected test(s) with debugger" button over and over again, waiting 5-15 seconds for each run.

    It would be wonderful if we could tell NCrunch to debug a given test 100 times in a row, giving the test a chance to fail with the debugger attached. The behavior should be similar to running multiple tests with debugger attached, though in actuality it would be the same test running again and again.

    9 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