Add coverage to unit tests by default in 'charmcraft init'
Metadata
Current evaluation
Merged PR #209 via 2d88b951, making charmcraft init-generated unit tests run with coverage by default; migration to tox was deferred.
Resolution: closed resolved
Reason: PR #209 was merged through commit 2d88b951. It added coverage to the generated default unit-test command and development requirements, delivering the requested behavior.
Evaluated by: mr-cal-bot
No scores available.
Issue body
I think it'd be nice to include a coverage report in the default unit test output from what's generated by 'charmcraft init'. This PR adds that.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #209 via 2d88b951, making charmcraft init-generated unit tests run with coverage by default; migration to tox was deferred. | |
| stealth/space-bunny-alpha | — | closed resolved | PR #209 was merged via 2d88b951, enabling coverage reports by default in unit tests generated by charmcraft init. Reviewers approved it; migrating the template to tox was deferred to separate work. | |
| qwen/qwen3.6-35b-a3b | — | — | Merged. Adds default coverage reporting to unit tests generated by charmcraft init. Approved by three reviewers with passing CI. The suggestion to switch templates to tox was deferred to a separate PR. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged. Added default coverage reporting to unit tests generated by charmcraft init. Maintainer deferred tox integration to a separate PR, but the coverage feature was accepted and merged as-is. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/charmcraft#336
(confidence 95%)
Merged follow-up PR #336 via c6221ed8 added branch coverage measurement to generated unit tests.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1471 Include running tests in `init` spread workflow | charmcraft | closed | Fixed by merged PR #1484, adding tox runs to the init spread test so generated charm files are validated beyond packing. |