Overview
Run your existing Selenium and Playwright suites on real browsers — Chrome, Edge, Firefox, and Safari on real macOS — straight from CI, with no rewrites.
Automate
TestKase Automate runs your existing Selenium and Playwright suites on real browsers — Chrome, Edge, Firefox, and Safari — on real macOS machines, driven straight from your CI pipeline.
There's no rewrite and no SDK lock-in. Point your suite at a TestKase endpoint by changing a single URL, and your tests run exactly as written in whatever language and framework you already use. Every run captures video, per-test recordings, and console/network/driver logs on a shared session dashboard.
Automate today is browser automation — Selenium (W3C WebDriver) and Playwright against desktop browsers. Native mobile app automation (Appium, on real Android & iOS) is coming soon.
Key capabilities
Selenium
W3C WebDriver at /wd/hub. Any language, any binding, no SDK required.
Playwright
Connect a vanilla @playwright/test install over a WebSocket endpoint.
Real browsers
Chrome, Edge, Firefox & Safari on genuine macOS Sequoia and Tahoe.
Rich artifacts
Session video, per-test recordings, console, network & driver logs.
Live view
Watch any run stream live in your dashboard while it executes.
One-URL migration
Move from BrowserStack or LambdaTest by changing a single URL.
How Automate differs from Live
Automate and Live are separate TestKase products that share the same device fleet but solve different jobs. Automate is for scripted, unattended test runs; Live is for manual, interactive sessions on a real device.
| Aspect | Automate | Live |
|---|---|---|
| How you use it | Scripted — your Selenium / Playwright suite drives the browser | Manual — you interact with a real device in your browser |
| Where it runs from | Your CI pipeline or a local script, no human in the loop | Your dashboard, hands-on |
| Protocol | W3C WebDriver (Selenium) and Playwright over WebSocket | Interactive streaming session |
| Best for | Regression suites, cross-browser E2E, CI gating | Exploratory testing, bug reproduction, one-off checks |
| Billing SKU | automate | live |
Both products are billed per SKU and each ships a one-time 90-minute free allowance. Buying automate does not unlock live, and vice versa. See Reference.
Next steps
FAQ
▶Do I have to rewrite my tests?
No. Automate speaks the same W3C WebDriver and Playwright protocols your suite already uses. You change the endpoint URL your suite connects to — your test code, assertions, language, and framework stay exactly as they are. There is no TestKase SDK to adopt.
▶Which browsers are supported?
Chrome, Edge, Firefox, and Safari — all running on real macOS machines (Sequoia 15 and Tahoe 26). You can request latest, latest-1/latest-N, or an exact browser major. See Browsers.
▶Is mobile app automation supported?
Not yet — it's coming soon. Automate today is browser automation — Selenium and Playwright against desktop browsers on macOS. Native mobile app automation with Appium on real Android and iOS devices is coming soon.
▶How does migration from BrowserStack or LambdaTest work?
Swap the WebDriver hub URL for your TestKase endpoint and rename the vendor capability block (bstack:options / LT:Options) to testkase:options. Your capabilities keep the same W3C shape, so nothing else changes. See Migrating.
▶How many minutes do I get, and how does concurrency work?
The automate SKU includes a one-time 90-minute lifetime free allowance. Parallelism is bounded by your plan's threads (seats) — each concurrent session consumes one thread. See Reference.