github/flutter
7
0
Fork 0
mirror of https://github.com/flutter/flutter.git synced 2025-06-03 00:51:18 +00:00
Code Issues Packages Projects Releases Wiki Activity
059de1537e
flutter/packages/flutter_tools
History
Jonah Williams 059de1537e
[flutter_tools] support code size tooling on iOS, linux, windows, macOS, and Android on Windows (#63610) 
Adds support for size analysis on iOS, macOS, linux, and Windows - using an uncompressed directory based approach. The output format is not currently specified.

Adds support for size analysis on android on windows, switching to package:archive

Updates the console format to display as a tree, allowing longer paths. Increases the number of dart libraries shown (to avoid only ever printing the flutter/dart:ui libraries, which dominate the size)
2020-08-25 10:00:24 -07:00
..
bin [flutter_tools] support code size tooling on iOS, linux, windows, macOS, and Android on Windows (#63610) 2020-08-25 10:00:24 -07:00
doc Return host and port from devtools launcher (#63795) 2020-08-17 10:46:05 -07:00
gradle [flutter_tools] support code size tooling on iOS, linux, windows, macOS, and Android on Windows (#63610) 2020-08-25 10:00:24 -07:00
ide_templates/intellij Move Android doctor SDK check to 29 and Cirrus images to 30 (#63517) 2020-08-20 11:06:32 -07:00
lib [flutter_tools] support code size tooling on iOS, linux, windows, macOS, and Android on Windows (#63610) 2020-08-25 10:00:24 -07:00
schema [Material] Updated icons and fonts (#61778) 2020-07-24 15:41:13 -07:00
static Implement screenshot test for flutter web. (#45530) 2019-12-06 14:25:39 -08:00
templates [windows] Update plugin template (#64521) 2020-08-25 08:30:05 -07:00
test [flutter_tools] support code size tooling on iOS, linux, windows, macOS, and Android on Windows (#63610) 2020-08-25 10:00:24 -07:00
tool [flutter_tools] add more info to coverage script (#64065) 2020-08-18 12:18:54 -07:00
analysis_options.yaml Reland: [flutter_tool] Where possible, catch only subtypes of Exception (#52021) 2020-03-06 10:22:12 -08:00
build.yaml
dart_test.yaml Clean up test infrastructure (#43030) 2019-10-18 16:35:39 -07:00
pubspec.yaml [flutter_tools] update dwds, roll to null-safe file and process (#64195) 2020-08-19 16:59:52 -07:00
README.md ✒ Spell Check All .md Files Related to Flutter 💙 (#61564) 2020-07-22 18:23:47 -07:00

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/cache/dart-sdk/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 its hermetic/ subdirectory. Non-hermetic tests go under its permeable sub-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.

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/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

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