1. 02 Aug, 2018 1 commit
  2. 27 Jul, 2018 1 commit
  3. 23 Jul, 2018 1 commit
  4. 16 Jul, 2018 2 commits
  5. 13 Apr, 2018 1 commit
  6. 11 Jan, 2018 1 commit
  7. 07 Oct, 2017 1 commit
  8. 08 Sep, 2017 1 commit
  9. 07 Sep, 2017 1 commit
  10. 28 Aug, 2017 1 commit
    • Ian Hickson's avatar
      RTL: Padding, Flex (#11709) · f235a2c1
      Ian Hickson authored
      * Introduce a Directionality inherited widget which sets the ambient LTR vs RTL mode (defaulting to null, which means you cannot use directionality-influenced values).
      
      * Make it possible to configure Padding (including Container.padding and Container.margin) using a directionality-agnostic EdgeInsets variant.
      
      * Provide textDirection and verticalDirection controls on Row and Column to make them RTL-aware.
      
      * Introduce a variant of FractionalOffset based on the EdgeInsets variant. Not yet actually used.
      
      * Fix all the tests that depended on Row defaulting to LTR.
      f235a2c1
  11. 23 Aug, 2017 1 commit
  12. 27 Apr, 2017 1 commit
  13. 07 Apr, 2017 1 commit
  14. 04 Mar, 2017 1 commit
  15. 09 Feb, 2017 1 commit
  16. 10 Jan, 2017 1 commit
    • Adam Barth's avatar
      Change `Flexible`'s default `FlexFit` (#7404) · 03d19807
      Adam Barth authored
      Change `Flexible`'s default `FlexFit`
      
      Previously, `Flexible` defaulted to `FlexFit.tight`, which forced the child to
      expand to fill the available space. Now, `Flexible` defaults to
      `FlexFit.loose`, which does not force the child to expand to fill the available
      space.
      
      If you want the child to expand to fill the available space, consider using
      `Expanded` instead.
      
      Fixes #5169
      03d19807
  17. 06 Jan, 2017 1 commit
  18. 07 Nov, 2016 1 commit
  19. 21 Jun, 2016 1 commit
  20. 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
  21. 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
  22. 14 Apr, 2016 1 commit
  23. 13 Mar, 2016 1 commit
    • Adam Barth's avatar
      [rename fixit] Flex alignments · d5b2e2a0
      Adam Barth authored
      * justifyContent -> mainAxisAlignment
      * alignItems -> crossAxisAlignment
      * FlexJustifyContent -> MainAxisAlignment
      * FlexAlignItems -> CrossAxisAlignment
      
      Fixes #231
      d5b2e2a0
  24. 11 Jan, 2016 1 commit
  25. 16 Dec, 2015 1 commit
  26. 03 Dec, 2015 1 commit
    • Adam Barth's avatar
      RenderFlex shouldn't assert when its out of space · 7e474f6d
      Adam Barth authored
      Previously, we would assert with FlexJustifyContent.collapse if we ran out of
      space. Now we do the same thing we do for the other types of justification,
      which is to let the children's layout overflow.
      7e474f6d
  27. 23 Nov, 2015 1 commit
  28. 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
  29. 03 Nov, 2015 2 commits
  30. 15 Oct, 2015 1 commit
  31. 10 Oct, 2015 1 commit
  32. 01 Oct, 2015 3 commits
  33. 25 Sep, 2015 1 commit
  34. 31 Aug, 2015 1 commit