Feature Requests

  1. Goto TestCaseSourceAttribute's source from Tests window.

    I would be nice if it was possible to opt-in to change behavior of the context menu "Go to selected test" in that way:

    With NUnit, one can write:

    public static IEnumerable<TestCaseData> MyTestCaseSourceMethodName()
    {
    // return test cases...
    }

    [TestCaseSource("MyTestCaseSourceMethodName")]
    public void MyTest(int someArgument)
    {
    // do test...
    }

    The test case factory method can be an separate (static) class.
    In my case, I have a test with several dozens of test cases.

    When a test fails, I can easily go to the failing test implementation, but I cannot easily find the culprit test case.

    2 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. Allow for easy command-line installation (e.g. Chocolatey)

    Our development machines are built via PowerShell script, which is a very flexible and maintainable way of scaling to many developers. The scripts rely heavily on Chocolatey packages to install software, but unfortunately the unofficial Chocolatey package for the NCrunch Visual Studio plugin is not reliably updated and does not cope well with upgrades. Also, there is no command-line NCrunch package.

    Given that Chocolatey packages are relatively simple wrappers around the existing product installers, it would be great if you could work with the existing package maintainer to improve the existing package, and create a package for the command-line application.

    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 →
  3. Time limit option for Churn mode

    I would like to be able to Churn tests for x seconds/minutes and if it hasn't failed within that time stop churning.

    This so after I have fixed a failing test, which I know fails in churn mode within x seconds, I don't want to run "Churn until it fails" but rather set a time period I know should be sufficient to reproduce it.

    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. Don't show "NCrunch Client Disabled" as an error in red

    When I try to connect to an NCrunch grid node and get "NCrunch Client DIsabled" in red text, my first impulse is to troubleshoot. Is it a firewall problem? Bad password? Something else?

    Then it clicks...*client*. I don't have NCrunch enabled in my current Visual Studio solution (or maybe I don't even have a solution loaded yet).

    Well, obviously NCrunch won't send anything to the node if there's nothing to send. This isn't really an *error*, per se, so I don't think NCrunch should show the message in red in this case.

    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 →
  5. Allow multiple simultaneous instances with different filters

    It would be great if I could get multiple risk/progress bars pointed at different categories of tests. I would like to see (for instance) one risk/progress bar for acceptance, one for integration, and one for unit tests. It would be great if these were full parallel instances - like with their own configuration and everything. For instance, having acceptance tests farmed out to servers makes a lot of sense but all my unit tests should run locally because it takes longer to farm out a batch than to run it.

    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. Toolbar button for "Run Selected Test(s) In Existing Process"

    I often have failing tests in my test window that I want to re-run in existing process (if there is one), e.g. when modifying database the tests are hitting.
    Today I must go via RMB->Advanced, rather than just clicking a toolbar button (similar what exists with "run test(s) in new process".

    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. History of work session

    I'd like to be able to see the history of my work session, meaning at the end of the day I'd like to see visually when my code was compiling, when my tests were all green.
    The purpose is to be able to identify if I spend a lot of time in those states and try to reduce that time.
    It would be useful for self-improvement or coaching.

    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. Extend line hit markers to include hit count and first hit order

    Two existing requests want hit count:

    https://ncrunch.uservoice.com/forums/245203-feature-requests/suggestions/15401490-hits-count-on-coverage-marker-circle

    https://ncrunch.uservoice.com/forums/245203-feature-requests/suggestions/6077791-show-number-of-lines-uniquely-covered-by-a-test

    , but I think that it would also be great if you could include a first hit order, then from a glance you could see the execution steps through the code (probably by thread in case multiple threads are used) and determine if line A was executed before line B

    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. Select current file in Metrics window

    I would like to select the file I have opened in visual studio, in the metrics window, so I don't manually have to find it by clicking through the project structure.

    Background: I have a build failing if metrics is below a threshold for specific files. When this build fails I get a list of file names. Then it is tedious for me to fix this "file by file" since I have no quick way of selecting current file in metrics window to verify my fixes.

    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 →
  10. Allow an ignored test to be run manually

    When a test is ignored either allow it to be run manually or disable the "Run selected test in new task runner process" in the popup menu in "NCrunch Tests" window.
    Right now you can click the item in the popup menu but the test is not run.
    Preferably I would rather be able to run the test on demand.

    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. 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 →
  12. Configuration option to completely remove the failing build message

    The message below is not necessary for users familiar with your product:

    NCrunch: If you are experiencing problems in getting this project to build, have a look at http://www.ncrunch.net/documentation/troubleshooting_project-build-issues

    It has 2 drawbacks:

    1) It contains a url which is easy to hit as there is no space between this url and the url for the first error in the build.

    2) It takes up screen space.

    So, a configuration option in General Settings to turn this off would be good. For those who wish to see the message, add a line between it and the first error message to…

    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. Show what it the currect engine mode on "NCrunch Test" screen or maybe via some icon in the VS status bar.

    Why?
    I often switch between modes like this:
    Run all tests automatically -> Run all tests manually or Run pinned test automatically -> Run all tests automatically
    This is due to make sure NCrunch does not get into the way by running tests that at the moment are doing more harm than good.

    1 vote
    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. A more obvious colour of the coverage markers to show a build error

    When working in code, test or otherwise I would like more obvious feedback for when a build has failed as I often mistake the dull green of a previously passing test with a failed build for the normal passing green.

    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. Gated Check In Support

    It would be great if Ncrunch provided an optional gate for check-ins when there are failing unit tests. Check-ins to version control systems would fail and display failing tests.

    This would be helpful for long-running unit test builds, so that the work could be offloaded from a central build server to incremental runs on everyone's dev machine.

    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 →
  16. Shortcut to run only failed tests

    Sometime I fix an issue for a failing test where NCrunch cannot detect the test is impacted.
    Instead of running all pinned tests I would like to bind a shortcut to only run failing tests (Similar to vstudio's TestExplorer.RunFailedTests) to verify the fix quickly.

    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 →
  17. "first failing test"

    I suggest you include the option to highlight the first failing test in the "NCrunch Tests" window and display the details.

    Right now when there are no tests failing and a test fails, I have to click on it in order to see the details of why.

    Having it automatically show the details would be very helpful and save a few clicks.

    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 →
  18. Test Coverage Analysis by Specific Test Class

    I suggest to make possible to change the way code coverage is calculated.
    While I am developing I do not do much end-to-end testing. What I do is purely unit testing as part of my TDD process. I would like to have the code coverage calculated class by test class.
    Example case: Class "Car" being tested by class "CarUnitTests". I would like to have the code coverage of class "Car" being calculated exclusively by the tests present in "CarUnitTests".

    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. Test results formatting

    Currently the test results appear as a block of text within the "NCrunch Tests" window. When compared to the built in display of test results in TestExplorer (im using VS2017), it feels rather raw and perhaps could be improved.

    Im not saying to get rid of the raw text output (we all have our preferences), but to have an option to format the display of results to allow the result of a test to be clear and distinct from the full result text. So, instead of:

    Microsoft.VisualStudio.TestTools.UnitTesting.AssertFailedException: Assert.AreEqual failed. Expected:<2>. Actual:<1>. Some random failure description i typed in as the…

    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 →
  20. Client priority setting for use by node servers

    We're looking into setting up an NCrunch node farm. This would be used by developer machines but it would also be used by the build server. When the build server goes to run tests, we'd like to have those test tasks take execution priority over test tasks coming from dev machines. Is this possible?

    From Remco: Presently it isn't possible to control this. The grid nodes operate on a round-robin type request system that treats every connected client equally. The only way to ensure priority for the build server given NCrunch's current feature set would be to set aside nodes…

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

Feature Requests

Categories

Feedback and Knowledge Base