Bug Report T523456
Visible to All Users

TestRunner window incorrectly displays parametrized tests

created 8 years ago

We use parameterized TestFixtures (https://www.nunit.org/index.php?p=testFixture&r=2.5) in our unit tests and I think support for these in Coderush could be better.

  1. When viewing tests in the TestRunner window, all TestFixture instances are listed without reference to their parameters, so when you have a large number it is very difficult to tell which one is which, ie: some may have failed and some succeeded.

So if you have test:

C#
[TestFixture("A")] [TestFixture("B")] [TestFixture("C")] public class MyTests { ... public void Test1() {} }

What you see in the test runner window is:

MyTests
  Test1
  Test1
  Test1

Classic Coderush used to display the parameters against each fixture instance, which would be very useful here.

  1. It is not possible to run a single test fixture instance. Our tests in this case are actually integration tests which take a long time to run. It is very useful to be able to run a specific one only.

In the code editor, it is only possible to click the run icon which appears against the first fixture instance, and it runs all of them

In the Test Runner window, it is possible to right click a test fixture instance and select Run, but it still runs all of them

Ideally the Run icon would appear against each test fixture, and in both cases would run only the selected test fixture.

Thanks

Show previous comments (1)

    Great, thanks

    DevExpress Support Team 8 years ago

      You are welcome.

      DevExpress Support Team 7 years ago

        Hi Wade,

        We have good news for you. In the 18.1.7 CodeRush, we have added the capability to run tests and test fixtures with certain parameters from the editor icon menu. To learn more about this and other new CodeRush features, please refer to our What's New. This version is already available in Visual Studio's Marketplace and Download Manager. We suggest you install it and look forward to your feedback.

        Answers approved by DevExpress Support

        created 8 years ago

        We have fixed the issue described in this ticket and will include the fix in our next maintenance update. To apply this solution before the official update, request a hotfix by clicking the corresponding link for product versions you require.

        Note: Hotfixes may be unavailable for beta versions and updates that are about to be released.

          Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.

          Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.