Overview
Run your existing Selenium, Playwright, Appium, Espresso and XCUITest suites on real browsers and real phones — straight from CI, with no rewrites.
TestKase Automate runs your existing Selenium and Playwright suites on real browsers — Chrome, Edge, Firefox, and Safari — on real macOS and Windows machines, your Appium suites on real iPhones and real Android phones, your Espresso suites on real Android phones and emulators, and your XCUITest suites on real iPhones and iPads, driven straight from your CI pipeline.
Point your tests at a TestKase connection by changing a single URL, and your tests run exactly as written in whatever language and framework you already use. Every run captures video and console/network/driver logs on a shared session dashboard.
Key capabilities
Selenium
standard WebDriver at /wd/hub. Any language, any client, nothing of ours to install.
Playwright
Connect a vanilla @playwright/test install over a WebSocket connection.
Real browsers
Chrome, Edge, Firefox & Safari on macOS; Chrome, Edge & Firefox on Windows. The capability generator has the current list.
Real mobile devices
Appium on physical iPhones and Android phones — apps and mobile browsers. Espresso on Android phones and emulators. XCUITest on iPhones and iPads.
Rich artifacts
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 an existing cloud-grid suite by changing a single URL.
How Automate differs from Live
Automate and Live are separate TestKase products that share the same devices 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 / Appium / Espresso / XCUITest suite drives the browser or device | 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 | standard WebDriver (Selenium and Appium), Playwright over WebSocket, and the Espresso and XCUITest REST APIs | Interactive streaming session |
| Best for | Regression suites, cross-browser E2E, CI gating | Exploratory testing, bug reproduction, one-off checks |
| Billing SKU | automate | live |
FAQ
▶Do I have to rewrite my tests?
No. Automate speaks the same standard WebDriver and Playwright protocols your tests already uses. You change the connection URL your tests 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 on macOS; Chrome, Edge, and Firefox on Windows. Safari is macOS-only — it doesn't exist on Windows. You can request latest, latest-1/latest-N, or an exact browser major. The capability generator shows the live list.
▶Is mobile app automation supported?
Yes. Appium sessions run against real iPhones and real Android phones over the same /wd/hub connection as Selenium, and are proven end-to-end on physical hardware. You can drive your own uploaded app, or the device's browser — mobile Safari on iOS, Chrome on Android. See Automate Mobile.
On Android you can also run your existing Espresso suite as it is: upload the app and androidTest APKs and start a build on a list of devices. See Espresso on real devices.
On iOS you can run your existing XCUITest suite the same way: upload the .ipa and the zipped test Runner and start a build. See XCUITest on real devices.
▶How does migration from another cloud grid work?
Swap the WebDriver hub URL for your TestKase connection and rename your old service's settings block to testkase:options. Your capabilities keep the same standard shape, so nothing else changes.
▶How many minutes do I get, and how does concurrency work?
The automate SKU includes a one-time 15-minute lifetime free allowance. Parallelism is bounded by your plan's threads (seats) — each concurrent session consumes one thread. See Reference.