Package-level declarations
Types
Identifies an account and how to log into it.
A list of Android device configurations in which the test is to be executed.
A single Android device.
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 test of an android application that explores the application on a virtual or physical Android Device, finding culprits and crashes as it goes.
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.
An Android package file to install.
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.
Key-value pair of detailed information about the client which invoked the test. Examples: {'Version', '1.0'}, {'Release Track', 'BETA'}.
Information about the client which invoked the test.
A single device file description.
The matrix of environments in which the test is to be executed.
The environment in which the test is run.
A key-value pair passed as an environment variable to the test.
A reference to a file, used for user inputs.
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).
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 single iOS device.
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.
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.
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.
An opaque binary blob file to install on the device before the test starts.
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.
Options for enabling sharding.
Output only. Details about the shard.
Shards test based on previous test case timing records.
A starting intent specified by an action, uri, and categories.
Additional details about the progress of the running test.
A single test executed in a single environment.
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. 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.
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.