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. 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
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)

      We’ll send you updates on this idea

    • Standalone UI which can be used with every other IDE

      Here are some feature requests for Visual Studio Code and Rider. But these require deep Integration.

      But since VS 2017 sucks so much these days. It would be nice if we can use another IDE.

      I propose a standalone Version with the NCrunch with the UI and Windows which are currently in Visual Studio. But without Visual Studio.

      Of course this is not such a tight integration with the IDEs (not jumping to the code, debug and break into failing tests etc.) but would be a good start. And of course, it is only running tests on save because of…

      9 votes
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        Signed in as (Sign out)

        We’ll send you updates on this idea

      • 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
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          Signed in as (Sign out)

          We’ll send you updates on this idea

        • 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
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            Signed in as (Sign out)

            We’ll send you updates on this idea

          • 2 votes
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              Signed in as (Sign out)

              We’ll send you updates on this idea

              1 comment  ·  Admin →
            • 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
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                Signed in as (Sign out)

                We’ll send you updates on this idea

              • 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
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  Signed in as (Sign out)

                  We’ll send you updates on this idea

                  1 comment  ·  Admin →
                • 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
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    Signed in as (Sign out)

                    We’ll send you updates on this idea

                  • 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
                    Check!
                    (thinking…)
                    Reset
                    or sign in with
                    • facebook
                    • google
                      Password icon
                      Signed in as (Sign out)

                      We’ll send you updates on this idea

                    • 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
                      Check!
                      (thinking…)
                      Reset
                      or sign in with
                      • facebook
                      • google
                        Password icon
                        Signed in as (Sign out)

                        We’ll send you updates on this idea

                      • "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
                        Check!
                        (thinking…)
                        Reset
                        or sign in with
                        • facebook
                        • google
                          Password icon
                          Signed in as (Sign out)

                          We’ll send you updates on this idea

                        • An option to automatically pin *modified* tests

                          Most of the time, I only want to automatically run tests that I'm working on.

                          So I use engine mode "Run pinned tests automatically, others manually". And manually pin tests I'm working on.

                          Would be nice if NCrunch could automatically pin modified tests (detect changes of test methods and test classes), and automatically pin modified tests.

                          I know we already have an option "Automatically pin newly discovered tests". Would be nice if there was another option "Automatically pin modified tests".

                          2 votes
                          Sign in
                          Check!
                          (thinking…)
                          Reset
                          or sign in with
                          • facebook
                          • google
                            Password icon
                            Signed in as (Sign out)

                            We’ll send you updates on this idea

                          • 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
                            Check!
                            (thinking…)
                            Reset
                            or sign in with
                            • facebook
                            • google
                              Password icon
                              Signed in as (Sign out)

                              We’ll send you updates on this idea

                            • 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
                              Check!
                              (thinking…)
                              Reset
                              or sign in with
                              • facebook
                              • google
                                Password icon
                                Signed in as (Sign out)

                                We’ll send you updates on this idea

                                1 comment  ·  Admin →
                              • Attribute to identify type/methods that must have 100% code coverage

                                It would be helpful to have NCrunch treat (or at least report) decreases in code coverage as "fail".

                                For example, supporting an attribute that marks a project/class/method as "100% code coverage required".

                                Or a larger flag such that any code coverage drop is a "failure". This would be a bit trickier to support as it may need to be include a way to identify a baseline. And it may be helpful to distinguish between coverage for old code vs coverage for new code.

                                I think starting with a numeric attribute indicating the required coverage would give the biggest ROI --…

                                1 vote
                                Sign in
                                Check!
                                (thinking…)
                                Reset
                                or sign in with
                                • facebook
                                • google
                                  Password icon
                                  Signed in as (Sign out)

                                  We’ll send you updates on this idea

                                  1 comment  ·  Admin →
                                • Add AlwaysImpactedAttribute for Run Impacted Tests Automatically mode

                                  It would be useful if there was an AlwaysImpactedAttribute that could be attached to a test method so that it always executes when a code change is made.

                                  The use case I am thinking of occurs with Automapper. We have a test that executes AssertConfigurationIsValid(), but when the engine mode is in "Run Impacted Tests Automatically" NCrunch will not detect that this test needs to be run whenever we make changes to the models in the solution.

                                  If I could put an attribute on that test method that says 'always run', I could continue to use the "impacted only" engine…

                                  1 vote
                                  Sign in
                                  Check!
                                  (thinking…)
                                  Reset
                                  or sign in with
                                  • facebook
                                  • google
                                    Password icon
                                    Signed in as (Sign out)

                                    We’ll send you updates on this idea

                                  • 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
                                    Check!
                                    (thinking…)
                                    Reset
                                    or sign in with
                                    • facebook
                                    • google
                                      Password icon
                                      Signed in as (Sign out)

                                      We’ll send you updates on this idea

                                    • 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
                                      Check!
                                      (thinking…)
                                      Reset
                                      or sign in with
                                      • facebook
                                      • google
                                        Password icon
                                        Signed in as (Sign out)

                                        We’ll send you updates on this idea

                                      • Support for debugging with the 'Microsoft Child Process Debugging Power Tool'

                                        When debugging tests with NCrunch the 'Microsoft Child Process Debugging Power Tool' (https://marketplace.visualstudio.com/items?itemName=GreggMiskelly.MicrosoftChildProcessDebuggingPowerTool) does not work.

                                        Maybe this can be fixed.

                                        1 vote
                                        Sign in
                                        Check!
                                        (thinking…)
                                        Reset
                                        or sign in with
                                        • facebook
                                        • google
                                          Password icon
                                          Signed in as (Sign out)

                                          We’ll send you updates on this idea

                                        • Support the new PackageReference nodes in VS 2017 project files.

                                          Currently NCrunch can't build projects that use the new PackageReference structure for NuGet packages as opposed to the "old" packages.config.

                                          Workaround is to use the old method.

                                          6 votes
                                          Sign in
                                          Check!
                                          (thinking…)
                                          Reset
                                          or sign in with
                                          • facebook
                                          • google
                                            Password icon
                                            Signed in as (Sign out)

                                            We’ll send you updates on this idea

                                          • Don't see your idea?

                                          Feature Requests

                                          Feedback and Knowledge Base