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

TestAdapterPath in runsettings does not take relative paths #135

Open
AbhitejJohn opened this issue Oct 14, 2016 · 2 comments
Open

TestAdapterPath in runsettings does not take relative paths #135

AbhitejJohn opened this issue Oct 14, 2016 · 2 comments

Comments

@AbhitejJohn
Copy link
Contributor

AbhitejJohn commented Oct 14, 2016

Description

The TestAdapterPaths XML section does not understand relative paths unlike ResultsDirectory. This however works on using a testadapterpath commandline switch. With most adapters dropping the test adapter binaries in bin\debug, this inconsistency surfaces more.

Steps to reproduce

  1. Create an MSTest V2 test project.
  2. Form a runsettings with a TestAdapterPath in the RunConfiguration section.
  3. Run vstest.console with this runsettings.

Expected behavior

The relative test adapter path gets honored and tests are discovered and run.

Actual behavior

The adapter path does not get honored and tests do not run.

Environment

Please share additional details about the test environment.
Operating system, Build version of vstest.console

AB#1865835

@SabotageAndi
Copy link

It looks like this is still a problem in VS 2017 15.7 Preview 3.0 and in vstest.console.exe 15.7.0-preview-20180320-02.

Is there a recommendation what to do, if devs have their sources on different locations on their machines?

@smadala smadala self-assigned this Jun 19, 2018
@vbondaryuk
Copy link

Dear vstest team, any update of it?

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

No branches or pull requests

9 participants