Draft UI tests for each journey

Turn the journeys of a workflow into draft tracks in UI Tester, one for each journey, ready to record.

In short

A workflow's journeys are ready-made scenarios. "Draft UI tests per journey…" makes one draft track in UI Tester for each journey, with a stage for every user step and the inputs as parameters. A draft does not run until you record each stage.

Before you start

Who: you need a UI Tester site you may add tracks to.
Plan: Designer and UI Tester must both be on your plan, and the plan's track limit applies. The drafts are made all together or not at all.
First: name or finish a journey that ends, and choose the site.

Steps

Open the workflow and press "Export". Under "Tests", choose "Draft UI tests per journey…".
Choose the "Site". Untick any of the "Journeys" you do not need.
Check each journey's stages, where it starts, such as "starts at /signup", and its parameters. A password is marked secret.
Press "Make 3 drafts".
Press "Record this stage" on a track to open the recorder in UI Tester.

Result: "3 drafts were made in UI Tester." Each reads "Draft · not runnable until recorded".

Good to know

Named journeys are drafted. When none is named, every journey that ends in success is drafted, up to 20.
Selectors are not guessed. Each stage is a placeholder step and every draft step is switched off, so a run is refused until the recorder adds steps.
A track opens the first product page its journey names. A Figma frame address is skipped, and a track with no page opens "/".
Parameters come from the inputs of the user steps. A password parameter is sensitive and has no default.
Recording adds steps at the end of the track. Delete the placeholders when you have recorded the stage.
After you edit the workflow, open this sheet again and choose the site. A journey with a track on that site reads "Already in UI Tester", names its "New stages" and the button says "Update": the new stages and inputs are added to that track, and what you recorded stays. A stage you removed from the workflow stays on the track until you delete it there.
A track on another site is left alone. The journey reads "On another site" and the site you chose gets a draft of its own.
UI Tester decides where tracks may be made. You need a site you may change, and your plan's track limit applies. The drafts are made all together or not at all.

If something goes wrong

"This workflow has no journey with a user step that ends yet. Finish or name a journey first."
"UI Tester is not on for you here, or there is no site you may add tracks to."
"Choose a site and at least one journey."