Skip to content

QA journey group tools

A QA journey group bundles a project’s QA journeys under one name so they can be run together. It holds QA journeys only; it is not a journey group.

See Manage QA journey groups for dashboard management, full membership replacement, deletion, CLI selection, and scheduling. Schedule through the dashboard, GraphQL, or set_qa_journey_group_schedule with input: { groupId, schedule }. The group id supplies its project; omit or clear schedule for manual runs only.

A group’s id is qag_…. Each qa_journey_group_id argument also accepts the group’s base64 QaJourneyGroup global id.

List a project’s QA journey groups, each with its member QA journeys and journey count.

NameTypeRequired
project_idstringyes

Returns: the project’s groups, each with its id, name, description, journeyCount and journeys (id and name). Not paginated. Groups are oldest first, with group ID breaking ties; members are ordered by journey ID.

Create a QA journey group for a project. The group is created empty; add QA journeys with set_qa_journey_group_members.

NameTypeRequired
project_idstringyes
namestringyes
descriptionstringno

Returns: the created group.

Update a QA journey group’s name or description.

NameTypeRequired
qa_journey_group_idstringyes
namestringno
descriptionstringno

Does not change membership.

Returns: the updated group.

Delete a QA journey group. The member QA journeys themselves are not deleted, only the grouping. Existing cloud requests and work already claimed by the scheduler continue.

NameTypeRequired
qa_journey_group_idstringyes

Returns: the confirmation line Deleted QA journey group: <id>.

Set the full member list of a QA journey group.

NameTypeRequiredNotes
qa_journey_group_idstringyes
qa_journey_idsstring[]yesThe complete desired set of members.

REPLACE semantics. The list you send becomes the membership; it is not a delta. An empty list clears membership. Repeated IDs become one member. Foreign-project and accessibility journeys are refused without changing the existing members.

Returns: the group with its updated journey count and members.

Run every QA journey in a group on the cloud runner as one cloud run request per 5 journeys.

NameTypeRequiredNotes
qa_journey_group_idstringyes
build_targetstringAndroid onlyThe uploaded build as <release>/<dist>. Required on an Android project, refused on a web project.

The run is cut into cloud run requests of up to 5 journeys, the most one VM runs inside its time bound, so a group of seven runs as two requests on two VMs.

Returns: one line per request, in the group’s order, in one of three forms:

  • Request N: started. Cloud run request ID: <id> (VM: <name>).
  • Request N: queued. Cloud run request ID: <id> (#<position> in line); it starts on its own when a cloud run slot on the plan frees. Every slot on the plan was busy, so the request waits in line.
  • Request N: not started. with why: the plan refused it, the project has no site to start on, or the reason the request could not start.

A later request that did not start stands beside an earlier one that did. Follow the payload’s journeyAudit.id with get_journey_audit, waiting for its pollAfterMs until done. Auditer returns each member’s outcome and the batch qaVerdict.

An unknown group, or a group with no journeys, is an error block, and so is an Android project’s group run with no build_target.