What PocketQA supports
PocketQA runs on your own computer and phones, so it meets a lot of different setups. This page lists the ones we test and fix, so you know what to expect before you plug something in. If your setup isn't listed, it may still work. We just can't promise it yet.
When something listed here misbehaves, ask your agent to run lab_doctor, or use Report to PocketQA (the report_to_pocket_lab tool). Each report comes to us with the lab's state attached.
Supported: we test it and fix it
| Part | Supported |
|---|---|
| Lab computer | A Mac with Apple silicon (M1 or later) or Intel, on macOS 13 Ventura or later |
| Its Python | The python3 that comes with the Mac's command line tools (3.9 or later) |
| Browsers on the lab | Chrome (installed for you); Safari, whatever version comes with that macOS |
| iPhone | iOS 15 or later, plugged in with a data cable, tested in Safari. It must be unlocked, trusted, with Developer Mode on and Auto-Lock set to Never |
| Android phone | Android 9 or later, plugged in with a data cable, tested in Chrome, with USB debugging allowed |
| Network | Any connection that reaches the internet over HTTPS. The lab only makes outgoing connections |
Works, not yet supported
These run, but we don't test them on every release yet.
- A Linux lab computer. Its Chrome browsers and Android phones work. Safari and iPhones need a Mac.
- iPads, tested as iPhones.
- Several phones on one computer. Each is tested in turn. Only one iPhone and one Android phone at a time are tested on each run.
- macOS 12 Monterey.
Not supported
- A Windows lab computer. Cloud Lab will cover Windows browsers.
- Phones on Wi-Fi only, with no cable.
- iOS 14 or earlier, and Android 8 or earlier.
- A lab computer behind a proxy that inspects HTTPS. Updates are to be checked against PocketQA's release signature, which an inspecting proxy breaks.
How updates reach your lab
Each lab updates itself between tests, and a new release reaches labs in stages:
- PocketQA's own labs get it first.
- About two hours later, one lab in ten gets it.
- After a day, every lab gets it.
If labs on the new release start failing on their own (lab errors or inconclusive runs) clearly more often than on the release before, the rollout stops by itself. Labs that already updated go back to the release before.
A small updater starts the lab. If a new release can't stay running, the updater puts the last working copy back.
What the lab keeps private
- Crash logs. An iPhone's crash logs list the apps on it. PocketQA reads them only on the lab computer, never stores them, and names only Safari's own processes and iOS's own. Any other app is "another app on the phone".
- Your local network. Agents and scripts can test the internet and the lab computer's own
localhost. They can't reach other addresses on your network unless your team adds them under Settings › Privacy. Every one-off address tested is recorded, with who asked. - Console output. Agents are told it's the tested site's own words, not instructions. Your team can stop agents receiving it under Settings › Privacy.
- Report links. For 30 days, anyone with a report link can see the whole report. After that, the link shows the verdict only, and the details need a sign-in to your team.
- Phone details. Agents never get a phone's battery level. A lab's name is the one your team gave it in PocketQA, not a person's name.