mirror of
https://github.com/pezkuwichain/pezkuwi-subxt.git
synced 2026-04-22 20:48:01 +00:00
Alexandru Vasile
868b465e01
* test-runtime: Fix README typo Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io> * test-runtime: Explicit error handling for missing substrate binary Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io> * test-runtime: Fix documentation typo Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io> * events: Test primitive decode_and_consume Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io> * events: Test tuple decode_and_consume Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io> * events: Test array decode_and_consume Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io> * events: Extend array with sequences Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io> * events: Test variant decode_and_consume Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io> * events: Test composite decode_and_consume Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io> * events: Test compact decode_and_consume Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
718 B
718 B
test-runtime
The logic for this crate exists mainly in the build.rs file.
At compile time, this crate will:
- Spin up a local
substratebinary (set theSUBSTRATE_NODE_PATHenv var to point to a custom binary, otherwise it'll look forsubstrateon your PATH). - Obtain metadata from this node.
- Export the metadata and a
node_runtimemodule which has been annotated using thesubxtproc macro and is based off the above metadata.
The reason for doing this is that our integration tests (which also spin up a Substrate node) can then use the generated subxt types from the exact node being tested against, so that we don't have to worry about metadata getting out of sync with the binary under test.