Flutter Confidence Checks Skill
This skill focuses on practical correctness, not exhaustive testing.
When to use this skill
- •Adding business logic
- •Refactoring providers or repositories
- •Touching auth or data flow
What to test
Priority order:
- •Providers (logic)
- •Repositories (data mapping)
- •Widgets only if logic-heavy
Provider testing
- •Test notifier methods directly
- •Mock repositories
- •Verify state transitions
What NOT to over-test
- •Simple UI layout
- •Generated code
- •One-line getters
Sanity checks (even without tests)
- •Error states handled?
- •Loading states visible?
- •Empty states intentional?
Goal
Confidence, not coverage.