Creating Simulations

To create a Simulation, open the Simulations page and click Run Exploration. This opens the Explore App modal.

Fill in the following, then click Run Exploration:

1. Instructions — Describe what the run should explore or test.
2. Driver — The single Persona the run acts as, plus an Experience slider from Novice to Expert (five levels, defaults to Expert). A higher level gives the run access to a richer set of learned Skills; lower levels narrow it toward core browser operations.
3. Riders — Personas that ride along and react to every step. Leave it empty for a run that records actions only.
4. Max Steps — Under Options. How far the run may go (see below).

Writing instructions

Instructions tell the run what to focus on. Be specific — for example, “Navigate to the settings page and test every account-management control.”

You can reference Application details with variables:

• {{url}} — Your Application’s URL.
• {{username}} and {{password}} — Sign-in credentials (available when your Application is an app rather than a public website).

The runtime substitutes the real values just before each action runs, so credentials are never stored in the transcript.

Tip

Not sure where to start? Click the Starter template chip under the instructions box to drop in a broad exploration prompt tailored to your Application type. Edit it from there.

Personas

A Persona shapes how the run approaches your Application:

• Driver — The one Persona the run acts as, in character. Leave it empty and Marketrix explores neutrally as Generic, following only your instructions.
• Riders — Personas that ride along without driving. Each one reacts to every step, so a single run yields several perspectives on the same journey. A run supports at most 50 rider persona-users in total.

If you don’t have Personas yet, run with no driver. See Generating Personas for how Marketrix builds them.

Max Steps

Max Steps is how many actions the run may take. Range 1–1000, default 100. Reaching the budget ends the run cleanly (it counts as Done, not Failed). Increase it for large Applications with many pages. Marketrix knows how much budget is left and paces its exploration accordingly.

Caution

High step counts (500+) can mean long-running Simulations. Start near the default of 100 and increase only if the run runs out of budget before covering what you need.

Next steps

Monitoring SimulationsWatch the run explore in real time.

Simulation ResultsReview the transcript once the run finishes.