drive library
The live half of the verb engine: scenarios' vocabulary executed against a
running app's real binding. For generated entrypoints and the guest
runtime, not for projects to import directly — a project's own tests want
package:flutterware/flutter_test.dart.
Classes
- Drive
-
The live half of the verb engine: scenarios' vocabulary — same targets,
same actionability ladder, same refusal wording — executed against a
running app's real
WidgetsBinding. - DriveStep
- What one drive verb did — the engine half of a journal step. The wire and observation bundle live with the guest extensions, not here.
- LiveSettleResult
- What a bounded wall-clock settle observed.
- Target
- The targets the plain vocabulary cannot express: the ones that need a property other than visible text, a scope, or an index.
- TargetMessages
- The wording of a refusal, flavored per host.
Enums
- TargetFailure
- The four ways the actionability ladder refuses a target.
Functions
-
settleLive(
{Duration budget = const Duration(milliseconds: 800), Duration frameTimeout = const Duration(milliseconds: 250)}) → Future< LiveSettleResult> -
Pumps the live app until nothing is pending or
budgetruns out, and never hangs. -
visibleTextsOf(
WidgetController controller) → List< String> -
Every
TextandEditableTextcurrently in the tree, in tree order — the text projection of the screen an agent reads next to the pixels, and the material of the nothing-matches message. Strings longer thanvisibleTextCapare truncated with a trailing….
Exceptions / Errors
- TargetError
-
A refusal from
TargetResolver— the message is the whole story, written to say what to do rather than dump matching render objects.