Skip to content
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: verify purse balances are updated after smartWallet upgrade #8909

Merged
merged 9 commits into from
Feb 17, 2024

Conversation

Chris-Hibbert
Copy link
Contributor

refs: #8787

Description

A copy of #8787 for master.

Verify that purse balances are updated after smartWallet upgrade in an a3p-integration test.

Security Considerations

None

Scaling Considerations

None

Documentation Considerations

None

Testing/Upgrade Considerations

This is a test that upgrading SmartWallet maintains the ability to update vstorage for purses.

Copy link
Member

@mhofman mhofman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Quick preliminary review

Comment on lines 2 to 12
"agoricProposal": {
"releaseNotes": "TBD",
"sdkImageTag": "unreleased",
"planName": "UNRELEASED_UPGRADE",
"upgradeInfo": {
"coreProposals": [
"@agoric/builders/scripts/vats/init-network.js"
]
},
"type": "Software Upgrade Proposal"
},
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this a 2nd chain software upgrade? it should be in the existing a:upgrade-next on master.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

a3p-integration/proposals/a:upgrade-next/use.sh Outdated Show resolved Hide resolved
a3p-integration/proposals/b:upgrade-14/repairs.test.js Outdated Show resolved Hide resolved
Copy link
Contributor Author

@Chris-Hibbert Chris-Hibbert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also rebased to master.

Comment on lines 2 to 12
"agoricProposal": {
"releaseNotes": "TBD",
"sdkImageTag": "unreleased",
"planName": "UNRELEASED_UPGRADE",
"upgradeInfo": {
"coreProposals": [
"@agoric/builders/scripts/vats/init-network.js"
]
},
"type": "Software Upgrade Proposal"
},
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

a3p-integration/proposals/a:upgrade-next/use.sh Outdated Show resolved Hide resolved
@mhofman mhofman changed the title 8445 a3p tests mastr test: verify purse balances are updated after smartWallet upgrade Feb 17, 2024
@mhofman mhofman added the force:integration Force integration tests to run on PR label Feb 17, 2024
@mhofman
Copy link
Member

mhofman commented Feb 17, 2024

@Chris-Hibbert I adapted the test to match the new style and helpers for core-eval in tests. Will squash-merge if you're of with the latest state

@mhofman mhofman added the automerge:squash Automatically squash merge label Feb 17, 2024
@mergify mergify bot merged commit a929734 into master Feb 17, 2024
75 checks passed
@mergify mergify bot deleted the 8445-a3p-tests-mastr branch February 17, 2024 23:04
mhofman added a commit that referenced this pull request Feb 18, 2024
)

* test: verify purse balances are updated after smartWallet upgrade

* chore: helpful suggestions from review

* refactor: testRepairs to Ava test

* chore: make test work on master

* chore: rearrange files, repair merge conflict

* chore: rename

* chore: adapt wallet a3p test to new core-eval style

* fixup

---------

Co-authored-by: Turadg Aleahmad <turadg@agoric.com>
Co-authored-by: Mathieu Hofman <mathieu@agoric.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge:squash Automatically squash merge contract-upgrade force:integration Force integration tests to run on PR wallet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants