- 27 Aug, 2019 1 commit
-
-
Jonah Williams authored
-
- 15 Aug, 2019 1 commit
-
-
Ingo Reinhart authored
-
- 19 Jul, 2019 1 commit
-
-
Jonah Williams authored
-
- 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)
-
- 15 Apr, 2019 1 commit
-
-
Christopher Fujino authored
* add a --build/--no-build flag to flutter drive command
-
- 21 Feb, 2019 1 commit
-
-
Alexandre Ardhuin authored
-
- 15 Nov, 2018 2 commits
-
-
Jonah Williams authored
* Revert "Add dashing config file for generating docset from flutter docs (#24374)" This reverts commit ec8ca860. * Revert "Update driver script to execute test through test_core (#24168)" This reverts commit 6c62cf33.
-
Jonah Williams authored
-
- 11 Oct, 2018 1 commit
-
-
Greg Spencer authored
This attempts to re-land #22656. There are two changes from the original: I turned off wrapping completely when not sending output to a terminal. Previously I had defaulted to wrapping at and arbitrary 100 chars in that case, just to keep long messages from being too long, but that turns out the be a bad idea because there are tests that are relying on the specific form of the output. It's also pretty arbitrary, and mostly people sending output to a non-terminal will want unwrapped text. I found a better way to terminate ANSI color/bold sequences, so that they can be embedded within each other without needed quite as complex a dance with removing redundant sequences. As part of these changes, I removed the Logger.supportsColor setter so that the one source of truth for color support is in AnsiTerminal.supportsColor. * Turn on line wrapping again in usage and status messages, adds ANSI color to doctor and analysis messages. (#22656) This turns on text wrapping for usage messages and status messages. When on a terminal, wraps to the width of the terminal. When writing to a non-terminal, wrap lines at a default column width (currently defined to be 100 chars). If --no-wrap is specified, then no wrapping occurs. If --wrap-column is specified, wraps to that column (if --wrap is on). Adds ANSI color to the doctor and analysis output on terminals. This is in this PR with the wrapping, since wrapping needs to know how to count visible characters in the presence of ANSI sequences. (This is just one more step towards re-implementing all of Curses for Flutter. :-)) Will not print ANSI sequences when sent to a non-terminal, or of --no-color is specified. Fixes ANSI color and bold sequences so that they can be combined (bold, colored text), and a small bug in indentation calculation for wrapping. Since wrapping is now turned on, also removed many redundant '\n's in the code.
-
- 06 Oct, 2018 2 commits
-
-
Greg Spencer authored
Revert "Turn on line wrapping in usage and status messages, adds ANSI color to doctor and analysis messages. (#22656)" (#22759) This reverts commit e4386321 because it breaks 160 benchmarks, and several devicelab tests, due to changing the format of the output.
-
Greg Spencer authored
Turn on line wrapping in usage and status messages, adds ANSI color to doctor and analysis messages. (#22656) This turns on text wrapping for usage messages and status messages. When on a terminal, wraps to the width of the terminal. When writing to a non-terminal, wrap lines at a default column width (currently defined to be 100 chars). If --no-wrap is specified, then no wrapping occurs. If --wrap-column is specified, wraps to that column (if --wrap is on). Adds ANSI color to the doctor and analysis output on terminals. This is in this PR with the wrapping, since wrapping needs to know how to count visible characters in the presence of ANSI sequences. (This is just one more step towards re-implementing all of Curses for Flutter. :-)) Will not print ANSI sequences when sent to a non-terminal, or of --no-color is specified. Fixes ANSI color and bold sequences so that they can be combined (bold, colored text), and a small bug in indentation calculation for wrapping. Since wrapping is now turned on, also removed many redundant '\n's in the code.
-
- 12 Sep, 2018 1 commit
-
-
Alexandre Ardhuin authored
* enable lint unnecessary_new * fix tests * fix tests * fix tests
-
- 04 Sep, 2018 1 commit
-
-
Chris Bracken authored
This patch eliminates the --preview-dart-2/--no-preview-dart-2 flag, hardcoding all uses to true. It also defaults all previewDart2 method parameters to true, where they hadn't yet been. A series of subsequent patches will eliminate all previewDart2 parameters and the associated code from within the codebase.
-
- 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
-
- 13 Jun, 2018 1 commit
-
-
Chris Bracken authored
fuchsia_tester.dart still assumes Dart 1. Previously, it ran tests directly from source, flutter_platform.dart automatically runs a kernel compile when operating in Dart 2 mode, but this assumes a functional Dart SDK is available in the artifacts directly, and fuchsia_tester.dart mocks out the artifacts directory with an empty temp dir. Remaining work is: 1. Get the frontend server building as a dependency on Fuchsia. 2. Patch fuchsia_tester.dart to use a valid Dart SDK and frontend server. This also reverts migration to Dart 2 typedef syntax. This reverts commit 6c56bb24. (#18362) This reverts commit 3daebd05. (#18316)
-
- 08 Jun, 2018 3 commits
-
-
Chris Bracken authored
* It's time to #deleteDart1 (#18293) Eliminates support for Dart 1 in flutter_tools, and drops our Dart 1 benchmarks. All commands now run in Dart 1 mode only. Eliminates --preview-dart-2 / --no-preview-dart-2 support. * Fix indentation, remove no longer necessary .toList() * Only push udpated kernel if >0 invalidated srcs
-
Chris Bracken authored
Several benchmarks started failing during kernel compile: 1. Timeouts: * commands_test * hot_mode_dev_cycle__benchmark * run_machine_concurrent_hot_reload * service_extensions_test 2. Kernel compiler crash: * hot_mode_dev_cycle_linux__benchmark * routing_test 3. Unexpected termination: * hot_mode_dev_cycle_win__benchmark This reverts commit ed63e708.
-
Chris Bracken authored
Eliminates support for Dart 1 in flutter_tools, and drops our Dart 1 benchmarks. All commands now run in Dart 1 mode only. Eliminates --preview-dart-2 / --no-preview-dart-2 support.
-
- 24 Feb, 2018 1 commit
-
-
Alexander Aprelev authored
* Add --preview-dart-2 to 'flutter drive' * Run driver side in --preview-dart-2 mode. * Fix test
-
- 19 Dec, 2017 1 commit
-
-
Alan Russian authored
* Change async stubbing to use thenAnswer. Mockito now prohibits calling thenReturn with Futures and Streams. dart-lang/mockito#79 * Update all Mockito deps to 3.0.0. * Revert "Update all Mockito deps to 3.0.0." This reverts commit e8ab9d37c33d3d7fe384abde64ea5b4d72623c75. I did not correctly update the mockito dep, and there's no easy way to update to 3.0 alpha right now. * Change thenAnswer((_) => to thenAnswer((invocation) => * Add Invocation type to thenAnswer lambdas
-
- 26 Sep, 2017 1 commit
-
-
Todd Volkert authored
This makes command validation happen as part of `verifyThenRunCommand()`, using a newly introduced protected method (`validateCommand()`) rather than a `commandValidator` property (that subclasses were responsible for manually invoking).
-
- 16 Jun, 2017 1 commit
-
-
Yegor authored
-
- 12 May, 2017 1 commit
-
-
Ian Hickson authored
-
- 26 Apr, 2017 1 commit
-
-
Todd Volkert authored
Fixes #9612
-
- 20 Apr, 2017 1 commit
-
-
Alexandre Ardhuin authored
* comprehensive list of lints * add comments to commented out lint * fix unnecessary_this lints * exclude prefer_final_fields
-
- 15 Mar, 2017 1 commit
-
-
Alexandre Ardhuin authored
-
- 10 Mar, 2017 2 commits
-
-
Todd Volkert authored
-
Todd Volkert authored
`all.dart` is no longer needed. Furthermore, it causes tests to be skipped, or to silently fail to run anything. Fixes #7941
-
- 04 Mar, 2017 1 commit
-
-
Chris Bracken authored
-
- 28 Feb, 2017 1 commit
-
-
Yegor authored
-
- 21 Feb, 2017 1 commit
-
-
Todd Volkert authored
-
- 18 Feb, 2017 1 commit
-
-
Todd Volkert authored
-
- 14 Feb, 2017 1 commit
-
-
Michael Goderbauer authored
... and run some more tests on Windows.
-
- 06 Feb, 2017 1 commit
-
-
Michael Goderbauer authored
-
- 27 Jan, 2017 1 commit
-
-
Ian Hickson authored
This remove a very brittle aspect of flutter drive, whereby it would assume a known port instead of explicitly finding out what it was. Fixes #7692 and hopefully fixes the devicelab tests.
-
- 23 Jan, 2017 1 commit
-
-
Ian Hickson authored
...now that we have generic methods, their types need to be specified too.
-
- 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.
-
- 06 Jan, 2017 1 commit
-
-
Todd Volkert authored
-