-
Notifications
You must be signed in to change notification settings - Fork 672
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
Adding v4 -> v5 upgrade chain test #2143
Adding v4 -> v5 upgrade chain test #2143
Conversation
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.
Wahoo!
func (s *UpgradeTestSuite) TestV4ToV5ChainUpgrade() { | ||
// TODO: temporarily hard code the version upgrades. | ||
oldVersion := "v4.0.0" | ||
targetVersion := "pr-2144" // v5 version with upgrade handler, replace with v5.0.0-rc3 when it is cut. |
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.
I guess we would need to backport upgrade handlers for each version we want to test?
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.
yep we won't be able to upgrade anything unless we have them.
chainA, _ := s.GetChains() | ||
|
||
chainAUser := s.CreateUserOnChainA(ctx, testvalues.StartingTokenAmount) | ||
s.UpgradeChain(ctx, chainA, chainAUser, "normal upgrade", targetVersion) |
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.
I guess followup pr's can allow pre/post upgrade checks
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.
Yes I think we can add before/after transfers in a follow up.
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.
Awesome, nice work! This will be so valuable
Description
This PR adds a test which for now uses a hard coded version of v4 and v5 (from this pr)
We can update this to use the next v5 rc tag when the changes are included.
part of: #1908
Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.
docs/
) or specification (x/<module>/spec/
)godoc
comments.Unreleased
section inCHANGELOG.md
Files changed
in the Github PR explorerCodecov Report
in the comment section below once CI passes