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

[Tracking] Isthmus End-to-End Tests #14249

Open
meyer9 opened this issue Feb 7, 2025 · 3 comments
Open

[Tracking] Isthmus End-to-End Tests #14249

meyer9 opened this issue Feb 7, 2025 · 3 comments
Labels
A-op-e2e Area: op-e2e H-isthmus Hardfork: change is planned for isthmus upgrade M-tracking Meta: tracking issue

Comments

@meyer9
Copy link
Contributor

meyer9 commented Feb 7, 2025

Tracks all end-to-end tests that need to be created for Isthmus.

@meyer9 meyer9 added A-op-e2e Area: op-e2e H-isthmus Hardfork: change is planned for isthmus upgrade M-tracking Meta: tracking issue labels Feb 7, 2025
@meyer9
Copy link
Contributor Author

meyer9 commented Feb 7, 2025

The tests above should cover everything except operator fee coverage.

Withdrawals root test coverage is already implemented: https://github.com/ethereum-optimism/optimism/blob/develop/op-e2e/actions/upgrades/isthmus_fork_test.go#L56-L261

@meyer9
Copy link
Contributor Author

meyer9 commented Feb 7, 2025

Operator fee might be covered here: #12166

As long as there are no other valuable tests we want to implement.

@meyer9
Copy link
Contributor Author

meyer9 commented Feb 7, 2025

Can any sane tests be created for EIP-6110? I would think the request processing tests with the consolidation and withdrawal queue are sufficient and 6110 might be hard to test (would have to deploy a different deposit contract that can emit deposit logs and ensure they're ignored).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-op-e2e Area: op-e2e H-isthmus Hardfork: change is planned for isthmus upgrade M-tracking Meta: tracking issue
Projects
Status: No status
Development

No branches or pull requests

1 participant