Tests and groups

A saved test captures a QA scenario you want to run again: its target, its description, and the identity it runs as. A group holds a set of tests and the identity they share. You run a single test, or run a whole group at once.

Saved tests

A test carries:

• A title and a description of the flow to walk.
• A target: a static URL, a deployment URL tied to a bound GitHub repo, or a mobile app.
• A trigger: manual, or a GitHub deployment that starts the run when a deployment succeeds.
• An optional identity override, so this test can run as a different test user than its group.

You create and manage tests from the Matcha QA screen. Every manual run there creates a saved test, so a run you start once is a run you can start again. There is no throwaway path in the desktop, though an ad-hoc run an agent starts can skip saving.

You can also ask an agent to list your saved tests or delete one. See MCP and local API.

Groups

A group names a set of tests and sets the identity they share. A group carries a name, an optional description, and the test user its runs sign in as. The QA home lists these under the Run Groups tab, next to Runs.

An agent can create and list groups for you too.

Run-as inheritance

A test inherits its group's identity by default. When a test's identity is set to inherit, a run of that test signs in as the group's test user. When a test overrides the identity, that test runs as its own test user instead, and the rest of the group is unaffected.

This is why you set the account once on the group and let its tests inherit. Override only the test that genuinely needs a different account.

A one-off run started under a group, without naming an identity of its own, inherits the group's identity too.

Run all

Run all runs every test in a group. Each test signs in as its own identity: the group's for inheriting tests, and its own test user for any test that overrides. You can ask an agent to trigger this as well.

Group runs also back GitHub PR testing: a qualifying pull request fans out runs for each configured group, each under its own group identity. See PR reporting.

Related

• Test users: the identities a group and its tests run as.
• Runs and results: reading the runs a test or group produces.