Skip to main content
A pack is a reusable checklist: checkout v4, “every SaaS admin I test,” your personal smoke. In spreadsheet land you duplicated a workbook. Here you install a pack into a project, then the copies are normal suites and cases.

​
What you can do

  • New pack: manual builder. Visibility: platform | organization | private. You will not be publishing platform packs (those are seeded). Yours are organization or private.
  • Import JSON: plan-gated.
  • Generate with AI: plan-gated.
Versioning exists on packs. The catalog field update_available is not actually computed. Do not expect the project to offer “apply pack update.” After install, maintain the project content (or install again with Create anyway if you want duplicates).

​
What you cannot do

There is no save-from-project. If the UI or a plan blurb implies you can snapshot a live project back into a pack, that feature is not there. Copy tests into the pack builder, import JSON, or generate.

​
Practical workflow

  1. After two similar jobs, open Test Suite Packs to New pack.
  2. Recreate the suites you actually ran, not the unused pack cases you deleted last time.
  3. Keep it private until your org should share it.
  4. Next client: Use This Pack, uncheck noise, install.
Create packs, Do I have to use packs?

Install into a project

Select all, skip existing, create anyway.

Reuse habits

After install, it’s just project tests.