test: Add unit tests for custom charm functionality#1
Closed
tonyandrewmeyer wants to merge 1 commit into
Closed
Conversation
tonyandrewmeyer
commented
Mar 9, 2026
7226e26 to
dd988cc
Compare
tonyandrewmeyer
commented
Mar 9, 2026
tonyandrewmeyer
commented
Mar 9, 2026
63c29c7 to
d9b4c17
Compare
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.
d9b4c17 to
46e28e5
Compare
Owner
Author
|
Opened upstream: canonical#310 |
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
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.
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.