-
Notifications
You must be signed in to change notification settings - Fork 2
Closed
Description
This is a tracking issue to find the best way to execute VS 2015 MSTest projects in VS 2017.
Here is a sample VS 2017 solution that can execute its test using TestDriven.Net or the built in Test Explore. It uses the test runner from VS 2015 (which can be found in the lib\MSTest folder): UnitTestProject2.zip
To convert an existing VS 2017 solution.
- Open the NuGet manager and delete the following packages:
-
Copy the
libfolderUnitTestProject2.zipto your solution folder. -
Add a reference to
lib\MSTest\PublicAssemblies\Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll.
You should now be able to execute your tests using either TestDriven.Net or the built in Test Explorer.
Please give this a try and let me know how well it works.
Would it be useful if this was deployed as a NuGet package?
