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. 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 →
  2. 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 →
  3. 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 →
  4. 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 →
  5. 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 →
  6. 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 →
  7. 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 →
  8. 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 →
  9. 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 →
  10. 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 →
  11. 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 →
  12. 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 →
  13. 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 →
  14. Option to select Test Suites dynamically

    We run all our tests from CI server (Jenkins).

    Currently, we add category to each test case. The NCrunch Engines are predefined (which is a huge number), with "Has category" option. When the runs are triggered, the predefined NCrunch Engine is selected for execution (from Console tool)

    This limits our option to trigger different combination of Test Suites from CI server.

    Could you please add the option to be able to dynamically create NCrunch Engines or define the Test Suites.

    For e.g, all test cases has a unique ID. I would like to pass the test case ID's and NCrunch…

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

    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. 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 →
  17. Add short exception message column in Tests window

    If there are multiple tests failing, you need to click each one and expand the bottom part of the window to read the text dump. It would save a lot of time if I could see the exception message beside each test. Especially for Asserts where I just want to see the expected value vs the actual value.

    Ideally the message is formatted as "{Message} [{ExceptionType}]". AggregateException etc should be unwrapped when creating the short message.

    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 →
  18. Support NSubstitute

    ...my favorite, fluent syntax mocking tool.

    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 →
  19. License server - Show client version

    On the license management page, show the client version for each line. This way I know who should update their clients.

    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 →
  20. Make the test timeout depends on RepeatAttribute (NUnit)

    The default timeout is 60 sec. One can change that value but it would be nice if NCrunch could adapt timeout based on the number of repetitions of the same test (in respect of RepeatAttribute of NUnit).
    Today, if I specify a timeout of 120 sec, that timeout is applied no matter how much times the test is repeated in the same tests session.

    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