This section of the Flutter repository contains the command line developer tools for building Flutter applications.
First, ensure that the Dart SDK and other necessary artifacts are available by invoking the Flutter Tools wrapper script. In this directory run:
$ ../../bin/flutter --version
To run Flutter Tools from source, in this directory run:
$ ../../bin/cache/dart-sdk/bin/dart bin/flutter_tools.dart
followed by command-line arguments, as usual.
To run the analyzer on Flutter Tools, in this directory run:
$ ../../bin/flutter analyze
As with other parts of the Flutter repository, all changes in behavior must be tested. Tests live under the
test/commands.shard. Hermetic tests go under its
hermetic/subdirectory. Non-hermetic tests go under its
In general, the tests for the code in a file called
file.dart should go in a file called
file_test.dart in the subdirectory that matches the behavior of the test.
We measure test coverage post-submit. A change that deletes code might decrease test coverage, however, most changes that add new code should aim to increase coverage. In particular, the coverage of the diff should be close to the average coverage, and should ideally be better.
To run the tests in the
test/ directory, first ensure that there are no connected devices. Then, in this directory run:
$ ../../bin/cache/dart-sdk/bin/pub run test
The tests in
test/integration.shard are slower to run than the tests in
test/general.shard. To run only the tests in
test/general.shard, in this directory run:
$ ../../bin/cache/dart-sdk/bin/pub run test test/general.shard
To run the tests in a specific file, run:
$ ../../bin/cache/dart-sdk/bin/pub run test test/general.shard/utils_test.dart
To force the Flutter Tools snapshot to be regenerated, delete the following files:
$ rm ../../bin/cache/flutter_tools.stamp ../../bin/cache/flutter_tools.snapshot