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
Live Unit testing does not work out of the box for VB unit test projects created using VS 2017
Steps to reproduce
Create a new VB Unit Test Project in VS 2017 -
Build the project
Turn on LUT (Test -> Live Unit Testing -> Start)
Expected behavior
LUT is turned on
Actual behavior
[14:16:35.202 Error] No test adapters are referenced by this solution. If you have a test project, add a NuGet reference to a test adapter corresponding to the test framework used in order to run the tests. If you already have the required NuGet reference in your test project, performing a NuGet restore may resolve the issue.
[14:16:35.202 Info] Start failed.
[14:16:35.264 Info] Live Unit Testing stopped.
Looks like VB project template for Unit Test Project is still adding a reference to the old 'MS.VS.QualityTools.UnitTestFramework.dll' instead of 'MS.VS.TestPlatform.TestFramework' nuget packages. Corresponding C# project template references the correct version.
Referencing the same nuget packages in the created VB project fixes the issue.
Environment
VS 2017 Enterprise
The text was updated successfully, but these errors were encountered:
@shyamnamboodiripad : The in-box VB templates have not moved to the new framework by default yet. This is on our backlog. As you mentioned, this should work automatically post the move.
Description
Live Unit testing does not work out of the box for VB unit test projects created using VS 2017
Steps to reproduce
Expected behavior
LUT is turned on
Actual behavior
Looks like VB project template for Unit Test Project is still adding a reference to the old 'MS.VS.QualityTools.UnitTestFramework.dll' instead of 'MS.VS.TestPlatform.TestFramework' nuget packages. Corresponding C# project template references the correct version.
Referencing the same nuget packages in the created VB project fixes the issue.
Environment
VS 2017 Enterprise
The text was updated successfully, but these errors were encountered: