-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Additional LxLy Tests #18
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
be sure to shellcheck new .bats files if you haven't already
| Variable | Purpose | | ||
|--------------------+--------------------------------------------------------------------| | ||
| RPC_URL | A generic JSON RPC URL for tests that do not require L1/L2 context | | ||
| L1_RPC_URL | An RPC URL that serves as the L1 for some rollup or validium | | ||
| L2_RPC_URL | An RPC URL for a rollup that's anchored on L1 | | ||
| PRIVATE_KEY | A private key that's funded for RPC_URL | | ||
| L1_PRIVATE_KEY | A private key that's funded for L1_RPC_URL | | ||
| L2_PRIVATE_KEY | A private key that's funded for L2_RPC_URL | | ||
| SEQUENCER_RPC_URL | An RPC URL that's directly connected to a sequencer | | ||
| GAS_TOKEN_ADDR | The L1 address of a custom gas token | | ||
| BRIDGE_SERVICE_URL | The URL of the bridge service used for claiming deposits | | ||
| L1_BRIDGE_ADDR | The address of the bridge on L1 | | ||
| L2_BRIDGE_ADDR | The address of the bridge on L2 | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fyi @rebelArtists / @leovct I reviewed the current tests and to define what looks like the common environment variables at this point. What do you guys think about this. It leaves out some stuff, but I think it would cover a lot of common cases
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, that's very useful!
Description
Please include a summary of the change and which issue is fixed. Also, include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)