How do I…

Get a run going

Run my first testFrom a fresh account to a first passing test in about ten minutes.Add a variant for a new environmentAdd a staging or prod URL alongside an existing application.Set up sign-in for my appGive OttoTester credentials once and let it handle authentication.Steer what the planner testsSet the Agent Prompt on a Test Authoring Template to focus the planner on specific flows.Upload reference docs for an appAttach specs, feature files, or scenario lists so the agents test with the context you already have.Review and manage candidate testsEdit, archive, or hand-add the suggested scenarios the planner draws from.

Read the results

Read a run reportNavigate from the run list to a failed test’s Playwright trace.See what’s newly failingSpot tests that flipped to failing this run from the variant dashboard.Compare runs across variantsSide-by-side comparison of two variants’ latest runs.

Fix and refine

Fix a failing testRead the healer’s attempt log; pick edit, regenerate, or add a hint.Edit or pin a test scriptEdit a generated script by hand and keep your changes through future heals.Create a test suiteGroup tests into a named set you can run, schedule, or trigger from CI.

Automate

Replay tests on demandSave a tests-plus-settings selection as a replay template and re-run it any time.Schedule recurring runsRun a suite on a cadence — hourly, daily, weekly.Connect CI/CDPick between the GitHub App webhook path and the Pipeline Integration API path — and wire either one up.Run OttoTester from your CIGenerate a token, paste the snippet OttoTester builds for you, and have your pipeline gate the next stage on pass/fail.Get notified when a run finishesConfigure email and PDF report delivery for run completions.