> ## 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.

# Choose a setup method

> Pick a pack, import a file, write tests by hand, import from a codebase, or use the guided wizard.

You already have tests somewhere: a sheet, last year's checklist, or in your head. Pick the shortest path into the project. You can mix later (install a pack, then import extras).

<Tabs>
  <Tab title="Pack">
    Open **Test Suite Packs**. Pick a seeded pack that matches the job (checkout, auth, smoke, API, and so on). **Use This Pack** / **Install into project**. Select all, then uncheck suites or tests you don't need. **Skip existing** vs **Create anyway** if names collide.

    After install, content is normal project suites and cases. Edit, delete, run. Packs do not auto-update into the project even if the catalog shows a version. There is no "save this project as a pack" from the project.

    Best when: you don't have a client sheet, or you want a starting checklist in minutes.

    [Which pack](/packs/which-pack), [Install](/packs/install)
  </Tab>

  <Tab title="Import">
    **Import tests** on the project. Two related flows exist:

    * **Smart Matrix Import:** Excel/CSV in a matrix layout.
    * **Unified Smart Import:** Excel, CSV, Word, PDF, mixed. Review, then apply. AI is optional (`smart_import_ai`); if it's off or fails, import still tries a deterministic fallback.

    Best when: the client already sent the UAT spreadsheet.

    [Bring existing tests](/imports/bring-existing)
  </Tab>

  <Tab title="Manual">
    **Test Suites** to **Create suite**. Then **Add First Case**. Nested `parent_suite_id` exists in the database, but creating from the list always makes a top-level suite (`parent_suite_id` null). Don't plan a deep folder tree in the UI.

    Best when: a few tests, one happy path, you want to start executing today.

    [First test](/start-here/first-test)
  </Tab>

  <Tab title="Codebase">
    **From my codebase**: copy the prompt, have your coding agent write `simpleuat-project-setup.json`, upload, preview, apply. **Import history** keeps past uploads. This path is paid on **Pro+**.

    Best when: the repo is the source of truth and you don't want to invent suites by hand.

    [Codebase setup](/setup/codebase)
  </Tab>

  <Tab title="Wizard">
    **Guided wizard** / **Start guided setup**. Eight questions (what you're testing, name, kind of change, where you'll test, how much structure, who tests, cadence, optional product description). Then it creates environments, suites, starter tests, first cycle, optional assignments. Everything is editable after.

    Best when: new project, no sheet, no strong pack pick yet.

    [Getting started wizard](/setup/getting-started)
  </Tab>
</Tabs>

<Columns cols={2}>
  <Card title="Write one case" icon="pen-line" href="/start-here/first-test">
    Fields that actually exist.
  </Card>

  <Card title="Playbook: new client" icon="briefcase" href="/playbook/new-client">
    How this choice fits a paid engagement.
  </Card>
</Columns>