API Reference google_api_testing v0.23.0

Modules

API client metadata for GoogleApi.Testing.V1.

API calls for all endpoints tagged ApplicationDetailService.

API calls for all endpoints tagged Projects.

API calls for all endpoints tagged TestEnvironmentCatalog.

Handle Tesla connections for GoogleApi.Testing.V1.

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. Next tag: 30

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 apk archive contents.

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.

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 value, with a zero year, such as an anniversary A year on its own, with zero month and day values A year and month value, with a zero day, such as a credit card expiration date Related types are google.type.TimeOfDay and google.protobuf.Timestamp.

A single device file description.

A single device IP block

List of IP blocks used by the Firebase Test Lab

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.

A reference to a file, used for user inputs.

Response containing the details of the specified Android application APK.

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

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.

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

Attributes

  • downRule (type: GoogleApi.Testing.V1.Model.TrafficRule.t, default: nil) - The emulation rule applying to the download traffic.
  • id (type: String.t, default: nil) - The unique opaque id for this network traffic configuration.
  • upRule (type: GoogleApi.Testing.V1.Model.TrafficRule.t, default: nil) - The emulation rule applying to the upload traffic.

Attributes

  • configurations (type: list(GoogleApi.Testing.V1.Model.NetworkConfiguration.t), default: nil) -

An opaque binary blob file to install on the device before the test starts.

Screen orientation of the device.

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.

A starting intent specified by an action, uri, and categories.

Attributes

  • durationSeconds (type: integer(), default: nil) - Systrace duration in seconds. Should be between 1 and 30 seconds. 0 disables systrace.

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.

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 test, it will be translated to "-e numShard" "-e shardIndex" AndroidJUnitRunner arguments. With uniform sharding enabled, specifying these sharding arguments via environment_variables is invalid.

An Xcode version that an iOS version is compatible with.