arbitrum-client: add integration test setup #269
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
joeykraut
approved these changes
Nov 25, 2023
akirillo
force-pushed
the
andrew/integration-test-scaffolding
branch
from
11ab84f to
7acd57b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR sets up scaffolding for integration tests for the Arbitrum client. This defines CLI arguments for running integration tests, the subsequent integration test arguments, and the invocation of the
integration_test_mainmacro. No tests are defined yet, and the docker-compose stack from the Starknet client tests is not yet replicated.Next steps will be to set up the tests themselves, at first running them against a separately-instantiated devnet, with a docker-compose stack to follow.