Document testing constructor authorization - #2682
Open
leighmcculloch wants to merge 1 commit into
Open
Conversation
|
Preview is available here: |
leighmcculloch
marked this pull request as ready for review
July 24, 2026 22:06
leighmcculloch
requested review from
ElliotFriend and
Copilot
and removed request for
Copilot
July 24, 2026 22:06
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
1 participant
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.
What
Document that
env.register/env.register_atmock a contract's constructor authorization, and that testing it requires deploying viaenv.deployer().with_address(...).deploy_v2(...)instead.Why
The testing guide covers asserting on auths but never mentioned that registration auto-authorizes a constructor's
require_authcalls, a nuance the SDK's rustdoc was just updated to call out in stellar/rs-soroban-sdk#1950.