canonical / canonical/charmlibs
Use pytest-jubilant in integration tests and upload juju debug-log
- Dominant language
- Python
- Stars
- 5
- Forks
- 28
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 24
Description
With the release of `pytest-jubilant` 2.0, we have a nice way to capture the `juju debug-log` on model teardown. We should use this in `charmlibs`.
- Require `pytest-jubilant` based integration tests (document, update existing tests).
- Update the template and example libraries to use `pytest-jubilant`.
- Pass `--juju-dump-logs` in CI and use `actions/upload-artifact` to export the logs nicely.
Contributor guide
Research direction
Start by locating the integration tests, their dependency documentation, the template and example libraries, and the CI workflow. Check how pytest-jubilant is currently configured, then verify that the tests require it, CI passes --juju-dump-logs, and uploaded artifacts contain the Juju debug logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100