You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 lib folder UnitTestProject2.zip to 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?
The text was updated successfully, but these errors were encountered:
I've made some good progress towards adding support for VS 2017 MSTest projects. It seems there are two flavors of MSTest project supported by VS 2017.
The first is where a VS 2017 MSTest project was ported from a VS 2015 solution. In this case the project continues to use the Microsoft.VisualStudio.QualityTools.UnitTestFramework assembly, but the assembly reference is changed to point at the VS 2017 PublicAssemblies folder. For example: C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\PublicAssemblies\
The second flavor is where a new MSTest project is created in VS 2017. In this case the project is created using the MSTest.TestAdapter and MSTest.TestFramework assemblies. The test attributes are split across two assemblies from the MSTest.TestFramework package, Microsoft.VisualStudio.TestPlatform.TestFramework.dll and Microsoft.VisualStudio.TestPlatform.TestFramework.Extensions.dll.
I've added support for the first type and am working on support for the second. It currently works with the new .vsix based installer for TestDriven.Net. I'll back port it so that it will also work with the .exe/.msi based installer.
For the moment, here is a .vsix installer that will allow the execution of MSTest projects in VS 2017 that were ported from VS 2015: TestDriven.VSPackage.zip
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.zipTo convert an existing VS 2017 solution.
Copy the
lib
folderUnitTestProject2.zip
to 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?
The text was updated successfully, but these errors were encountered: