1. 08 Feb, 2017 1 commit
  2. 03 Feb, 2017 1 commit
  3. 31 Jan, 2017 1 commit
    • Ian Hickson's avatar
      Make tests more resilient to timing. (#7753) · b257f6ea
      Ian Hickson authored
      These tests would fail sometimes when run locally. Since they happen
      to also be the ones that are flaky on bots, maybe there's some
      relationship, even though the failure mode on bots is different. In
      any case, this removes a variable.
      b257f6ea
  4. 24 Jan, 2017 1 commit
  5. 15 Dec, 2016 1 commit
  6. 14 Nov, 2016 1 commit
    • Dan Rubel's avatar
      Refactor flutter command exit code - part 3 of 3 (#6838) · 34e466f1
      Dan Rubel authored
      * Remove the workaround that pinned args to v0.13.6
      This reverts most of the changes in commit 6331b6c8
      * throw exception if exit code is not an integer
      * rework command infrastructure to throw ToolExit when non-zero exitCode
      * convert commands to return Future<Null>
      * cleanup remaining commands to use throwToolExit for non-zero exit code
      * remove isUnusual exception message
      * add type annotations for updated args package
      34e466f1
  7. 08 Nov, 2016 1 commit
  8. 23 Sep, 2016 1 commit
  9. 14 Jun, 2016 1 commit
    • Ian Hickson's avatar
      Lock flutter tool while updating artifacts (#4476) · f92f71fe
      Ian Hickson authored
      This prevents multiple simultaneous runs of the analyzer from stomping
      over each other (e.g. multiple runs of 'update-packages'). Certain
      long-lived commands (like analyze, run, logs) are exempted once they've
      done enough work to be safe from most stomping action.
      
      This still doesn't make us entirely safe from craziness, e.g. if you're
      half way through an 'update-packages' run and you call 'git pull', who
      knows what state you'll end up in. But there's only so much one can do.
      
      Fixes https://github.com/flutter/flutter/issues/2762
      f92f71fe
  10. 17 May, 2016 1 commit
    • Ian Hickson's avatar
      Fix tests (#3977) · f284c1a0
      Ian Hickson authored
      Also, make sure that broken tests actually break the bots.
      
      And add a test to make sure that keeps happening.
      f284c1a0
  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