- 13 Jul, 2019 1 commit
-
-
Ian Hickson authored
Move tools tests into a general.shard directory in preparation to changing how we shard tools tests (#36108)
-
- 22 Mar, 2019 1 commit
-
-
Alexandre Ardhuin authored
-
- 12 Sep, 2018 1 commit
-
-
Alexandre Ardhuin authored
* enable lint unnecessary_new * fix tests * fix tests * fix tests
-
- 17 Aug, 2018 1 commit
-
-
Ian Hickson authored
All temporary directory start with `flutter_` and have their random component separated from the name by a period, as in `flutter_test_bundle.YFYQMY`. I've tried to find some of the places where we didn't cleanly delete temporary directories, too. This greatly reduces, though it does not entirely eliminate, the directories we leave behind when running tests, especially `flutter_tools` tests. While I was at it I standardized on `tempDir` as the variable name for temporary directories, since it was the most common, removing occurrences of `temp` and `tmp`, among others. Also I factored out some common code that used to catch exceptions that happen on Windows, and made more places use that pattern.
-
- 15 Aug, 2018 1 commit
-
-
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
-
- 12 May, 2017 1 commit
-
-
Ian Hickson authored
-
- 04 Mar, 2017 1 commit
-
-
Chris Bracken authored
-
- 14 Feb, 2017 1 commit
-
-
Michael Goderbauer authored
-
- 26 Jan, 2017 1 commit
-
-
Todd Volkert authored
-
- 09 Jan, 2017 1 commit
-
-
Todd Volkert authored
This ensures that accidental usages of dart:io's file API don't creep in over time.
-
- 07 Jan, 2017 1 commit
-
-
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.
-
- 30 Nov, 2016 1 commit
-
-
Todd Volkert authored
With this change, they're run via instance methods on an object obtained through the context. This will allow us to substitute that object in tests with replay/record versions to allow us to mock out the os-layer in tests.
-
- 29 Nov, 2016 1 commit
-
-
John McCutchan authored
-
- 10 Mar, 2016 1 commit
-
-
Hixie authored
And fix a zillion omissions this uncovered.
-
- 28 Jan, 2016 1 commit
-
-
Devon Carew authored
rename to printTrace(), printStatus(), and printError()
-
- 29 Nov, 2015 1 commit
-
-
Adam Barth authored
1) Moved basic utility code into base/ directory to make it clear which code doesn't depend on Flutter-specific knowldge. 2) Move the CommandRunner subclasses into a runner/ directory because these aren't commands themselves.
-
- 18 Nov, 2015 1 commit
-
-
Adam Barth authored
Fixes #311
-
- 10 Nov, 2015 1 commit
-
-
Adam Barth authored
-
- 07 Nov, 2015 1 commit
-
-
Adam Barth authored
-
- 02 Nov, 2015 1 commit
-
-
Devon Carew authored
-