From Sign-Up to Your First Run in 10 Minutes

You don't need a QA process in place to start with Cycluno. This guide takes you from an empty workspace to your first automated run in about ten minutes, then shows what the first month typically looks like.

1. The 10-minute setup checklist

1. 0–1 min: Create your free account — email and password, or one click with Google.
2. 1–3 min: Add your first product: name it and paste in the address of the site or app you want to test.
3. 3–5 min: Upload a PRD (PDF) or paste your requirements. Cycluno drafts features, a test plan and test cases from it.
4. 5–7 min: Open the Environments & Data tab and set a base_url for the app under test. Add any variables your steps need.
5. 7–9 min: Save a login as a test data set so runs can sign in once and stay signed in.
6. 9–10 min: Press Run Autopilot and watch the first cases execute live, with recordings you can replay.

2. What to prepare

Cycluno generates its best test cases from a small amount of material. Four things, nothing more:

• A PRD or feature list: A PDF or plain text of your product requirements. Even a rough feature list works — Cycluno turns it into features, test cases and a test plan. If you don't have one yet, start with your two or three most-used flows and write them down.
• The address of the app under test: A base URL for the environment you want to test (staging is a good first choice). If your sign-in page is not at /login, note its address so you can add a login_url variable.
• A test login: The username and password of a test account, so Autopilot can sign in once per run instead of typing credentials on every test.
• Sample requirements for tricky flows: For anything complicated — checkout, onboarding, permissions — a sentence or two of expected behaviour is enough to anchor the generated cases.

3. What success looks like in 30 days

4. Customer outcomes

Teams that follow this path typically see results like these within their first month: