Current filter:
                                You should refresh the page.
                                  • 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

                                • Dmitry O (DevExpress) 08.12.2016

                                  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.

                                • Dmitry O (DevExpress) 08.12.2016

                                  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.

                                1 Solution

                                Creation Date Importance Sort by


                                • Matt Psaltis 08.17.2016

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

                                • Dmitry O (DevExpress) 08.18.2016

                                  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.