Acceptance tests frequently flake on persistent devnets. In addition to writing new tests in a defensive style that is resilient to subtle environment changes (such as expected response times from RPC servers), we can make some changes to op-devstack that reduce flakes across the board. These are listed in sub-issues.
Writing acceptance tests is like writing normal go programs with syntactic sugar for common error handling and blockchain operations. It is less like writing traditional unit tests, where environmental factors like response times are irrelevant.