Skip to main content
A pack is the workbook you used to duplicate for every similar client: “checkout regression,” “auth smoke.” Catalog visibility: platform | organization | private.

​
Platform packs

Seeded, real names only: Web Application Essentials, E-commerce Checkout, Authentication & Account, Mobile Application Essentials, API UAT Essentials, Forms & Validation, Role-Based Access Control, File Uploads, Search & Filtering, Product Catalog, SaaS Account Administration, SaaS Billing, Accessibility & Responsive, Regression Essentials, Pre-Production Smoke. When to use which.

​
Install

Use This Pack / Install into project. Select all, uncheck suites/tests. Skip existing vs Create anyway. Then it’s project content. Edit it. Run it.

​
Create

New pack (manual builder), Import JSON (plan-gated), Generate with AI (plan-gated). Versioning exists. Catalog update_available is not computed: packs do not auto-update projects. No save-from-project. Honest create guide. You do not have to use packs. Do I have to?

Install

Checkboxes and skip existing.

Pre-Production Smoke

Go/no-go before launch.