-
Notifications
You must be signed in to change notification settings - Fork 11
test: rewrite upgrade test as a sandbox integration tests #1186
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: rewrite upgrade test as a sandbox integration tests #1186
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.
Nice stuff!
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.
Thank you.
I would like to see some more state added before the migration call (at least what we have in the pytest we are about to delete, but even better if we were to resolve #415 with this PR)
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 think there are still a few details to work out s.t. we don't lose test coverage compared to the pytests.
…ate_to_current-as-a-sandbox-integration-tests
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.
Thanks for all the work. I think we are getting close to merge, but there are still a few things we need to look at.
Hard blockers for me right now are the following:
- concerning large key event timeout #1186 (comment)
- use of
DomainId::legacy_ecdsa_id()in non-backwards compatibility tests #1186 (comment) - slight regression testing the upgrade functionality of the current contract #1186 (comment)
| Ok(()) | ||
| } | ||
|
|
||
| pub async fn sign_and_validate( |
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.
Nice refactor, I like that we are breaking the logic out into smaller, re-usable functions!
Could we add a doc comment for this function?
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.
This function already existed before. Seems like the diff is getting messed up because of re-ordering. Feel free to create an issue to document.
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.
Feel free to create an issue to document.
I think the effort of opening an issue and following it with a PR is not justified for a doc comment that could be added as a broken-window fix.
But this was never a blocker for this PR, so, if you are happy without the comment, we don't need one.
| ) -> anyhow::Result<()> { | ||
| let status = submit_sign_request(request, contract).await?; | ||
|
|
||
| tokio::time::sleep(std::time::Duration::from_secs(3)).await; |
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.
Out of scope for this PR, but could we open an issue to get rid of this sleep?
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.
Sure, feel free to create cone.
|
Thank for the very in depth review. I believe all these hard blockers have been addressed now.
|
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.
Thanks!
| Ok(()) | ||
| } | ||
|
|
||
| pub async fn sign_and_validate( |
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.
Feel free to create an issue to document.
I think the effort of opening an issue and following it with a PR is not justified for a doc comment that could be added as a broken-window fix.
But this was never a blocker for this PR, so, if you are happy without the comment, we don't need one.
…ate_to_current-as-a-sandbox-integration-tests
closes #1185