Four ways to create scenarios

There are four ways to turn what you want to check into a scenario (one flow in your app, written out as steps). Pull them from your code automatically, build them through a chat with AI, get walk-through suggestions from AI, or write them yourself. You can mix all four, or start with just the one that feels easiest. Below, we walk through which method fits which situation.

Method 1. Pull them from your code

This is the fastest way to start. Connect your code to a project (we call it a Spec here), and AI reads that code, figures out "this app probably has these flows," and drafts scenario candidates for you automatically.

It doesn't just skim the code. AI actually walks through your app once and looks at the screens. That way it catches flows that exist in the code but never show up on screen, and flows that show up on screen but were never tidied up in code.

The candidates aren't final. Review them once, keep the ones you like, and drop the rest. You can expand each candidate to see which steps it contains beforehand, so you choose based on whether the flow fits your app. Because several are generated at once, this saves the most time when you're first sketching the big picture.

Because AI explores your app directly, there's a cost. One run takes about 28 credits (you're only charged for what's actually used). Credits are what you spend to run verification. See Credits and plans for details.

To use this method, your code needs to be connected first — that means registering the address of the app you want to check. See Connect your code for how.

If you want to check an app that already has code, this is the lowest-effort way to get going.

Method 2. Build them through a chat with AI

This one fits anyone thinking "I have no idea what steps to write." AI asks a few questions as grouped multiple choice. For a question like "Do you log in with email, or a social account?" you pick an option, and AI gathers your answers to build a scenario automatically.

The best part: you don't need to know the details. AI proposes a draft first, based on your connected code. You just fix the parts that are wrong. Instead of filling in blanks from scratch, you're trimming something that's already filled in, which takes a lot less effort.

As you answer the questions, a full scenario comes out within a single round. Since the draft is code-based, familiar flows like "sign up" come back mostly correct, and you only touch the parts that are unique to your app. If the scenario isn't quite right, you can ask AI again and refine the steps further. You don't have to nail it perfectly in one shot — it gets more accurate as you go back and forth.

Method 3. Get walk-through suggestions

Here, AI walks through your app directly and proposes "this would be worth turning into a scenario" before you ask. Suggestions come in two kinds.

• Empty spots — flows that clearly exist in your code but haven't been organized into a scenario yet. AI points them out, as in "looks like you haven't been checking this screen."
• Removal candidates — flows that used to be in your code but are gone now. AI tells you "this scenario doesn't seem to exist in the app anymore," so you can clean up scenarios you no longer use.

You don't have to take every suggestion at once. Look at them one by one — "I'll make this," "skip that" — and any suggestion you accept goes straight into your scenario list. When it's hard to think of what to check yourself, AI finding the gaps for you makes a good starting point. It especially helps fill the blind spots that pile up after you've been building an app for a while.

Method 4. Write them yourself

The simplest, most certain method. You just write the steps out in plain words, one by one — like "open the signup page → enter email and password → complete signup → confirm the welcome email arrives."

When you note which screen element (a button, an input field, and so on) each step uses, autocomplete helps you. Type just "sig" and it offers the "Sign up" button that's actually on the screen. That keeps what you write from drifting away from what's really on the page.

This fits when you want to control the flow with your own hands, with no AI suggestions, or when you just want to quickly make one very simple flow.

Group them into areas

As scenarios pile up, they get hard to take in at a glance. So similar scenarios get grouped into areas — like "Sign up and log in," "Payments," or "Edit profile." Think of an area like a folder.

An area can also have a perspective, which splits flows by whose eyes you're seeing them through.

Perspective	Whose flow is it
All	Flows common to every user
Visitor	Flows for someone not logged in yet
Member	Flows only a logged-in person can see

Splitting by perspective lets you clearly check things like "a not-logged-in person shouldn't even reach the checkout screen."

Scenarios grouped into areas show up neatly by area in the workspace's service map (the "User scenarios" tab). You can rename an area later, and reorder it so the ones you check most sit at the top. Even when scenarios grow into the dozens, as long as you've split areas and perspectives well, you won't wander around wondering "now where was that one?"

Which method should you pick

Here's a situation-by-situation recommendation.

• Code already exists and you want a quick sweep of everything → Method 1. Pull them from your code
• You're stuck on what steps to write → Method 2. Build them through a chat with AI
• You'd like AI to point out what you missed → Method 3. Get walk-through suggestions
• The flow is simple and you want to control it yourself → Method 4. Write them yourself

If it's your first time, we recommend connecting your code, sketching the big picture with Method 1, then filling the gaps with Methods 2 and 4. Once your scenarios are ready, head to Running verification and reading results and give it an actual run.

The Create your first scenario button shows up anywhere in the workspace. From there you can pick one of the four methods above and start right away.