MD-26: User-facing checks
- Description: Automate checking user experience by submitting transactions every few minutes
- Authors: Andy Golay
Overview
We need to check that users can submit transactions. This MD outlines a simple automated solution.
Definitions
Provide definitions that you think will empower the reader to quickly dive into the topic.
Desiderata 26
User-facing Suzuka Checks
User Journey: Users get more assurance that we know when Suzuka testnet has a transaction-processing outage.
Description:
-
Implement e2e tests which are already packaged as containers. See https://github.com/movementlabsxyz/movement/tree/main/networks/suzuka/suzuka-client/src/bin/e2e for the test logic and https://github.com/orgs/movementlabsxyz/packages?repo_name=movement for the containers (those with e2e in the name).
-
Run these checks periodically, say once every 3 minutes, to simulate users sending transactions, and add to monitoring infrastructure, reporting based on the exit code of the e2e test binaries and not requiring any modifications to the implementation.
(See @l-monninger comments in discussion and reference implementation by Liam below.)
Justification:
It’s a high priority to have testnet running and able to process transactions, or alerting us otherwise.
Guidance and suggestions:
We will need the address for this job allowlisted to use the Suzuka testnet faucet.
Reference Implementation: