The eight questions
- What are you testing? Website/web app, mobile app, API/backend, or a product with several parts.
- What should we call this release or project? Something you’ll recognize: “September MVP,” “Checkout Redesign.”
- What kind of change? Brand-new / major launch, new feature, fixes, or a regular mixed release.
- Where will your team test? Dev, Test/QA, Staging/Implementation, Production (multi-select). Creates environments; one recommended default.
- How much structure? Lean, Recommended, Thorough, or start small.
- Who will actually perform UAT? Mostly me, small internal team, business users, or clients/external. This controls whether assignments get created.
- How do you expect testing to happen? One focused cycle, every release, weekly, or not sure. Becomes the first cycle template.
- Optional: describe your product: short plain English to tailor starter tests. Skip for generic templates.
What it creates
You’ll see build stages: validate to project to environments to suites to starter tests to first cycle to optional assignments to done. That’s a first pass, not a locked methodology. Add a pack, import more, delete suites. Can I change it?Empty project options
Wizard vs import vs manual.
Then run
Assign yourself and start a run.

