Concepts

The core objects you’ll see across the app: properties, pages, runs, issues, and flows.

Organization

Your workspace. Everything (properties, issues, runs) is scoped to an organization.

The app/site you’re testing. A property typically maps to a domain or environment (production, staging).

Saved login information that allows Canary to access authenticated areas of your app.

A crawl discovers pages and builds a map of what Canary can reach.

Discovered URLs (grouped into canonical pages) with observed history and QA status.

Automated QA executions. Runs generate artifacts (screenshots, traces) and can open/close issues.

Problems detected by Canary (e.g., broken UI, auth failures, regressions). Issues are deduped and tracked over time.

Repeatable user journeys you define (e.g., “checkout”, “invite teammate”). Flows can be executed in runs.

A test suite is a set of flows run together. A smoke suite is the small “must-pass” set you run on every release to catch breakages quickly.

Product requirements (often imported from Jira) that issues and flows can be associated with.

Uploaded artifacts (images/PDFs) used as evidence or training/context for QA and investigations.

Captured API requests/responses observed during QA for debugging and understanding app behavior.