didericis/bot-bottle
1
0
Fork 0
Code Issues 7 Pull Requests 15 Actions Packages Projects Releases Wiki Activity

Add coverage reporting to CI #277

New Issue
Closed
opened 2026-06-25 04:00:53 -04:00 by didericis-codex · 0 comments
didericis-codex commented 2026-06-25 04:00:53 -04:00
Collaborator
Copy Link
Copy Source

Add Python coverage reporting to the existing unittest-based CI.

Background:

  • The repo already uses stdlib unittest discovery.
  • coverage.py works directly with unittest, including branch coverage and HTML/XML/LCOV/JSON reports.
  • Unit and integration tests are already split by directory, and integration tests skip cleanly when Docker is unavailable.

Recommended scope:

  • Add coverage.py as a dev-only dependency.
  • Run unit tests under coverage in CI.
  • Keep integration tests optional or separate so missing Docker does not block coverage collection.
  • Prefer branch coverage and a text summary; HTML artifacts are a nice-to-have.

Acceptance criteria:

  • CI produces a coverage report for bot_bottle code.
  • The existing unittest workflow continues to pass.
  • Coverage does not require migrating the test suite to pytest.
Add Python coverage reporting to the existing unittest-based CI. Background: - The repo already uses stdlib unittest discovery. - coverage.py works directly with unittest, including branch coverage and HTML/XML/LCOV/JSON reports. - Unit and integration tests are already split by directory, and integration tests skip cleanly when Docker is unavailable. Recommended scope: - Add coverage.py as a dev-only dependency. - Run unit tests under coverage in CI. - Keep integration tests optional or separate so missing Docker does not block coverage collection. - Prefer branch coverage and a text summary; HTML artifacts are a nice-to-have. Acceptance criteria: - CI produces a coverage report for bot_bottle code. - The existing unittest workflow continues to pass. - Coverage does not require migrating the test suite to pytest.
didericis added the Kind/Testing
Priority
Low
4
 labels 2026-06-25 04:01:29 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No Label Kind/Testing
Priority
Low
4
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
didericis-claude (didericis (claude)) didericis-codex (didericis (codex)) didericis-gemma (gemma) didericis
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: didericis/bot-bottle#277
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?