Create a project

A project is the engagement: one product (or one slice) you are testing now. It is not your whole freelance business, and it is not the client’s company record. Freelancers usually work in Projects. Applications (products), Providers, Portfolio, Inbox, and Archive are the recipient/client side. You can ignore most of that until someone is receiving your delivery. Project vs product.

​

Create it

From the empty state you’ll see Create First Project or Create Client Project. Fill in a name people will recognize on an invoice. Type is one of: web | ios | android | admin_portal | api | wordpress | saas | other. Pick the closest. It helps pack recommendations; it does not lock you out of other tests. Under the org, a project can hold surfaces, features, environments, personas, suites, cases, cycles, and runs. You don’t have to fill every bucket on day one.

​

After create: empty project

You’ll land on setup options:

• Guided wizard: eight questions, then the app creates project pieces, environments, suites, starter tests, a first cycle, optional assignments. Wizard.
• Import tests: Excel, CSV, Word, PDF, mixed. Imports.
• From my codebase: prompt to agent JSON simpleuat-project-setup.json to upload to preview to apply. Paid on Pro+. Codebase.
• Import history: past codebase setup uploads.
• Manual: you add suites and cases yourself.

You can change structure later. Can I change it?.

​

What “done enough” looks like

You can start executing when you have: an environment, at least one case (in a suite), a cycle that includes that case, and you as an active tester. Can’t start a run.