Describes an automated test step. Custom test steps must register with the
TestStepRegistry and create an instance of this class. This binds the
input form, any quick-add values, the help and title translation entities,
and the requirements of the step that determines if the step will show or
not given the current constraints.
Test store that can be used to read and write tests from / to the clipboard.
The clipboard may contain one or more tests when attempting to load from the
clipboard. [...]
Technically not a step but is instead a place where testers can put comments
into the test. Comments will be emitted into the logs in addition to being
viewable in the test editor itself.
A command class intended to be extended to provide comamnds and controls
events between the backend server, the device drivers, and the devices
themselves. [...]
Command to tell the remote connection that the socket is about to be
disconnected by the sender. If the complete attribute is true then the
session is also being terminated. Otherwise, if the receiver initiates a
reconnection then the session will be resumed.
Command that can be sent to the server simply to check if it is online and
still properly responding to commands. This is one of the only commands
that can traditionally be sent without needing authentication.
Command to list the devices currently online for testing. Use the
availableOnly flag to filter between devices that are online, but actively
in use, vs ones that are both online and available to run tests.
Command sent to let the other side know the connection is still ongoing and
that the sender is still actively processing commands. Devices may
optionally provide information about the device and the device's test state
as part of these periodic check ins.
Command sent by a test driver to reserve a test device. If this is ack'd
with a successful response, the device will now accept commands from the
test driver.
Command to start a log stream from the device to the test driver. When
accepted the device will send a CommandAck with this command's id and the
log information in the response.
Command instructing the device to send a screenshot periodically to the
driver. The default implementation will only send screenshots that have
changed since the previous one rather than constantly sending the same
screenshot over and over.
Set of gestures that Testable widgets will respond to when the
TestRunner is enabled. Applications can (should) set the gestures based
on their typical usage patterns such that the gestures have a minimal
amount of conflict with application based gestures. [...]
Controller that is used to provide information for the Testable. This
includes information such as what gestures to respond to as well as how to
render the global and / or individual overlays.
Page that displays all the test steps for the current test. This will allow
the reordering, clearing, editing, and saving of the steps w/in a current
test.
The result for an executed test step. It's important to note that times in
the report are relative to each run and should not be thought of in absolute
terms. Too many variables such as animations, built in delays, etc. can
cause an individual test step to take 1-2 seconds despite a perceived
expectation that something should be sub-second. When comparing the times,
do so only across tests and look for trends. Avoid the temptation to look
at the times as absolutes.
Describes a single step in a test. A test step is required to have an id
which is the human-readable key for the test step. It has an optional
image that is a capture of the widget for reference. Finally, it has an
optional set of values that configure the step.
Registry that allows for the binding of custom test steps. There exists a
default instance that will always be used when a custom instance is not
available. [...]
ChildWidgetBuilder that can be used to wrap child widgets with a
Testable widget. This particular builder will only wrap the child if
the child has a ValueKey set on it. In that case, the Testable will
be given the a new ValueKey with the value from the child's key prefixed
with value_key_.
Reader to load a golden image from a data store and return it for
comparison. If testVersion is omitted, this should default to the highest
version listed in the golden file.
A resolver that takes a variable name to a value. If this resolver does not
recognize the variable, it must throw an UnknownVariableException rather
than returning null. A null return value will be interpreted as the
variable was explicitly resolved to null.
