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

E2E test for runtime upgrades #5817

Open
alexggh opened this issue Sep 24, 2024 · 3 comments
Open

E2E test for runtime upgrades #5817

alexggh opened this issue Sep 24, 2024 · 3 comments
Assignees

Comments

@alexggh
Copy link
Contributor

alexggh commented Sep 24, 2024

#5738, Postmortem, has showed that we have a gap in testing with regards to runtime upgrades, one of the action items in the post mortem is to have E2E test where:

  1. Spawn a zombienet test with the runtime version Westend/Rococo testnet is running.
  2. Upgrade the runtime to the latest version a PR introduces.
  3. Check various asserts hold true immediately after the runtime upgrade, ideas of things we can check:
  • All runtime ParachainHostAPIs return expected values.
  • Parachains are producing blocks as expected around the blocks we did the runtime upgrade.
@pepoviola
Copy link
Contributor

Part of the test is implemented here #5794. We should add the checks you mention.
Thx!

@tdimitrov
Copy link
Contributor

We also did runtime upgrade with zombienet-sdk during for the disabling tests - https://github.com/paritytech/disabling-e2e-tests/blob/452ba09ed6874e4b5a55dedb338b669cabcbf8f0/src/lib.rs#L212

@pepoviola
Copy link
Contributor

I added a helper into zombienet to make more easy to permorm upgrades 😃

@alexggh alexggh self-assigned this Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants