Skip to content

First steps

Find your way around a session

What every part of the session page is for, from the header buttons to the cards next to the phone and the tools on the right.

Why: the session page packs a lot into one screen. Two minutes here and you’ll know where to look for each thing instead of hunting for it mid-test.

  1. The header is about the session: the app and its build (click it to install another build), the state badge, the time left, and Share, Extend and Stop.
  2. The cards on the left are the device’s quick settings. Hover one to open its panel: change the country, the network, the GPS position, the battery, the language or the clock.
  3. The phone in the middle is the real screen. Its side keys work like the hardware ones.
  4. The tools on the right are tabs: DevTools, WebSockets, Logcat, Files, Terminal and Pixel perfect.
  • A small amber dot on a card means that setting differs from the default, so you can see at a glance what you changed.
  • Right-click the screen to wake the device when its display is off.
  • If the app closes or crashes, it stays closed; the play button in the app card starts it again.
  • Some cards and tabs only appear when your server turns the feature on, so your page may have fewer of them.
  • The screen stays on “Connecting to the screen…”: reload the page. If it keeps happening, try a recent Chrome, Edge, Firefox or Safari.
  • Share, Extend and Stop are greyed out: the session belongs to someone else. You can watch it, but only its owner and admins can manage it.

More details: Sessions and slots.