You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add more tests for events.rs/decode_and_consume_type (paritytech#430)
* test-runtime: Fix README typo
Signed-off-by: Alexandru Vasile <[email protected]>
* test-runtime: Explicit error handling for missing substrate binary
Signed-off-by: Alexandru Vasile <[email protected]>
* test-runtime: Fix documentation typo
Signed-off-by: Alexandru Vasile <[email protected]>
* events: Test primitive decode_and_consume
Signed-off-by: Alexandru Vasile <[email protected]>
* events: Test tuple decode_and_consume
Signed-off-by: Alexandru Vasile <[email protected]>
* events: Test array decode_and_consume
Signed-off-by: Alexandru Vasile <[email protected]>
* events: Extend array with sequences
Signed-off-by: Alexandru Vasile <[email protected]>
* events: Test variant decode_and_consume
Signed-off-by: Alexandru Vasile <[email protected]>
* events: Test composite decode_and_consume
Signed-off-by: Alexandru Vasile <[email protected]>
* events: Test compact decode_and_consume
Signed-off-by: Alexandru Vasile <[email protected]>
Copy file name to clipboardExpand all lines: test-runtime/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,8 +3,8 @@
3
3
The logic for this crate exists mainly in the `build.rs` file.
4
4
5
5
At compile time, this crate will:
6
-
- Spin up a local `substrate` binary (set the `SUBSTRATE_NODE_PATH` env var to point to a custom binary, otehrwise it'll look for `substrate` on your PATH).
6
+
- 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).
7
7
- Obtain metadata from this node.
8
8
- Export the metadata and a `node_runtime` module which has been annotated using the `subxt` proc macro and is based off the above metadata.
9
9
10
-
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.
10
+
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.
0 commit comments