-
Notifications
You must be signed in to change notification settings - Fork 229
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test baggage #9659
test baggage #9659
Conversation
Deploying agoric-sdk with
|
Latest commit: |
fbe4414
|
Status: | ✅ Deploy successful! |
Preview URL: | https://22a2feab.agoric-sdk.pages.dev |
Branch Preview URL: | https://ta-baggage-tests.agoric-sdk.pages.dev |
_incidental_ ## Description Some cleanups noticed in the course of [#9659](#9659) ### Security Considerations none ### Scaling Considerations none ### Documentation Considerations none ### Testing Considerations "Dependency Graph" test has been failing on the recent change to `replay-membrane.js`. Maybe that should be a Required test in the repo. ### Upgrade Considerations This changes Zoe but in a fully backwards and forward compatible way. I think it can get into master and reach chain whenever Zoe is next upgraded.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, although I'm curious what behavior we are testing or what invariants we are trying to uphold.
How should we be evaluating the snapshots? Two things coming to mind -
- userspace keys do not interfere with service level endowments
- baggage contents are available after upgrade
Good questions. In general, I think snapshot tests are valuable for:
Both are helpful right now for the PRs refactoring zones for retriable and a new boilerplate abstraction.
Yes, though I expect that will be maintained by a sub-baggage.
These don't test upgrade per se. I take it you mean that any change observed is backwards compatible. |
incidental
Description
Adds a way to test contract baggage, to detect changes.
Security Considerations
Uses the
setTestJig
to expose baggage. Safe by design.Scaling Considerations
none
Documentation Considerations
Could be useful at some point
Testing Considerations
CI
Upgrade Considerations
none