The revive differential testing framework allows to define smart contract tests in a declarative manner in order to compile and execute them against different Ethereum-compatible blockchain implmentations. This is useful to:
- Analyze observable differences in contract compilation and execution across different blockchain implementations, including contract storage, account balances, transaction output and emitted events on a per-transaction base.
- Collect and compare benchmark metrics such as code size, gas usage or transaction throughput per seconds (TPS) of different blockchain implementations.
- Ensure reproducible contract builds across multiple compiler implementations or multiple host platforms.
- Implement end-to-end regression tests for Ethereum-compatible smart contract stacks.
For now, the format used to write tests is the matter-labs era compiler format. This allows us to re-use many tests from their corpora.
The retester helper utilty is used to run the tests. To get an idea of what retester can do, please consults its command line help:
cargo run -p revive-dt-core -- --help
For example, to run the complex Solidity tests, define a corpus structure as follows:
{
"name": "ML Solidity Complex",
"path": "/path/to/era-compiler-tests/solidity/complex"
}Assuming this to be saved in a ml-solidity-complex.json file, the following command will try to compile and execute the tests found inside the corpus:
RUST_LOG=debug cargo r --release -p revive-dt-core -- --corpus ml-solidity-complex.json