TTestFlow/Docs
Product guide/The builder/Results & history

The builder

Results and history

Where a run's data goes, how to read it while it happens, and how to find it again three weeks later.

What a run produces

OutputWhere it landsContents
Results fileOutput/ in the packageOne row per recorded point: loop variables, operator inputs from a pause, every measured column, and each column’s verdict.
LogOutput/The complete run output, including everything the view truncated.
OutcomeRead by the productStatus, rows written, columns, failed limits, failed instruments, duration.
Reportthe Report paneThe document form of the above.
PDF reportOutput/, when the package was built with reporting onGenerated next to the results file at the end of the run.
The streaming execution log: progress lines with percentages and step counts, instrument command lines naming the SCPI sent, waiting lines for the delays, and VAR lines recording each measured value.
The log is the audit trail of a run: every command sent, every value read back, and every variable recorded, in order.

The measurement dashboard

While a bench run is in flight, the dashboard shows each measured column as a card, updating as the results file grows. It is the fastest way to notice that a rail is 200 mV low without waiting for the run to end.

Run history

Live values under the steps rail: Loop 1 at 6 of 9, N4(Measurement) reading 0.998, and vin reading 3.5.
While the run is live, the same values that are being written to the results file are shown here.

The History tab in Executor lists your past runs. Each entry carries the workflow, the timestamp, the outcome, and an export. Use it to compare a run before and after a board change, or to retrieve results from a session you have closed.

Statuses, and what each one means

StatusMeaningIs it a pass?
passedThe run completed, rows were written, and every evaluated limit was met.Yes
failedThe run completed and at least one limit was not met.No. A result, not a fault.
errorThe run did not complete. An instrument, the connection, or the code failed.No
stoppedYou stopped it.No
unknownThe run ended without reporting an outcome.No. Unknown is never a pass.