Authoring Guide

Drag-drop editor tour

A guided tour of the test editor — Toolbox on the left, test column in the center, header chips on top. Where each piece lives and what it's for.

The drag-drop editor is where you build a test. There are three regions: the Toolbox on the left, the test column in the center, and the header chips along the top.

Full editor screenshot with annotations: Toolbox sections on the left, test column with three example steps in the center, and the header chip row across the top showing the test name, run controls, and the Self-Healing chip.

Toolbox (left)

The Toolbox is your palette. It's organized into sections — built-in interaction tiles (the ten kinds described in The Toolbox) and a User Defined section that lists every template you've created.

You drag a tile from the Toolbox into the test column. The tile becomes a step.

Test column (center)

The test column is the ordered list of steps Mavster will execute top-to-bottom when you press play.

  • Click a step to select it.
  • Double-click a step to open its editor (a freshly-dropped step shows the placeholder "Double-click to edit").
  • Drag a step to reorder it.
  • Right-click a step to:
    • Nest it under the previous step as a conditional child — pick Execute on previous true or Execute on previous false. Mavster runs the child only when the parent step's outcome matches.
    • Unnest a child via Extract from parent.
    • Copy, paste, duplicate, or delete the step.

Each step has a status indicator that updates live during a run: gray (not running) → blue (running) → green (success) or red (failed).

Header chips (top)

The test header carries the test's name (which can contain $placeholders) plus a row of chips:

  • Self-Healing — pick Strict (off), Per Step, or Full Test. Tier-gated to Ultra; non-Ultra users see a yellow lock chip with the tooltip "Self-healing is an Ultra feature — click to upgrade". See Self-healing.
  • Run controls — play this test, cancel a running test.

Step editor

Double-clicking a step opens its editor. The editor shape varies by interaction kind:

  • Common to all: an instruction field — labeled per interaction (Control description, List description, Question to answer, …) — an AI Segmentation picker, sometimes a Memory toggle.
  • Type-specific fields: Tap shows Tap Count, Region of Interest, and Repeat Until; Scroll shows Direction, Speed, Until; Built-In shows the command picker; etc.

See the Interactions Reference for each interaction's full settings list.

Drag from anywhere

Tiles are draggable, but so are steps. You can:

  • Drag a step within the same test (reorder).
  • Drag a step into another test's editor (move/copy across tests).

Nesting a step under another step (to create a conditional branch) is not done by dragging — use the right-click context menu on the step you want to nest. See Conditional children.