Identifies an account and how to log into it.
A single Android device.
The currently supported Android devices.
A list of Android device configurations in which the test is to be executed.
A test of an Android application that can control an Android component independently of its normal lifecycle. Android instrumentation tests run an application APK and test APK inside the same process on a virtual or physical AndroidDevice. They also specify a test runner class, such as com.google.GoogleTestRunner, which can vary on the specific instrumentation framework chosen. See for more information on types of Android tests.
A set of Android device configuration permutations is defined by the the cross-product of the given axes. Internally, the given AndroidMatrix will be expanded into a set of AndroidDevices. Only supported permutations will be instantiated. Invalid permutations (e.g., incompatible models/versions) are ignored.
A description of an Android device tests may be run on.
A test of an android application that explores the application on a virtual or physical Android Device, finding culprits and crashes as it goes.
Android configuration that can be selected at the time a test is run.
A test of an Android Application with a Test Loop. The intent \ will be implicitly added, since Games is the only user of this api, for the time being.
A version of the Android OS.
An Android package file to install.
Android application details based on application manifest and archive contents.
An Android app manifest. See http://developer.android.com/guide/topics/manifest/manifest-intro.html
An Android App Bundle file format, containing a BundleConfig.pb file, a base module directory, zero or more dynamic feature module directories. See https://developer.android.com/guide/app-bundle/build for guidance on building App Bundles.
Gets the details of an Android application APK.
A builder providing access to all methods supported on
applicationDetailService resources.
It is not used directly, but through the
Testing hub.
The request object for cancelling a Device Session.
Response containing the current state of the specified test matrix.
Information about the client which invoked the test.
Key-value pair of detailed information about the client which invoked the test. Examples: {‘Version’, ‘1.0’}, {‘Release Track’, ‘BETA’}.
Represents a whole or partial calendar date, such as a birthday. The time of day and time zone are either specified elsewhere or are insignificant. The date is relative to the Gregorian Calendar. This can represent one of the following: * A full date, with non-zero year, month, and day values. * A month and day, with a zero year (for example, an anniversary). * A year on its own, with a zero month and a zero day. * A year and month, with a zero day (for example, a credit card expiration date). Related types: * google.type.TimeOfDay * google.type.DateTime * google.protobuf.Timestamp
A single device file description.
A single device IP block
List of IP blocks used by the Firebase Test Lab
Protobuf message describing the device message, used from several RPCs.
Denotes whether Direct Access is supported, and by which client versions. DirectAccessService is currently available as a preview to select developers. You can register today on behalf of you and your team at https://developer.android.com/studio/preview/android-device-streaming
Data about the relative number of devices running a given configuration of the Android platform.
A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); }
The environment in which the test is run.
The matrix of environments in which the test is to be executed.
A key-value pair passed as an environment variable to the test.
A reference to a file, used for user inputs.
Response containing the details of the specified Android application.
Enables automatic Google account login. If set, the service automatically generates a Google test account and adds it to the device, before executing the test. Note that test accounts might be reused. Many applications show their full set of functionalities when an account is present on the device. Logging into the device with these generated accounts allows testing more functionalities.
A storage location within Google cloud storage (GCS).
The section of an tag. https://developer.android.com/guide/topics/manifest/intent-filter-element.html
A single iOS device.
The currently supported iOS devices.
A file or directory to install on the device before the test starts.
A list of iOS device configurations in which the test is to be executed.
A description of an iOS device tests may be run on.
A test that explores an iOS application on an iOS device.
iOS configuration that can be selected at the time a test is run.
A test of an iOS application that implements one or more game loop scenarios. This test type accepts an archived application (.ipa file) and a list of integer scenarios that will be executed on the app sequentially.
A description of how to set up an iOS device prior to running the test.
An iOS version.
A test of an iOS application that uses the XCTest framework. Xcode supports the option to “build for testing”, which generates an .xctestrun file that contains a test specification (arguments, test methods, etc). This test type accepts a zip file containing the .xctestrun file and the corresponding contents of the Build/Products directory that contains all the binaries needed to run the tests.
Specifies an intent that starts the main launcher activity.
A list of device sessions.
A location/region designation for language.
Shards test cases into the specified groups of packages, classes, and/or methods. With manual sharding enabled, specifying test targets via environment_variables or in InstrumentationTest is invalid.
Describes a single error or issue with a matrix.
A tag within a manifest. https://developer.android.com/guide/topics/manifest/meta-data-element.html
There is no detailed description.
There is no detailed description.
Skips the starting activity
An opaque binary blob file to install on the device before the test starts.
Screen orientation of the device.
A version-specific information of an Android model.
A version-specific information of an iOS model.
POST /v1/projects/{project_id}/deviceSessions/{device_session_id}:cancel Changes the DeviceSession to state FINISHED and terminates all connections. Canceled sessions are not deleted and can be retrieved or listed by the user until they expire based on the 28 day deletion policy.
POST /v1/projects/{project_id}/deviceSessions
GET /v1/projects/{project_id}/deviceSessions/{device_session_id} Return a DeviceSession, which documents the allocation status and whether the device is allocated. Clients making requests from this API must poll GetDeviceSession.
GET /v1/projects/{project_id}/deviceSessions Lists device Sessions owned by the project user.
PATCH /v1/projects/{projectId}/deviceSessions/deviceSessionId}:updateDeviceSession Updates the current device session to the fields described by the update_mask.
A builder providing access to all methods supported on
project resources.
It is not used directly, but through the
Testing hub.
Cancels unfinished test executions in a test matrix. This call returns immediately and cancellation proceeds asynchronously. If the matrix is already final, this operation will have no effect. May return any of the following canonical error codes: - PERMISSION_DENIED - if the user is not authorized to read project - INVALID_ARGUMENT - if the request is malformed - NOT_FOUND - if the Test Matrix does not exist
Creates and runs a matrix of tests according to the given specifications. Unsupported environments will be returned in the state UNSUPPORTED. A test matrix is limited to use at most 2000 devices in parallel. The returned matrix will not yet contain the executions that will be created for this matrix. Execution creation happens later on and will require a call to GetTestMatrix. May return any of the following canonical error codes: - PERMISSION_DENIED - if the user is not authorized to write to project - INVALID_ARGUMENT - if the request is malformed or if the matrix tries to use too many simultaneous devices.
Checks the status of a test matrix and the executions once they are created. The test matrix will contain the list of test executions to run if and only if the resultStorage.toolResultsExecution fields have been populated. Note: Flaky test executions may be added to the matrix at a later stage. May return any of the following canonical error codes: - PERMISSION_DENIED - if the user is not authorized to read project - INVALID_ARGUMENT - if the request is malformed - NOT_FOUND - if the Test Matrix does not exist
The currently provided software environment on the devices under test.
A file or directory to install on the device before the test starts.
Locations where the results of running the test are stored.
Directs Robo to interact with a specific UI element if it is encountered during the crawl. Currently, Robo can perform text entry or element click.
Message for specifying the start activities to crawl.
The section of an tag. https://developer.android.com/guide/topics/manifest/service-element
A message encapsulating a series of Session states and the time that the DeviceSession first entered those states.
Output only. Details about the shard.
Options for enabling sharding.
Shards test based on previous test case timing records.
A starting intent specified by an action, uri, and categories.
There is no detailed description.
Additional details about the progress of the running test.
A description of a test environment.
Gets the catalog of supported test environments. May return any of the following canonical error codes: - INVALID_ARGUMENT - if the request is malformed - NOT_FOUND - if the environment type does not exist - INTERNAL - if an internal error occurred
A builder providing access to all methods supported on
testEnvironmentCatalog resources.
It is not used directly, but through the
Testing hub.
A single test executed in a single environment.
TestMatrix captures all details about a test. It contains the environment configuration, test specification, test executions and overall state and outcome.
A description of how to set up the Android device prior to running the test.
A description of how to run the test.
Test targets for a shard.
Central instance to access all Testing related resource activities
Represents a tool results execution resource. This has the results of a TestMatrix.
Represents a tool results history resource.
Represents a tool results step resource. This has the results of a TestExecution.
Network emulation parameters.
Uniformly shards test cases given a total number of shards. For instrumentation tests, it will be translated to “-e numShard” and “-e shardIndex” AndroidJUnitRunner arguments. With uniform sharding enabled, specifying either of these sharding arguments via environment_variables is invalid. Based on the sharding mechanism AndroidJUnitRunner uses, there is no guarantee that test cases will be distributed uniformly across all shards.
A tag within a manifest. https://developer.android.com/guide/topics/manifest/uses-feature-element.html
An Xcode version that an iOS version is compatible with.