Skip to content
This repository has been archived by the owner on Apr 20, 2023. It is now read-only.

Vstest args for dotnet cli #9211

Closed

Conversation

mayankbansal018
Copy link

@mayankbansal018 mayankbansal018 commented May 7, 2018

Fixes: microsoft/vstest#1319

dotnet-maestro-bot and others added 9 commits May 9, 2018 00:31
…tup, fsharp, sdk, templating, templating, templating, websdk to rtm-62908-03, alpha-62908-03, rtm-26508-02, rtm-26508-02, rtm-26508-02, rtm-180508-0, rtm-62908-02, beta3-20180508-1667431, beta3-20180508-1667431, beta3-20180508-1667431, rtm-20180508-1667423, respectively
…x-UpdateDependencies

Update clicommandlineparser, climigrate, coresetup, coresetup, coresetup, fsharp, sdk, templating, templating, templating, websdk to rtm-62908-03, alpha-62908-03, rtm-26508-02, rtm-26508-02, rtm-26508-02, rtm-180508-0, rtm-62908-02, beta3-20180508-1667431, beta3-20180508-1667431, beta3-20180508-1667431, rtm-20180508-1667423, respectively (release/2.1.3xx)
Commit 1028950 changed the default verbosity
option used for MSBuild from `-v:quiet` to `-verbosity:quiet`.  This triggered a
match that was being done against arguments starting with `-verbosity` to
forward the value to VSTest via the `VSTestVerbosity` property.  The result is
that VSTest is using a default verbosity of `quiet`, suppressing error output
that users expect to see.

The fix is to change the check to only match against user-supplied options.
The default level the command uses for MSBuild is not forwarded to VSTest.

Fixes #9229.
Fix incorrect default VSTest verbosity level.
.With(name: LocalizableStrings.CmdTestAdapterPath)
.ForwardAsSingle(o => $"-property:VSTestTestAdapterPath={o.Arguments.Single()}")),
.ForwardAsSingle(o => $"/p:VSTestTestAdapterPath=\"{string.Join(";", o.Arguments)}\"")),

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

@@ -31,7 +31,7 @@ public static TestCommand FromArgs(string[] args, string msbuildPath = null)
var msbuildArgs = new List<string>()
{
"-target:VSTest",
"-verbosity:quiet",
"-verbosity:minimal",

This comment was marked as spam.

@mayankbansal018 mayankbansal018 changed the title [WIP]Update Vstest args for dotnet cli Update Vstest args for dotnet cli May 14, 2018
.With(name: LocalizableStrings.CmdLoggerOption)
.ForwardAsSingle(o =>
{
var loggersString = string.Join(";", GetSemiColonEscapedArgs(o.Arguments));

return $"-property:VSTestLogger={loggersString}";
return $"/p:VSTestLogger=\"{loggersString}\"";

This comment was marked as spam.

Copy link

@peterhuene peterhuene left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Other than changing back to -property, I'm 👍

@peterhuene
Copy link

Also, could we rebase this off of release/2.1.4xx rather than having the merge commit (I wouldn't mind a squash too, but we can do that at merge time)?

Note that release/2.1.4xx now has the fix for the verbosity issue.

@mayankbansal018
Copy link
Author

@peterhuene , I've rebased the branch from 2.1.4xx, please do a squash merge if the changes look good to you.

@mayankbansal018 mayankbansal018 changed the title Update Vstest args for dotnet cli Vstest args for dotnet cli May 16, 2018
@mayankbansal018
Copy link
Author

@livarcocc , @peterhuene , I'm not sure why the wip check is not passing, but can you please take a look at this PR, & merge it.

@peterhuene
Copy link

It's not passing because one of your commits has WIP in it.

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

Successfully merging this pull request may close these issues.

6 participants