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
There are a lot of places within integration test code that validators are queried for chain state like so. Currently, the first validator in a config list fulfills these queries. However, as we add validator downtime testing, these queries can fail if the desired validator is not operational.
Solution: a dedicated non validating, full node should be spawned up for integration tests. This node will never be taken down during the test, and can fulfill all queries
The text was updated successfully, but these errors were encountered:
* add quiery node to integration tests
Closes: #263
* use query node for tx and query RPC
* ignore unused function declaration
* connect relayer query node instead of validator
* refactor integration test scripts after review
Co-authored-by: Jehan <[email protected]>
Co-authored-by: Daniel T <[email protected]>
There are a lot of places within integration test code that validators are queried for chain state like so. Currently, the first validator in a config list fulfills these queries. However, as we add validator downtime testing, these queries can fail if the desired validator is not operational.
Solution: a dedicated non validating, full node should be spawned up for integration tests. This node will never be taken down during the test, and can fulfill all queries
The text was updated successfully, but these errors were encountered: