History

Update gradle lockfiles template (#140115 )

This PR updates almost* all Gradle buildscripts in the Flutter repo the `example` and `dev` (in particular, in `dev/integration_tests` and in `dev/benchmarks`) directories to apply Flutter's Gradle plugins using the declarative `plugins {}` block.

*almost, because:
- add-to-app (aka hybrid) apps are not migrated (related https://github.com/flutter/flutter/issues/138756)
- apps that purposefully use build files to ensure backward compatibility (e.g. [`gradle_deprecated_settings`](https://github.com/flutter/flutter/tree/3.16.0/dev/integration_tests/gradle_deprecated_settings))

2024-02-04 13:10:49 +00:00

android

Update gradle lockfiles template (#140115 )

2024-02-04 13:10:49 +00:00

lib

Prepare dev (minus flutter_gallery) for use_super_parameters (#100516 )

2022-03-29 12:52:42 -07:00

test

Manual roll Flutter Engine from 4f4734cd48da to a0d650e37f5d (3 revisions) (#131967 )

2023-08-05 01:22:17 +00:00

pubspec.yaml

Unpin test (#141427 )

2024-02-01 18:53:23 +00:00

README.md

…

README.md

Tracing tests

"Application"

The lib/test.dart and lib/control.dart files in this directory are used by dev/bots/test.dart's runTracingTests function to check whether aspects of the tracing logic in the framework get compiled out in profile and release builds. They're not meant to be run directly.

The strings in these files are used in dev/bots/test.dart.

Tests

The tests in this folder must be run with flutter test --enable-vmservice, since they test that trace data is written to the timeline by connecting to the observatory.

These tests will fail if run without this flag.