-
Notifications
You must be signed in to change notification settings - Fork 62
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
Include Integration tests in code coverage #147
Conversation
<DataCollectors> | ||
<DataCollector friendlyName="Code Coverage"> | ||
<Configuration> | ||
<SplitCoverage>True</SplitCoverage> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what does SplitCoverage mean?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SplitCoverage is so that we can see the Code Coverage tab in ADO.
More details from this comment here: microsoft/vstest#981 (comment)
@@ -6,7 +6,12 @@ parameters: | |||
|
|||
steps: | |||
- task: UseDotNet@2 | |||
displayName: 'Install .NET Core SDK 3.1.x for Build' | |||
displayName: 'Install .NET Core SDK 5.0.x for Build' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
are we really using this for the build? Or just for running the tests?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be for tests - the Microsoft.NET.Test.Sdk v17 did not work with .NET Core SDK v3.1
Fixes: #141
Successful run in pipeline: https://mssqltools.visualstudio.com/CrossPlatBuildScripts/_build/results?buildId=127471&view=codecoverage-tab