Skip to content
Marketrix Docs

QA Flows Overview

QA Flows let you generate Journeys from natural-language requirements and run them against your application in a real browser. Instead of writing tests by hand, describe what you want to test and let Marketrix build executable Journeys for you.

How QA Flows work

Section titled “How QA Flows work”
  1. Create a QA Flow — Describe what you want tested and pick the personas it should be tailored for. Marketrix turns that into a QA Flow containing structured Journeys and the personas that drive them; it’s saved in one step, with no separate draft state.
  2. Edit the Journeys — Open the flow’s detail page to refine its Journeys and personas at any time.
  3. Run the flow — Execute the Journeys against your application in a real browser. Each execution is called a QA Run.
  4. Review results — See which Journeys passed, which failed, and which were indecisive, and why. Every Journey run is evaluated automatically and given an outcome.

Key features

Section titled “Key features”
  • AI-powered generation — Describe what to test in plain language; Marketrix writes the Journeys.
  • Real-browser execution — Journeys run in Chrome across selectable viewports (desktop, tablet, mobile) — no scripting required.
  • Automatic evaluation — Every Journey run is judged against its expected outcome and given a passed / failed / indecisive outcome.
  • Run history & reports — Track every QA Run with passed/failed/indecisive counts and a per-Journey report that includes screenshots and the steps Marketrix actually followed.
  • Multiple viewports — Run the same flow across desktop, tablet, and mobile viewports and compare results side by side.
  • Editable flows — Open a QA Flow’s detail page to edit its Journeys and personas at any time.

Next steps

Section titled “Next steps”
Creating QA FlowsGenerate Journeys from a description of what to test.
QA RunsRun flows, read outcomes, and download reports.
SimulationsThe browser automation QA Runs are built on.