Testing Standards
Priority: P1 (HIGH)
Ensuring code reliability through multi-layered testing strategies.
Structure
test/
├── unit/ # Business logic & mapping (Blocs, Repositories, UseCases)
├── widget/ # UI component behavior (Screens, Widgets)
└── integration/ # End-to-end flows
Implementation Guidelines
- Testing Pyramid: Maintain ~70% Unit Tests, ~20% Widget Tests, ~10% Integration Tests.
- Mocks: Use
mocktail for type-safe, boilerplate-free mocking.
- Unit Tests: Test logic in isolation. Verify all edge cases (Success, Failure, Exception).
- Widget Tests: Test high-value interactions (Button clicks, Error states, Loading indicators).
- BLoC Tests: Use
blocTest to verify state emission sequences.
- Code Coverage: Aim for 80%+ coverage on Domain and Presentation (Logic) layers.
Deep Dive References
🚫 Anti-Patterns
- Thread Sleep:
**No Future.delayed**: Use FakeAsync or expectations for deterministic timing.
- Missing Assertions:
**No "Execution Only" Tests**: A test without an expect() call is invalid.
- Over-Mocking:
**No Mocking Data Classes**: Use real instances for Entities/Models; mock only I/O.
- Test Pollution:
**No Shared State**: Ensure every test is Independent (FIRST).
Related Topics
layer-based-clean-architecture | dependency-injection | cicd
1---2name: flutter-testing-standards3description: Unit, widget, and integration testing using mocktail and bloc_test.4metadata:5 labels: [testing, junit, mocktail, bloc_test, golden-tests]6 triggers:7 files: ['**/test/**.dart']8 keywords: [test, group, expect, mocktail, blocTest, when, any]9---1011# Testing Standards1213## **Priority: P1 (HIGH)**1415Ensuring code reliability through multi-layered testing strategies.1617## Structure1819```text20test/21├── unit/ # Business logic & mapping (Blocs, Repositories, UseCases)22├── widget/ # UI component behavior (Screens, Widgets)23└── integration/ # End-to-end flows24```2526## Implementation Guidelines2728- **Testing Pyramid**: Maintain ~70% Unit Tests, ~20% Widget Tests, ~10% Integration Tests.29- **Mocks**: Use `mocktail` for type-safe, boilerplate-free mocking.30- **Unit Tests**: Test logic in isolation. Verify all edge cases (Success, Failure, Exception).31- **Widget Tests**: Test high-value interactions (Button clicks, Error states, Loading indicators).32- **BLoC Tests**: Use `blocTest` to verify state emission sequences.33- **Code Coverage**: Aim for 80%+ coverage on Domain and Presentation (Logic) layers.3435## Deep Dive References3637- [Unit Testing Strategies](./references/unit-testing.md) (Test Data Builders, Mocktail)38- [Widget Testing Strategies](./references/widget-testing.md) (Robot Pattern)39- [Integration Testing](./references/integration-testing.md) (Shared Robots, Real Device)40- [Robot Pattern Implementation](./references/robot-pattern.md)4142## 🚫 Anti-Patterns4344- **Thread Sleep**: `**No Future.delayed**: Use FakeAsync or expectations for deterministic timing.`45- **Missing Assertions**: `**No "Execution Only" Tests**: A test without an expect() call is invalid.`46- **Over-Mocking**: `**No Mocking Data Classes**: Use real instances for Entities/Models; mock only I/O.`47- **Test Pollution**: `**No Shared State**: Ensure every test is Independent (FIRST).`4849## Related Topics5051layer-based-clean-architecture | dependency-injection | cicd
fierzone