Struct google_testing1::AndroidInstrumentationTest

pub struct AndroidInstrumentationTest {
    pub app_bundle: Option<AppBundle>,
    pub test_apk: Option<FileReference>,
    pub test_runner_class: Option<String>,
    pub test_package_id: Option<String>,
    pub app_apk: Option<FileReference>,
    pub app_package_id: Option<String>,
    pub orchestrator_option: Option<String>,
    pub sharding_option: Option<ShardingOption>,
    pub test_targets: Option<Vec<String>>,
}

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 http://developer.android.com/tools/testing/testing_android.html for more information on types of Android tests.

This type is not used in any activity, and only used as part of another schema.

Fields

app_bundle: Option<AppBundle>

A multi-apk app bundle for the application under test.

test_apk: Option<FileReference>

Required. The APK containing the test code to be executed.

test_runner_class: Option<String>

The InstrumentationTestRunner class. The default value is determined by examining the application's manifest.

test_package_id: Option<String>

The java package for the test to be executed. The default value is determined by examining the application's manifest.

app_apk: Option<FileReference>

The APK for the application under test.

app_package_id: Option<String>

The java package for the application under test. The default value is determined by examining the application's manifest.

orchestrator_option: Option<String>

The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not. ** Orchestrator is only compatible with AndroidJUnitRunner version 1.0 or higher! ** Orchestrator offers the following benefits:

• No shared state
• Crashes are isolated
• Logs are scoped per test

See https://developer.android.com/training/testing/junit-runner.html#using-android-test-orchestrator for more information about Android Test Orchestrator.

If not set, the test will be run without the orchestrator.

sharding_option: Option<ShardingOption>

The option to run tests in multiple shards in parallel.

test_targets: Option<Vec<String>>

Each target must be fully qualified with the package name or class name, in one of these formats:

• "package package_name"
• "class package_name.class_name"
• "class package_name.class_name#method_name"

If empty, all targets in the module will be run.

Trait Implementations

impl Clone for AndroidInstrumentationTest

fn clone(&self) -> AndroidInstrumentationTest

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for AndroidInstrumentationTest

fn fmt(&self, f: &mut Formatter) -> Result

Formats the value using the given formatter.

impl Default for AndroidInstrumentationTest

fn default() -> AndroidInstrumentationTest

Returns the "default value" for a type.

impl<'de> Deserialize<'de> for AndroidInstrumentationTest

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error> where
    __D: Deserializer<'de>, 

Deserialize this value from the given Serde deserializer.

impl Part for AndroidInstrumentationTest

impl Serialize for AndroidInstrumentationTest

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error> where
    __S: Serializer, 

Serialize this value into the given Serde serializer.