← Back to issue list

Add coverage to unit tests by default in 'charmcraft init'

View original Github issue

Metadata

Project
charmcraft
Number
#209
Type
pull request
State
merged
Author
mthaddon
Labels
Created
Updated
Closed

Current evaluation

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.

Suggested action:

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
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.
qwen3.6-35b-a3b-mtp-q6 Merged to add default coverage reporting to unit tests generated by charmcraft init. Maintainers deferred a potential template switch to tox for a separate PR.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#1660 feat: add test command and templates charmcraft merged Merged addition of the charmcraft test command and templates. The feature invokes spread to run test suites locally and remotely using a multipass backend. Approved by two reviewers and rebased on main before integration.
71%
#1329 test(style): remove pydocstyle tests on charmcraft code charmcraft merged Merged removal of pydocstyle tests from charmcraft code, as they are now redundant due to ruff adoption. Test functions for the init command were also relocated. Approved by two reviewers and passed CI.
70%