Skip to main content
Imagine Acme hired you to UAT their new checkout on staging. You would normally keep a sheet, a test account, screenshots, and a recap email. Here is the same job in SimpleUAT.
1

Project

Create a project. Type: web. Name it something you and Acme both recognize, like “Acme checkout, Sep release.”
2

Environment

Add Staging with https://staging.acme.example as the base URL. Mark it default if that is where you will test this week.
3

Suite and tests

Install E-commerce Checkout from Test Suite Packs, or create a suite named “Checkout” and add a case: “Guest can place an order with a valid card.” After install, pack content is normal project content. Edit freely.
4

Persona (optional but useful)

Create Guest shopper under Personas. That is the “login as…” row you used to put in the sheet header.
5

Cycle

Create a cycle: “Checkout UAT, week of Sep 8.” Attach staging, pick the checkout cases, set dates. Status starts as draft; make it active when you’re ready.
6

Run

Start a run. Work the case. On each step use Pass, Fail, Blocked, or N/A. Attach a PNG of the confirmation page when it works.
7

Finding

Payment declined with no message? Fail the step, file the issue when prompted, or Log a finding on Findings. Severity major, status open. That is the bug email you used to write.
8

Delivery

Connect Acme (Delivery ID, code, or invitation). Wait until the connection is ACTIVE. Build delivery snapshot, then Deliver UAT. They review in their inbox: accept, accept with known issues, not ready, or request retest.
You still tested. The platform organized the checklist, captured the run, stored the bug with evidence, and produced the client packet. You do not rebuild the spreadsheet to send results.

Full 10-step job

Same Acme story with more decision points.

Create the project

Names, types, and empty-project setup options.