TestKit

Open your app in the browser and capture a test by simply using it. Install the extension, press Record, then walk through a real scenario—sign in, add an item to cart, complete checkout, or submit a form. As you click, type, and navigate, your actions become steps. Add checks on text, element states, or URLs with a single tap. Name and tag the flow, choose environments, and save. From the dashboard you can run the test immediately, group it into a suite, and set it to watch key user journeys with no scripting required.

Turn one-off recordings into repeatable quality gates. Link your repository and wire TestKit into your build with a native CI step (GitHub Actions, GitLab CI, CircleCI, and more). Map tests to branches or services, pass environment variables and secrets, and route runs to staging, preview, or production. Parameterize inputs to cover multiple users, locales, and payment methods without duplicating tests. Execute in parallel across browsers and viewport sizes to speed feedback. Schedule suites to run on a timer for ongoing health checks, and surface results as commit statuses, dashboards, and downloadable artifacts.

When the UI shifts, keep momentum instead of rewriting. TestKit watches for changed text, attributes, and structure, then updates selectors to match the new interface. Failing steps show side-by-side before/after snapshots; accept the fix, tweak it, or roll back with a click. Auto-waits, retries, and network stabilization reduce flakiness. Tag unstable tests for quarantine, view failure trends over time, and route alerts to Slack or email. Open a ticket with linked screenshots, console logs, and a full timeline so developers can reproduce issues instantly.

Use it across the team. Product managers turn acceptance criteria into runnable checks during planning. Developers capture acceptance tests for a feature branch and enforce them on pull requests. QA builds a smoke pack for login, search, and checkout that runs every hour in production. Content editors verify that new articles render correctly across templates before publishing. Growth teams validate sign-up, onboarding, and billing flows across countries and currencies. Support reproduces customer-reported issues by recording the exact steps, then hands a sharable test to engineering. With tags, roles, and audit history, everyone contributes without stepping on each other’s work.