Test settings

Every test has a settings page, reachable from the test itself or from the Tests list. It is organised into tabs, and almost everything that governs how a test behaves outside the recorder lives there.

1234567

1. 1General: name, description, and target URL.
2. 2Notifications and integrations, configured per test.
3. 3Webhooks: the inbound trigger URL and outbound endpoints.
4. 4Schedule: turn recurring runs on and pick an interval.
5. 5Sharing: generate or revoke an import URL.
6. 6On a mobile test this field is a launch URL instead.
7. 7The email inbox toggle, which a wait-for-email step needs.

The tabs

• General: name, description, and target URL. On a mobile test the target URL is replaced by an optional launch URL, a deep link into your own app. Renaming is safe: history and schedules follow the test, not the name.
• App build: mobile tests only. Swap in a new release, change the device, OS version, and orientation, read the bundle identifier and version the device cloud found in the build, and retry a publish that failed.
• Notifications & Integrations: per-integration notify-on-success and notify-on-failure switches, the issue tracker this test files to, and its email report schedule.
• Webhooks: the inbound trigger URL, and outbound endpoints notified when a run finishes.
• Schedule: turn scheduling on, choose an interval and timezone, and fire an off-schedule run.
• Sharing: generate or revoke an import URL so somebody else can copy the test.
• Advanced: the destructive actions, including deleting the test.

Environments

The General tab has an Environments section. Tick the environments this test may run in and save. Every enabled environment then appears in the test's Run dropdown. The Schedule tab gets an environment selector with No environment, Selected, and All enabled, and it only offers the environments enabled here.

Variables and AI settings

Test-level variables are edited from the recorder rather than settings, because you usually want them in front of you while writing the steps that consume them. The same is true of the AI variable settings, which control whether the AI is allowed to fill values into steps it generates.