The Cycluno Execution Blueprint

Cycluno turns your test cases into guided, step-by-step runs in a real browser. Every step is tracked, every failure is logged with evidence, and runs can start automatically when your code changes. This blueprint walks through the full execution workflow.

1. Configure your environments

Open your product and go to the Environments & Data tab. Each environment (for example Staging or Production) holds the variables a run needs, and one environment is marked as the default.

• Add a base_url for the app under test. If your sign-in page isn't at /login, add a login_url variable.
• Reference variables in steps as {{variable}}, and test data sets as {{Set.field}}.
• Pick a saved login when you start a run so each browser window signs in once and stays signed in. Credentials typed in for a single run are never stored.

Environment: Staging (default)
  base_url   = https://staging.example.com
  login_url  = https://staging.example.com/sign-in

Step: Open {{base_url}}/checkout and enter {{Customer.email}}

2. Monitor test run status

Start a run from Run Autopilot or the Execute tab, then open the Live tab. Each run shows a progress bar, passed and failed counts, and one tile per browser window with the current test and step. Up to four windows work through your tests side by side.

• Running — the window is actively executing steps.
• Waiting for Chrome — the run is queued until your local runner picks it up.
• Runner disconnected — no update has arrived recently; unfinished work is retried.
• Finished — all tests in that window have reported results.

3. Interpret intelligent logs

Open any test on the run page to see its step log and recording. Each step is marked passed, failed or could-not-check, with timing and the reason for any failure. Replay the recording, scrub to the failing moment, or download it as a video to share with your developers. Failed tests can be logged as bugs automatically.

✓ 1. Open {{base_url}}/login                     1.2s
✓ 2. Type {{Admin.email}} into "Email"            0.4s
✓ 3. Click "Sign in"                              0.9s
✗ 4. Assert "Dashboard" heading is visible        5.0s
     Expected heading "Dashboard" — found "Welcome back"
     → Bug drafted: "Login lands on Welcome page, not Dashboard"

Every execution is saved as its own run linked to the previous one, so you can compare results over time instead of overwriting history.

4. Integrate with CI/CD

In the Execute tab, turn on Automatic re-runs (product owners and admins only). Cycluno creates a private link you add to your tools:

1. GitHub — Settings → Webhooks → Add webhook, paste the link, choose push events. Optionally limit runs to one branch.
2. Vercel, Netlify or other hosts — add the link as a deploy notification so every successful deploy starts a run.
3. Each automatic run reuses the settings from your last Autopilot run and starts within about a minute. At most one automatic run starts every two minutes.

POST https://cycluno.com/api/public/rerun?key=••••••
event: push   branch: main   → run queued
event: push   branch: docs   → ignored (not the watched branch)
event: deploy state: ready   → run queued

5. Troubleshooting tips with sample logs

Tests stuck on "Waiting for Chrome"

status: blocked
note:   Waiting for your Chrome — no browser result yet.

Your local runner isn't open. Download the latest runner from Settings, start it, and keep your computer on during the run.

Every test in a window is blocked

status: blocked
note:   Not run — shared sign-in failed.

The one-time sign-in for that window failed. Check the saved login is still valid and that login_url points to the right page.

A step can't find an element

✗ Click "Submit order"
  No element matching "Submit order" after 20s

Replay the recording to see what was on screen. Make the step text match the visible label, or split long steps into shorter Act / Assert steps.

Push didn't start a run

Confirm the push was to the watched branch and that no other automatic run started in the last two minutes.