docs: add pytest-operator migration guide from Jubilant docs#2381
docs: add pytest-operator migration guide from Jubilant docs#2381dwilding merged 6 commits intocanonical:mainfrom
Conversation
james-garner-canonical
left a comment
There was a problem hiding this comment.
This looks great, thanks @dwilding!
tonyandrewmeyer
left a comment
There was a problem hiding this comment.
Makes sense to me, thanks!
I skipped reviewing the migration guides, trusting that they're copied over as in the PR description.
Seeing the Jubilant one makes me think maybe I should open a PR with a "how to get started using AI" section added ... I wonder if we're open to having that in our docs.
|
|
||
| ## pytest-operator | ||
|
|
||
| pytest-operator and python-libjuju are deprecated. You should migrate integration tests to Jubilant. |
There was a problem hiding this comment.
I wonder if this should be "to Jubilant and pytest-jubilant" given the work that @james-garner-canonical is doing? Or maybe that's kind of implied and too noisy for right here?
There was a problem hiding this comment.
Yeah, this PR is partly to get things ready for James to start making pytest-jubilant updates
This PR is the companion to [operator#2381](canonical/operator#2381). It removes the pytest-operator migration guide (which is the only how-to guide in the Jubilant docs). The new location of the migration guide is https://documentation.ubuntu.com/ops/latest/howto/migrate/migrate-integration-tests-from-pytest-operator/. **[Preview build of Jubilant docs](https://canonical-ubuntu-documentation-library--270.com.readthedocs.build/jubilant/)**, with no how-to guides. Follow-up actions: - Define a redirect in RTD for the removed URL.
We're working on making the scope of the Jubilant docs narrower, to focus on standalone use of Jubilant. Guidance related to charm integration testing is moving to the Ops docs.
This PR:
Follow-up actions: