galacticcouncil / galacticcouncil/hydration-node
Test: add xcm tests for important use cases
- Dominant language
- Rust
- Stars
- 208
- Forks
- 109
- Avg merge
- 6d 3h
- Merged PRs (30d)
- 3
Description
Time to time we have breaking xcm integrations on PROD, for example when we do an upgrade.
For example [this](https://moonbeam.subscan.io/xcm_message/polkadot-975ba80e59c8165f126e4f8e1d24ba4c66235a68) resulted in AssetTrapped event on Moonbeam side.
We should write xcm tests using chopsticks to cover the most important scenarios.
Check first [Polkadot Ecosystem Tests](https://github.com/open-web3-stack/polkadot-ecosystem-tests), it was announced recently
Acala also does such xcm integration tests, check that out also if we could leverage it.
Otherwise we could do something like:
- We build our new in CI.
- We spin up our chain with it, and also other needed parachains with chopstics, on a dedicated machine
- In JS, we can write tests where we run the extrinsics and the verifications
Contributor guide
Assessment
This issue has not been assessed yet.