You didn’t get into QA to click through flows all day.

Every test session produces a full audit log: which flows were executed with video, screenshots, and logs. This is accessible in the Ito dashboard per PR and also linked directly from the PR comment.

It uses what you give it. With zero config, it mocks external dependencies (payment processors, email, analytics, etc.) that would otherwise cause intermittent failures. We don't want them to get in the way of testing the code changes. You have the ability to add credentials to any services, environment secrets and variables, and any other seed data used in regular testing.

Yes. Ito auto-generates flows from observed behavior, but you can add explicit flows in natural language via the dashboard ("user adds item to cart, applies promo code, checks out as guest") and Ito will translate those into browser-level test execution.

They serve different purposes. Your existing suite is regression coverage for known, stable paths -- high-value to keep. Ito covers the PR-level surface you can't afford to maintain test scripts for: new flows, recently changed behavior, flows introduced by non-technical contributors. The practical pattern most teams land on is keeping Playwright/Cypress for your critical path smoke suite (login, checkout, core CRUD) and letting Ito cover everything else on every PR. Over time, some teams retire their maintained suites entirely as Ito's coverage matures. There's no forced migration.