#[non_exhaustive]pub struct ScheduleRunTest {
pub type: TestType,
pub test_package_arn: Option<String>,
pub test_spec_arn: Option<String>,
pub filter: Option<String>,
pub parameters: Option<HashMap<String, String>>,
}
Expand description
Represents test settings. This data structure is passed in as the test parameter to ScheduleRun. For an example of the JSON request syntax, see ScheduleRun
.
Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. }
syntax; cannot be matched against without a wildcard ..
; and struct update syntax will not work.type: TestType
The test's type.
Must be one of the following values:
-
BUILTIN_FUZZ
-
APPIUM_JAVA_JUNIT
-
APPIUM_JAVA_TESTNG
-
APPIUM_PYTHON
-
APPIUM_NODE
-
APPIUM_RUBY
-
APPIUM_WEB_JAVA_JUNIT
-
APPIUM_WEB_JAVA_TESTNG
-
APPIUM_WEB_PYTHON
-
APPIUM_WEB_NODE
-
APPIUM_WEB_RUBY
-
INSTRUMENTATION
-
XCTEST
-
XCTEST_UI
test_package_arn: Option<String>
The ARN of the uploaded test to be run.
test_spec_arn: Option<String>
The ARN of the YAML-formatted test specification.
filter: Option<String>
The test's filter.
parameters: Option<HashMap<String, String>>
The test's parameters, such as test framework parameters and fixture settings. Parameters are represented by name-value pairs of strings.
For all tests:
-
app_performance_monitoring
: Performance monitoring is enabled by default. Set this parameter to false to disable it.
For Appium tests (all types):
-
appium_version: The Appium version. Currently supported values are 1.6.5 (and later), latest, and default.
-
latest runs the latest Appium version supported by Device Farm (1.9.1).
-
For default, Device Farm selects a compatible version of Appium for the device. The current behavior is to run 1.7.2 on Android devices and iOS 9 and earlier and 1.7.2 for iOS 10 and later.
-
This behavior is subject to change.
-
For fuzz tests (Android only):
-
event_count: The number of events, between 1 and 10000, that the UI fuzz test should perform.
-
throttle: The time, in ms, between 0 and 1000, that the UI fuzz test should wait between events.
-
seed: A seed to use for randomizing the UI fuzz test. Using the same seed value between tests ensures identical event sequences.
For Instrumentation:
-
filter: A test filter string. Examples:
-
Running a single test case:
com.android.abc.Test1
-
Running a single test:
com.android.abc.Test1#smoke
-
Running multiple tests:
com.android.abc.Test1,com.android.abc.Test2
-
For XCTest and XCTestUI:
-
filter: A test filter string. Examples:
-
Running a single test class:
LoginTests
-
Running a multiple test classes:
LoginTests,SmokeTests
-
Running a single test:
LoginTests/testValid
-
Running multiple tests:
LoginTests/testValid,LoginTests/testInvalid
-
Implementations§
Source§impl ScheduleRunTest
impl ScheduleRunTest
Sourcepub fn type(&self) -> &TestType
pub fn type(&self) -> &TestType
The test's type.
Must be one of the following values:
-
BUILTIN_FUZZ
-
APPIUM_JAVA_JUNIT
-
APPIUM_JAVA_TESTNG
-
APPIUM_PYTHON
-
APPIUM_NODE
-
APPIUM_RUBY
-
APPIUM_WEB_JAVA_JUNIT
-
APPIUM_WEB_JAVA_TESTNG
-
APPIUM_WEB_PYTHON
-
APPIUM_WEB_NODE
-
APPIUM_WEB_RUBY
-
INSTRUMENTATION
-
XCTEST
-
XCTEST_UI
Sourcepub fn test_package_arn(&self) -> Option<&str>
pub fn test_package_arn(&self) -> Option<&str>
The ARN of the uploaded test to be run.
Sourcepub fn test_spec_arn(&self) -> Option<&str>
pub fn test_spec_arn(&self) -> Option<&str>
The ARN of the YAML-formatted test specification.
Sourcepub fn parameters(&self) -> Option<&HashMap<String, String>>
pub fn parameters(&self) -> Option<&HashMap<String, String>>
The test's parameters, such as test framework parameters and fixture settings. Parameters are represented by name-value pairs of strings.
For all tests:
-
app_performance_monitoring
: Performance monitoring is enabled by default. Set this parameter to false to disable it.
For Appium tests (all types):
-
appium_version: The Appium version. Currently supported values are 1.6.5 (and later), latest, and default.
-
latest runs the latest Appium version supported by Device Farm (1.9.1).
-
For default, Device Farm selects a compatible version of Appium for the device. The current behavior is to run 1.7.2 on Android devices and iOS 9 and earlier and 1.7.2 for iOS 10 and later.
-
This behavior is subject to change.
-
For fuzz tests (Android only):
-
event_count: The number of events, between 1 and 10000, that the UI fuzz test should perform.
-
throttle: The time, in ms, between 0 and 1000, that the UI fuzz test should wait between events.
-
seed: A seed to use for randomizing the UI fuzz test. Using the same seed value between tests ensures identical event sequences.
For Instrumentation:
-
filter: A test filter string. Examples:
-
Running a single test case:
com.android.abc.Test1
-
Running a single test:
com.android.abc.Test1#smoke
-
Running multiple tests:
com.android.abc.Test1,com.android.abc.Test2
-
For XCTest and XCTestUI:
-
filter: A test filter string. Examples:
-
Running a single test class:
LoginTests
-
Running a multiple test classes:
LoginTests,SmokeTests
-
Running a single test:
LoginTests/testValid
-
Running multiple tests:
LoginTests/testValid,LoginTests/testInvalid
-
Source§impl ScheduleRunTest
impl ScheduleRunTest
Sourcepub fn builder() -> ScheduleRunTestBuilder
pub fn builder() -> ScheduleRunTestBuilder
Creates a new builder-style object to manufacture ScheduleRunTest
.
Trait Implementations§
Source§impl Clone for ScheduleRunTest
impl Clone for ScheduleRunTest
Source§fn clone(&self) -> ScheduleRunTest
fn clone(&self) -> ScheduleRunTest
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl Debug for ScheduleRunTest
impl Debug for ScheduleRunTest
Source§impl PartialEq for ScheduleRunTest
impl PartialEq for ScheduleRunTest
impl StructuralPartialEq for ScheduleRunTest
Auto Trait Implementations§
impl Freeze for ScheduleRunTest
impl RefUnwindSafe for ScheduleRunTest
impl Send for ScheduleRunTest
impl Sync for ScheduleRunTest
impl Unpin for ScheduleRunTest
impl UnwindSafe for ScheduleRunTest
Blanket Implementations§
Source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
Source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Source§impl<T> CloneToUninit for Twhere
T: Clone,
impl<T> CloneToUninit for Twhere
T: Clone,
Source§impl<T> Instrument for T
impl<T> Instrument for T
Source§fn instrument(self, span: Span) -> Instrumented<Self>
fn instrument(self, span: Span) -> Instrumented<Self>
Source§fn in_current_span(self) -> Instrumented<Self>
fn in_current_span(self) -> Instrumented<Self>
Source§impl<T> IntoEither for T
impl<T> IntoEither for T
Source§fn into_either(self, into_left: bool) -> Either<Self, Self>
fn into_either(self, into_left: bool) -> Either<Self, Self>
self
into a Left
variant of Either<Self, Self>
if into_left
is true
.
Converts self
into a Right
variant of Either<Self, Self>
otherwise. Read moreSource§fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
self
into a Left
variant of Either<Self, Self>
if into_left(&self)
returns true
.
Converts self
into a Right
variant of Either<Self, Self>
otherwise. Read moreSource§impl<T> Paint for Twhere
T: ?Sized,
impl<T> Paint for Twhere
T: ?Sized,
Source§fn fg(&self, value: Color) -> Painted<&T>
fn fg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self
with the foreground set to
value
.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like red()
and
green()
, which have the same functionality but are
pithier.
§Example
Set foreground color to white using fg()
:
use yansi::{Paint, Color};
painted.fg(Color::White);
Set foreground color to white using white()
.
use yansi::Paint;
painted.white();
Source§fn bright_black(&self) -> Painted<&T>
fn bright_black(&self) -> Painted<&T>
Returns self
with the
fg()
set to
Color::BrightBlack
.
§Example
println!("{}", value.bright_black());
Source§fn bright_red(&self) -> Painted<&T>
fn bright_red(&self) -> Painted<&T>
Source§fn bright_green(&self) -> Painted<&T>
fn bright_green(&self) -> Painted<&T>
Returns self
with the
fg()
set to
Color::BrightGreen
.
§Example
println!("{}", value.bright_green());
Source§fn bright_yellow(&self) -> Painted<&T>
fn bright_yellow(&self) -> Painted<&T>
Returns self
with the
fg()
set to
Color::BrightYellow
.
§Example
println!("{}", value.bright_yellow());
Source§fn bright_blue(&self) -> Painted<&T>
fn bright_blue(&self) -> Painted<&T>
Source§fn bright_magenta(&self) -> Painted<&T>
fn bright_magenta(&self) -> Painted<&T>
Returns self
with the
fg()
set to
Color::BrightMagenta
.
§Example
println!("{}", value.bright_magenta());
Source§fn bright_cyan(&self) -> Painted<&T>
fn bright_cyan(&self) -> Painted<&T>
Source§fn bright_white(&self) -> Painted<&T>
fn bright_white(&self) -> Painted<&T>
Returns self
with the
fg()
set to
Color::BrightWhite
.
§Example
println!("{}", value.bright_white());
Source§fn bg(&self, value: Color) -> Painted<&T>
fn bg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self
with the background set to
value
.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like on_red()
and
on_green()
, which have the same functionality but
are pithier.
§Example
Set background color to red using fg()
:
use yansi::{Paint, Color};
painted.bg(Color::Red);
Set background color to red using on_red()
.
use yansi::Paint;
painted.on_red();
Source§fn on_primary(&self) -> Painted<&T>
fn on_primary(&self) -> Painted<&T>
Source§fn on_magenta(&self) -> Painted<&T>
fn on_magenta(&self) -> Painted<&T>
Source§fn on_bright_black(&self) -> Painted<&T>
fn on_bright_black(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightBlack
.
§Example
println!("{}", value.on_bright_black());
Source§fn on_bright_red(&self) -> Painted<&T>
fn on_bright_red(&self) -> Painted<&T>
Source§fn on_bright_green(&self) -> Painted<&T>
fn on_bright_green(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightGreen
.
§Example
println!("{}", value.on_bright_green());
Source§fn on_bright_yellow(&self) -> Painted<&T>
fn on_bright_yellow(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightYellow
.
§Example
println!("{}", value.on_bright_yellow());
Source§fn on_bright_blue(&self) -> Painted<&T>
fn on_bright_blue(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightBlue
.
§Example
println!("{}", value.on_bright_blue());
Source§fn on_bright_magenta(&self) -> Painted<&T>
fn on_bright_magenta(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightMagenta
.
§Example
println!("{}", value.on_bright_magenta());
Source§fn on_bright_cyan(&self) -> Painted<&T>
fn on_bright_cyan(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightCyan
.
§Example
println!("{}", value.on_bright_cyan());
Source§fn on_bright_white(&self) -> Painted<&T>
fn on_bright_white(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightWhite
.
§Example
println!("{}", value.on_bright_white());
Source§fn attr(&self, value: Attribute) -> Painted<&T>
fn attr(&self, value: Attribute) -> Painted<&T>
Enables the styling Attribute
value
.
This method should be used rarely. Instead, prefer to use
attribute-specific builder methods like bold()
and
underline()
, which have the same functionality
but are pithier.
§Example
Make text bold using attr()
:
use yansi::{Paint, Attribute};
painted.attr(Attribute::Bold);
Make text bold using using bold()
.
use yansi::Paint;
painted.bold();
Source§fn underline(&self) -> Painted<&T>
fn underline(&self) -> Painted<&T>
Returns self
with the
attr()
set to
Attribute::Underline
.
§Example
println!("{}", value.underline());
Source§fn rapid_blink(&self) -> Painted<&T>
fn rapid_blink(&self) -> Painted<&T>
Returns self
with the
attr()
set to
Attribute::RapidBlink
.
§Example
println!("{}", value.rapid_blink());
Source§fn quirk(&self, value: Quirk) -> Painted<&T>
fn quirk(&self, value: Quirk) -> Painted<&T>
Enables the yansi
Quirk
value
.
This method should be used rarely. Instead, prefer to use quirk-specific
builder methods like mask()
and
wrap()
, which have the same functionality but are
pithier.
§Example
Enable wrapping using .quirk()
:
use yansi::{Paint, Quirk};
painted.quirk(Quirk::Wrap);
Enable wrapping using wrap()
.
use yansi::Paint;
painted.wrap();
Source§fn clear(&self) -> Painted<&T>
👎Deprecated since 1.0.1: renamed to resetting()
due to conflicts with Vec::clear()
.
The clear()
method will be removed in a future release.
fn clear(&self) -> Painted<&T>
resetting()
due to conflicts with Vec::clear()
.
The clear()
method will be removed in a future release.Source§fn whenever(&self, value: Condition) -> Painted<&T>
fn whenever(&self, value: Condition) -> Painted<&T>
Conditionally enable styling based on whether the Condition
value
applies. Replaces any previous condition.
See the crate level docs for more details.
§Example
Enable styling painted
only when both stdout
and stderr
are TTYs:
use yansi::{Paint, Condition};
painted.red().on_yellow().whenever(Condition::STDOUTERR_ARE_TTY);