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. Add coverage aggregates to the xml report produced by the console runner

    The output of the console runner contains HTML and raw xml reports.

    The HTML report is nice, however the contents of the XML files is a bit too detailed to get statistics from it.

    It would be nice to have the same kind of data that is in the HTML file but in XML form (meaning, the % coverage per method/class/assembly/global). Something similar to the DotCover XML or JSON reports. In fact if the format was exactly the same as the dotcover reports we could leverage tools that can already process these files, like SonarQube.

    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 →
  2. Provide history of failed tests

    When working on a project where NCrunch is running (all) the tests automatically in the background, some tests occassionally fail and then suddenly pass.

    I would like to have some kind of history for failed tests so that I can even later on delve further into the failed tests to figure out what's going wrong.

    In addition it would be nice to be able to configure the time span (or number of tests runs) for that historical data to limit the memory consumed (I could imagine that using that feature on large projects will have a significant memory impact).

    6 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 →
  3. Display test output in text window (on button click)

    We use extensive logging information to analyze test failures.

    Currently the test output is only displayed in a split window of the tests window. This makes reading and analyzing long test outputs (especially with long lines) rather difficult.

    Therefore it would be nice to be able to display the test output with one button click in a separate (temporary) text window (similar to the Visual Studio test runner).

    Posted in response to: http://forum.ncrunch.net/yaf_postsm5490_Ability-to-display-test-output-in-text-window.aspx#post5490

    6 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. Allow to run in memory only

    It would be nice if I could run ncrunch in memory only. That would extend the lifetime of SSDs and would be much faster. At the moment this is only possible with a ram drive.

    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 →
  5. Option to enter debugger when churn mode makes a test fail

    I would like to use churn mode for a single test and make NCrunch enter the debugger as soon as churn mode was able to fail the test.

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

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

    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 →
  9. 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 →
  10. Allow navigation to test in test window

    From the test status gutter or test name, I would like to be able to navigate to the test (right click or hotkey) in the test status window so that I can quickly ignore/unignore all tests in a test class easily.

    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. SSL support for NCrunch Grid Node server

    Its a must for remote grid nodes

    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 →
  12. Doubleclicking a failing test should jump to the failing line

    If I doubleclick a test in the tests window the test, the file containing the test is opened in the IDE and the cursor jumps to the beginning of the test (Feature: Go to selected test").

    It would be nice to have a "Go to selected test at failing line" feature that can be accessed via right click a failing test and even being able to set this as default action for double click.

    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. Add PriorityAttribute: This can Improve parallel execution dramatically

    The tests are ordered for execution depending on automatic generated priorities.

    Execution of an isolated test (e.g. needing exclusively the "Task Runner" Resource) causes that no new tests are put into the Pipeline (local and grid node) until this test is started.

    If I could set the PriorityAttribute to all isolated tests, I could run them all together at the end rather then often interrupting the Pipeline that contains many long running 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 →
  14. 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 →
  15. 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 →
  16. Move ">" test marker up to the method name

    This would leave the marker visible when the method is collapsed.

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

    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 →
  18. Shortened name should just be the test name when viewing with Tree Structure set to test

    Currently, when I want to view tests in flat list, I set the tree structure to "Test" but all the following columns display the same values

    Name, Shortened Name and Full Test Name !

    It would be helpful if the Shortened Name just displayed the test name rather than the full namespace.

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

    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 →
  20. Add an attribute like [Isolated] which applies to each member of a fixture rather than the fixture as a whole

    The [Isolated] attribute currently only provides isolation for the fixture, not each test within it. Where tests need to be isolated, they need to be individually annotated.

    It would be nice to have an attribute like [IsolateEachMember] which could apply to each test in a fixture.

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

Feature Requests

Feedback and Knowledge Base