Module invariant

Modules§

CheckSequenceOptions
InvariantExecutor: Wrapper around any Executor implementer which provides fuzzing support using [proptest].
InvariantFailureMetrics 🔒: Tracks invariant failure counts during a campaign.
InvariantFailures: Stores information about failures and reverts of the invariant tests.
InvariantFuzzTestResult: The outcome of an invariant fuzz test
InvariantMetrics: Contains invariant metrics for a single fuzzed selector.
InvariantTest 🔒: Contains invariant test data.
InvariantTestData 🔒: Contains data collected during invariant test runs.
InvariantTestRun 🔒: Contains data for an invariant test run.
InvariantThroughputMetrics 🔒: Campaign-level throughput metrics for invariant progress reporting.

build_invariant_progress_json 🔒: Builds the machine-readable invariant progress payload emitted during a campaign.
call_after_invariant_function 🔒: Calls the afterInvariant() function on a contract. Returns call result and if call succeeded. The state after the call is not persisted.
call_invariant_function 🔒: Calls the invariant function and returns call result and if succeeded.
check_sequence: Checks if the given call sequence breaks the invariant.
check_sequence_value: Executes a call sequence and returns the optimization value (int256) from the invariant function. Used during shrinking for optimization mode.
collect_data 🔒: Collects data from call for fuzzing. However, it first verifies that the sender is not an EOA before inserting it into the dictionary. Otherwise, we flood the dictionary with randomly generated addresses.
execute_tx 🔒: Executes a fuzz call and returns the result. Applies any block timestamp (warp) and block number (roll) adjustments before the call.
rate_per_sec 🔒: Converts a cumulative campaign total into an average per-second rate.
replay_error: Replays and shrinks a call sequence, collecting logs and traces.
replay_run: Replays a call sequence for collecting logs and traces. Returns counterexample to be used when the call sequence is a failed scenario.