Identifies an account and how to log into it.
A message to an ADB server.
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.
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.
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 <intent-name> 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 Bundle file format, containing a BundleConfig.pb file,
a base module directory, zero or more dynamic feature module directories.
The request object for cancelling a Device Session.
Request to stop running all of the tests in the specified matrix.
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’}.
Message signifying that the stream closed.
A Request for the device session from the session service.
Request to submit a matrix of tests for execution.
A single device file description.
A single device IP block
List of IP blocks used by the Firebase Test Lab
A message returned from a device.
Protobuf message describing the device message, used from several RPCs.
Denotes whether Direct Access is supported, and by which client versions.
Data about the relative number of devices running a
given configuration of the Android platform.
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.
Message signifying that the stream failed to open
A reference to a file, used for user inputs.
A request to get the details of an Android application.
Response containing the details of the specified Android application.
The request object for a Device Session.
Request to list the currently supported values for an environment type.
Request to get the Test Matrix with the given id.
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).
Details behind an invalid request.
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.
Request a list of device sessions in the provided parent matching the given
filter.
A list of device sessions.
A location/region designation for language.
Shards test cases into the specified groups of packages, classes, and/or
methods.
Describes a single error or issue with a matrix.
Skips the starting activity
An opaque binary blob file to install on the device before the test starts.
Message signifying that the stream is open
Message for opening a new stream.
Screen orientation of the device.
A version-specific information of an Android model.
A version-specific information of an iOS model.
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.
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.
A StatusUpdate message given over the ADB protocol for the device state.
Data for a stream.
The result of a stream.
Additional details about the progress of the running test.
A description of a test environment.
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.
Represents a tool results execution resource.
Represents a tool results history resource.
Represents a tool results step resource.
Network emulation parameters.
Uniformly shards test cases given a total number of shards.
The request object for the UpdateDeviceSession RPC.
An Xcode version that an iOS version is compatible with.