Retesteth Tool #357
Merged
Retesteth Tool #357
Conversation
This file contains 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
xavier-romero
approved these changes
Oct 2, 2024
leovct
approved these changes
Oct 2, 2024
Co-authored-by: Léo Vincent <[email protected]>
Co-authored-by: Léo Vincent <[email protected]>
Co-authored-by: Léo Vincent <[email protected]>
Co-authored-by: Léo Vincent <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 main focus of this PR is to add a small too which could take test fillers for retesteth and marshal them into a form that that can be used to generate RPC level tests for
castor assertoor.Right now the tool can handle some of the basics, but there are a bunch of gaps like:
solidityfieldEven if all of those worked, there are always going to be severe limitiations with this approach because the exact pass/fail status of these transactions can't be asserted with the same degree of confidence that we might have in the test environment. We can't control the blocks, state, or genesis.
This PR also includes some other odds and ends like: