Skip to content
drawtonomy drawtonomy

Sketching ADAS test scenarios

ADAS and AD test catalogs — and broader self-driving / AV test plans — always need a clear scenario figure: lane layout, participants, the trigger, the expected response. drawtonomy is good for producing those figures quickly.

Common ADAS scenarios that sketch well

Section titled “Common ADAS scenarios that sketch well”
  • Cut-in.
  • Lead-vehicle braking.
  • Lane merge.
  • Stationary obstacle.
  • Pedestrian crossing.
  • Unprotected left turn.
  • Roundabout entry.
  • Crossing path.

Each is a five- or ten-minute sketch once you have road templates set up.

What you’ll get

Section titled “What you’ll get”
  • A clean, editable diagram suitable for test plans, design-review slides, and reports.
  • A small library of reusable road templates and scenario variants.
  • A runnable scenario: add actions and trigger conditions, set END / FAIL conditions, and play it in the browser on esmini-WASM with a PASS / FAIL verdict — no install. Export the run as a .webm, or the scenario as a .xosc + .xodr bundle for native esmini.

What you won’t get

Section titled “What you won’t get”
  • A parameter-swept test campaign. drawtonomy authors and runs one concrete scenario at a time; it does not sample a parameter space. To generate a fleet of variants across ranges, write them in a DSL or a Python library.
  • Sensor-grade data or a safety-case quantitative artifact. drawtonomy runs the storyboard and reports PASS / FAIL, but it doesn’t produce camera / LiDAR / radar data or the safety analysis itself.

For a swept catalog that feeds a large regression pipeline, generate the variants from a DSL and use drawtonomy to author, review, and replay individual concrete scenarios.

The workflow

Section titled “The workflow”
  1. Build a small library of road templates for your team — 2-lane road, 3-lane highway, 4-way intersection, T-junction, roundabout. Save each one as a .drawtonomy.svg file and reuse them for every new scenario.
  2. Copy a template and place participants — use the Vehicle templates so participant types are explicit.
  3. Annotate the trigger with a Text label and a contrasting color.
  4. Save as .drawtonomy.svg (drawtonomy’s native SVG format). This is the editable source — when the test parameter changes, you reopen the same file, change the offset / TTC label, and re-export. The lane geometry, participant layout, and Path arrows survive the round-trip.
  5. Export PNG (or PDF) from the same scene for the test plan, slides, or report.

Where it doesn’t reach

Section titled “Where it doesn’t reach”
  • Parameter sweeps — write the variants in code, not by copying canvases.
  • Detailed safety-case analysis — different tool.
Section titled “Related reading”