missing coverage of charm events
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
charm-k8s-jenkins-agent |
Fix Released
|
Medium
|
Unassigned |
Bug Description
https:/
has no test coverage for what happens if a user changes config.
You could do that testing with the operator framework's testing harness along the lines of:
from ops import testing
harness = testing.
harness.begin()
harness.
and then introspect attributes of 'harness.charm' to see if config changed was properly handled.
Note there is an open Operator issue for cleaner testing support of pod-spec-set:
https:/
If there is something that you would like to see that would make testing of charm behavior clear and clean for you, please leave comments on that issue.
Changed in charm-k8s-jenkins-agent: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
We've since updated tests for this charm, and currently have 100% unit test coverage.