Skip to main content

​
Overview: Using groups and flows

Groups and flows organize your testing environment. Groups are the top-level feature areas (for example, Authentication, Checkout, or Billing). Flows break each group into specific user journeys or scenarios. Each flow contains the tests that run those steps. Use groups to keep your environment easy to navigate—for both your team and the AI—so coverage planning and flow management stay organized. Use flows to plan how you’ll test a feature before writing code. You can generate a starting plan with AI or create flows manually for more control. The Flows tab is where you create and manage flows for the selected environment. By default, the list shows All Flows.

​
How to create, edit & delete groups

​
To create a new group:

1
Open the Flows tab, then click the icon to the right of the workspace name.
Use clear, descriptive names that reflect your app’s feature areas—this helps both you and AI keep plans organized.

​
To rename or delete a group:

1
Hover over a group row, click the icon to open the context menu.

​
How to create, edit & delete flows

To add a flow, you must first [add a group](/qawolf/Getting-familiar-with-flows-and-groups-29c5b2a994fb80b292d7cf32e6dfd37d#to- create-a-new-group).

​
To create a new flow

1
On the Flows tab, go to the Flows list.
2
Hover over the group where you want to add a flow.
3
Click the icon to the right of the group name.
4
Type the new flow’s name in the text field that appears.
5
Press Enter to add the flow to that group.
Use clear, descriptive names that reflect your app’s feature areas—this helps both you and AI keep plans organized.

​
To rename a flow:

1
Hover over the flow in question, then click the icon to open the context menu.

​
To delete a flow:

1
On the Flows tab, in the Flows list, hover over the space next to a flow’s status icon ( or ).
2
Click the icon so that it shows the icon.
3
Click the icon below the list.

​
To review and publish changes:

When you add, edit, or delete a group, or edit or delete a flow, you must review and publish your changes.
1
When adding groups, or editing groups and flows, the icon will appear next to all affected items in the Flows list on the Flows tab.
2
When deleting flows or groups, the name will be struck through, and red icons appear on the right to indicate they’re marked for deletion.
3
Click Review, then Publish changes to confirm the update.
You may need to share information about a specific flow for troubleshooting or reporting.

​
To share flow information:

1
Select Copy name as link or Copy URL to copy a link to the flow to your clipboard so you can paste it where the other person can use it.
2
Select Copy name to copy a link to the flow to your clipboard so you can paste it where the other person can use it.
3
Select Copy ID to copy the flow’s system identifier to your clipboard, then paste it where the other person can use it. This is useful for troubleshooting.

​
How to search and filter flows

​
To search for flows by name:

1
Click the icon in the Flows list to search Group and Flow names.

​
To filter flows by status or tag:

1
Click the icon to filter by status and tags.

​
How to edit flow settings

​
To access flow settings:

1
Selecting a flow from the Flows list while in No-code Mode.

​
To add or remove tags from a flow:

1
Hover over the tag names under Tags.
2
Click the icon. This opens a drawer where you can also create new tags.

​
To set the Readiness status of a flow:

1
Hover over the status under Readiness.
2
Click the icon.
3
Select either Draft or Active status.
Only flows in Active status can be executed in scheduled runs.

​
To move a flow to a different group:

1
Hover over the group name under Group.
2
Click the icon.
3
Select either group you want to move the flow to.

​
To change the browser or device a flow uses to execute:

1
Hover over the browser name under Runs on.
2
Click the icon. A modal appears.
3
Select the App type and configure the relevant settings.
Use the Other app type lets you run a test against a non-UI target, such as testing APIs or coordinating state for Hopper flows.
Last modified on March 2, 2026