Vstest: Enable 'dotnet test' to be run on published output

[livarcocc]

_From @kendrahavens on August 31, 2017 17:9_

Steps to reproduce

After publishing users should be able to run tests on an already compiled executable.
Would address dotnet/core #917
This is more important with the development of IL Linker #915. The Linker Instructions mention that the final executables need to be tested after linking.

Expected behavior

Be able to run 'dotnet test' on published output.

Actual behavior

You can not today. (Or we need to add documentation if you can!)

@smalpani-msft

_Copied from original issue: dotnet/cli#7570_

[livarcocc]

_From @kendrahavens on September 6, 2017 16:46_

@pvlakshm Adding Pratap here for visibility.

Edit: Would you mind adding the 'dotnet-test' label?

[livarcocc]

You can use dotnet vstest for that today. Is that not enough?

[livarcocc]

Closing this for now since dotnet vstest should be able to do this for you. If you were asking for something different, please, re-activate.

[livarcocc]

_From @Petermarcu on October 6, 2017 20:12_

@livarcocc are there instructions on how to do that?

[livarcocc]

_From @Petermarcu on October 6, 2017 20:14_

Beyond dropping to the command line, is there a way to make the tests in the IDE run against the published output?

[livarcocc]

Not that I know of, but I will move this to the vstest repo and they should be able to say for sure.

[Petermarcu]

sounds good. I mainly want to make sure folks have a good answer because this is going to become more and more common.

[kendrahavens]

We now have a doc for this scenario: https://docs.microsoft.com/en-us/dotnet/core/testing/unit-testing-published-output

[codito]

Closing the issue since the behavior is now documented.

[giggio]

Using dotnet vstest does not work with TestServer. Is there a work around that?