TTestFlow/Docs
Open TestFlow
Product guide/The builder/Builder anatomy

The builder

Builder anatomy

Every control in the builder, and what each one is for. The builder is where you spend your time in TestFlow, so it is worth ten minutes.

The builder is three regions: a toolbar across the top, the agent chat on the left, and one artifact pane on the right. The pane you are looking at is chosen by the pill row in the toolbar. Your instruments dock along the bottom of the artifact pane and stay visible whatever else you are doing.

The builder as it ships today: chat left, the active artifact right, your bench docked underneath.
Three-pane layout: chat, the workflow pinned, and a second artifact beside it. Toggled from the toolbar.

The toolbar

The left of the builder toolbar: the TestFlow mark, the project name, and a chevron that opens the project menu.
Left: the project name. The chevron opens the project menu.
The right of the builder toolbar: the account avatar, Share, Upgrade, and the green Run button.
Right: your avatar, Share, and Run.
ControlWhereWhat it does
Project nameTop leftOpens the project menu: rename, star, move to a folder, remix a copy, delete, appearance, and the project id. The autosave state sits beside it.
HistoryLeft of the pillsOpens revision history. Click a revision to preview it in the panes, then restore it or go back to latest.
ExpandLeft of the pillsHides the chat and gives the artifact the full width. Useful for reading a plan or a long log.
Three-paneLeft of the pillsPins Preview in the middle and puts the pill-driven artifact on the right, so you can watch the workflow while reading the report.
Pane pillsCentrePreview, Code, Plans, Report, Schematic, Executor. One is always active.
ShareTop rightInvite teammates by email, or copy a read-only link to the project.
RunTop rightStarts the run and switches to Executor. The arrow beside it chooses simulate or bench.

The six panes

The builder toolbar's centre cluster: history, expand and three-pane icons, then six pane pills reading Preview, Code, Plans, Report, Schematic and Executor, with Preview active.
The pill row. Preview is active here; whichever pill is lit decides what fills the pane on the right.

Preview

The workflow: steps in order, with their instruments, actions, parameters, and limits.
Read more

Code

The generated Python package, file by file, exactly as it will run.
Read more

Plans

Documents. A formal validation plan, a spec, a procedure. Word-styled, exportable.
Read more

Report

The run’s measured columns, limits, charts, and verdict.
Read more

Schematic

Bench wiring between instruments and the DUT, as an ordered hookup checklist.
Read more

Executor

Runs the test. Progress, log, live measurements, run history.
Read more

Plans and Report are not the same pane

This distinction is the one worth internalising.

Plans holds what you INTENDED

  • Prose about the test: objective, procedure, coverage, spec tables.
  • Written before the run, and often before the hardware exists.
  • Ask for it with words like plan, spec, procedure, document.

Report holds what HAPPENED

  • Measured columns from a real run, with units, limits, and verdicts.
  • Structure written by the agent, numbers written only by the run.
  • Ask for it with words like results, limits, tolerance, pass/fail.
INTENT — THE AGENT MAY WRITE THISPreviewthe ordered steps of the testand the limits each must meetPlansprose about the test: coverage,procedure, spec table, approvalsSchematicwhich cable goes where,in hookup ordernothing crosses this lineFACT — ONLY A RUN MAY WRITE THISReportThe agent writes its STRUCTURE: which measured columns to show, their units, their limits, which charts to draw.Every number in it comes from the run's results file. There is no field the agent could put a measurement in.
The four artifacts, split by what each is allowed to contain.

The instrument dock

The instrument dock: a count of two instruments, Add Instruments, an Auto detect control marked desktop app only, Test connection, and two instrument cards for a Keithley power supply and a Tektronix oscilloscope, each reading Configured and Offline.
The dock, at the bottom of every pane. One card per instrument, with its model and its connection status. Auto detect is greyed out in the browser: it needs the desktop app.

The strip along the bottom of the artifact pane is your bench. Each instrument is a card with its icon, type, manufacturer, model, and connection status. From a card you can edit it, test the connection, or remove it. Add Instruments opens the catalog. The dock minimises when you need the height.

See also
Layout and revisionsConnect your instruments