Google Cloud Testing API

Name: Cloud Testing API
Brand: Cloud Testing API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsTesting Qaoauth210 EndpointsREST

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.

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 | sh

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 instance

Jentic 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

GET STARTED

Start building with Cloud Testing API

Explore with Jentic

View OpenAPI Document

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

Your Cloud Testing service-account credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'submit a firebase test lab matrix' or 'cancel a mobile test run', and Jentic returns the matching Cloud Testing v1 operation with its input schema, including the deviceMatrix and testSpecification blocks, so the agent calls the right endpoint without browsing the reference docs.

Time to first call

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 with Jentic One, the self-hosted execution layer.

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.

Can I limit what my agent is allowed to do with the Cloud Testing API?

Yes. Because you run Jentic One yourself, your own rules decide which Cloud Testing operations and credentials the agent may use. Since the project ID sits in the URL path (/v1/projects/{projectId}/testMatrices), you can pin the agent to a single project so it only submits and reads test matrices there and nothing else. You also choose the exact operations it may call, so canceling an in-flight matrix stays off limits unless you explicitly allow it.

Google Cloud Testing API

Connect the Cloud Testing API to your agent

Capabilities

Start building with Cloud Testing API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs