Testing in Acton

This section contains guides and reference documentation for the Acton test runner.

Available since: Acton 1.2

Start acton studio to retain test history and inspect results in the Studio workspace.

Generate wrappers for Tolk smart contracts

Control test behavior, skip tests, and set expectations with @test.* attributes

Run parameterized tests with generated inputs, assumptions, and bounds

Configure the test runner in Acton.toml and with CLI flags

Save and restore local emulation state as JSON fixtures inside tests

Use testing.createTraceIterationCursor() and TxCursor to run transaction chains in parts

Inspect traces, transaction trees, logs, failures, coverage, and gas profiles in the browser UI

Reference for JSON artifacts from acton test --save-test-trace, reused by the Test UI

Reference for transaction predicates, map expectations, and out-action helpers

Read the text trace format from println(txs) and matcher failures

Profile gas hot paths, inspect flamegraphs, save snapshots, and compare baselines

Test contracts against real chain state by forking testnet or mainnet

Measure and inspect code coverage in Tolk smart contract tests

Run mutation testing to assess the test suite quality and find hidden gaps in the coverage

Short examples for common assertions, helpers, and scenarios in tests

Extend expect() with domain-specific matchers