flutter-testing

原文涵盖的主题

• Flutter testing
• Rules that apply to every level
• Unit tests
• Widget tests
• Golden tests
• UI / E2E tests with Patrol
• Component catalogs & previews
• Debugging

Verified 2026-09-25: Flutter 3.47, patrol 4.10, alchemist 0.14, mocktail 1.0, bloctest 10, flutterriverpod 3.4. For Riverpod/Bloc-specific test APIs, see flutter-state-management/references/. Use the testing pyramid on purpose. Most coverage in fast unit tests of logic, widget tests for components, a few goldens for visuals, and E2E UI tests only for critical user journeys. Each level checks something the others can't. Don't duplicate edge cases upward. | Level | Checks | Tool | |---|---|---| | Unit | Business logic, Cubits/Notifiers/ViewModels, repositories, mappers, validators | fluttertest + mocktail | | Widget | A component/screen's behavior in isolation | fluttertest (patrolfinders for nicer finders) | | Golden | How it looks: design-system components | Alchemist | | UI / E2E | The app's main purpose works end-to-end, including native UI | Patrol | Fakes over mocks (Flutter team, "strongly recommend"). Write FakeUserRepository implements UserRepository with in-memory behavior in testing/fakes/. Mocks (mocktail) are for checking interactions or one-off stubs. Keep them private per test file (class MockApi extends Mock implements Api {}), so a stub in one file can't leak into an

这里只展示节选，请以完整原文和当前要求为准。