pezkuwi-subxt

mirror of https://github.com/pezkuwichain/pezkuwi-subxt.git synced 2026-04-26 16:57:58 +00:00

Files

T

Bruno Galvao b2a62a56c9 Use TEST_WS in all remote-externalities tests (#3284 )

Refactor in accordance with
https://github.com/paritytech/polkadot-sdk/issues/2245#issuecomment-1937025951

Prior to this PR, the `remote_tests` test module would either use
`TEST_WS` or `DEFAULT_HTTP_ENDPOINT`.

With the PR, `TEST_WS` is the default for the `remote_tests` test module
and the fallback is `DEFAULT_HTTP_ENDPOINT`.

The only downside I see to this PR is that for particular tests in the
`remote_tests` module, one would want to use a different http endpoint.
If that is the case, they would have to manually hardcode the http
endpoint for that particular test.

Note: The `TEST_WS` node should fulfill the role for all test cases e.g.
include child tries.

Give it a _try_:
```
TEST_WS=wss://rococo-try-runtime-node.parity-chains.parity.io:443 cargo test --features=remote-test -p frame-remote-externalities -- --nocapture
```

---------

Co-authored-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>

2024-02-13 09:23:22 +00:00

binary-merkle-tree

Lift dependencies to the workspace (Part 1) (#2070 )

2024-02-12 11:19:20 +00:00

build-script-utils

Sync Cargo.toml and crates.io versions (#3034 )

2024-01-26 18:14:03 +00:00

fork-tree

Sync Cargo.toml and crates.io versions (#3034 )

2024-01-26 18:14:03 +00:00

frame

Use TEST_WS in all remote-externalities tests (#3284 )