mirror of https://github.com/pezkuwichain/pezkuwi-subxt.git synced 2026-04-22 16:08:00 +00:00

Files

T

James Wilson 2f1b67b384 Factor substrate node runner into separate crate (#913 )

* factor out node starting thing to separate crate to use in test-runtime and integration-tests

* remove subxt dep on test-runtime build, and clippy tidyup

* remove now-unneeded dep

* Update testing/substrate-runner/Cargo.toml

Co-authored-by: Alexandru Vasile <60601340+lexnv@users.noreply.github.com>

* Update testing/integration-tests/Cargo.toml

Co-authored-by: Niklas Adolfsson <niklasadolfsson1@gmail.com>

* remove unneeded port things for backward compat

---------

Co-authored-by: Alexandru Vasile <60601340+lexnv@users.noreply.github.com>
Co-authored-by: Niklas Adolfsson <niklasadolfsson1@gmail.com>

2023-04-17 12:42:17 +02:00

src

Add 'Static' type and improve type substitution codegen to accept it (#886 )

2023-03-31 16:56:19 +01:00

build.rs

Factor substrate node runner into separate crate (#913 )

2023-04-17 12:42:17 +02:00

Cargo.toml

Factor substrate node runner into separate crate (#913 )

2023-04-17 12:42:17 +02:00

README.md

Move test crates into a "testing" folder and add a ui (trybuild) test and ui-test helpers (#567 )

2022-06-17 14:33:58 +01:00

README.md

test-runtime

The logic for this crate exists mainly in the build.rs file.

At compile time, this crate will:

Spin up a local substrate binary (set the SUBSTRATE_NODE_PATH env var to point to a custom binary, otherwise it'll look for substrate on your PATH).
Obtain metadata from this node.
Export the metadata and a node_runtime module which has been annotated using the subxt proc 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.