automated_testing_framework_models library Null safety

Classes

AbortTestCommand
AnnounceDeviceCommand
AnnounceDriverCommand
AsyncTestLoader
Loader that loads the test from an async callback.
BaseSize
CancelToken
Token can can be used to cancel test steps.
ChallengeCommand
ChallengeResponseCommand
CommandAck
CommandResponse
ConnectedDevice
DeviceCommand
DriverSignatureHelper
Helper class to generate signatures for use by test drivers as well as driven devices.
GoldenTestImages
GoodbyeCommand
JsonLogRecord
ListDevicesCommand
ListDevicesResponse
LogResponse
MemoryTestLoader
Loader that loads the test from an in-memory object.
PendingTest
Describes a pending test. The pending test should describe the name, number of steps, version, and provide a loader to load the full test details.
PingCommand
ReleaseDeviceCommand
RequestScreenshotCommand
ReserveDeviceCommand
RunTestCommand
ScreenshotResponse
StartLogStreamCommand
StartScreenshotStreamCommand
StopLogStreamCommand
StopScreenshotStreamCommand
Test
PODO for a test that can be executed.
TestableGestureAction
Built-in actions that are available to be set either by-default or by-widget on Testable widgets.
TestableGestures
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. [...]
TestAppSettings
Provides settings for the test app that apply globaly. Any settings set here will globally override values from other parts of the framework.
TestControllerState
TestDeviceCommunicator
Interface that plugins may implement to provide their own solution for communicating with external sources.
TestDeviceInfo
Container class for the device information for the device the test is being executed on.
TestDeviceStatus
TestImage
Represents an image from a test.
TestLoader
Interface for loading tests.
TestReport
Represents a report from a test run.
TestReportMetadata
TestReportStep
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.
TestStatusResponse
TestStep
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.
TestStepDelays
Defines the various delays and timeouts involved when executing tests.
TestSuiteReport
A summary of all the results from all the runs in a single test suite.
TestSuiteResult
Represents a the summarized results from a single test run within a larger test suite.

Typedefs

ConnectionChangedCallback = Future<void> Function(TestDeviceCommunicator communicator, bool connected)
DeviceCommandHandler = Future<CommandAck> Function(DeviceCommand command)