Code Quality Gates for Large-Scale Flutter Apps
summary
Continuous integration is mandatory and the checklist here is concrete: run flutter analyze and a strict linter, enable null safety and import checks, add community linters to cover more than the default 46% detection, and use golden tests for UI regressions. Structure code as physical packages in a mono repo to get incremental builds that finish in seconds, run integration tests that take ~20 minutes to install and inspect with a UI inspector, enforce coverage thresholds like 80%, and automate architecture rules to block forbidden feature-to-feature dependencies.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:09Quality gates for Flutter teams
- 1:55CI/CD for Flutter projects
- 3:01Static analysis tools
- 4:28Community code quality tools
- 5:11Architecture separation
- 7:43Monorepo with melos
- 8:26Detecting copy-paste code
- 9:10Automated testing strategies
- 10:41Unit and widget testing
- 11:25Accessibility and snapshots
- 12:45Test coverage thresholds
- 13:29End-to-end testing
- 14:54Fast UI testing with Patrol
- 15:14Architecture rules automation
- 16:42CI pipeline optimization
- 18:19Code review policies
- 19:25Closing and resources
related talks
16mEnsuring quality throughout the application lifecycle
40mBeyond the widgets Evaluating Flutter apps with code assessments
37mTaming Legacy: Refactoring Patterns for Large Flutter Codebases
30mAccelerating the Dev Loop with DCM Lints at Betterment
36mSecuring Flutter Apps
45mFlutter: A journey of productivity and happiness
51mAll About Testing Flutter
32mexpect(isTestingInFlutterEasy, isTrue);