Skip to content

Conversation

@jrha
Copy link
Member

@jrha jrha commented Jan 20, 2026

The previous config ran coverage, but never reported anything.
This adds a quick-and-dirty coloured annotation to the test output as well as a report to the test summary page.

Ideally we could use the orgoro/coverage action, but it can't be used on PRs from forks until orgoro/coverage#281 is merged.

@jrha jrha force-pushed the python-coverage branch 3 times, most recently from e6cf06e to 6696865 Compare January 20, 2026 11:57
@jrha jrha changed the title Use action to report coverage as a comment on PRs Report coverage at end of tests Jan 20, 2026
@jrha jrha force-pushed the python-coverage branch 12 times, most recently from c0e5029 to 549d660 Compare January 20, 2026 15:59
@jrha jrha added this to the 10.9 milestone Jan 20, 2026
@jrha jrha added the panlint label Jan 20, 2026
@jrha jrha changed the title Report coverage at end of tests workflows: Report coverage at end of tests Jan 20, 2026
@jrha jrha marked this pull request as ready for review January 20, 2026 16:02
@jrha jrha force-pushed the python-coverage branch 2 times, most recently from 5c86bce to 4e2901c Compare January 20, 2026 16:44
Copy link
Contributor

@ned21 ned21 left a comment

Choose a reason for hiding this comment

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

This is awesome. Agree it's probably not scalable to larger code bases, but for panlint I can easily see what the tests are exercising and what needs more careful review (i.e. main() !)

@jrha jrha merged commit bb22dd7 into quattor:main Jan 26, 2026
2 checks passed
@jrha jrha deleted the python-coverage branch January 26, 2026 10:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Development

Successfully merging this pull request may close these issues.

2 participants