1. 04 Mar, 2017 1 commit
  2. 23 Feb, 2017 1 commit
    • Phil Quitslund's avatar
      Bump to test `0.12.20`. (#8349) · a002e720
      Phil Quitslund authored
      * Bump to test `0.12.20`.
      
      Some test `0.12.20` highlights:
        * introduces `expectLater()`  that returns a `Future` that completes when the matcher has finished running
        * deprecates the `verbose` parameter to `expect()` and the `formatFailure()` (to be removed in `0.13.0`)
      
      Otherwise:
        * to keep up w/ the deprecation of `verbose`, removes `widget_tester` API to pass `verbose` flag (alternatively we could suppress the warning for now)
      
      * Update stack manipulation.
      
      * Fix framecount.
      a002e720
  3. 18 May, 2016 1 commit
  4. 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