See Maestro in four steps

You don't open a sequence editor or hand-write code. You tell the assistant what to measure and the limits — in plain language — and it generates the test as readable, version-controlled YAML plus any Python and/or C# methods it needs. You review the intent, not the source.

steps:
  - name: "Bode Sweep — Gain at 1 kHz"
    type: mock
    measurement:
      name: "GAIN_1KHZ"
      value: "{{test.gain_1k}}"
      low_limit: -10.0
      high_limit: -4.0
      unit: "dB"

  - name: "Generate Interactive Bode Chart"
    runner: python
    parameters:
      module: "bode_artifacts"
      function: "generate_bode_plotly"

def generate_bode_plotly(frequencies, gains_db, phases_deg):
    """Emit an interactive Plotly chart artifact."""
    fig = make_bode_figure(frequencies, gains_db, phases_deg)
    with open(_artifact_path("bode.plotly.json"), "w") as f:
        f.write(fig.to_json())     # Maestro renders it inline

The Test Runner streams progress, variables and each step's verdict in real time. We've pre-selected the Artifact Visualization Demo for you — just press Start Test.

Each run produces a report with the pass/fail verdict, a measurement table against its limits, and any artifacts rendered inline — including the interactive Plotly Bode chart (zoom, hover, export) and the sweep data as a table. Open Test Results, search Artifact, and open the most recent run.

Now zoom out — the real power is querying across every run on the floor, not just the one you launched. Because results are structured data, the assistant reasons over yields, process capability (Cpk), marginal passes and failure patterns. Try one in the chat drawer: