> ## Documentation Index
> Fetch the complete documentation index at: https://docs.simpleuat.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Suites vs packs

> A suite is a group of tests in a project. A pack is a reusable catalog of suites you install, then own.

## Suite

A **test suite** is a group of tests **in this project**. Spreadsheet tab. **Create suite** on **Test Suites**. After you run, results hang off runs, not off the suite definition.

## Pack

A **Test Suite Pack** is a reusable checklist in the catalog (platform-seeded, or your org/private packs). **Use This Pack** copies selected suites/tests into the project. Then they are ordinary suites and cases.

Visibility: `platform` | `organization` | `private`.

Platform packs are seeded (Web Application Essentials, E-commerce Checkout, and so on). [List](/packs/which-pack).

## Don't mix the jobs

* Tests for Acme this week to **suite** (in the project)
* The same checkout checklist next month for another shop to **pack**, then install
* Last Tuesday's pass/fail to **run**

Packs are not automatically updated in the project. Nested suites exist in schema (`parent_suite_id`) but the suites list always creates parent = null.

<Columns cols={2}>
  <Card title="What is a pack" icon="package" href="/packs/what-is-a-pack">
    Visibility, install, no save-from-project.
  </Card>

  <Card title="What is a suite" icon="list" href="/tests/what-is-a-suite">
    Create, group cases.
  </Card>
</Columns>