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: e2e tests with kurtosis #47

Merged
merged 8 commits into from
Oct 17, 2024
Merged

feat: e2e tests with kurtosis #47

merged 8 commits into from
Oct 17, 2024

Conversation

klkvr
Copy link
Member

@klkvr klkvr commented Oct 16, 2024

Adds github workflow which launches kurtosis and runs (for now 2 simple) tests against running network.

This is for now patched to use my repo for optimism-package until we have paradigmxyz/optimism-package#4 merged.

Here's example workflow run https://github.com/klkvr/odyssey/actions/runs/11372561760/job/31637163326

I wasn't able to make docker caching work so right now it takes ~30m, I'm wondering if there are some easy optimizations we could do?

Copy link
Member

@onbjerg onbjerg left a comment

Choose a reason for hiding this comment

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

let's rename testing to e2e-tests in the same go

use url::Url;

static REPLICA_RPC: LazyLock<Url> = LazyLock::new(|| {
std::env::var("REPLICA_RPC")
Copy link
Member

Choose a reason for hiding this comment

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

i'm wondering if we could just skip the tests instead of failing them when u run these locally, not particularly great ux running cargo test and having them fail :( same issue in foundry. not a blocker though

@onbjerg onbjerg merged commit d922f5e into ithacaxyz:main Oct 17, 2024
14 checks passed
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