Mouad Debbar caf0c82b82
[web] More granular configuration of the test environment (#168767)
There's today a single boolean `debugEmulateFlutterTesterEnvironment`
that determines certain behaviors in the engine to emulate how the
Flutter Tester runs (more details at
https://github.com/flutter/flutter/issues/145779).

With this PR:
- Run all engine unit tests in production mode by default.
- Give tests more granular control over which test behaviors to
enable/disable (e.g. Ahem font).
- Keep it easy for framework tests to enable all emulation behaviors.

Fixes https://github.com/flutter/flutter/issues/145779
2025-06-24 19:45:19 +00:00
..
2024-12-19 20:06:21 +00:00
2024-12-19 20:06:21 +00:00
2024-12-19 20:06:21 +00:00
2024-12-19 20:06:21 +00:00
2024-12-19 20:06:21 +00:00
2024-12-19 20:06:21 +00:00
2024-12-19 20:06:21 +00:00
2024-12-19 20:06:21 +00:00
2024-12-19 20:06:21 +00:00

The rule for packages in this directory is that they can depend on nothing but core Dart packages. They can't depend on dart:ui, they can't depend on any package:, and they can't depend on anything outside this directory.

Currently they do depend on dart:ui, but only for VoidCallback and clampDouble (and maybe one day lerpDouble), which are all intended to be moved out of dart:ui and into dart:core.

There is currently also an unfortunate dependency on the platform dispatcher logic (SingletonFlutterWindow, Brightness, PlatformDispatcher, window), though that should probably move to the 'services' library.

See also: