TestAdapterPath should work together with other lookup methods

[smadala]

From @NikolayPianikov on November 17, 2017 15:8

I mean project output directory, nuget and etc.

• We could have the identical behavior for full and core .net, I mean when I specify TestAdapterPath for .net full it does not try to find adapters in the project output directory but for .net core it properly finds.

So I should copy my custom adapter to the root of solution directory to run tests for mixed solution (with full .net and core .net projects). And vstest could spend potentially significant time finding all required adapters when agent checkout directory has a lot of files/directories. It is very important for CI.

• It would be great if we could specify several paths separated by semicolon or add new parameter TestAdapterPaths for that to work together with other lookup methods.

Copied from original issue: microsoft/vstest-docs#103

[smadala]

@NikolayPianikov

It would be great if we could specify several paths separated by semicolon or add new parameter TestAdapterPaths for that to work together with other lookup methods.

You can use /TestAdapterPath argument multiple times code.

[smadala]

From @NikolayPianikov on November 18, 2017 14:23

@smadala yes, but I used it under dotnet test or msbuild /t:vstest. Error is specified in the 'TestAdapterPath' is invalid. Error: The given path's format is not supported.
Exception is here

[smadala]

From @dtretyakov on December 5, 2017 12:40

@smadala, in VSTestTask, which is shipped with .net core sdk, allowed only one argument for VSTestTestAdapterPath and it's is bypassed into vstest console as a single argument:

And it's blocking use case in our integration, see JetBrains/teamcity-dotnet-plugin#101

When do you plan to fix it?

[smadala]

@NikolayPianikov @dtretyakov Feel free to raise PR. Let us know if you need any help.
/cc @pvlakshm for triage.

[dtretyakov]

@smadala, it was also mentioned in #141 (comment) by @AbhitejJohn that:

the commandline testadapterpath argument does not take in multiple paths which is another gap.

[dtretyakov]

@smadala, please take a look at the following PR: #1320

[smadala]

• This issue need to address handling multiple values in VSTestTask for applicable parameters.
• Should have same adapter picking up logic for both .NET Core & .NET Full?
  /cc thoughts @singhsarab @pvlakshm @mayankbansal018