To reproduce the issue:
- Open the attached solution.
- Restore the Nuget packages for UnitTestProject1.
- Right-click on the solution, and choose Run Tests.
The Test Runner will run the test in UnitTestProject1, but then won't end.
This has something to do with ClassLibrary1 being there. ClassLibrary1 references the MSTest.TestFramework NuGet package, but does not have any unit tests, and is not a unit test project.
In case this makes a difference, I am running the 15.5.2 version of VS 2017.
Hi Joe,
In the last Visual Studio updates, Microsoft changed some API in its TestRunner. We were reported about this and fixed the following issues:
Test Runner - It is impossible to run MSTests with the Visual Studio's 15.6.0 update
Test Runner does not run MSTest tests in Visual Studio 15.5.2
We are trying to ensure correct work of our product in the latest Visual Studio version, so we recommend you update Visual Studio. With the latest update, all works fine on my side.
Anyway, I will try to reproduce the issue in v15.5.2 and let you know my results.
Hi Joe,
We can't reproduce this problem with the 15.5.2 update.
Did you install the latest Visual Studio update? Is this issue reproducible with it?
I have been able to reproduce this issue on a clean Windows 10 1803 installation with Visual Studio 15.7.3 and CodeRush 18.1.4.
Here are the steps I followed to reproduce the issue:
Windows Install
Visual Studio Install
Visual Studio Configuration
CodeRush Install
Run the Test Project
Hello Joe,
Thank you for providing us with the steps to reproduce the issue. This information has helped us to reproduce the problem.
To make sure that we reproduced the same problem, may I ask you to check if the steps illustrated in attached video also lead to a problem on your side?
At the same time, we will examine why our TestRunner hangs in the situation we reproduced and will keep you posted of our results.
I am able to reproduce the issue by following the steps shown in the video. However, the only difference I saw between the video steps and my steps were that the UnitTest1 class name was selected before clicking "Run Tests" the first time, and then the Test Runner output text was selected before running clicking "Run Tests" the second time. Is that what you wanted me to do? Or did I miss some other steps?
Hi Joe,
Thank you for informing us of your results. We selected code and output text just for demonstration purposes, not like steps to reproduce. So, your results confirmed that we reproduced the same problem. We are working on it and will inform you of our progress.