feat: use the newer ops.testing classes for the charm unit tests #1933
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…style of unit testing.
Co-authored-by: Dima Tisnek <dimaqq@gmail.com>
…g the entire layer.
mr-cal
approved these changes
Oct 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates the
simple,machine, andkubernetesprofiles to use the ops.testing state transition classes (previously: Scenario) rather than the legacy Harness API.The content of what each set of tests is testing remains unchanged, it's just using the new API to do the tests.
ops[testing]is installed via the tox dependencies (but should likely be in an optional dependencies group in the future, once CC005 is finalised). I've included it in thestaticdependencies as well, because as the charm gains additional tests those should also be statically checked and that will require theops[testing]classes.