Configure once. Copy code that runs on the grid.

Notes

Before you paste it in

What are capabilities?

A block of settings your test sends when it opens a session — which browser, which operating system, and which extras you want switched on. Your framework already sends them; this page just builds the block for our grid so you do not have to look up the key names.

Does my test code change?

No. Selenium and Playwright both speak their standard protocols here, so the suite you have keeps working. You change the endpoint it connects to and paste in the block above.

Why is my option being ignored?

Almost always one of three things: extras belong inside testkase:options rather than at the top level; booleans must be real booleans, since "true" in quotes is a string and is silently ignored; and an uploaded app is referenced with a hyphen, as farm://app-<id>.

Where does the device list come from?

The running fleet, read live each time you open this page — so it offers combinations that exist rather than ones that used to. Selenium options are filtered further, to combinations with a matching driver actually installed.

Running your suite against a site on your own machine? Local testing covers that.