Module driver 

One drive, run in-process: the steps a scenario names, performed through the shipped FrameHarness path, answering what the app showed rather than writing it to files.

drive runs the steps --headless-drive runs, on the same FrameHarness and through the same FrameHarness::perform_bound — no test copy — and answers the state the app is in afterwards where the CLI writes it to files. A scenario that passes here therefore passes in the app’s own process, on the same frames; what changes is only who reads the answer.

Structs

Outcome

Everything one drive answers: the state the app is in once the steps ran, step by step, and the first step that failed.

StepRecord

One step, and what it did.

Enums

Step

One step of a drive. Every action --headless-drive accepts is a step, and so is a question about the app’s state that no action asks.

StepStatus

What driving one step did.

Functions

drive

Run steps against the app harness hosts and answer what it shows.

steps_of

The steps a --headless-drive payload names, in order: its actions, as the steps drive runs them.

Type Aliases

Bindings

The answers earlier steps bound, by the name their step kept them under ({"name": {"value": ..., "resources": [...]}}): what a later invocation’s resource and arguments fill their {{name.path}} placeholders from.