2e75f52ae4
Overhaul of flutter drive in order to deliver a better experience, namely: flutter run and flutter drive now share more flags, so code paths that were previously only testable on run are now testable on drive. Removes web-initialize-platform as this is no longer used flutter drive correctly sets up a logger that shows native exceptions, by connecting to the vm service. VM service connection now provides access to memory info without launching devtools (only for debug/profile mode) Web changes Passes on the one test in the repo, otherwise the webdriver code has been isolated as much as possible Additional NNBD related bug fixes: No longer passes --enable-experiment to the test script. (FYI @blasten ). earlier we might have assumed that the flutter gallery benchmarks would be migrated along side the app and flutter driver, but only the app under test needs to be migrated. The test scripts should never be run with the experiment. |
||
|---|---|---|
| .. | ||
| bin | ||
| doc | ||
| gradle | ||
| ide_templates/intellij | ||
| lib | ||
| schema | ||
| static | ||
| templates | ||
| test | ||
| tool | ||
| analysis_options.yaml | ||
| dart_test.yaml | ||
| pubspec.yaml | ||
| README.md | ||
Flutter Tools
This section of the Flutter repository contains the command line developer tools for building Flutter applications.
Working on Flutter Tools
Be sure to follow the instructions on CONTRIBUTING.md to set up your development environment. Further, familiarize yourself with the style guide, which we follow.
Setting up
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
Running the Tool
To run Flutter Tools from source, in this directory run:
$ ../../bin/dart bin/flutter_tools.dart
followed by command-line arguments, as usual.
Running the analyzer
To run the analyzer on Flutter Tools, in this directory run:
$ ../../bin/flutter analyze
Writing tests
As with other parts of the Flutter repository, all changes in behavior must be
tested.
Tests live under the test/ subdirectory.
- Hermetic unit tests of tool internals go under
test/general.shard. - Tests of tool commands go under
test/commands.shard. Hermetic tests go under itshermetic/subdirectory. Non-hermetic tests go under itspermeablesub-directory. - Integration tests (e.g. tests that run the tool in a subprocess) go under
test/integration.shard.
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.
Using local engine builds in integration tests
The integration tests can be configured to use a specific local engine
variant by setting the FLUTTER_LOCAL_ENGINE environment variable to the
name of the local engine (e.g. "android_debug_unopt"). If the local engine build
requires a source path, this can be provided by setting the FLUTTER_LOCAL_ENGINE_SRC_PATH
environment variable. This second variable is not necessary if the flutter and
engine checkouts are in adjacent directories.
export FLUTTER_LOCAL_ENGINE=android_debug_unopt
../../bin/dart test test/integration.shard/some_test_case
Running the tests
To run the tests in the test/ directory, first ensure that there are no
connected devices. Then, in this directory run:
$ ../../bin/dart pub run test
The tests in test/integration.shard are slower to run than the tests in
test/general.shard. They also require the FLUTTER_ROOT environment variable
to be set and pointing to the root of the Flutter SDK. To run only the tests in test/general.shard, in this
directory run:
$ ../../bin/dart pub run test test/general.shard
To run the tests in a specific file, run:
$ ../../bin/dart pub run test test/general.shard/utils_test.dart
Forcing snapshot regeneration
To force the Flutter Tools snapshot to be regenerated, delete the following files:
$ rm ../../bin/cache/flutter_tools.stamp ../../bin/cache/flutter_tools.snapshot