Struct google_testing1::api::AndroidTestLoop
source · pub struct AndroidTestLoop {
pub app_apk: Option<FileReference>,
pub app_bundle: Option<AppBundle>,
pub app_package_id: Option<String>,
pub scenario_labels: Option<Vec<String>>,
pub scenarios: Option<Vec<i32>>,
}Expand description
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.
This type is not used in any activity, and only used as part of another schema.
Fields§
§app_apk: Option<FileReference>The APK for the application under test.
app_bundle: Option<AppBundle>A multi-apk app bundle for the application under test.
app_package_id: Option<String>The java package for the application under test. The default is determined by examining the application’s manifest.
scenario_labels: Option<Vec<String>>The list of scenario labels that should be run during the test. The scenario labels should map to labels defined in the application’s manifest. For example, player_experience and com.google.test.loops.player_experience add all of the loops labeled in the manifest with the com.google.test.loops.player_experience name to the execution. Scenarios can also be specified in the scenarios field.
scenarios: Option<Vec<i32>>The list of scenarios that should be run during the test. The default is all test loops, derived from the application’s manifest.
Trait Implementations§
source§impl Clone for AndroidTestLoop
impl Clone for AndroidTestLoop
source§fn clone(&self) -> AndroidTestLoop
fn clone(&self) -> AndroidTestLoop
1.0.0 · source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more