-
Notifications
You must be signed in to change notification settings - Fork 122
feat(tests): add increased nonce with invalid nonce tests #1441
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(tests): add increased nonce with invalid nonce tests #1441
Conversation
Created PR #1444 to fix the logic of the test expectation for the two added tests, and added a new case. Basically, because the delegation had an invalid nonce, the test expected that there was no delegation at the authority address, but that's not true because the type of the authority was Sorry about the confusing logic to this test, at this point we are close to re-implement the EVM in the tests. I added some more comments to help understand the test a bit better. |
0fe233f
to
0a9472e
Compare
This fills with the I diffed the fixtures against those from @marioevz I updated Feel free to revert the latest commit, if you'd rather leave the old eels branch. |
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, I think the eels_resolutions.json change is ok, and I have this other PR #1454 to update to forks/prague once ethereum/execution-specs#1191 is merged, but this temporary workaround should be ok.
Thanks!
🗒️ Description
This PR attempts to add some missing test cases based purely on a coverage analysis of the test source itself. In particular, L269 in
test_gas
was not hit:execution-spec-tests/tests/prague/eip7702_set_code_tx/test_gas.py
Lines 256 to 276 in 62d2563
Either of these two test cases fill the line coverage gap, but I am out of my depth with 7702 and would appreciate feedback on the test cases and whether they're reasonable. In particular, the second case fails to fill for all but one parameter combo - it need further restriction on the conditions it runs (ran out of time on this one).
multiple_invalid_nonce_authorizations_self_sponsored_multiple_signers
test cases fill and add coverage. All clients pass with consume-engine.single_invalid_authorization_eoa_authority_multiple_signers
test cases only fill successfully for one parameter combo - this is WIP, needs further debugging.Perhaps this already helps you understand the fails from 2.:
Generate coverage for this module with:
🔗 Related Issues
None
✅ Checklist