QA Runs
A QA Run is a single execution of a QA Flow. Each run launches one simulation for every selected Persona (or Generic) × Journey × viewport combination and records an outcome of Passed, Failed, or Indecisive for each one. Journeys in the same Persona/Generic × viewport lane run serially and carry the browser session forward, while distinct lanes can run independently.
Starting a run
Section titled “Starting a run”From a QA Flow, choose Run and configure the run:
- Viewports — Choose one or more of desktop, tablet, and mobile. Runs are Chrome-only; each selected viewport multiplies the selected Persona/Generic × Journey cells so you can compare every Journey 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”The run itself moves through running → finalizing → completed (or failed / stopped). A run that reaches your Billing Cycle’s credit allowance goes Paused instead of failing; Resume run dispatches only the persona/viewport lanes that never started. See Billing and Credits. Each Journey stays In progress until its outcome settles, then reads as one of:
| Outcome | Meaning |
|---|---|
| Passed | The persona reached the expected outcome and the followed steps aligned with the plan. |
| Failed | The expected outcome was not reached. |
| Indecisive | Marketrix could not conclusively pass or fail the Journey; you resolve it, and the resolution is remembered per application. |
The run summary shows live counts of Passed, Failed, and Indecisive Journeys. You can Stop run at any time — the run ends immediately and the outcomes collected so far are kept.
Reading results
Section titled “Reading results”Every Journey is evaluated automatically against its expected outcome. The outcome explains:
- Whether the outcome was reached.
- Whether the followed steps aligned with the planned steps.
- A short, human-readable reason for the outcome.
Each Journey also has a walkthrough: the steps Marketrix actually followed and screenshots captured along the way. An Indecisive outcome 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 outcome, planned steps, the steps actually followed, and a screenshot carousel.
Run history
Section titled “Run history”Every run is kept, so you can revisit the results and the report for any past run. The run history table lists each run with when it ran, the viewports it covered, its simulation count (selected Persona/Generic × Journey cells multiplied by selected viewports), its coverage (landed outcomes out of the expected Persona/Generic × Journey × viewport cells), and its status.
Triggering runs from workflows
Section titled “Triggering runs from workflows”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 timer — using Connectors.