Manage QA journey groups
Use a QA journey group to keep a named set of one project’s QA journeys together. Any member of the project’s organization can list, create, edit, delete, replace members, and change its schedule. These groups hold QA journeys only, separate from accessibility journey groups.
Create a group
Section titled “Create a group”Open your project’s QA journeys, then its Groups page. Create a group with a nonblank name, an optional description, and the QA journeys you want to include. Names are trimmed. Different groups may have the same name, so use the group ID when a name is ambiguous.
With MCP, call create_qa_journey_group with project_id, name, and optionally
description. It creates an empty group, with an empty description when omitted.
Then call set_qa_journey_group_members with its ID and the desired QA journey IDs.
See the MCP tool reference
for arguments and responses.
Change the name or members
Section titled “Change the name or members”Use Edit on the Groups page to change the name, description, or selected journeys.
With MCP, update_qa_journey_group changes only the supplied name or description
and keeps membership intact.
Before calling set_qa_journey_group_members, send the complete set you want to
keep. For example, replacing [cart, pay] with [cart] removes pay from the
group. Send [] to clear it. Repeated IDs become one member. A journey from
another project, or an accessibility journey, is refused without changing the
existing members.
Call list_qa_journey_groups to check the result. It returns all project groups,
oldest first, with ties ordered by group ID. Members are ordered by journey ID.
Group IDs start with qag_; MCP group ID arguments also accept base64
QaJourneyGroup global IDs.
There is no advertised per-group member cap. Five is the maximum number of journeys in one cloud request, not a group size limit.
Set a schedule
Section titled “Set a schedule”Use the group’s schedule control on the dashboard. Scheduling is also available
through GraphQL’s setQaJourneyGroupSchedule or MCP’s
set_qa_journey_group_schedule. Send input: { groupId, schedule }; the group id
supplies its project.
Choose Off for manual runs only, daily for a rolling day, weekly for seven days,
or Every 30 days for 30 rolling days. The wire value for Every 30 days is
monthly; it does not mean a calendar month. Each group has its own schedule,
separate from the project’s accessibility audit schedule.
Schedules are offered where the project has cloud QA capability. Web and Android have separate enablement; iOS cloud QA is unsupported. Off can still clear an existing schedule. Empty groups are not claimed for scheduled work.
A nonempty scheduled group with no previous attempt becomes eligible at the next hourly scheduler tick. For later attempts, the interval starts when the scheduler claims the group. Changing cadence or switching Off and back on keeps that timestamp, so re-enabling does not necessarily start a run immediately.
Read the timestamp as Last scheduled attempt. A missing timestamp means no scheduled attempt yet.
For scheduled Android work, the scheduler selects a production build, or the newest uploaded build if none is marked production. A missing build can cause the attempt to be refused. Refused or failed dispatches still consume the interval; the scheduler does not immediately retry them. Historical iOS schedules are skipped and also consume their interval. Execution time and completion are not guaranteed by a claim.
Select a group from the CLI
Section titled “Select a group from the CLI”After selecting the project with b8e project, run by group ID or exact name:
b8e qa audit --group qag_123b8e qa audit --group "Checkout"With --group alone, the CLI selects the project’s only group or prompts when
there are several and the terminal can ask. Duplicate names require an ID. An
empty group cannot run. Do not combine --group with --journeys.
For CI, select a project and give a resolvable group. CI cannot answer a prompt:
b8e qa audit --group qag_123 --ciLocal execution selects every group member. Add --cloud to use cloud runners;
a group of seven journeys becomes two requests of at most five, each on its own
VM. Android cloud runs also require --build-target <release>/<dist>; web runs
refuse that option. See the CLI reference
for run options.
Delete the grouping
Section titled “Delete the grouping”Use Delete on the Groups page, or call delete_qa_journey_group with the group
ID. Deletion removes the group and memberships, keeping the QA journeys.
It does not cancel existing cloud requests or work already claimed by the
scheduler. That claimed work uses the member snapshot it already received.
Deleting an individual QA journey removes its memberships. Deleting the project removes its groups.