1. 21 Feb, 2019 1 commit
  2. 05 Oct, 2018 1 commit
  3. 20 Sep, 2018 1 commit
    • Greg Spencer's avatar
      Simplify Gradle compiler output. (#21760) · efcd9a80
      Greg Spencer authored
      This changes the compiler output for gradle to be less verbose and more easily read.
      
      This only applies to compilation error messages: other gradle messages will continue to print as before.
      
      It also fixes a small problem with the performance measurement printing (see that "7.1s" on it's own line in the original?) so that if something is expected to have multiple lines of output, it prints an initial line, and a "Done" line with the elapsed time, so that it's possible to know what the time applies to.
      
      It also updates the spinner to be fancier, at least on platforms other than Windows (which is missing a lot of symbols in its console font).
      
      Addresses #17307
      efcd9a80
  4. 12 Sep, 2018 1 commit
  5. 16 Aug, 2018 1 commit
  6. 15 Aug, 2018 1 commit
    • Ian Hickson's avatar
      Shim package:test to avoid matcher issues (#20602) · 686d8f8a
      Ian Hickson authored
      * Upgrade everything except matcher.
      * Roll matcher (and test)
      * Adjust tests that depend on flutter:test directly to depend on a shim
      * Require use of package:test shim and remove other references to package:test
      686d8f8a
  7. 05 Jun, 2018 1 commit
  8. 02 Feb, 2018 1 commit
  9. 18 Jan, 2018 2 commits
  10. 09 Dec, 2017 1 commit
  11. 08 Nov, 2017 1 commit
  12. 04 Aug, 2017 1 commit
  13. 30 Jun, 2017 1 commit
  14. 12 May, 2017 1 commit
  15. 13 Apr, 2017 1 commit
  16. 22 Mar, 2017 1 commit
  17. 13 Mar, 2017 1 commit
  18. 10 Mar, 2017 1 commit
  19. 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
  20. 14 Feb, 2017 1 commit
  21. 06 Feb, 2017 1 commit
  22. 03 Feb, 2017 1 commit
  23. 31 Jan, 2017 1 commit
  24. 10 Jan, 2017 1 commit
  25. 09 Jan, 2017 1 commit
  26. 07 Jan, 2017 1 commit
    • Todd Volkert's avatar
      Update flutter_tools to use package:file throughout (#7385) · 8bb27034
      Todd Volkert authored
      This removes direct file access from within flutter_tools
      in favor of using `package:file` via a `FileSystem` that's
      accessed via the `ApplicationContext`.
      
      This lays the groundwork for us to be able to easily swap
      out the underlying file system when running Flutter tools,
      which will be used to provide a record/replay file system,
      analogous to what we have for process invocations.
      8bb27034
  27. 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
  28. 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