There's no way to easily detect loss of test coverage
Bug #1218834 reported by
Roger Peppe
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Won't Fix
|
Low
|
Unassigned | ||
Bug Description
When refactoring tests, it's quite easy to inadvertently remove existing
test coverage (see https:/
where this happened).
With the new go coverage tool, we could potentially have an automated
check that existing test coverage is not lost.
| Changed in juju-core: | |
| importance: | Undecided → Wishlist |
| status: | New → Triaged |
| tags: | added: improvement |
| Changed in juju-core: | |
| importance: | Wishlist → Low |
| Changed in juju-core: | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
