Execution
Configure how TofuPilot executes your test procedures, including phase order, failure handling, and parallel execution strategies.
You can configure test execution behavior using the execution section in your procedure file.
Options
TofuPilot provides options to control test execution:
On Fail
Control behavior when phases fail
Workers
Control worker thread count
Slots
Configure parallel test slots
Strategy
Choose phase-first or slot-first
Run Outcome
TofuPilot determines the overall run outcome after all phases complete:
| Outcome | Condition |
|---|---|
| Error | Any phase threw unhandled exception |
| Stop | Run was stopped by user or phase.stop() |
| Timeout | Any phase exceeded timeout limit |
| Fail | Any phase failed |
| Pass | All phases passed |
TofuPilot evaluates each condition in order and assigns the first matching outcome.
Run Again
After a run completes, the execution bar shows the option to quickly re-execute.
Starts a new run with the same unit identification — serial number, part number, revision number, batch number, and sub-units are all reused from the previous run.
The identify unit row will use the same values as finished run. All other behavior is identical to a normal run: phases reset, outcomes are cleared. In multi-slot setups, each slot's last unit is independently reused.
Auto-identify
If the procedure has auto_identify: true, the Run Again button is
disabled. Unit identification is already automatic via YAML defaults — use Run
instead.
How is this guide?