Targets and triggers

Targets define coverage. Triggers define when that coverage runs.

Targets

Choose one target type:

• All: Run every test case in the project.
• Priority: Run test cases that match a selected priority.
• Test cases: Run an explicit set of selected cases.
• Folder: Run test cases in a selected folder.

Use explicit test case targets for small release gates. Use priority or folder targets when coverage ownership maps cleanly to risk or product area.

Triggers

Triggers are optional. A plan can be run manually with no trigger.

Use Schedule for recurring checks. Scheduled plans require at least one weekday, one run time, and a timezone.

Use Webhook for deployment-driven checks. Webhook plans require a generated webhook URL.

Operational guidance

Keep automated plans small enough that failures are reviewed. Large plans are useful only when the team has the ownership and process to act on every failed result.