Physical-Device Examples
Physical-Device Integrations
The /tests/execute
endpoint can run your GPT Driver test suites on real hardware by connecting to the most common device-cloud vendors—or by using GPT Driver-hosted phones if you don’t yet have a third-party account.
Good to know
All integrations share the same security model: credentials are encrypted at rest, used only for the current execution, and never persisted in plain text.
If any key is missing the request will fail with a
400 Invalid request
response that lists the missing fields.The example objects below can be mixed with the other request parameters you already use (such as
tests
,tags
, orinputs
).
Provider
Required fields
Optional fields
Notes
BrowserStack
userName
, accessKey
app
If app
is omitted we re-use the latest build already uploaded to BrowserStack.
AWS Device Farm
accessKeyId
, secretAccessKey
, projectArn
appArn
The project’s default device pool will be used unless you add the devicePoolArn
field.
LambdaTest
userName
, accessKey
appUrl
appUrl
may point to an existing LambdaTest build (lt://APP_ID
) or a public artifact.
GPT Driver Hosted Devices
deviceType
osVersion
, locale
Leave all keys blank to let GPT Driver choose the next available device for you.
1. BrowserStack
2. AWS Device Farm
3. LambdaTest
4. GPT Driver-Hosted Devices
Verifying the run
Last updated