simulators/ethereum/engine: Refactor Test Verification Syntax #524
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.
This PR includes a refactoring of the Test Verification syntax to make the test cases much more readable and explicit on what they expect as outcome.
The
Expect*
methods are introduced to allow test cases to explicitly indicate what to expect from each call they perform, to either the Engine API or the Eth JSON-RPC.E.g. this verification:
becomes:
The verification fail check is now embedded within all the
Expect*
methods and, unless they explicitly expect an error (e.g.ExpectError
), the call automatically checks forerr == nil
.