Run guided Journey QA
Journey QA guides a human tester through Openhood's documented workflows while recording exactly what was checked. It is for release validation, not for working in a customer organisation, and it never performs product actions for you.
Who can use Journey QA
Journey QA is available to two platform roles after normal Openhood sign-in:
- Platform Tester can open the Journey QA console, enter an available testing context, switch among the listed QA personas, run journeys, inspect QA evidence, and explicitly report and link a bug.
- Platform Admin can do the same testing work and can also manage tester access through the existing platform user lifecycle and revoke an active testing context.
Synthetic QA data only
Hosted Journey QA works only inside the dedicated synthetic QA workspace enabled for that environment. It cannot open a customer organisation, accept an arbitrary user or organisation, or grant a Platform Tester access to platform administration or the data console. Demo, sandbox, customer, and uncommissioned environments stay unavailable.
Local development keeps the existing localhost-only dev login and role switcher. A hosted tester always uses normal platform authentication before Openhood accepts a testing context.
Start or resume testing
- Sign in with your normal Platform Tester or Platform Admin account.
- Open Journey QA from the platform navigation. The console shows the current environment and any testing context that is still valid.
- If testing is not active, choose one of the personas offered in the selector and choose Start testing. The list is fixed by the synthetic workspace; you cannot enter a user ID or select someone outside it.
- Check the displayed environment, build, and expiry before starting a run.
If you close the browser and return while the same normal session and testing context are still valid, the console resumes that context. It does not create a new identity or extend the context lifetime.
You can choose Switch persona when no task is unresolved. Finish the task or explicitly abandon it first. To stop, return to the console and choose End testing after resolving the active task.
Contexts are short-lived and release-bound
A hosted context expires, can be revoked, and becomes invalid when the deployed build changes. Openhood closes unfinished evidence without recording a pass or skip. If testing is still enabled, start a fresh context against the current build.
Run a journey
- Enter the synthetic workshop through the active persona.
- Open the account menu and choose Run journey.
- Choose a journey from the role-compatible list. The footer shows its ID, current step, title, and expected result.
- Perform the product action yourself. Locate current step can highlight a registered target, but it never clicks, navigates, submits, or decides the result. If no target is available, follow the manual locate text.
- Choose OK when the expected result is true. Choose X when it is not.
Passing the final required step completes that run. When the task contains another journey compatible with the active persona, the runner moves to it automatically.
Record and resolve a failure
Choosing X opens What happened?. Record one concise observation and choose Pause. The run stays on that failed step until you make one explicit decision:
- Retry starts a new run. It does not rewrite the failed run.
- Skip records that you deliberately moved past the failed step.
- Abandon ends the unresolved task without recording a pass.
Nothing silently passes or skips. A completed run and its step evidence stay append-only.
Choose Report bug and link only when the failure should become a bug report. Complete the normal bug report flow, including any evidence you deliberately attach. Journey QA then links that report to the run. A failed step never creates a bug automatically.
Review exact-release evidence
Open Journey QA and use the run filters for task, journey, tester, role, persona, status, environment, or build. Select a run to see:
- the accountable platform tester and the effective workshop persona;
- the environment, context state, start and completion times;
- the full journey revision and build identifier, available through the copy actions;
- every recorded step, observation, route and viewport evidence, failure decision, and linked bug.
A Platform Tester can inspect the QA evidence and linked bug identifier. A Platform Admin can also open the linked bug from the run detail and revoke an active context with a recorded reason.
Human Journey QA evidence confirms what a person checked against one exact release. It supports release review but does not replace deterministic end-to-end evidence or change deployment and promotion rules.