Start free
Integrations

Bring your own pipeline.

SpawnDroid fits the CI, WebDriver and chat tools your team already uses. No SDK, no test format, and no new dashboard to learn.

Start testing freeIntegration docs

Shortest path

One action, from build to report.

The official action uploads the APK, starts a hosted runner, runs your test command, attaches JUnit XML and always tears the device down.

Action reference
.github/workflows/android.yml
- name: Run on Android
  uses: kl3jvi/spawndroid/actions/android-test@v1
  with:
    api-key: ${{ secrets.SPAWNDROID_API_KEY }}
    app-path: app/build/outputs/apk/debug/app-debug.apk
    profile: android-14-phone
    command: npm test

CI & automation

Upload and run from the pipeline you already have.

OfficialGitHub ActionsThe official action wraps upload, runner creation, your test command and JUnit reporting.Via APIGitLab CIRun the upload and session calls from a GitLab job with a scoped API key.Via APIJenkinsCall the API from a Jenkinsfile stage. No plugin to install or keep current.Via APIBitbucket PipelinesThe same four REST calls work inside a Bitbucket pipeline step.Via APICircleCIUpload the build and start a hosted runner from a CircleCI job.Via APIAny CIIf it can run curl, it can upload a build and start a session.

Test frameworks

Bring your own tests. SpawnDroid supplies the device.

NativeAppiumHosted Appium 3 with UiAutomator2. Point any Appium client at the WebDriver URL.Any clientWebdriverIOYour existing WebdriverIO suite runs unchanged against the session URL.Any clientSeleniumSelenium and every other W3C WebDriver client work with the same endpoint.JUnit reportMaestroUpload its JUnit XML and the run page shows the failing flows and messages.JUnit reportEspressoAttach Gradle or Espresso JUnit XML to the run; the raw report is kept.Any clientAny W3C clientIf it speaks WebDriver, it works. There is no SDK or adapter to add.

Alerts

Send the result where the team already works.

NativeSlackPost run and session events to a channel from the console integrations page.NativeWebhooksSigned JSON for session.started, session.ended and artifact.uploaded.NativeEmailSend run notifications to your team's inbox, with the same event filters.

Platform

The primitives underneath every integration.

NativeREST APIUploads, sessions, logcat, recordings, reports and device profiles.NativeShare linksGive a designer or PM a revocable link to a live session. No account needed.NativeArtifactsLogcat, screen recording and JUnit reports retained per run.

Three calls, any pipeline.

Every integration uses the same API underneath. The action and the console are conveniences, not a proprietary test format.

01

Upload

Send the APK from CI with a scoped key, or let the action do it.

Docs
02

Run

Open a browser session, or point a W3C client at the WebDriver URL.

Docs
03

Report

Attach JUnit XML. Logcat and recording are retained; events go to Slack or a webhook.

Docs

Using something not listed? Check the help center or tell us what you use. Anything that can POST to the API works.

Start with your pipeline

Start with the pipeline you already have.

The Free plan includes one parallel runner, no card and no time cap. Add the action to one workflow and watch a real device come up.

Start testing freeTalk to the team