feat: add fork choice endpoint to api spec tests#439
Merged
tcoratger merged 1 commit intoleanEthereum:mainfrom Mar 9, 2026
Merged
Conversation
2 tasks
unnawut
approved these changes
Mar 9, 2026
Kayden-ML
approved these changes
Mar 9, 2026
tcoratger
approved these changes
Mar 9, 2026
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🗒️ Description
The API spec test currently tests the get heath, finalized state and justified checkpoint endpoints in a target client implementation. To cover the recently added fork choice endpoint we should include tests for that as well.
Tests against a client implementations endpoint similar to other API spec tests have been added.
🔗 Related Issues or PRs
This was the initial PR outlining the API spec test suite.
#346
✅ Checklist
toxchecks to avoid unnecessary CI fails:uvx tox