On each PR, SimpleCov will determine the line and branch coverage for the project and the github-actions bot will comment on the PR with a table that shows the coverage numbers alongside the current project minimum values for each.
In addition to reporting the PR branch's code coverage numbers and minimum numbers, the table in the comment should also contain the current baseline numbers for the branch that the PR is targetting.
If a PR is targetting dev, the table should look something like this:
SimpleCov Report
Coverage
Baseline
Threshold
Line
94.13%
94.02%
94%
Branch
85.72%
85.70%
85%
with a new "Baseline" column (column name to be decided by the assignee) appearing right next to the "Coverage" column, we will be able to easily see if this PR is about to make coverage go up or down in addition to whether or not it meets the thresholds.
Once an approach for this has been decided upon, optionally create a separate follow-up issue to enforce a "never go lower" validation on PRs.
workato-integration[bot]
commented
1 year ago
On each PR, SimpleCov will determine the line and branch coverage for the project and the
github-actionsbot will comment on the PR with a table that shows the coverage numbers alongside the current project minimum values for each.In addition to reporting the PR branch's code coverage numbers and minimum numbers, the table in the comment should also contain the current baseline numbers for the branch that the PR is targetting.
If a PR is targetting
dev, the table should look something like this:SimpleCov Report
with a new "Baseline" column (column name to be decided by the assignee) appearing right next to the "Coverage" column, we will be able to easily see if this PR is about to make coverage go up or down in addition to whether or not it meets the thresholds.
Once an approach for this has been decided upon, optionally create a separate follow-up issue to enforce a "never go lower" validation on PRs.