-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Enable 'dotnet test' to be run on published output #8679
Comments
@pvlakshm Adding Pratap here for visibility. Edit: Would you mind adding the 'dotnet-test' label? |
You can use dotnet vstest for that today. Is that not enough? |
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 are there instructions on how to do that? |
Beyond dropping to the command line, is there a way to make the tests in the IDE run against the published output? |
Not that I know of, but I will move this to the vstest repo and they should be able to say for sure. |
This issue was moved to microsoft/vstest#1176 |
Steps to reproduce
After publishing users should be able to run tests on an already compiled executable.
Would address dotnet/core dotnet/sdk#4835
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
The text was updated successfully, but these errors were encountered: