- 04 Mar, 2017 1 commit
-
-
Chris Bracken authored
-
- 28 Feb, 2017 1 commit
-
-
Yegor authored
-
- 23 Feb, 2017 1 commit
-
-
Alexandre Ardhuin authored
-
- 17 Feb, 2017 2 commits
-
-
Adam Barth authored
Rename all the "2" classes related to scrolling to remove the "2". Now that the old scrolling code is gone, we don't need to use the suffix.
-
Adam Barth authored
All the clients have migrated to Scrollable2.
-
- 09 Feb, 2017 1 commit
-
-
Ian Hickson authored
-
- 08 Feb, 2017 1 commit
-
-
Adam Barth authored
Also, switch Stepper over to using sliver-based scrolling.
-
- 31 Jan, 2017 2 commits
-
-
Jason Simmons authored
-
Jason Simmons authored
The finder will only match the widget's ValueKey if both have identical runtime types
-
- 13 Jan, 2017 2 commits
-
-
Michael Goderbauer authored
With frameSync enabled, flutter_driver actions will only be performed when there are no pending frames in the app under test. This helps with reducing flakiness.
-
Michael Goderbauer authored
fixes #7433
-
- 11 Jan, 2017 2 commits
-
-
Michael Goderbauer authored
-
Michael Goderbauer authored
It is now handled at a higher level for all commands.
-
- 09 Jan, 2017 1 commit
-
-
Michael Goderbauer authored
-
- 28 Nov, 2016 1 commit
-
-
Chris Bracken authored
Returns a dump of the application's render tree.
-
- 08 Nov, 2016 1 commit
-
-
Yegor authored
-
- 18 Oct, 2016 1 commit
-
-
Yegor authored
Add an option to provide a custom description to predicate finders. Without a custom description we default to printing the predicate function's signature, which is not all that useful. Use this new option in the driver extension to print the text of the sought after tooltip.
-
- 13 Sep, 2016 1 commit
-
-
Yegor authored
-
- 09 Sep, 2016 1 commit
-
-
Yegor authored
-
- 08 Sep, 2016 1 commit
-
-
Phil Quitslund authored
* Udpate to Dart `1.20.0-dev.1.0`. Udpate to Dart `1.20.0-dev.1.0` and corresponding `analyzer` package. * Added `--no-packages-dir`. * Revert extension to master. * Added ignores. * Review nits. * More nits.
-
- 14 Jul, 2016 1 commit
-
-
YoungSeok Yoon authored
* Driver commands for controlling the Input widget This commit introduces two new driver commands for controlling the material Input widget. * setInputText(SerializableFinder finder, String text) * submitInputText(SerializableFinder finder) Since it is not possible to directly modify the Input widget text, these driver commands invokes the handler functions of the Input widget: onChanged and onSubmitted, respectively. The `submitInputText` command returns the submitted String as a result. * Make input command handler methods private Addressing comments from @yjbanov.
-
- 04 May, 2016 1 commit
-
-
Hans Muller authored
* Gallery demo start-time performance test
-
- 29 Apr, 2016 1 commit
-
-
Ian Hickson authored
* Refactor widget test framework Instead of: ```dart test("Card Collection smoke test", () { testWidgets((WidgetTester tester) { ``` ...you now say: ```dart testWidgets("Card Collection smoke test", (WidgetTester tester) { ``` Instead of: ```dart expect(tester, hasWidget(find.text('hello'))); ``` ...you now say: ```dart expect(find.text('hello'), findsOneWidget); ``` Instead of the previous API (exists, widgets, widget, stateOf, elementOf, etc), you now have the following comprehensive API. All these are functions that take a Finder, except the all* properties. * `any()` - true if anything matches, c.f. `Iterable.any` * `allWidgets` - all the widgets in the tree * `widget()` - the one and only widget that matches the finder * `firstWidget()` - the first widget that matches the finder * `allElements` - all the elements in the tree * `element()` - the one and only element that matches the finder * `firstElement()` - the first element that matches the finder * `allStates` - all the `State`s in the tree * `state()` - the one and only state that matches the finder * `firstState()` - the first state that matches the finder * `allRenderObjects` - all the render objects in the tree * `renderObject()` - the one and only render object that matches the finder * `firstRenderObject()` - the first render object that matches the finder There's also `layers' which returns the list of current layers. `tap`, `fling`, getCenter, getSize, etc, take Finders, like the APIs above, and expect there to only be one matching widget. The finders are: * `find.text(String text)` * `find.widgetWithText(Type widgetType, String text)` * `find.byKey(Key key)` * `find.byType(Type type)` * `find.byElementType(Type type)` * `find.byConfig(Widget config)` * `find.byWidgetPredicate(WidgetPredicate predicate)` * `find.byElementPredicate(ElementPredicate predicate)` The matchers (for `expect`) are: * `findsNothing` * `findsWidgets` * `findsOneWidget` * `findsNWidgets(n)` * `isOnStage` * `isOffStage` * `isInCard` * `isNotInCard` Benchmarks now use benchmarkWidgets instead of testWidgets. Also, for those of you using mockers, `serviceMocker` now automatically handles the binding initialization. This patch also: * changes how tests are run so that we can more easily swap the logic out for a "real" mode instead of FakeAsync. * introduces CachingIterable. * changes how flutter_driver interacts with the widget tree to use the aforementioned new API rather than ElementTreeTester, which is gone. * removes ElementTreeTester. * changes the semantics of a test for scrollables because we couldn't convince ourselves that the old semantics made sense; it only worked before because flushing the microtasks after every event was broken. * fixes the flushing of microtasks after every event. * Reindent the tests * Fix review comments
-
- 22 Apr, 2016 1 commit
-
-
Ian Hickson authored
The old names were getting silly and started stepping on valuable namespace. The new names are consistent and clear.
-
- 21 Apr, 2016 2 commits
-
-
Ian Hickson authored
Previously the widgets layer only provided a concrete binding, which makes it awkward to extend it compared to other bindings. This moves widgets to the same style as the other layers. In a subsequent patch I'll use this to make the tests layer saner.
-
Ian Hickson authored
Moves TestGesture into test_pointer.dart and makes it more self-contained. This is part of a general refactoring of flutter_test. Depends on https://github.com/flutter/flutter/pull/3459
-
- 20 Apr, 2016 1 commit
-
-
Yegor authored
-
- 19 Apr, 2016 2 commits
-
-
Ian Hickson authored
Bindings now have a debugRegisterServiceExtensions() method that is invoked in debug mode (only). (Once we have a profile mode, there'll be a registerProfileServiceExtensions() method that gets called in that mode only to register extensions that apply then.) The BindingBase class provides convenience methods for registering service extensions that do the equivalent of: ```dart void extension() { ... } bool extension([bool enabled]) { ... } double extension([double extension]) { ... } Map<String, String> extension([Map<String, String> parameters]) { ... } ``` The BindingBase class also itself registers ext.flutter.reassemble, which it has call a function on the binding called reassembleApplication(). The Scheduler binding now exposes the preexisting ext.flutter.timeDilation. The Renderer binding now exposes the preexisting ext.flutter.debugPaint. The Renderer binding hooks reassembleApplication to trigger the rendering tree to be reprocessed (in particular, to fix up the optimisation closures). All the logic from rendering/debug.dart about service extensions is replaced by the above. I moved basic_types to foundation. The FlutterWidgets binding hooks reassembleApplication to trigger the widget tree to be entirely rebuilt. Flutter Driver now uses ext.flutter.driver instead of ext.flutter_driver, and is hooked using the same binding mechanism. Eventually we'll probably move the logic into the Flutter library so that you just get it without having to invoke a special method first.
-
Yegor authored
* [driver] "waitFor" command in place of broken "exits" * [driver] wait using frame callback
-
- 15 Apr, 2016 1 commit
-
-
Yegor authored
-
- 08 Apr, 2016 1 commit
-
-
Yegor authored
-
- 30 Mar, 2016 1 commit
-
-
Devon Carew authored
-
- 03 Mar, 2016 2 commits
-
-
yjbanov authored
Turns out VM service only accepts flat parameter name/value pairs. It only worked this far because vm_service_client (mistakenly) uses JSON encoder to encode parameters. This change separates the Command type hierarchy from that of Result and tightens type constraints on Command object parameters.
-
yjbanov authored
-
- 01 Mar, 2016 1 commit
-
-
Yegor Jbanov authored
-
- 24 Feb, 2016 1 commit
-
-
yjbanov authored
-
- 18 Feb, 2016 1 commit
-
-
Yegor Jbanov authored
This commit contains: - FlutterDriver API for e2e tests usable in conjunction with package:test - FlutterDriverExtension to be enabled by the application in order to allow an external agent to connect to it and drive user interactions and probe into the element tree - initial implementations of tap, findByValueKey and getText commands (to be expanded in future PRs)
-