TestingTest UI
Quickstart
Step-by-step guide to run Test UI and inspect failed tests, traces, transactions, and logs
This quickstart shows how to go from acton test --ui to diagnosing a failed test.
1. Run tests with UI
acton test --uiUseful variants:
# Choose a custom UI port
acton test --ui --ui-port 23456
# Run only selected tests
acton test tests/counter.test.tolk --ui --filter "test deploy"
# Open Test UI with coverage viewer enabled
acton test --coverage --uiIf you start Test UI with both --coverage and --ui, an additional
Coverage tab appears next to the regular test results view.
2. Open failed test first
In the left sidebar:
- filter by
Failed - click the failed test
- open
Infotab
In Info tab, check:
- error message and matcher context
- source location (
file:line:column) - fee summary per trace

3. Inspect execution graph
Open Transactions tab:
- select trace (if multiple)
- inspect transaction tree and failed nodes
- click node to open detailed phase/fee/exit-code panel

4. Inspect VM logs
Open Logs tab:
Executor Logfor high-level execution flowVM Logfor low-level VM details
Common issues
- UI server did not start: selected port may be busy; try
--ui-port 23456. - Coverage tab is missing: rerun tests with both
--coverageand--ui.
Last updated on