# SimpleUAT Help Center

> Freelancer help for SimpleUAT: organize tests, reuse packs, run UAT, track findings, and deliver results without maintaining spreadsheets.

- [Testing is the part you know](https://docs.simpleuat.com/index.md): SimpleUAT organizes, reuses, runs, tracks, and delivers UAT so you don't keep spreadsheets and reports by hand.
- [Quickstart](https://docs.simpleuat.com/start-here/quickstart.md): Sign in, create a project, add tests or install a pack, run UAT, log findings, and deliver — without a spreadsheet.
- [Five minutes: Acme checkout](https://docs.simpleuat.com/start-here/five-minutes.md): Follow one checkout gig through project, suite, test, run, finding, and delivery.
- [If you live in a spreadsheet](https://docs.simpleuat.com/start-here/spreadsheets.md): Map your UAT spreadsheet to SimpleUAT suites, cases, runs, findings, and deliveries — without a giant table.
- [A testing gig, start to finish](https://docs.simpleuat.com/start-here/testing-gig.md): Ten steps for an Acme checkout UAT job: project, pack, run, findings, client connection, and delivery.
- [Create your first project](https://docs.simpleuat.com/start-here/first-project.md): A project is the testing job. Create it, pick a type, then add environments, tests, and a cycle.
- [Choose how to set up tests](https://docs.simpleuat.com/start-here/choose-setup.md): Pick a pack, import a file, write tests by hand, import from a codebase, or use the guided wizard.
- [Write your first test](https://docs.simpleuat.com/start-here/first-test.md): Create a suite and a case with the real fields: steps, expected outcome, priority, and optional persona.
- [Freelancer playbook](https://docs.simpleuat.com/playbook.md): Repeatable UAT habits: new client, packs, reuse, running, bugs, retest, updates, and delivery.
- [New client](https://docs.simpleuat.com/playbook/new-client.md): Stand up a client UAT project quickly: name it, load tests, connect delivery, then run.
- [Build your own pack](https://docs.simpleuat.com/playbook/own-pack.md): Create reusable Test Suite Packs with the manual builder, JSON import, or AI generate. You cannot save a pack from a project.
- [Reuse tests without duplicating spreadsheets](https://docs.simpleuat.com/playbook/reuse.md): Install packs into projects, edit the copies, and keep a personal pack for work you repeat.
- [Running the work](https://docs.simpleuat.com/playbook/running.md): Use cycles as the testing round and runs as execution. Mark pass, fail, blocked, and N/A as you go.
- [Bugs and findings](https://docs.simpleuat.com/playbook/bugs.md): Log findings with severity, status, evidence, and optional Jira links. Fail a step can prompt you to file an issue.
- [Retesting](https://docs.simpleuat.com/playbook/retesting.md): Retest after a fail, a finding in retest status, or a client request. Use the Retest requests queue.
- [Keep the client updated](https://docs.simpleuat.com/playbook/keeping-client-updated.md): Use connection status, delivery review, comments, and notifications instead of a weekly status spreadsheet.
- [Delivering UAT](https://docs.simpleuat.com/playbook/delivering.md): Connect the client, build an immutable snapshot, deliver, and let them accept or request retest.
- [How SimpleUAT is organized](https://docs.simpleuat.com/concepts/how-organized.md): Org → project → environments, personas, suites, cases, cycles, runs. Recipients use applications, inbox, and archive.
- [Projects vs applications (products)](https://docs.simpleuat.com/concepts/projects-products.md): A project is the testing job. Applications are the recipient UI for products. Most freelancers only need a project.
- [Suites vs packs](https://docs.simpleuat.com/concepts/suites-vs-packs.md): A suite is a group of tests in a project. A pack is a reusable catalog of suites you install, then own.
- [Cycles vs runs](https://docs.simpleuat.com/concepts/cycles-vs-runs.md): A cycle is the testing round (scope, dates, environment). A run is one execution of those cases.
- [Failed vs finding](https://docs.simpleuat.com/concepts/failed-vs-finding.md): A fail is a result on a run. A finding is the issue you file (bug/defect) with severity, status, and evidence.
- [Environments](https://docs.simpleuat.com/concepts/environments.md): An environment is the place you test: name, base URL, description, and default flag. Create it on the Environments page.
- [Personas](https://docs.simpleuat.com/concepts/personas.md): A persona is who you test as: name, description, color, role category, active flag, plus access types and login methods.
- [Snapshots](https://docs.simpleuat.com/concepts/snapshots.md): A delivery snapshot is an immutable copy of recorded UAT work. Later runs do not change what you already sent.
- [Connections](https://docs.simpleuat.com/concepts/connections.md): Connect to a client with Delivery ID SUA-XXXX-XXXX, a connection code, or an invitation. They must approve before you can deliver.
- [Pass, fail, blocked, skipped, N/A](https://docs.simpleuat.com/concepts/statuses.md): What each run result means compared to spreadsheet color-coding, including not run and not applicable.
- [Empty project setup](https://docs.simpleuat.com/setup/empty-project.md): After you create a project, choose Guided wizard, Import tests, From my codebase, Import history, or Manual.
- [Guided wizard](https://docs.simpleuat.com/setup/getting-started.md): Eight questions that create environments, suites, starter tests, a first cycle, and optional assignments. You can change everything later.
- [From my codebase](https://docs.simpleuat.com/setup/codebase.md): Prompt an agent to write simpleuat-project-setup.json, upload it, preview, and apply. Paid on Pro+.
- [Can I change setup later?](https://docs.simpleuat.com/setup/can-i-change-it.md): Yes. Wizard, packs, imports, and codebase JSON are starters. Edit suites, environments, personas, and cycles anytime.
- [What is a test suite?](https://docs.simpleuat.com/tests/what-is-a-suite.md): A suite is a group of tests in a project — the tab in your old UAT workbook. Create it from the Test Suites page.
- [What is a test case?](https://docs.simpleuat.com/tests/what-is-a-case.md): A case is one test script: title, steps, expected outcome, priority, and the other fields that actually exist.
- [Create and organize tests](https://docs.simpleuat.com/tests/create-and-organize.md): Create suites and cases, use module and tags, and deprecate tests you no longer run.
- [What is a Test Suite Pack?](https://docs.simpleuat.com/packs/what-is-a-pack.md): A pack is a reusable checklist you install into a project. After install it is normal suites and cases.
- [Which pack should I use?](https://docs.simpleuat.com/packs/which-pack.md): All 15 seeded platform Test Suite Packs and when each one fits a freelance UAT job.
- [Install a pack into a project](https://docs.simpleuat.com/packs/install.md): Use This Pack or Install into project, uncheck suites and tests you don't need, then treat the copies as normal tests.
- [Create a pack](https://docs.simpleuat.com/packs/create.md): Build a pack with New pack, Import JSON (plan-gated), or Generate with AI (plan-gated). You cannot save a pack from a project.
- [Do I have to use packs?](https://docs.simpleuat.com/packs/do-i-have-to.md): No. Packs are optional reusable checklists. You can import a spreadsheet or write suites by hand.
- [Pre-Production Smoke](https://docs.simpleuat.com/packs/pre-production-smoke.md): The Pre-Production Smoke pack is a short go/no-go set: reachable environment, login, primary save, no blocking errors.
- [Test runs](https://docs.simpleuat.com/running/runs.md): Start a run from an active cycle with an assigned tester. Record case results and complete or abort the run.
- [Pass, fail, blocked, N/A](https://docs.simpleuat.com/running/pass-fail-blocked.md): How to mark steps and cases so results match what you would have put in a spreadsheet.
- [Exploratory testing](https://docs.simpleuat.com/running/exploratory.md): Use lightweight cases, standalone Log a finding, and evidence when you are not following a heavy script.
- [Findings](https://docs.simpleuat.com/findings/overview.md): Findings are bugs/defects. Log them at /defects with severity, status, priority, comments, evidence, and optional Jira links.
- [Evidence](https://docs.simpleuat.com/findings/evidence.md): Attach PNG, JPEG, GIF, WebP, PDF, WebM, or MP4 up to 25MB on runs, steps, and findings.
- [Retest findings](https://docs.simpleuat.com/findings/retest.md): Retest after a fail, a finding in retest status, or a client retest request on /retests.
- [Jira links and GitHub issues](https://docs.simpleuat.com/findings/jira.md): Jira is links only — this does not sync with Jira. GitHub Issues can create issues from defects.
- [How delivery works](https://docs.simpleuat.com/delivery/how-it-works.md): You connect a client, freeze a snapshot of recorded work, deliver UAT, and they review in their inbox.
- [Connect a client](https://docs.simpleuat.com/delivery/connect.md): Connect with Delivery ID SUA-XXXX-XXXX, a connection code, or Send invitation. They must approve before you deliver.
- [Client doesn't have an account](https://docs.simpleuat.com/delivery/client-no-account.md): Send an invitation. They sign up, the pending connection resumes, then they can approve and receive UAT.
- [What the client sees](https://docs.simpleuat.com/delivery/what-client-sees.md): Recipients use UAT Inbox to review deliveries, findings, and exports, then accept, accept with issues, mark not ready, or request retest.
- [Build a delivery snapshot](https://docs.simpleuat.com/delivery/snapshot.md): A snapshot is an immutable copy of the UAT work you recorded. Build it, then deliver. Later runs do not rewrite it.
- [Exports and reports](https://docs.simpleuat.com/delivery/exports.md): Reports are generated from recorded runs and findings. Formats are plan-gated: PDF, HTML, Word, PowerPoint, and more.
- [Dashboard](https://docs.simpleuat.com/account/dashboard.md): The dashboard is your home for projects and deliveries. Empty states point you to create a project or deliver UAT.
- [Notifications](https://docs.simpleuat.com/account/notifications.md): Watch sidebar New pills for connection, delivery, retest, and comments so you don't keep a side status spreadsheet.
- [Plans and upgrades](https://docs.simpleuat.com/account/plans.md): Plans include Free, Solo, Pro, Agency, Client Pro, and Client Business. Upgrade at /settings/billing. This is not a pricing page.
- [Integrations](https://docs.simpleuat.com/account/integrations.md): Jira Links do not sync. GitHub Issues can create issues from defects. Slack uses incoming webhooks.
- [Organization and team](https://docs.simpleuat.com/account/organization.md): Your org holds members, billing, and the Delivery ID you share when you receive UAT. Projects live under the org.
- [Troubleshooting](https://docs.simpleuat.com/troubleshooting.md): Human questions: can't start a run, can't deliver, connection stuck, import looks wrong, feature missing, still stuck.
- [Can't start a run](https://docs.simpleuat.com/troubleshooting/cant-start.md): You need an active tester, an environment, cases on a cycle, and a cycle that's actually ready.
- [Can't deliver UAT](https://docs.simpleuat.com/troubleshooting/cant-deliver.md): Delivery needs an approved connection, a title, a project, and a plan that allows it.
- [Connection problems](https://docs.simpleuat.com/troubleshooting/connection.md): Fix pending approvals, wrong Delivery IDs, declined or blocked connections, and invitation email mismatches.
- [Import problems](https://docs.simpleuat.com/troubleshooting/import.md): If import preview looks wrong, fix the file, try the other importer, or rely on deterministic fallback when AI is off.
- [A feature is missing](https://docs.simpleuat.com/troubleshooting/missing-feature.md): Hidden buttons are usually plan limits, feature flags, or a viewer role — not a down status page.
- [Still stuck](https://docs.simpleuat.com/troubleshooting/still-stuck.md): Email support@simpleuat.com with what you tried, the project or delivery name, and what happened. No stack traces. No public status page.
- [Glossary](https://docs.simpleuat.com/glossary.md): SimpleUAT words mapped to freelance testing: suites, cases, packs, cycles, runs, findings, snapshots, connections.
- [Your words → SimpleUAT words](https://docs.simpleuat.com/glossary/your-words.md): Test script becomes a case, defect becomes a finding, testing round becomes cycle and run, and so on.