Crate fidl_fuchsia_test_manager
source ·Macros
Pattern that matches an unknown
Artifact member.Pattern that matches an unknown
CaseStatus member.Pattern that matches an unknown
LaunchError member.Pattern that matches an unknown
LogsIteratorOption member.Pattern that matches an unknown
LogsIterator member.Pattern that matches an unknown
RunEventPayload member.Pattern that matches an unknown
SuiteEventPayload member.Pattern that matches an unknown
SuiteStatus member.Pattern that matches an unknown
Syslog member.Structs
Information about the enumerated test case.
A Stream of incoming requests for CaseIterator
Arbitrary artifacts produced by a test.
A Stream of incoming requests for DebugDataIterator
A handle to a directory and a token used to indicate when the client has
completed inspecting the directory. The server end will retain all resources,
such as subdirectories and files, within |directory| while |token| is open.
|token| is used instead of observing the |directory| channel directly as it
is possible to clone and open new channels to the same directory.
A Stream of incoming requests for Query
A Stream of incoming requests for RunBuilder
A Stream of incoming requests for RunController
Optional additional instructions for executing a test suite.
Optional instructions for how to execute and schedule suites in the test run.
A Stream of incoming requests for SuiteController
Enums
Iterator for listing available test cases.
Represent status of a test case run execution.
An iterator protocol over which a client may retrieve debug data information.
Error for
LaunchSuite call.Holds the server end of an iterator over the isolated logs of a test.
Option which specifies which kind of iterator the client supports
This is the entry point of running test suites. A test “run” consists of
multiple test “suites” which consists of running multiple “test cases”.
The server end will disconnect after all the suite runs have finished and
the events are drained.
If the client disconnects, the tests will be terminated immediately and all
results discarded.
Various events for run execution. The first event for a test run will
always be
run_started. run_stopped fires when the test run stops
and will always fire after run_started.The server end will disconnect after all the suite run has finished and
all events are drained. If the client disconnects, the suite will be
terminated immediately and all results discarded.
Various events for test execution.
Represents status of a suite run. This ordering is the explicit ordering of
preference, from lowest priority to highest priority.
for example, if all Cases PASSED except one that FAILED, the status for the
whole suite will be FAILED.