-
Notifications
You must be signed in to change notification settings - Fork 50
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
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.
let's rename testing
to e2e-tests
in the same go
crates/testing/src/tests.rs
Outdated
use url::Url; | ||
|
||
static REPLICA_RPC: LazyLock<Url> = LazyLock::new(|| { | ||
std::env::var("REPLICA_RPC") |
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.
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
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?