template <typename BuilderImpl>

class WireTableBaseBuilder

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

Public Methods

::fuchsia_test_manager::wire::RunOptions Build ()

Build and return the table. The builder should not be used after this.

bool has_run_disabled_tests ()

void clear_run_disabled_tests ()

Clears the run_disabled_tests field.

This method should be used sparingly, such as only during tests, as it has

O(number_of_fields) complexity.

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.

BuilderImpl & run_disabled_tests (bool elem)

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

will nonetheless be executed. Defaults to false.

bool has_parallel ()

void clear_parallel ()

Clears the parallel field.

This method should be used sparingly, such as only during tests, as it has

O(number_of_fields) complexity.

uint16_t & parallel ()

Defines maximum number of test cases to run simultaneously.

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

implementation.

BuilderImpl & parallel (uint16_t elem)

Defines maximum number of test cases to run simultaneously.

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

implementation.

bool has_arguments ()

void clear_arguments ()

Clears the arguments field.

This method should be used sparingly, such as only during tests, as it has

O(number_of_fields) complexity.

::fidl::VectorView< ::fidl::StringView> & arguments ()

Optional arguments to pass to the test.

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

BuilderImpl & arguments (Wrapper_Ignore_Me_< ::fidl::ObjectView< ::fidl::VectorView< ::fidl::StringView>>> elem)

Optional arguments to pass to the test.

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

bool has_timeout ()

void clear_timeout ()

Clears the timeout field.

This method should be used sparingly, such as only during tests, as it has

O(number_of_fields) complexity.

int64_t & timeout ()

Timeout in seconds for the entire suite.

BuilderImpl & timeout (Wrapper_Ignore_Me_< ::fidl::ObjectView<int64_t>> elem)

Timeout in seconds for the entire suite.

bool has_case_filters_to_run ()

void clear_case_filters_to_run ()

Clears the case_filters_to_run field.

This method should be used sparingly, such as only during tests, as it has

O(number_of_fields) complexity.

::fidl::VectorView< ::fidl::StringView> & 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`.

BuilderImpl & case_filters_to_run (Wrapper_Ignore_Me_< ::fidl::ObjectView< ::fidl::VectorView< ::fidl::StringView>>> elem)

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`.

bool has_log_iterator ()

void clear_log_iterator ()

Clears the log_iterator field.

This method should be used sparingly, such as only during tests, as it has

O(number_of_fields) complexity.

::fuchsia_test_manager::wire::LogsIteratorOption & log_iterator ()

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

Batch iterator.

BuilderImpl & log_iterator (::fuchsia_test_manager::wire::LogsIteratorOption elem)

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

Batch iterator.

bool has_log_interest ()

void clear_log_interest ()

Clears the log_interest field.

This method should be used sparingly, such as only during tests, as it has

O(number_of_fields) complexity.

::fidl::VectorView< ::fuchsia_diagnostics::wire::LogInterestSelector> & log_interest ()

Configures the minimum severity for the components under test.

BuilderImpl & log_interest (Wrapper_Ignore_Me_< ::fidl::ObjectView< ::fidl::VectorView< ::fuchsia_diagnostics::wire::LogInterestSelector>>> elem)

Configures the minimum severity for the components under test.

bool has_break_on_failure ()

void clear_break_on_failure ()

Clears the break_on_failure field.

This method should be used sparingly, such as only during tests, as it has

O(number_of_fields) complexity.

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.

BuilderImpl & break_on_failure (bool elem)

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.

bool has_no_exception_channel ()

void clear_no_exception_channel ()

Clears the no_exception_channel field.

This method should be used sparingly, such as only during tests, as it has

O(number_of_fields) complexity.

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.

BuilderImpl & no_exception_channel (bool elem)

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.

Protected Methods

void WireTableBaseBuilder< ::fuchsia_test_manager::wire::RunOptions, BuilderImpl> (::fidl::ObjectView< ::fidl::WireTableFrame< ::fuchsia_test_manager::wire::RunOptions>> && frame)

Records

```
class Wrapper_Ignore_Me_
```