Add unit tests for custom charm functionality#138
Merged
dwilding merged 7 commits intocanonical:mainfrom Apr 7, 2026
Merged
Conversation
Use ops.testing (Scenario) with the proposed charmcraft extension autoloading from canonical/operator#2367 to test the charm's custom code on top of the paas-charm base.
dwilding
approved these changes
Apr 1, 2026
Collaborator
|
@alithethird I think you'll be interested in this too. We may want to port some of the general improvements to the 12-factor profile in Charmcraft. |
Co-authored-by: Tony Meyer <tony.meyer@gmail.com>
Collaborator
|
Thanks again Tony! |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR adds state transition tests that use the new charmcraft extension autoloading from canonical/operator#2367 to test the charm's custom code on top of the paas-charm base. It also sets up CI to run
lintandunit, and combines the oldstaticenvironment intolint(as per current Charm Tech recommendations).Manual checks
If you changed the Dashboard application or the rock, have you increased the version number inN/Arockcraft.yaml? Remember to use the same version number inREADME.md.