Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VB unit test project templates that ship in VS 2017 do not reference TestPlatform nugets #673

Closed
shyamnamboodiripad opened this issue Mar 30, 2017 · 3 comments

Comments

@shyamnamboodiripad
Copy link
Contributor

shyamnamboodiripad commented Mar 30, 2017

Description

Live Unit testing does not work out of the box for VB unit test projects created using VS 2017

Steps to reproduce

  1. Create a new VB Unit Test Project in VS 2017 -
    image
  2. Build the project
  3. 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.

image

Referencing the same nuget packages in the created VB project fixes the issue.

Environment

VS 2017 Enterprise
image

@AbhitejJohn
Copy link
Contributor

@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.

@AbhitejJohn
Copy link
Contributor

Copied to microsoft/testfx#132.

@shyamnamboodiripad
Copy link
Contributor Author

@AbhitejJohn Thanks for clarifying. Hopefully this can be fixed for the next major update of VS 2017.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants