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

# New testing job

> Ten steps for an Acme checkout UAT job: project, pack, run, findings, client connection, and delivery.

Use this when a client asks you to UAT checkout before they go live. These steps move that work into SimpleUAT so you do not maintain a spreadsheet and a recap by hand.

<Steps>
  <Step title="Create the client project">
    **Projects** to **Create Client Project** (or **Create First Project** if this is your first). Type **web**. Name it so invoices and Slack match: "Acme checkout UAT."
  </Step>

  <Step title="Pick a setup">
    Empty project shows: **Guided wizard**, **Import tests**, **From my codebase**, **Import history**, **Manual**. For checkout, skip the wizard: go to **Test Suite Packs** and install **E-commerce Checkout**. Uncheck suites you don't need (no PayPal? uncheck it). [Choose setup](/start-here/choose-setup).
  </Step>

  <Step title="Add staging">
    **Environments** to **Add First Environment**. Name, base URL, description. Default is the one you'll open all week.
  </Step>

  <Step title="Personas and data">
    Create **Guest** and **Returning customer** if the pack cases mention them. Put real test cards and promo codes in case preconditions (the same notes you used to keep in the sheet header).
  </Step>

  <Step title="Trim the suite">
    After install, it's your project. Delete or deprecate cases that don't exist in Acme. Edit titles so they sound like Acme, not generic pack language. [Create and organize](/tests/create-and-organize).
  </Step>

  <Step title="Open a cycle">
    **Test Cycles** to **Create First Cycle**. Title, dates, staging, select the checkout `case_ids`. Move **draft** to **active** when testing starts.
  </Step>

  <Step title="Run it">
    **Start a run**. You need an active tester (that's you, assigned). Work cases. **Pass / Fail / Blocked / N/A** on steps. Attach evidence when a result needs proof. [Running](/running/runs).
  </Step>

  <Step title="Log findings as you go">
    Fail a step to file issue when prompted, or **Log a finding** anytime (exploratory counts). Severity, priority, comments, evidence. Optional Jira **link**: it does not sync. [Findings](/findings/overview).
  </Step>

  <Step title="Connect the client">
    **Deliver UAT** / **Clients**: Delivery ID `SUA-XXXX-XXXX`, connection code, or **Send invitation**. Status stays **PENDING** until they approve. Connect them before you build the snapshot. [Connect](/delivery/connect).
  </Step>

  <Step title="Snapshot and deliver">
    **Build delivery snapshot** (immutable copy of this work). **Deliver UAT**. They see inbox + review: accept, accept with known issues, not ready, request retest. Export PDF/Excel/etc. if your plan includes it: that's the report, generated from the run. [Delivering](/playbook/delivering).
  </Step>
</Steps>

Next job: repeat this flow. If you test checkout often, keep a private or organization pack. Build that pack in the pack builder. You cannot save a project as a pack. [Reuse](/playbook/reuse).

<Columns cols={2}>
  <Card title="New client checklist" icon="user-plus" href="/playbook/new-client">
    Same flow, less Acme-specific.
  </Card>

  <Card title="What the client sees" icon="inbox" href="/delivery/what-client-sees">
    Inbox, review, findings, exports, retest.
  </Card>
</Columns>