This pulse has seen a lot of roadmap planning by the team. We’re also excited to promote the use of pytest-jubilant for charm integration tests. We’ve been opening PRs to help charms migrate from pytest-operator and to the 2.0 release of pytest-jubilant, and updating our documentation around integration testing.
Ops
- Began updating the Ops documentation to recommend the use of pytest-jubilant (#2406), and updating the charmcraft init profiles accordingly (#2623).
Charming
- Set 7-day dependabot cooldowns across the Charm Tech repositories (#2413)
- Opened PRs to 12-factor charms to demonstrate the ease of using ops[testing] with the new support for charmcraft extensions (#21, #164, #608, #81, #23, #310)
- Fixed a couple of bugs with the way that Jubilant transparently handles Juju snap confinement (#275)
- Improved the Concierge logging so that expected errors are not logged (#173)
- Updated various “migrate to Jubilant” PRs, primarily to adjust for the changes in pytest-jubilant 2.0
- Released pytest-jubilant 2.0.1, adding the py.typed marker. Don’t hesitate to report any issues you encounter with pytest-jubilant.
- Improved Jubilant’s Juju.offer() method so that it uses the model from the Juju instance (#276)
Charmlibs
- Began documenting how interface libraries should provide relation data for use in charm unit tests, and updating the interface library template and example (and the repository infrastructure) accordingly (#408).
Pebble
- Investigated issues using remote-build for building Pebble snaps
Documentation
- Moved guidance about charm integration testing from the Jubilant docs to How to write integration tests for a charm in the Ops docs (#2390)
- Worked on upcoming documentation for using spread and charmcraft test for charm testing