Skip to content
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

feat(test): E2E tests #145

Open
wants to merge 18 commits into
base: main
Choose a base branch
from

Conversation

janjakubnanista
Copy link
Collaborator

@janjakubnanista janjakubnanista commented Jan 26, 2025

In this PR

The ultimate goal of this PR is proposal of E2E testing strategy for the optimism-package based on BATS. It is not intended to be merged in one go - it combines several steps needed to get to the point where CI E2E pipeline is running:

@janjakubnanista janjakubnanista changed the title proposal: E2E tests feat(test): E2E tests Jan 26, 2025
mise.toml Outdated Show resolved Hide resolved
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could we potentially install bats (and support/assert libs) through mise?

Copy link
Collaborator Author

@janjakubnanista janjakubnanista Jan 27, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunately not, they do not package them as binaries, especially the assert & support don't expose a binary - they just need to be sourced into the test file.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually I found bats itself in the package registries so I dropped that submodule, the support & assert remain

@janjakubnanista janjakubnanista requested a review from sigma January 27, 2025 16:57
@janjakubnanista janjakubnanista marked this pull request as ready for review January 27, 2025 17:40
local OP_GETH_ISTHMUS_TIME=$(jq '.result.protocols.eth.config.isthmusTime' <<< $OP_GETH_NODE_INFO_JSON)
assert_equal "$OP_GETH_ISTHMUS_TIME" "0"

kurtosis enclave rm -f $ENCLAVE_ID
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm worried we might be leaking enclaves if the tests fail.

Should we have "kurtosis enclave add/rm" in setup/teardown functions around the test itself (or at the suite level to save time/resources)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants