Add basic support for generating code coverage reports #499
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
TODO include in GitHub actions etc setup, e.g. https://josh-ops.com/posts/github-code-coverage/, once microsoft/vstest#1811 is fixed
mminns
force-pushed
the
issue/498-add-code-coverage
branch
from
902d307 to
15fdf1b
Compare
mminns
changed the title
|
Could this also be integrated into the CI builds? |
|
Yes, I don't see why not. I'm not as familiar with the CI setup as I probably should be to understand where it would fit, where you would see the results etc. I had assumed I'd do that as a follow up if the general idea was agreed. |
mjcheetham
approved these changes
Nov 25, 2021
|
👍 Thanks |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
I'd like to refactor parts of the Bitbucket code, but I'm uncomfortable about the level of security provided by the automated testing to avoid regressions.
I'd like to expand the testing, so I'd like to know what is currently tested or not.
Solution
This adds a first pass at adding basic code coverage metrics and reporting.
They have to be run manually, they are not currently wired up to CI etc, I'd suggest doing that in a follow up.