Skip to main content
In the web app, every test starts as a conversation. Here’s what happens between “paste URL” and “Run Test.”

Step 1 — Paste the URL

On the Tests page, paste the URL you want to test. This can be any publicly reachable page: your homepage, a specific feature, a landing page, a checkout flow, anything.
The web app needs to be able to reach the URL from our servers. To test localhost or any internal URL, use the agent CLI instead — it runs the browser on your machine.

Step 2 — Percio scrapes page context

As soon as you submit the URL, Percio fetches a lightweight representation of the page: the title, visible headings, key actions, and structural hints. This grounds the rest of the conversation so Percio’s questions are specific to your product rather than generic. You don’t see the scrape happen — just a brief loading state and then the chat opens.

Step 3 — The Q&A

Percio asks 2 to 5 short questions to understand what you actually want to test. Typical questions:
  • “What is the goal you want the user to complete?”
  • “Is there a specific segment of user you’re worried about?”
  • “Are there any known constraints — sign-in required, feature flags, limited inventory?”
  • “What does success look like for you?”
Answer in your own words. The tone is conversational — you’re not filling out a form.

Step 4 — Scenario generation

When Percio has enough, it generates a scenario: a clear, actionable description of the task the persona will attempt. Something like:
“As a first-time visitor, find a pair of running shoes under $120, add them to the cart, and proceed to checkout.”
You’ll see the scenario before the test runs. If it doesn’t match what you meant, say so in the chat — Percio will refine it.

Step 5 — Persona selection

Once the scenario is locked in, you pick the persona to run the test through. Your onboarding persona is available by default. Any personas you’ve created on /personas show up in the same picker. See Picking a persona.

Step 6 — Run

Hit Run Test. Percio checks you have enough credits, kicks off a server-side execution, and takes you to the live view at /test-running/[executionId].

Editing mid-test

You can’t change the scenario once a test is running — the execution runs to completion (or abandons itself early; see Live execution). If something’s wrong, stop the run and start over.

What’s next