1. 07 Feb, 2017 1 commit
  2. 04 Feb, 2017 2 commits
  3. 02 Feb, 2017 1 commit
  4. 01 Feb, 2017 2 commits
  5. 31 Jan, 2017 1 commit
    • Adam Barth's avatar
      Add SliverGrid and ScrollGrid (#7745) · 9119969a
      Adam Barth authored
      This patch adds grid supports to slivers and introduces a ScrollGrid
      convenience class for making the common types of scrollable grids.
      
      This patch also deploys ScrollGrid in an example in the Flutter Gallery.
      9119969a
  6. 30 Jan, 2017 1 commit
    • Adam Barth's avatar
      Add SliverList (#7727) · 098af183
      Adam Barth authored
      Add SliverList
      
      A SliverList is a linear layout of box children in a viewport that all
      have a common, fixed extent along the scroll axis. The layout is similar
      to a SliverBlock but more efficient.
      098af183
  7. 27 Jan, 2017 2 commits
    • Adam Barth's avatar
      Add ScrollView.padding (#7690) · 5ecf8786
      Adam Barth authored
      Uses SliverPadding to implementing paddding in ScrollView. Also, deploy
      ScrollView in more places now that it implements padding.
      
      Finally, remove loader_app.dart because it is not referenced.
      5ecf8786
    • Adam Barth's avatar
      Improve SliverBlockDelegate.estimateScrollOffsetExtent (#7689) · 9c288040
      Adam Barth authored
      We now report an accurate estimate when the lastIndex is the final index
      in the list.
      
      Also, we now project forward from the lastIndex using the extent of the
      reified children instead of trying to project forward from index 0.
      
      This new algorithm leads to estimation error as you reach the end of a
      list, avoiding some ballistic overscrolls.
      9c288040
  8. 09 Dec, 2016 1 commit
  9. 07 Nov, 2016 1 commit
  10. 19 May, 2016 1 commit
  11. 16 May, 2016 1 commit
    • Ian Hickson's avatar
      Make it possible to run tests live on a device (#3936) · 32527017
      Ian Hickson authored
      This makes it possible to substitute 'flutter run' for 'flutter test'
      and actually watch a test run on a device.
      
      For any test that depends on flutter_test:
      
      1. Remove any import of 'package:test/test.dart'.
      
      2. Replace `testWidgets('...', (WidgetTester tester) {`
            with `testWidgets('...', (WidgetTester tester) async {`
      
      3. Add an "await" in front of calls to any of the following:
          * tap()
          * tapAt()
          * fling()
          * flingFrom()
          * scroll()
          * scrollAt()
          * pump()
          * pumpWidget()
      
      4. Replace any calls to `tester.flushMicrotasks()` with calls to
         `await tester.idle()`.
      
      There's a guarding API that you can use, if you have particularly
      complicated tests, to get better error messages. Search for
      TestAsyncUtils.
      32527017
  12. 29 Apr, 2016 1 commit
    • Ian Hickson's avatar
      Refactor the test framework (#3622) · 91dd9699
      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
      91dd9699
  13. 14 Apr, 2016 1 commit
  14. 27 Feb, 2016 1 commit
  15. 25 Feb, 2016 1 commit
    • Hixie's avatar
      Remove size observers from scrollables. · f8080557
      Hixie authored
      Also:
       - add operator==/hashCode/toString to ViewportDimensions
       - add toString to BindingBase
       - add toString and debugFillDescription to ScrollBehavior
       - fix a bug in the RawGestureDetectorState's replaceGestureRecognizers
       - rename MixedViewport's onExtentsUpdate to onExtentChanged
       - replace ExtentsUpdateCallback with ValueChanged<double>
       - remove a microtask for dispatching scroll start, since it
         did not appear to have any purpose
       - added dartdocs to Instrumentation until I understood it
       - made all event dispatch in Instrumentation drain microtasks
      f8080557
  16. 21 Feb, 2016 1 commit
    • Adam Barth's avatar
      Add TestGesture · 1484add1
      Adam Barth authored
      This helper makes it easier to write correct tests that involve
      gestures.
      
      Fixes #1855
      1484add1
  17. 09 Feb, 2016 1 commit
  18. 22 Jan, 2016 1 commit
  19. 16 Dec, 2015 1 commit
  20. 23 Nov, 2015 1 commit
  21. 16 Nov, 2015 1 commit
    • Hixie's avatar
      More resilient Widget tests · d041f3ea
      Hixie authored
      - force the time dilation to 1.0 for the Widget tests, so that a local
        change doesn't break all the tests during development.
      - add missing license block to all the files.
      - set ui.window.onBeginFrame to null when you use WidgetTester, so that
        the engine doesn't trigger any confusing frames after our fake frames.
      d041f3ea
  22. 15 Oct, 2015 1 commit
  23. 10 Oct, 2015 1 commit
  24. 01 Oct, 2015 3 commits
  25. 25 Sep, 2015 1 commit
  26. 24 Sep, 2015 1 commit
  27. 22 Sep, 2015 1 commit
    • Hixie's avatar
      Fix scrolling of Block. · 59f7e7f0
      Hixie authored
      Since our build function depends on scrollBehavior.isScrollable, any
      time we update scrollBehavior we are implicitly updating our state. As
      such, we must do so during a setState() call, or else we won't rebuild
      and might not bother to listen to the scroll gestures.
      
      This probably broke when we made Block not listen to gestures if it
      wasn't overflowing.
      59f7e7f0