-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Description
Due to repository structure (the engine lives in flutter/engine, and the framework lives in flutter/flutter), it is [not possible for me to atomically write and update a (good) test]1 in flutter/engine#49938.
This issue is to track adding a test in a [follow-up PR]2.
Footnotes
-
Much has been said and re-said about the repo structure making good engine testing hard. For example, if I want to write code the same way an end-user would (i.e. a plugin, and register textures, etc), I really need the full flutter framework available, which it is not in
flutter/engine. ↩ -
It's theoretically possible to write a test first, but the test would immediately start failing (and turn the
flutter/fluttertree red) once the engine patch is written. To avoid pain for all Flutter contributors, I'll just take the pain myself I suppose. ↩