Struct google_testing1::api::TestSetup
source · pub struct TestSetup {
pub account: Option<Account>,
pub additional_apks: Option<Vec<Apk>>,
pub directories_to_pull: Option<Vec<String>>,
pub dont_autogrant_permissions: Option<bool>,
pub environment_variables: Option<Vec<EnvironmentVariable>>,
pub files_to_push: Option<Vec<DeviceFile>>,
pub network_profile: Option<String>,
pub systrace: Option<SystraceSetup>,
}Expand description
A description of how to set up the Android device prior to running the test.
This type is not used in any activity, and only used as part of another schema.
Fields§
§account: Option<Account>The device will be logged in on this account for the duration of the test.
additional_apks: Option<Vec<Apk>>APKs to install in addition to those being directly tested. Currently capped at 100.
directories_to_pull: Option<Vec<String>>List of directories on the device to upload to GCS at the end of the test; they must be absolute paths under /sdcard, /storage or /data/local/tmp. Path names are restricted to characters a-z A-Z 0-9 _ - . + and / Note: The paths /sdcard and /data will be made available and treated as implicit path substitutions. E.g. if /sdcard on a particular device does not map to external storage, the system will replace it with the external storage path prefix for that device.
dont_autogrant_permissions: Option<bool>Whether to prevent all runtime permissions to be granted at app install
environment_variables: Option<Vec<EnvironmentVariable>>Environment variables to set for the test (only applicable for instrumentation tests).
files_to_push: Option<Vec<DeviceFile>>List of files to push to the device before starting the test.
network_profile: Option<String>The network traffic profile used for running the test. Available network profiles can be queried by using the NETWORK_CONFIGURATION environment type when calling TestEnvironmentDiscoveryService.GetTestEnvironmentCatalog.
systrace: Option<SystraceSetup>Deprecated: Systrace uses Python 2 which has been sunset 2020-01-01. Support of Systrace may stop at any time, at which point no Systrace file will be provided in the results. Systrace configuration for the run. If set a systrace will be taken, starting on test start and lasting for the configured duration. The systrace file thus obtained is put in the results bucket together with the other artifacts from the run.