Bug Report T414108
Visible to All Users

Visual Studio 2015 Code Rush Test Runner does not run any tests in the 16.1.6 release

created 9 years ago

We upgraded to the 16.1.6 release from 16.1.5 Build 16222. Unfortunately this breaks our NUnit 3 tests. Basically the test runner reports zero tests successful, failed, ignored. The CodeRush test runner can definitely discover the tests and the options are there as normal to run or debug the tests.

I've been able to successfully rollback to Build 16222 for now which resolves the issue. Just wanted to make you aware of this problem in build 16.1.6

Comments (2)
DevExpress Support Team 9 years ago

    Hi Matt,
    I am concerned to hear that you are experiencing this problem. We were already informed about it in the past.
    In fact, it can occur when NUnit is installed via NuGet without NUnit.Runners and NUnit of an earlier version than the NuGet version is installed on your PC.
    As a result, after staring, NUnit(NuGet) will take NUnit.Runners from NUnit(PC) of a different version.
    If this is the case and you have two different NUnit versions, please perform the following steps to work around the issue:

    1. Install NUnit.Runners 3 via NuGet for your project.
    2. Update your CodeRush for Roslyn to version 16.1.6 and restart your Visual Studio instance.
    3. Try to reproduce the problem and provide us with your results.

    If problem still exists, let us know your current CodeRush settings so that I can examine them. They are stored in the following folder: %appdata%\CodeRush\Settings.

    I am looking forward to your response.

    DevExpress Support Team 9 years ago

      Thank you for the settings and additional information.
      I have reproduced the problem. We will try to fix it as soon as possible.
      Once we make any progress, we will let you know.

      Answers approved by DevExpress Support

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

        Comments (2)

          Unfortunately this hotfix hasn't resolved my particular condition. I'm using build 16.1.6.16229 after requesting a hotfix for this issue. Any suggestions or things I can try to help narrow it down?

          DevExpress Support Team 9 years ago

            Thank you for your response, Matt.

            Would you help me reproduce the problem on my side and provide this information?

            1. A project.json file for your project with tests.
            2. Try to reproduce the issue in a small test project and describe what steps I need to perform to reproduce the problem.

            I am looking forward to your answer.

            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.