Scenario Templates
VeriWasp ships with five built-in scenario templates: pre-written step sequences for the most common SaaS user flows, so you don't have to write a scenario from a blank page for the flows nearly every app shares. Selecting one on the New Playtest form pre-fills the step editor with its full step list, which you're free to edit, reorder, extend, or trim before confirming.
This page documents the exact steps each template starts you with, and what each one is testing for.
Every template's first step is navigate with the description "Load the
homepage," a reminder that this description text is never actually read for
navigate steps (see Step Types & AI Resolution).
It's there purely as a human-readable label.
Sign up flow
Slug: signup · Tests account creation end to end.
| # | Action | Description | Value |
|---|---|---|---|
| 1 | navigate | Load the homepage | |
| 2 | click | the Sign Up button | |
| 3 | type | the email field | playtest+signup@example.com |
| 4 | type | the password field | PlaytestPassword123! |
| 5 | click | the submit or create account button | |
| 6 | assert | a welcome message or dashboard is visible |
The final assert step is the actual pass/fail signal for the whole
scenario: if no element matching "a welcome message or dashboard is visible"
exists on the page after submitting, the step (and therefore the run) fails,
flagging that account creation didn't visibly succeed.
Checkout process
Slug: checkout · Tests completing a purchase using Stripe's well-known
test-mode card.
| # | Action | Description | Value |
|---|---|---|---|
| 1 | navigate | Load the homepage | |
| 2 | click | a pricing or upgrade link | |
| 3 | click | the checkout or subscribe button | |
| 4 | type | the card number field | 4242424242424242 |
| 5 | type | the card expiry field | 12/34 |
| 6 | type | the card CVC field | 123 |
| 7 | click | the pay or submit button | |
| 8 | assert | a confirmation or success message is visible |
4242 4242 4242 4242 is Stripe's standard test-mode card number. It only
works against a Stripe integration that's actually in test mode, and it will
be declined (or simply not exist as a valid card) against a live/production
Stripe integration. Don't point this template at a target with live payments
enabled expecting it to succeed.
Some payment providers, Stripe included, render the card number, expiry, and CVC fields inside a cross-origin iframe for PCI-compliance reasons. VeriWasp's browser automation cannot type into fields inside a cross-origin iframe. If your checkout form is built this way, steps 4 through 6 will fail to resolve, not because the description is wrong, but because the element genuinely isn't reachable from the parent page's DOM. This is a known limitation, not a bug to report.
Create project + invite teammate
Slug: invite-teammate · Tests workspace/project creation followed by
inviting a collaborator.
| # | Action | Description | Value |
|---|---|---|---|
| 1 | navigate | Load the homepage | |
| 2 | click | a create project or new project button | |
| 3 | type | the project name field | Playtest Project |
| 4 | click | the create or save button | |
| 5 | click | an invite teammate or invite member button | |
| 6 | type | the invite email field | teammate@example.com |
| 7 | click | the send invite button | |
| 8 | assert | the invite appears as pending or sent |
Like the signup template, this assumes an already-logged-in-or-otherwise-open project creation flow is reachable without a prior login step. If your app requires signing in first, prepend signup/login steps ahead of step 2 (subject to the login-automation limitation described in Account & Sessions).
Mobile navigation
Slug: mobile-nav · Exercises primary navigation at a mobile viewport.
| # | Action | Description | Value |
|---|---|---|---|
| 1 | navigate | Load the homepage | |
| 2 | click | the mobile menu or hamburger icon | |
| 3 | assert | the navigation menu is visible | |
| 4 | click | the first navigation link in the menu | |
| 5 | assert | the page loaded without errors |
This template is meant to be run with the Mobile viewport option set on the New Playtest form (see Creating a Playtest Run). Selecting the template does not change the viewport for you, so double check that dropdown before confirming.
Full user onboarding
Slug: full-onboarding · The complete first-time user journey: signup
followed by whatever onboarding steps stand between account creation and the
main app experience.
| # | Action | Description | Value |
|---|---|---|---|
| 1 | navigate | Load the homepage | |
| 2 | click | the Sign Up button | |
| 3 | type | the email field | playtest+onboarding@example.com |
| 4 | type | the password field | PlaytestPassword123! |
| 5 | click | the submit or create account button | |
| 6 | click | the continue or next button | |
| 7 | assert | the main dashboard or app experience is visible |
This is the broadest of the five templates and the most likely to need
editing. Step 6 ("the continue or next button") assumes a single-screen
onboarding wizard. If your app's onboarding spans several distinct screens
(profile setup, then a tour, then a first-project prompt, for instance), add
additional click/type/assert steps between 6 and 7 to walk through each
one explicitly.