Skip to content
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

Do not show skip message always #1867

Merged
merged 1 commit into from
Dec 12, 2018

Conversation

singhsarab
Copy link
Contributor

Show skip message only when the IsTestProject is not defined

Fixes #1866

Show skip message only when the IsTestProject is not defined
Copy link
Contributor

@abhishkk abhishkk left a comment

Choose a reason for hiding this comment

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

Approved with suggestions

@@ -52,7 +52,7 @@ Copyright (c) .NET Foundation. All rights reserved.
/>
</Target>

<Target Name="ShowInfoMessageIfProjectHasNoIsTestProjectProperty" Condition="'$(IsTestProject)' != 'true'">
<Target Name="ShowInfoMessageIfProjectHasNoIsTestProjectProperty" Condition="'$(IsTestProject)' == ''">
Copy link
Contributor

Choose a reason for hiding this comment

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

If solution contains non-test dlls, then currently we are logging dll skip message as info. Ideally this message should be logged as verbose level.

If possible, can we make log level of skipping test dll message as verbose?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

There is no infra like that in place today.

Copy link
Contributor

Choose a reason for hiding this comment

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

There is no infra like that in place today.

I beg to differ. VSTestLogsTask inherits from Task, which provides a logger. VSTestLogsTask can use that logger, with appropriate importance levels, instead of Console.WriteLine. Here's a PR: #1882

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

Successfully merging this pull request may close these issues.

3 participants