#52034 closed defect (bug) (fixed)
Generate a test coverage report with a GitHub Action workflow
Reported by: | desrosj | Owned by: | desrosj |
---|---|---|---|
Milestone: | 5.7 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Build/Test Tools | Keywords: | has-patch |
Focuses: | Cc: |
Description
To help increase test coverage, let's use GitHub actions to generate a nightly code coverage report.
While this is not the only metric to consider, introducing some reporting is better than no reporting, and hopefully will shed some light into areas of core with little to no automated testing.
Change History (8)
This ticket was mentioned in Slack in #core by desrosj. View the logs.
4 years ago
This ticket was mentioned in PR #807 on WordPress/wordpress-develop by desrosj.
4 years ago
#2
- Keywords has-patch added
This ticket was mentioned in Slack in #core by sergey. View the logs.
4 years ago
4 years ago
#6
Since the default retention period is 90 days, are there any follow-up plans with those uploaded reports before they get deleted?
I accidentally nested my response here to a different comment for a specific line of code:
For now, the idea is just to surface the report so anyone interested in writing tests can find an area to focus on. We could submit the reports to a third party service. Do you have any that you recommend?
This generates a code coverage report on a nightly cron with a GitHub Action workflow (the
push
event will be removed when committed totrunk
.For now, reports are only generated for single site, multisite, and REST API results, as those are the only setups/groups that would generate any meaningful reports.
Trac ticket: https://core.trac.wordpress.org/ticket/52034.