Launch Test #

URL: /launch

A single-form view for starting a test session from the browser instead of the command line. Fill in the form, click Start Test, and the page redirects to the live monitor at /live/{run_id}.

The form takes a Product, DUT Serial, Test Path, Station, optional Operator name, and a Mock Hardware checkbox.

Form #

Launch — form

Field	Purpose	Required
Product	The DUT part / product the test targets. Dropdown is populated from the project's `products/` directory. Selecting a product filters the Station dropdown to compatible stations.	optional
DUT Serial Number	The serial number stamped on the unit you're about to test (e.g. `DPB001-0001`). Free-text.	yes
Test Path	Which test file or directory to run. Dropdown is populated from tests Litmus discovered in the project.	yes
Station	Which station to run on. Dropdown is filtered by the selected Product when one is selected; otherwise shows every station. A hint line below the dropdown tells you what's filtered ("3 compatible station(s)" / "Showing all stations. Select a product to filter." / "No compatible stations - consider mock mode").	yes
Mock Hardware	When checked, runs against mock-instrument stand-ins instead of real hardware. Useful for dry runs and CI.	optional
Operator	Your name. Stamped on the run record for traceability.	optional
Start Test button	Submits the form. Validates required fields, starts the run via the API, then redirects to `/live/{run_id}`.

If DUT Serial or Station is empty, the form pops "Please fill in required fields". If Test Path is empty, the form pops "Select a test directory". Either way the form stays on the page so you can fix the input and retry.

Pre-fill via URL #

The Dashboard's station cards link here with the station pre-filled (/launch?station=<id>). The Product field accepts the same query parameter (product=<id>), and mock=1 pre-checks the Mock Hardware box. Useful for bookmarking a specific test setup.

URL parameter	Pre-fills
`product`	The Product dropdown
`station`	The Station dropdown
`mock`	Set to `1` to pre-check Mock Hardware

After Start Test #

Successful submit redirects to /live/{run_id} — the live monitor view for the new session. From there, the run progresses through RunStarted, step events, measurements, and finally RunEnded, at which point the Results detail page becomes the canonical view.

A failure (network error, missing station, etc.) pops an error toast and stays on the form so you can fix the input and retry.

Underlying data #

Stations come from the same discover_stations query the Dashboard uses. Products come from the project's products/ directory. Tests come from the project's tests/ directory (discover_tests).

The "compatible stations" filter behind the Product dropdown uses the capability matching machinery — a station is compatible with a product when its instruments cover every required characteristic of the product.

Common tasks #

Run a quick smoke test on this bench — select Station, leave Product blank, pick a Test Path, check Mock Hardware, Start.
Production launch — select Product first (filters stations), pick a compatible Station, enter DUT Serial, leave Mock unchecked, enter your name as Operator, Start.