PocketQA

Help

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

PartSupported
Lab computerA Mac with Apple silicon (M1 or later) or Intel, on macOS 13 Ventura or later
Its PythonThe python3 that comes with the Mac's command line tools (3.9 or later)
Browsers on the labChrome (installed for you); Safari, whatever version comes with that macOS
iPhoneiOS 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 phoneAndroid 9 or later, plugged in with a data cable, tested in Chrome, with USB debugging allowed
NetworkAny 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.

Not supported

How updates reach your lab

Each lab updates itself between tests, and a new release reaches labs in stages:

  1. PocketQA's own labs get it first.
  2. About two hours later, one lab in ten gets it.
  3. 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