emulator.wtf

Visit Website

Introduction

emulator.wtf describes itself as an Android cloud emulator laser-focused on performance to deliver quick feedback on pull requests. Instead of maintaining emulators on CI runners, teams send their app and test APKs to emulator.wtf, which runs instrumentation tests on cloud emulators and returns results.

Its documentation lists integration options: a CLI (ew-cli), a Gradle plugin, and GitHub Actions, with GitHub-specific features such as commit statuses, PR comments, tokenless invocation and GitHub SSO. Concepts covered include code coverage collection, sharding tests across many emulators to cut wall-clock time, pulling files (such as screenshots or reports) from devices, pushing files to devices, and networking. Security and administration topics include OIDC authentication for GitHub Actions and CircleCI, SSO/SAML with Google Workspace and Okta, and SCIM provisioning. Patrol’s website lists emulator.wtf among compatible device farms. Pricing is listed on its website; see site for current plans.

Because tests are standard Android instrumentation tests, existing Espresso, UI Automator, Compose and Kaspresso suites can run on emulator.wtf without rewriting.

Features

1. Fast cloud emulators: Built for quick PR feedback.
2. CLI, Gradle and Actions: Multiple integration paths.
3. Sharding and coverage: Split tests and collect coverage.
4. Enterprise auth: OIDC, SSO/SAML and SCIM.

Pros

1. Speed-focused: Optimised for quick PR feedback.
2. Easy integration: CLI, Gradle plugin and GitHub Actions.

Cons

1. Android emulators only: No iOS or physical devices.
2. Hosted service: Test artefacts are uploaded to a third party.

Usage and Links (Example)

Typical workflow (see the emulator.wtf docs for current commands and options):

1. Create an API token and store it as a CI secret.
2. Build your app and test APKs (for example with ./gradlew assembleDebug assembleDebugAndroidTest).
3. Run the tests on cloud emulators with the ew-cli CLI, the Gradle plugin or the GitHub Action, choosing device models, API levels and the number of shards.
4. Review results in the PR comment or commit status, and pull reports, screenshots or coverage files back to CI.

Resources:

• emulator.wtf website

Pricing

Commercial; see the pricing page on the website for current plans.

Recommended for?

1. Android teams wanting fast instrumentation tests without self-hosted emulators.
2. GitHub-centric teams using PR comments and statuses.

Conclusion

emulator.wtf focuses squarely on fast Android emulator testing in CI, with practical GitHub and enterprise integrations.