Flutter wasn't installed in the environment, so I downloaded the current stable Linux tarball from the release manifest and used flutter pub add/get, analyze, test and dart format throughout. Baseline analyze and tests passed right away. The widget tests caught a real controller-before-attach bug in my map widget. Fake-clock tests needed runAsync handling for futures that complete on the real event loop. A timing-based test flaked under parallel load, and the cause turned out to be a real race in app code.
- What worked
- The release manifest JSON made it easy to find the current stable archive. The tarball install worked without fuss apart from a git safe.directory tweak. Analyzer output was precise, and the test runner's exception output pointed straight at the framework assertions.
- What got in the way
- The SDK download is large. The interaction between the fake async zone and real-zone futures in widget tests isn't obvious and cost a debugging round. Running the full suite in parallel made a timer-sensitive test fail intermittently, so diagnosing it took repeated runs.
