Vstest honor nologo#9791
Conversation
|
@smadala , for review |
|
@dotnet-bot please test Ubuntu x64 Release |
|
@dotnet-bot test this please |
| } | ||
|
|
||
| // Add VSTestNoLogo property if specified by user | ||
| if(parsedTest.Arguments.Contains("--nologo") || parsedTest.Arguments.Contains("/nologo")) |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
|
@livarcocc , can you please merge this PR |
peterhuene
left a comment
There was a problem hiding this comment.
This looks good. Can we add a unit test to cover the suppression of VSTest's logo when --nologo is passed to dotnet test?
|
@peterhuene , I will add unit tests, once we have inserted our latest sdk, which supports this. Do we want to wait till then to merge the PR? |
|
Hi @mayankbansal018, Sorry, this fell of my radar when I was on vacation. Since 2.1.4xx has shipped and this might not meet the 2.2.100 bar at this point, could you retarget this PR at Additionally, I'd hold off merging this until you have a test SDK inserted (or can do so as part of this PR) so we can have a test added. It's fine to also add the test now for review purposes and have the PR CI fail, which can then be rerun once the test SDK is inserted. |
|
Hi @mayankbansal018. I just wanted to follow up and make sure we retarget this PR against master. We should be able to easily insert a new test SDK there as well. Thanks! |
|
Hi @mayankbansal018, I just wanted to follow-up one more time so that we don't lose track of this PR. Is this still something the test team wants to move forward with for 3.0? Thanks! |
|
Thanks @peterhuene , for keeping track of this, unfortunately this slipped from my mind. I'll raise a new PR against appropriate branch. |
|
Closing in favor of #10662. |
Passing /nologo user input to VSTest task
Related: microsoft/vstest#1717
Bug: microsoft/vstest#1701