PEOPLES CLINIC QA SUITE

Watch a check fail and keep its evidence.

Scheduled checks look for problems in selected browser and API journeys. Saved screenshots and run history help a person investigate a failure.

What you are watching The conveyor item is a test run. The camera is a check, the tray holds evidence, and the flag shows whether an email is sent.

Camera shutter: selected behaviour is inspectedRecord tray: evidence available for investigationIllustrative example. No clinic tests run and no patient information is loaded. A pass does not prove clinical accuracy or availability.

Choose an example

Move through the example

Example timeline

Selected check: in progress.

Notification not reached.

How this relates to the QA suite

The item moves through a check. When it fails, the saved record represents screenshots and run history that a person can inspect.

Examples, email rules and source

Passing: a selected assertion passes, not every behaviour. Failing: available screenshots and history support investigation. Cooldown: the illustrated smoke email is suppressed while its failed result remains visible. Paused: a dashboard monitor setting is shown; GitHub scheduling is not assumed disabled.

Smoke email policy only: failure, UTC hour from 04:00 inclusive to 16:00 exclusive, and more than 3600 seconds since an existing notification timestamp. The illustration uses fixed fictional examples, not your account state.