# All the Things Example
URL: /examples/all-the-things

The upstream all_the_things.py example — configuration-bound plugs, a frontend-aware plug, a monitor, htf.Dimension, attachments, templated limits with with_args, test metadata, and three output callbacks (pickle, JSON, console) in one script.

The kitchen-sink script from upstream: nearly every feature in one test. Based on `examples/all_the_things.py` and `example_plugs.py`, merged into one file.

Create `example_attachment.txt` next to the script (any content), then:

Type anything not ending in `Widget` to see a `FAIL` with the regex validator in the summary; type `raise` to see an `ERROR`.

Plug constructor arguments resolved from configuration at test start. `--config-value example_plug_increment_size=3` changes behaviour without code edits. Plug configuration →

Plugs whose `_asdict()` state is streamed to the Operator UI whenever they call `notify_update()`. `UserInput` is built this way.

Runs `example_monitor` in a background thread while `set_measurements` executes, recording a timestamped series. The monitor function uses plugs like any phase. Monitors →

A labelled axis for multi-dimensional measurements, alongside plain `UnitDescriptor`s. Multi-dimensional →

Validator limits as templates, filled per phase copy — table-driven limits without rewriting phases. With plugs example →

Binary and file attachments, readable during the test. Attachments →

The phase is not run and does not appear in the record, unlike `PhaseResult.SKIP`. Run if →

Keyword arguments to `htf.Test` land in `metadata`; `test_name` also names the test in the banner. Metadata →

`OutputToFile` (pickle), `OutputToJSON`, `ConsoleSummary` — all run after the test, in order. Patterns can reference `{metadata[test_name]}`. Output Callbacks →

<Card title="Tutorial" href="/tutorial" description="The same features, built up one step at a time." />

<Card title="Test Record" href="/test-record" description="What all of this looks like in the record." />