Your first phone test
About 30 minutes, most of it waiting for downloads. You need a Mac (any from the last few years), a phone, and a cable that carries data (not a charge-only one).
1. Add your site
- Sign in at your dashboard.
- Type your site's address (for example
www.example.com) and press Add site. - Add the pages that matter most, like
//pricing/checkout. Three to five is plenty to start.
2. Turn your Mac into a lab
- On the dashboard: Labs › Add a lab. Give it a name your team will recognise, and say whether it's only for testing or someone also works on it.
- Copy the install command, open Terminal on the Mac (⌘ Space, type Terminal, Return), paste it and press Return.
- When it asks for a password, type the Mac's own. Nothing shows as you type: that's normal.
- At the end it checks everything a test needs and prints a ✓ or a fix for each. Your dashboard's Labs page shows the same list and keeps it up to date.
Rather check the installer before it runs? Download it and its checksum, check it (it should say install.sh: OK), then run it with the code from your own install command:
curl -fsSL -O https://staging.pocketqa.dev/install.sh -O https://staging.pocketqa.dev/install.sh.sha256
shasum -a 256 -c install.sh.sha256
bash install.sh --code ABCD-2345On Linux the check is sha256sum -c install.sh.sha256. If it says FAILED, don't run it. The installer is signed with PocketQA's release key too: how to check its signature.
3a. Plug in an Android phone
- On the phone: Settings › About phone › tap Build number seven times (on Samsung: About phone › Software information › Build number).
- Settings › System › Developer options › USB debugging on.
- Plug it into the Mac and unlock it. Tick Always allow from this computer, then tap Allow.
- Within a minute the phone appears on your lab as ready.
3b. Or an iPhone
- Plug it into the Mac and unlock it. Tap Trust and enter its passcode.
- Settings › Apps › Safari › Advanced: turn on Web Inspector and Remote Automation (on older iOS: Settings › Safari › Advanced).
- Settings › Privacy & Security › Developer Mode › on. It restarts; unlock it and confirm.
- Optional: on a phone kept for testing, Settings › Display & Brightness › Auto-Lock › Never. On your own phone, keep it unlocked while a test runs; if it locks, that test is inconclusive, never a failure.
4. Test
- Press Test now on the dashboard. The picture shows your site going to your lab and each device in turn.
- Each device ends green (passed), red (your site broke) or yellow (the lab couldn't judge: never counted against your site).
- A red one opens to what broke, in the page's own words, and what to try. Results › Issues lists each problem once, however often it happens.
If something's stuck
Every line on your lab's Recommended settings says what to do. Most are a tap on the phone or a Fix it on the Mac button. Still stuck? What a failure means, or ask your coding agent to run lab_doctor.