Bug Report T405155
Visible to All Users

Test Runner doesn't run tests for the NUnit 3.4 framework

created 9 years ago

Hi,

I updated NUnit references in my test proj ect from version 2.6 to 3.4.1 and I get the following error in the DXCore test output:

Testing started:

System.MissingMethodException
Method not found: 'NUnit.Framework.Interfaces.ITest NUnit.Framework.Api.NUnitTestAssemblyRunner.Load(System.Reflection.Assembly, System.Collections.IDictionary)'.
No tests found.
Duration : 2.21967516510678

I tried using both NUnit MSI installer and Nunit.Runners nuget package. Neither works.
Is this the same issue as with the Roslyn version https://www.devexpress.com/Support/Center/Question/Details/T277984?
If so are there any plans to fix it?
Thanks.

Show previous comments (1)
MB MB
Mariusz Bialobrzeski 9 years ago

    Thanks for taking care of that.
    I was able to use NUnit 3.2.1 instead and I will be using it until the fix is released.

      DevExpress: You may find information from this NUnit issue report helpful: https://github.com/nunit/nunit/issues/1665

      I had a similar problem with NCrunch recognizing some of my tests. They pinned it down to a change in the XML NUnit returns, particularly in regards to test inheriting from a base class in another assembly.

      The NCrunch team was able to fix their software over the weekend and release an update.

      DevExpress Support Team 9 years ago

        Hi Ben,

        Thanks for providing a link to the NUnit issue report. CodeRush Unit Test Runner uses a different way to interact with NUnit test framework than NCrunch. Therefore the information from this report is not related to the initial issue of this ticket. Anyway, let me thank you for sharing this information with us.

        We have already addressed this problem and implemented the NUnit 3.4 support in CodeRush Unit Test Runner. I suggest you download and install the following hotfix: DevExpressCodeRush-16.1.4.16203.exe.

        Please let us know if you have any issues with NUnit 3.4.

        Answers approved by DevExpress Support

        created 9 years ago (modified 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.

          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.