class RunOptions

Defined at line 3193 of file fidling/gen/sdk/fidl/fuchsia.test.manager/fuchsia.test.manager/cpp/fidl/fuchsia.test.manager/cpp/natural_types.h

Optional additional instructions for executing a test suite.

Public Methods

void RunOptions (Storage_ storage)

void RunOptions ()

Defined at line 3198 of file fidling/gen/sdk/fidl/fuchsia.test.manager/fuchsia.test.manager/cpp/fidl/fuchsia.test.manager/cpp/natural_types.h

void RunOptions (RunOptions && )

Defined at line 3199 of file fidling/gen/sdk/fidl/fuchsia.test.manager/fuchsia.test.manager/cpp/fidl/fuchsia.test.manager/cpp/natural_types.h

void RunOptions (const RunOptions & other)

RunOptions & operator= (RunOptions && )

Defined at line 3200 of file fidling/gen/sdk/fidl/fuchsia.test.manager/fuchsia.test.manager/cpp/fidl/fuchsia.test.manager/cpp/natural_types.h

RunOptions & operator= (const RunOptions & other)

bool operator== (const RunOptions & other)

bool operator!= (const RunOptions & other)

bool IsEmpty ()

const std::optional<bool> & run_disabled_tests ()

If set to true, test cases that have been disabled by the test author

will nonetheless be executed. Defaults to false.

::std::optional<bool> & run_disabled_tests ()

If set to true, test cases that have been disabled by the test author

will nonetheless be executed. Defaults to false.

RunOptions & run_disabled_tests (std::optional<bool> value)

If set to true, test cases that have been disabled by the test author

will nonetheless be executed. Defaults to false.

const std::optional<uint16_t> & parallel ()

Defines maximum number of test cases to run simultaneously.

If unspecified, the default behavior is chosen by the `Suite`

implementation.

::std::optional<uint16_t> & parallel ()

Defines maximum number of test cases to run simultaneously.

If unspecified, the default behavior is chosen by the `Suite`

implementation.

RunOptions & parallel (std::optional<uint16_t> value)

Defines maximum number of test cases to run simultaneously.

If unspecified, the default behavior is chosen by the `Suite`

implementation.

const std::optional< ::std::vector< ::std::string>> & arguments ()

Optional arguments to pass to the test.

Test runners will decide how to pass these arguments to tests.

::std::optional< ::std::vector< ::std::string>> & arguments ()

Optional arguments to pass to the test.

Test runners will decide how to pass these arguments to tests.

RunOptions & arguments (std::optional< ::std::vector< ::std::string>> value)

Optional arguments to pass to the test.

Test runners will decide how to pass these arguments to tests.

const std::optional<int64_t> & timeout ()

Timeout in seconds for the entire suite.

::std::optional<int64_t> & timeout ()

Timeout in seconds for the entire suite.

RunOptions & timeout (std::optional<int64_t> value)

Timeout in seconds for the entire suite.

const std::optional< ::std::vector< ::std::string>> & case_filters_to_run ()

glob case filter. This filter will match based on glob pattern

[https://en.wikipedia.org/wiki/Glob_(programming)].

Only test cases matching at least one pattern will be run. In

addition, negative filters may be specified by prepending '-'. When

negative filters are specified, test cases matching the negative filter

are excluded.

The behavior of combinations of these filters is as follows:

* When no filters are specified, all test cases are run.

* When only positive filters are specified, test cases that match at

least one filter are run.

* When only negative filters are specified, test cases that match none

of the filters are run.

* When both positive and negative filters are specified, test cases

that match at least one positive filter, but do not match any

negative filters, are run.

For example, given that a suite has the test cases `Foo.Test1`,

`Foo.Test2`, `Bar.Test1`, and `Bar.Test2`:

* The filters `["Foo.*"]` will execute `Foo.Test1` and `Foo.Test2`.

* The filters `["-Foo.*"]` will execute `Bar.Test1` and `Bar.Test2`.

* The filters `["Foo.*", "-*.Test1"]` will execute `Foo.Test2`.

::std::optional< ::std::vector< ::std::string>> & case_filters_to_run ()

glob case filter. This filter will match based on glob pattern

[https://en.wikipedia.org/wiki/Glob_(programming)].

Only test cases matching at least one pattern will be run. In

addition, negative filters may be specified by prepending '-'. When

negative filters are specified, test cases matching the negative filter

are excluded.

The behavior of combinations of these filters is as follows:

* When no filters are specified, all test cases are run.

* When only positive filters are specified, test cases that match at

least one filter are run.

* When only negative filters are specified, test cases that match none

of the filters are run.

* When both positive and negative filters are specified, test cases

that match at least one positive filter, but do not match any

negative filters, are run.

For example, given that a suite has the test cases `Foo.Test1`,

`Foo.Test2`, `Bar.Test1`, and `Bar.Test2`:

* The filters `["Foo.*"]` will execute `Foo.Test1` and `Foo.Test2`.

* The filters `["-Foo.*"]` will execute `Bar.Test1` and `Bar.Test2`.

* The filters `["Foo.*", "-*.Test1"]` will execute `Foo.Test2`.

RunOptions & case_filters_to_run (std::optional< ::std::vector< ::std::string>> value)

glob case filter. This filter will match based on glob pattern

[https://en.wikipedia.org/wiki/Glob_(programming)].

Only test cases matching at least one pattern will be run. In

addition, negative filters may be specified by prepending '-'. When

negative filters are specified, test cases matching the negative filter

are excluded.

The behavior of combinations of these filters is as follows:

* When no filters are specified, all test cases are run.

* When only positive filters are specified, test cases that match at

least one filter are run.

* When only negative filters are specified, test cases that match none

of the filters are run.

* When both positive and negative filters are specified, test cases

that match at least one positive filter, but do not match any

negative filters, are run.

For example, given that a suite has the test cases `Foo.Test1`,

`Foo.Test2`, `Bar.Test1`, and `Bar.Test2`:

* The filters `["Foo.*"]` will execute `Foo.Test1` and `Foo.Test2`.

* The filters `["-Foo.*"]` will execute `Bar.Test1` and `Bar.Test2`.

* The filters `["Foo.*", "-*.Test1"]` will execute `Foo.Test2`.

const std::optional< ::fuchsia_test_manager::LogsIteratorOption> & log_iterator ()

Defines what kind of log iterator the client supports. Default value is

Batch iterator.

::std::optional< ::fuchsia_test_manager::LogsIteratorOption> & log_iterator ()

Defines what kind of log iterator the client supports. Default value is

Batch iterator.

RunOptions & log_iterator (std::optional< ::fuchsia_test_manager::LogsIteratorOption> value)

Defines what kind of log iterator the client supports. Default value is

Batch iterator.

const std::optional< ::std::vector< ::fuchsia_diagnostics::LogInterestSelector>> & log_interest ()

Configures the minimum severity for the components under test.

::std::optional< ::std::vector< ::fuchsia_diagnostics::LogInterestSelector>> & log_interest ()

Configures the minimum severity for the components under test.

RunOptions & log_interest (std::optional< ::std::vector< ::fuchsia_diagnostics::LogInterestSelector>> value)

Configures the minimum severity for the components under test.

const std::optional<bool> & break_on_failure ()

If true, the test runner should halt (if supported) the test suite when

a failure is encountered such that a debugger may attach to the process

in the future. Test runners may safely ignore this if they do not

support stopping running test suites.

::std::optional<bool> & break_on_failure ()

If true, the test runner should halt (if supported) the test suite when

a failure is encountered such that a debugger may attach to the process

in the future. Test runners may safely ignore this if they do not

support stopping running test suites.

RunOptions & break_on_failure (std::optional<bool> value)

If true, the test runner should halt (if supported) the test suite when

a failure is encountered such that a debugger may attach to the process

in the future. Test runners may safely ignore this if they do not

support stopping running test suites.

const std::optional<bool> & no_exception_channel ()

If true, indicates the test creates an exception channel. In this case, the test manager

will refrain from creating its own exception channels to avoid conflicts. Default value

is false.

::std::optional<bool> & no_exception_channel ()

If true, indicates the test creates an exception channel. In this case, the test manager

will refrain from creating its own exception channels to avoid conflicts. Default value

is false.

RunOptions & no_exception_channel (std::optional<bool> value)

If true, indicates the test creates an exception channel. In this case, the test manager

will refrain from creating its own exception channels to avoid conflicts. Default value

is false.

void RunOptions (::fidl::internal::DefaultConstructPossiblyInvalidObjectTag )

Friends

class MemberVisitor

class NaturalTableCodingTraits