Feature Requests

I suggest you ...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(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. 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…

    12 votes
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      1 comment  ·  Admin →
    • 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.

      3 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        I agree to the terms of service
        Signed in as (Sign out)
        You have left! (?) (thinking…)
        1 comment  ·  Admin →
      • 3 votes
        Vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          I agree to the terms of service
          Signed in as (Sign out)
          You have left! (?) (thinking…)
          1 comment  ·  Admin →
        • 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
          Vote
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            I agree to the terms of service
            Signed in as (Sign out)
            You have left! (?) (thinking…)
          • 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.

            1 vote
            Vote
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              I agree to the terms of service
              Signed in as (Sign out)
              You have left! (?) (thinking…)
            • "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.

              10 votes
              Vote
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                I agree to the terms of service
                Signed in as (Sign out)
                You have left! (?) (thinking…)
              • 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".

                4 votes
                Vote
                Sign in
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  I agree to the terms of service
                  Signed in as (Sign out)
                  You have left! (?) (thinking…)
                • Support multiple Visual Studio 2017 Installations

                  If you install NCrunch to Visual Studio 2017 you cannot selected to which instance the installation should go.

                  NCrunch picks one, and install. As a Workaround it is possible to do manual Installation with is not that complicated, but needs several steps, which also needs administration rights.

                  This makes upgrading to newer Version a real pain point. Also it might not be a great first impression for new Users. If they don't find NCrunch after installation.

                  A Solution might be to switch from MSI to VSIX for VS2017 and following Version.

                  18 votes
                  Vote
                  Sign in
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    I agree to the terms of service
                    Signed in as (Sign out)
                    You have left! (?) (thinking…)
                    1 comment  ·  Admin →
                  • 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".

                    3 votes
                    Vote
                    Sign in
                    Check!
                    (thinking…)
                    Reset
                    or sign in with
                    • facebook
                    • google
                      Password icon
                      I agree to the terms of service
                      Signed in as (Sign out)
                      You have left! (?) (thinking…)
                    • 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
                      Vote
                      Sign in
                      Check!
                      (thinking…)
                      Reset
                      or sign in with
                      • facebook
                      • google
                        Password icon
                        I agree to the terms of service
                        Signed in as (Sign out)
                        You have left! (?) (thinking…)
                        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…

                        4 votes
                        Vote
                        Sign in
                        Check!
                        (thinking…)
                        Reset
                        or sign in with
                        • facebook
                        • google
                          Password icon
                          I agree to the terms of service
                          Signed in as (Sign out)
                          You have left! (?) (thinking…)
                        • 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…

                          3 votes
                          Vote
                          Sign in
                          Check!
                          (thinking…)
                          Reset
                          or sign in with
                          • facebook
                          • google
                            Password icon
                            I agree to the terms of service
                            Signed in as (Sign out)
                            You have left! (?) (thinking…)
                            1 comment  ·  Admin →
                          • 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
                            Vote
                            Sign in
                            Check!
                            (thinking…)
                            Reset
                            or sign in with
                            • facebook
                            • google
                              Password icon
                              I agree to the terms of service
                              Signed in as (Sign out)
                              You have left! (?) (thinking…)
                            • 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.

                              12 votes
                              Vote
                              Sign in
                              Check!
                              (thinking…)
                              Reset
                              or sign in with
                              • facebook
                              • google
                                Password icon
                                I agree to the terms of service
                                Signed in as (Sign out)
                                You have left! (?) (thinking…)
                              • In Test window, Server column for grouping rows should include all servers for children (not just one of them).

                                In my case Server always says "(Local)" if any child test ran locally. I think this should be a comma-delimited list like Category. Next best thing would be leaving it blank.

                                If I'm filtering for failed tests only, the current behavior is really a bug, because all of the failing tests may have ran on one node server that isn't (local), yet the grouping row alone still says (local). So it makes scanning the server column to troubleshoot issues (in this case node server dependency config issues) confusing.

                                1 vote
                                Vote
                                Sign in
                                Check!
                                (thinking…)
                                Reset
                                or sign in with
                                • facebook
                                • google
                                  Password icon
                                  I agree to the terms of service
                                  Signed in as (Sign out)
                                  You have left! (?) (thinking…)
                                • 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
                                  Vote
                                  Sign in
                                  Check!
                                  (thinking…)
                                  Reset
                                  or sign in with
                                  • facebook
                                  • google
                                    Password icon
                                    I agree to the terms of service
                                    Signed in as (Sign out)
                                    You have left! (?) (thinking…)
                                  • 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.

                                    14 votes
                                    Vote
                                    Sign in
                                    Check!
                                    (thinking…)
                                    Reset
                                    or sign in with
                                    • facebook
                                    • google
                                      Password icon
                                      I agree to the terms of service
                                      Signed in as (Sign out)
                                      You have left! (?) (thinking…)
                                    • 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.

                                      12 votes
                                      Vote
                                      Sign in
                                      Check!
                                      (thinking…)
                                      Reset
                                      or sign in with
                                      • facebook
                                      • google
                                        Password icon
                                        I agree to the terms of service
                                        Signed in as (Sign out)
                                        You have left! (?) (thinking…)
                                        1 comment  ·  Admin →
                                      • 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.

                                        12 votes
                                        Vote
                                        Sign in
                                        Check!
                                        (thinking…)
                                        Reset
                                        or sign in with
                                        • facebook
                                        • google
                                          Password icon
                                          I agree to the terms of service
                                          Signed in as (Sign out)
                                          You have left! (?) (thinking…)
                                        • Introduce NCrunch.TestContext or similar to get info of current running test, e.g. attributes

                                          Original thread: http://forum.ncrunch.net/yaf_postst2127_NCrunch-attributes-on-interface.aspx

                                          I would like a way, in similar to NUnit\s TestContext, to read information about current running test.

                                          One piece of information I would like is attributes like [ExclusivelyUses]; In a complex test setup I might share test logic for multiple tests, and then it would be good to ensure that the proper attributes are applied on the tests to e.g. avoid deadlocks, or ensure an integration test has [ExclusivelyUeses("IntegrationTest")] attribute set etc.

                                          1 vote
                                          Vote
                                          Sign in
                                          Check!
                                          (thinking…)
                                          Reset
                                          or sign in with
                                          • facebook
                                          • google
                                            Password icon
                                            I agree to the terms of service
                                            Signed in as (Sign out)
                                            You have left! (?) (thinking…)
                                          ← Previous 1 3 4 5 9 10
                                          • Don't see your idea?

                                          Feature Requests

                                          Feedback and Knowledge Base