Skip to main content
Start from the job, not from collecting packs. After you install one, uncheck or delete what you will not run.
Core UAT coverage for a typical web application release. Use when you are testing a normal website or web app and you do not already have a client script.
Cart through confirmation, including payment failures. Use when checkout is the job.
Registration, login, recovery, and profile. Use when the release is mostly accounts and sign-in.
Install, journeys, permissions, offline, and notifications. Use when the project type is iOS or Android.
Smoke, auth, validation, and error coverage for APIs. Use when the client gave you an API to exercise, not a UI.
Required fields, formatting, and submit behavior. Use when the release is a form-heavy flow.
Authorized, unauthorized, and privilege-change checks. Use when Admin and Customer should not see the same things.
Allowed files, size limits, and failure handling. Use when uploads are in scope.
Keyword search, filters, sort, and pagination. Use when search or list views changed.
Browse, variants, inventory, and pricing. Use when catalog or product detail is in scope.
Users, invitations, roles, and org settings. Use when you are testing the admin side of a SaaS product.
Trial, upgrade, cancellation, and entitlements. Use when plans or billing changed.
Responsive layout and accessibility basics. Use when they asked you to check layout and keyboard/basic a11y. This is UAT coverage, not a full audit product.
A short repeatable regression set. Use when it is a small release and you need a basic “did we break the usual paths?” pass.
Go/no-go checks before production. Use right before launch. What is in this pack?
You can install more than one pack. On the second install, use Skip existing if names already match.

Install a pack

Use This Pack, uncheck suites, skip existing.

Do I have to use packs?

No. Import or create tests instead.