User journeys

Letting WebLens draft a user journey from a plain-language task, then reviewing it.

A user journey is a short path through your app, like sign-up, checkout, or a configurator. WebLens runs every assessment by following these journeys step by step, so they tell the agent where to go and what to check.

You usually don't write these by hand. The quickest way is to let AI discover them: describe a task and WebLens drafts the whole journey for you to review. Writing one manually is only for when you want full control.

What a good journey looks like

Whether the AI drafts it or you write it, a good journey follows a few simple ideas. This is all you need to review a draft with confidence:

  • It starts somewhere clear. The first step says where to begin, a URL or a homepage, so the agent isn't guessing.
  • Each step moves to one place. One screen or section per step, not a whole flow crammed into one line.
  • It says where to go, not what to type. Point the agent to a page or button; it explores and tests the rest on its own.
  • It's safe. Where a step could submit, save, or delete something, it includes a "do not submit or save" note so nothing real changes.

A quick example

Instead of something vague like:

Explore and interact with all the elements.

a good journey reads like a short set of directions:

1. Open the app and go to the Home page.
2. Click "Create Member" to open the form.
3. Explore the form's fields and tabs. Do not submit or save.

That's the whole idea, clear starting point, one move per step, and a safety note where it matters.

Next

Make sure WebLens can reach your application, see How to give WebLens access to my platform. Then pick which criteria to run against each journey.