Creating QA Flows
To create a QA Flow, open the QA Flows page for your application and start a New QA Flow.
Describe what to test
Section titled “Describe what to test”Describe the feature or area you want tested in plain language — for example, “Sign-up and onboarding for a new free-tier user”. The more specific you are, the more focused the generated Journeys will be.
Under Who should the tests be tailored for?, pick the personas that should drive the QA Flow, or pick none for the generic lane. The personas you pick steer what Marketrix emphasises while generating. They become the drivers of every Journey in the QA Flow, each with its own prefilled values for the Journey’s Inputs. Personas come from Personas.
Generate Journeys
Section titled “Generate Journeys”When you start generation, Marketrix reads your input and produces structured Journeys. Each Journey has:
- Objective — The feature-usage task the driver is meant to accomplish.
- Expectation — The outcome that counts as success.
- Steps — The sequence of actions Marketrix expects the persona to take.
- Inputs — Values the Journey needs at run time (for example, a search term or a sign-up email) that you can fill in or let Marketrix prefill.
Save and edit
Section titled “Save and edit”Generating saves the QA Flow — there’s no separate draft or activate/deactivate state. Open the QA Flow’s detail page to edit it at any time:
- Edit a Journey directly — change its Objective, Expectation, Steps, or Inputs.
- Reorder Journeys — Journeys execute in the order they appear in the QA Flow.
- Adjust drivers — add or remove the personas that drive a Journey. Each driver is a column of field values on that Journey, so you can give two personas different sign-up emails for the same steps.