mirror of
https://github.com/pezkuwichain/pezkuwi-subxt.git
synced 2026-06-20 02:21:03 +00:00
joe petrowski
6007549589
* change dir names * cargo toml updates * fix crate imports for build * change chain spec names and PR review rule * update cli to accept asset-hub * find/replace benchmark commands * integration tests * bridges docs * more integration tests * AuraId * other statemint tidying * rename statemint mod * chain spec mod * rename e2e test dirs * one more Runtime::Statemine * benchmark westmint * rename chain spec name and id * rename chain spec files * more tidying in scripts/docs/tests * rename old dir if exists * Force people to manually do the move. (Safer as there could be additional considerations with their setup) * review touchups * more renaming * Update polkadot-parachain/src/command.rs Co-authored-by: Bastian Köcher <git@kchr.de> * better error message * do not break on-chain spec_name * log info message that path has been renamed * better penpal docs --------- Co-authored-by: gilescope <gilescope@gmail.com> Co-authored-by: Bastian Köcher <git@kchr.de> Co-authored-by: parity-processbot <>
24 lines
1.0 KiB
Markdown
24 lines
1.0 KiB
Markdown
# xcm-emulator
|
|
|
|
XCM-Emulator is a tool to emulate XCM program execution using
|
|
pre-configured runtimes, including those used to run on live
|
|
networks, such as Kusama, Polkadot, Asset Hubs, et cetera.
|
|
This allows for testing cross-chain message passing and verifying
|
|
outcomes, weights, and side-effects. It is faster than spinning up
|
|
a zombienet and as all the chains are in one process debugging using Clion is easy.
|
|
|
|
## Limitations
|
|
|
|
As the messages do not physically go through the same messaging infrastructure
|
|
there is some code that is not being tested compared to using slower E2E tests.
|
|
In future it may be possible to run these XCM emulated tests as E2E tests (without changes).
|
|
|
|
As well as the XCM message transport being mocked out, so too are areas around consensus,
|
|
in particular things like disputes, staking and iamonline events can't be tested.
|
|
|
|
## Alternatives
|
|
|
|
If you just wish to test execution of various XCM instructions
|
|
against the XCM VM then the `xcm-simulator` (in the polkadot
|
|
repo) is the perfect tool for this.
|