template <typename BuilderImpl>class WireTableBaseBuilder
Defined at line 1102 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::RunSuiteOptions Build ()Build and return the table. The builder should not be used after this.
bool has_realm_options ()void clear_realm_options ()Clears the realm_options field.
This method should be used sparingly, such as only during tests, as it has
O(number_of_fields) complexity.
::fuchsia_test_manager::wire::RealmOptions & realm_options ()Specifies the realm in which to run the test suite. If this field is not supplied, the
test will run in a hermetic realm inside the test manager. This option is
used by clients that require non-hermetic realms or test realms with custom runners.
BuilderImpl & realm_options (Wrapper_Ignore_Me_< ::fidl::ObjectView< ::fuchsia_test_manager::wire::RealmOptions>> elem)Specifies the realm in which to run the test suite. If this field is not supplied, the
test will run in a hermetic realm inside the test manager. This option is
used by clients that require non-hermetic realms or test realms with custom runners.
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. This value is false by default.
BuilderImpl & run_disabled_tests (bool elem)If set to true, test cases that have been disabled by the test author will
nonetheless be executed. This value is false by default.
bool has_max_concurrent_test_case_runs ()void clear_max_concurrent_test_case_runs ()Clears the max_concurrent_test_case_runs field.
This method should be used sparingly, such as only during tests, as it has
O(number_of_fields) complexity.
uint16_t & max_concurrent_test_case_runs ()Defines the maximum number of test cases to run concurrently. If unspecified, the
test suite component decides this value.
BuilderImpl & max_concurrent_test_case_runs (uint16_t elem)Defines the maximum number of test cases to run concurrently. If unspecified, the
test suite component decides this value.
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 ()Command-line arguments to pass to the test. Test runners decide how to pass these
arguments to tests. This value is an empty vector (no arguments) by default.
BuilderImpl & arguments (Wrapper_Ignore_Me_< ::fidl::ObjectView< ::fidl::VectorView< ::fidl::StringView>>> elem)Command-line arguments to pass to the test. Test runners decide how to pass these
arguments to tests. This value is an empty vector (no arguments) by default.
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 for the entire suite run. If unspecified, there is no timeout, and the suite run
may hang indefinitely.
BuilderImpl & timeout (Wrapper_Ignore_Me_< ::fidl::ObjectView<int64_t>> elem)Timeout for the entire suite run. If unspecified, there is no timeout, and the suite run
may hang indefinitely.
bool has_test_case_filters ()void clear_test_case_filters ()Clears the test_case_filters field.
This method should be used sparingly, such as only during tests, as it has
O(number_of_fields) complexity.
::fidl::VectorView< ::fidl::StringView> & test_case_filters ()Test case filters as glob patterns [https://en.wikipedia.org/wiki/Glob_(programming)].
Negative filters may be specified by prepending '-'. This value is an empty vector
(no filters) by default.
A given test case is run if both of the following are true:
* No positive filters are specfied, or the test case matches one of the positive filters.
* The test case does not match any specified negative filter.
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 & test_case_filters (Wrapper_Ignore_Me_< ::fidl::ObjectView< ::fidl::VectorView< ::fidl::StringView>>> elem)Test case filters as glob patterns [https://en.wikipedia.org/wiki/Glob_(programming)].
Negative filters may be specified by prepending '-'. This value is an empty vector
(no filters) by default.
A given test case is run if both of the following are true:
* No positive filters are specfied, or the test case matches one of the positive filters.
* The test case does not match any specified negative filter.
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_logs_iterator_type ()void clear_logs_iterator_type ()Clears the logs_iterator_type field.
This method should be used sparingly, such as only during tests, as it has
O(number_of_fields) complexity.
::fuchsia_test_manager::wire::LogsIteratorType & logs_iterator_type ()Specifies what kind of iterator the client will use for retrieving logs. This value is
`BATCH` by default.
BuilderImpl & logs_iterator_type (::fuchsia_test_manager::wire::LogsIteratorType elem)Specifies what kind of iterator the client will use for retrieving logs. This value is
`BATCH` by default.
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 to apply when filtering logs from the test suite
component.
BuilderImpl & log_interest (Wrapper_Ignore_Me_< ::fidl::ObjectView< ::fidl::VectorView< ::fuchsia_diagnostics::wire::LogInterestSelector>>> elem)Configures the minimum severity to apply when filtering logs from the test suite
component.
bool has_accumulate_debug_data ()void clear_accumulate_debug_data ()Clears the accumulate_debug_data field.
This method should be used sparingly, such as only during tests, as it has
O(number_of_fields) complexity.
bool & accumulate_debug_data ()If set to true, debug data collected for this run will be accumulated in test manager's
tmp folder with debug data collected in previous runs with this flag set true. Defaults
to false.
This option is used when many tests are run in a batch, and delivering the accumulated
data is more performant than delivering the debug data one test at a time.
BuilderImpl & accumulate_debug_data (bool elem)If set to true, debug data collected for this run will be accumulated in test manager's
tmp folder with debug data collected in previous runs with this flag set true. Defaults
to false.
This option is used when many tests are run in a batch, and delivering the accumulated
data is more performant than delivering the debug data one test at a time.
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.
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.
Protected Methods
void WireTableBaseBuilder< ::fuchsia_test_manager::wire::RunSuiteOptions, BuilderImpl> (::fidl::ObjectView< ::fidl::WireTableFrame< ::fuchsia_test_manager::wire::RunSuiteOptions>> && frame)