Google Cloud Testing
Allows developers to run automated tests for their mobile applications on Google infrastructure (Google OAuth2).
OCNORA ships 6 typed Google Cloud Testing operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Google Cloud Testing
- Authentication
- OAuth 2.0
- Credential
- {"client_id", "client_secret", "refresh_token"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with Google Cloud Testing
Operations, grouped by what they do to your data.
Create and send 2
Read and search 3
Update 1
A sample Google Cloud Testing workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Cloud Testing trigger is needed.
- 2Get Device Sessioncloud_testing.get_device_sessionGET /v1/projects/{project_id}/deviceSessions/{device_session_id} Return a DeviceSession, which documents the allocation status and whether the device is allocated.
- 3Create Device Sessioncloud_testing.create_device_sessionPOST /v1/projects/{project_id}/deviceSessions.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 6
- Create Device SessionPOST /v1/projects/{project_id}/deviceSessions.cloud_testing.create_device_session
- Create Test MatriceCreates and runs a matrix of tests according to the given specifications. Unsupported environments will be returned in the state UNSUPPORTED.cloud_testing.create_test_matrice
- Get Device SessionGET /v1/projects/{project_id}/deviceSessions/{device_session_id} Return a DeviceSession, which documents the allocation status and whether the device is allocated.cloud_testing.get_device_session
- Get Test MatriceChecks the status of a test matrix and the executions once they are created.cloud_testing.get_test_matrice
- List Device SessionsGET /v1/projects/{project_id}/deviceSessions Lists device Sessions owned by the project user.cloud_testing.list_device_sessions
- Update Device SessionPATCH /v1/projects/{projectId}/deviceSessions/deviceSessionId}:updateDeviceSession Updates the current device session to the fields described by the update_mask.cloud_testing.update_device_session
Google Cloud Testing questions
- How does OCNORA authenticate with Google Cloud Testing?
- With a stored OAuth 2.0 credential, shaped {"client_id", "client_secret", "refresh_token"}. A connection test can check it when you add it.
- What can I automate with Google Cloud Testing?
- 6 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Cloud Testing operation I need is not listed?
- Where Google Cloud Testing has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Google Cloud Testing?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Cloud Testing calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first Google Cloud Testing workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.