Google Cloud Testing API
Browse all Google APIs✓ Official Vendor SpecDeveloper ToolsTesting Qaoauth210 EndpointsREST
For Agents
Submit and monitor Firebase Test Lab test matrices for Android and iOS apps across physical and virtual device fleets.
Use for: I need to run my Android app on a Firebase Test Lab device matrix, Submit an XCTest run for my iOS app, List the available test devices for Android, Cancel a running test matrix
Not supported: Does not handle code coverage analysis, build artefact storage, or non-mobile testing — use for submitting Firebase Test Lab device matrices only.
Cloud Testing API drives Firebase Test Lab, Google's managed mobile-app testing infrastructure. Submit Android APKs or iOS XCTest archives plus instrumentation and Robo test specifications, and Test Lab runs them on a matrix of physical and virtual device models, OS versions, locales, and orientations. The API exposes the test environment catalog (which devices and APIs are available), submits test matrices, and reports back execution status. Pairs with Cloud Tool Results API to retrieve detailed logs, screenshots, and video recordings.
Install Jentic One Beta
Connect the Cloud Testing API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cloud Testing API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Cloud Testing API.
Submit instrumentation, Robo, and game-loop test matrices for Android apps
Run XCTest test matrices for iOS apps on physical devices
Query the device catalog to discover available models, OS versions, and locales
Cancel an in-flight test matrix
Inspect APK manifest details before submitting a test
Track test matrix state through validation, pending, running, and finished phases
Use Cases
Patterns agents use Cloud Testing API for, with concrete tasks.
★ Pre-Release Device Matrix Testing
Mobile teams running a release pipeline submit each candidate build to Firebase Test Lab across a curated matrix of devices — typically the top five most popular phones for their region plus one tablet and one low-end device. Cloud Testing API submits the matrix from CI; the build fails the pipeline if any matrix execution reports a crash. The Test Lab matrix runs in parallel and finishes in under twenty minutes for most apps.
POST /v1/projects/{projectId}/testMatrices with the APK GCS URI, instrumentation test APK URI, and a deviceMatrix targeting Pixel 7, Galaxy S23, and a low-end Android 11 device.
Robo Crawl for Pre-Launch Reports
QA teams submit a Robo test which crawls the app autonomously, exercising UI elements without scripted instrumentation. The Cloud Testing API accepts a Robo test specification, runs it on selected devices, and produces a crawl graph plus screenshots. This is how Google Play's pre-launch report works under the hood, and the same API is available for in-house pre-release sweeps.
Submit a Robo test matrix with roboDirectives describing login fields and a 5-minute crawl duration on three representative devices.
Device-Specific Bug Reproduction
A bug report comes in for a specific device and OS combination. Engineering uses the Cloud Testing API to run an instrumentation test isolated to that exact model and Android API level, capturing logcat, video, and screenshots through the linked Cloud Tool Results API. This narrows reproduction to minutes instead of waiting for a physical device to ship.
GET /v1/testEnvironmentCatalog/ANDROID to find the matching model, then POST a test matrix targeting just that AndroidModel and AndroidVersion.
Agent-Driven Mobile QA via Jentic
An AI agent monitoring a mobile build pipeline detects a new release candidate, submits a Test Lab matrix through Jentic, polls until completion, and posts a summary of pass/fail counts back to the team chat. Jentic isolates the OAuth credential and provides a stable schema across the submit-and-poll loop.
Through Jentic, search 'submit firebase test lab matrix', load POST /v1/projects/{projectId}/testMatrices, execute it with the build URI, then poll GET /v1/projects/{projectId}/testMatrices/{testMatrixId} until state is FINISHED.
Key Endpoints
10 endpoints — cloud testing api drives firebase test lab, google's managed mobile-app testing infrastructure.
METHOD
PATH
DESCRIPTION
POST
/v1/projects/{projectId}/testMatrices
Submit a new test matrix for an Android or iOS app
GET
/v1/projects/{projectId}/testMatrices/{testMatrixId}
Retrieve the status of a submitted test matrix
POST
/v1/projects/{projectId}/testMatrices/{testMatrixId}:cancel
Cancel an in-flight test matrix
GET
/v1/testEnvironmentCatalog/{environmentType}
Get the catalog of available test devices for Android or iOS
POST
/v1/applicationDetailService/getApkDetails
Read the manifest of an APK before submitting a test
POST
/v1/projects/{projectId}/testMatrices
Submit a new test matrix for an Android or iOS app
GET
/v1/projects/{projectId}/testMatrices/{testMatrixId}
Retrieve the status of a submitted test matrix
POST
/v1/projects/{projectId}/testMatrices/{testMatrixId}:cancel
Cancel an in-flight test matrix
GET
/v1/testEnvironmentCatalog/{environmentType}
Get the catalog of available test devices for Android or iOS
POST
/v1/applicationDetailService/getApkDetails
Read the manifest of an APK before submitting a test
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Service-account JSON or OAuth tokens are stored encrypted in the Jentic vault. Agents submit test matrices and poll for status through Jentic with no raw credential ever entering the agent context.
Intent-based discovery
Agents search 'submit firebase test lab matrix' or 'cancel mobile test run' and Jentic returns the matching v1 operation with input schema, including the deviceMatrix and testSpecification blocks.
Time to first call
Direct Cloud Testing integration: 2-4 days for GCS upload wiring, OAuth, and matrix-spec authoring. Through Jentic: under 1 hour for submit-and-poll loops.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Cloud Testing API through Jentic.
What authentication does the Cloud Testing API use?
Cloud Testing uses OAuth 2.0 with the cloud-platform scope (read/write) or cloud-platform.read-only for inspection. Service-account credentials are typical for CI integrations. Through Jentic, the credential is held in the encrypted vault and refresh handling is automatic across long-running test polls.
Can I run iOS tests with the Cloud Testing API?
Yes. Submit an XCTest matrix by passing iosXcTest in the test specification along with the test zip URI uploaded to GCS. Use GET /v1/testEnvironmentCatalog/IOS to list available iPhone and iPad models and iOS versions before submitting.
What are the rate limits for the Cloud Testing API?
The control-plane API allows several requests per second per project for matrix submission and polling. The actual constraint is the Test Lab quota of concurrent device executions per project (default 5 physical and 10 virtual), which can be raised via Cloud Console quota request. Matrix submissions queue rather than fail when the device cap is reached.
How do I submit a test matrix through Jentic?
Search Jentic for 'submit firebase test lab matrix', load POST /v1/projects/{projectId}/testMatrices, and execute it with your project ID, GCS APK URI, test APK URI, and a deviceMatrix block. Poll GET /v1/projects/{projectId}/testMatrices/{testMatrixId} until state is FINISHED to retrieve outcome. Get started at https://app.jentic.com/sign-up.
Is the Cloud Testing API free?
The API itself is free to call. Test executions are billed per device-hour at Firebase Test Lab rates — the Spark plan includes a daily allotment of free device-minutes; Blaze plan customers pay per device-minute beyond that. Virtual devices are cheaper than physical ones.
How do I inspect APK contents before submitting a test?
POST /v1/applicationDetailService/getApkDetails with the GCS URI of the APK and Test Lab returns the manifest fields including package name, version, permissions, and intent filters. This is useful for sanity-checking the build artefact before consuming a test slot.
GET STARTED