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
We often want to make client calls straight after (e.g. namadac tx), these require that the RPC server has started up, which we can check by awaiting for this string:
validator_0.exp_string("Starting RPC HTTP server on")?;
Sometimes tests can flake locally as the client call is made before the RPC server is started. We should ensure we await the RPC server to be started in any tests where that is required - we could factor out a helper function to do this, which would also reduce code duplication.
The text was updated successfully, but these errors were encountered:
In many of our e2e tests, we wait for the ledger node to start up by looking for a string like below:
We often want to make client calls straight after (e.g.
namadac tx
), these require that the RPC server has started up, which we can check by awaiting for this string:Sometimes tests can flake locally as the client call is made before the RPC server is started. We should ensure we await the RPC server to be started in any tests where that is required - we could factor out a helper function to do this, which would also reduce code duplication.
The text was updated successfully, but these errors were encountered: