Author integration tests using Ginkgo

[cam-schultz]

Action items
The Ginkgo test framework has already been implemented in other tickets, for example #94. Much of the discussion in the following sections have already been resolved and implemented, but I'll leave the text there for context.

The main remaining action item to close this ticket out is to port the existing bash integration tests to our Ginkgo framework. Below are the test cases we need to port.

• example_messenger.sh
  • PR: General Ginkgo E2E test framework + Teleporter test cases #93
• basic_send_receive.sh
  • PR: e2e test case: basic send *and receive* #139
• erc20_bridge_multihop.sh
  • PR: ERC20 bridge multihop #140
• send_specified_receipts.sh
  • PR: General Ginkgo E2E test framework + Teleporter test cases #93
• block_hash_publisher_receiver.sh
  • PR: Ginkgo e2e test case: block hash publish receive #163
• Remove bash integration test setup
  • PR: Remove bash integration tests #168

Context and scope
The current integration test setup consists of a set of docker containers that:

1. Spin up a local avalanche network and deploys subnets and Teleporter contracts
2. Runs an awm-relayer instance
3. Executes integration tests

These steps are performed within the containers using a set of bash scripts. For example, https://github.com/ava-labs/teleporter/blob/main/docker/run_setup.sh starts the networks, and https://github.com/ava-labs/teleporter/blob/main/scripts/local/test.sh runs the integration tests.

Discussion and alternatives
Ginkgo is a test framework written in Go that performs very similar steps to our current setup, but in a much more user friendly and less error prone way. Ginkgo:

• handles container setup and teardown
• is easier to avoid bugs when authoring tests due to Go's static typing
• produces much more readable tests with clearly defined expected behavior
• is under active development

To convert our bash-based integration tests to Ginkgo, the following development strategy is proposed:

1. Port awm-relayer E2E tests written in Ginkgo to teleporter. The high-level changes here are:
   a. Implement basic send and receive integration test.
   b. Modify message relaying to either build and run awm-relayer directly, or manually aggregate signatures and deliver the message from within the E2E test. subnet-evm Warp E2E tests take the latter approach.
2. Consolidate awm-relayer and teleporter E2E tests to reduce code duplication.
3. Iteratively expand teleporter Ginkgo E2E test suite to achieve parity with the existing bash integration tests.
4. Remove bash integration test CI jobs, and optionally remove all docker and bash code.

Open questions

• One nice feature of the docker setup is that we can start up the system, but not execute tests, (see run.sh) allowing the user to open a shell inside one of the containers and interact with the system in real time. Is this possible with Ginkgo?