QA Runs
A QA Run is a single execution of a QA Flow. Each run launches one persona-driven simulation per (persona × viewport) — the persona works through the flow’s Journeys in a real browser — and records a verdict of passed, failed, or indecisive for every (persona × Journey × viewport).
Starting a run
Section titled “Starting a run”From a QA Flow, click Run Now (or Run Again if the flow has run before) and configure the run:
- Viewports — Choose one or more of desktop, tablet, and mobile. Runs are Chrome-only; each viewport fans out into its own simulation so you can compare how each Journey behaves across screen sizes.
A run starts immediately and you’re taken to its live view. Journeys update in real time as each persona works through them.
Watching a run
Section titled “Watching a run”While a run is in flight, each Journey moves through these states:
| Status | Meaning |
|---|---|
| Queued | The Journey is waiting to start. |
| Running | Marketrix is actively executing the Journey in the browser. |
| Passed | The persona reached the expected outcome and the followed steps aligned with the plan. |
| Indecisive | Marketrix could not conclusively pass or fail the Journey; you resolve it, and the resolution is remembered per application. |
| Failed | The expected outcome was not reached. |
| Stopped | The Journey was stopped before completing. |
The run summary shows live counts of passed, failed, and indecisive Journeys, along with elapsed time. You can Stop a run at any time — in-flight Journeys are marked stopped.
Reading results
Section titled “Reading results”Every Journey is evaluated automatically against its expected outcome. The verdict explains:
- Whether the outcome was reached.
- Whether the followed steps aligned with the planned steps.
- A short, human-readable reason for the verdict.
Each Journey also has a walkthrough: the steps Marketrix actually followed and screenshots captured along the way. An indecisive verdict is one you can resolve manually, and Marketrix remembers your resolution for that application.
Reports
Section titled “Reports”From a run you can generate a report on demand — a downloadable PDF that lays out every Journey with its verdict, planned steps, the steps actually followed, and a screenshot carousel.
Run history
Section titled “Run history”Every run is kept, so you can compare pass rates over time and revisit the report for any past run. Runs also record their source — whether they were started manually or triggered by an automation — so you can tell apart on-demand checks from automated ones.
Triggering runs from automations
Section titled “Triggering runs from automations”QA Runs don’t have to be started by hand. They can be triggered automatically — for example, from a GitHub pull request, a Slack command, or a scheduled automation — using Connectors.