Skip to main content
Test Sauce Demo flows or your own Android app, keep evidence, and run the same test across devices.

Test one login

Test the public demo login and check the Products heading. Needs: Cloud Android · Chrome · API key + DEVICE_ID · credits and device minutes · no account · one-shot, about 1 min.
Open Sauce Demo in Chrome on my device, log in as standard_user with secret_sauce, and report whether the Products heading appears.

Test your own app

Install an APK from your app library and check that its home screen shows the expected text. Needs: Ready Cloud Android device · uploaded APK · API key + DEVICE_ID · APP_PACKAGE + EXPECTED_TEXT · credits and device minutes · one-shot. First, upload your APK in the Apps library, or use an app already uploaded there. Wait for processing to finish, then set APP_PACKAGE to its Android package name and EXPECTED_TEXT to text that should appear on its home screen. The SDK also exposes a signed-upload and confirmation API; this example uses the dashboard for upload.

Run a test suite with a report

Run two independent tests and save a JSON report. Needs: Cloud Android · Chrome · API key + DEVICE_ID · credits and device minutes · public demo credentials · one-shot, several minutes.

Test 1 · Checkout completes

The standard user completes a fictional checkout; the confirmation is the expected result.

Test 2 · Locked-out user is blocked

The locked-out user must see the expected error: that error means the test passes.

Keep video and screenshots as proof

Save each test’s screenshots, trajectory, and, when supported, the recording video in evidence/<test>/. Needs: Cloud Android · Chrome · API key + DEVICE_ID · credits and device minutes · recording capability for video · public demo credentials · one-shot, several minutes.

Run it on many devices

Run the suite on as many devices as you need: one report per device, all in parallel.
Run the login test concurrently on distinct devices and print one result per device. Needs: Ready Cloud Android devices · Chrome · API key + comma-separated DEVICE_IDS · credits and device minutes per device · public demo credentials · one-shot.

Next steps

Start with the login test, or upload an APK to the app library and test it by package name. Use task run, status, screenshots and trajectory APIs. Sauce Demo credentials are public demo credentials. Report results for each test and device.