-
Notifications
You must be signed in to change notification settings - Fork 47
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Execution traces for call sequences failing tests (#105)
* Introduction of execution trace attaching and displaying for failed test call sequences * Added helpers to extract Solidity errors/panics (now used by assertion test provider and execution tracer) * Added fuzzer tests to verify execution trace output * Updated README with required solidity version for unit tests * Provided a wrapper for ExecuteCallSequenceIteratively, to simply re-execute a given call sequence without any custom checks * Updated FuzzerWorker to re-execute the finalized shrunken sequence before performing the "finalized shrunken sequence" callback, so all providers can assume state is post-execution. * Updated assertion test provider to attach an execution trace for the last call in a failing sequence * Updated property test provider to attach execution traces for the last call in a failing sequence, and for its property test * Updated the fuzzer worker so if a "trace all" flag is provided, it will attach execution traces to all finalized shrunken call sequence elements prior to returning the results to any test provider * Updated TestChain to provide a method to get the post-execution state root hash for a given block number * Cleaned up ABI error and event helpers by splitting them off to a compilation-related "abiutils" package. --------- Co-authored-by: anishnaik <[email protected]>
- Loading branch information
Showing
32 changed files
with
1,412 additions
and
126 deletions.
There are no files selected for viewing
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
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
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
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
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
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
Oops, something went wrong.