testing

From README

Dart & Flutter Testing VGV testing conventions for Dart and Flutter. The framework APIs are assumed; what follows is the house style layered on top of them. Core Standards Apply these standards to all test work: Descriptive test names — verbose, readable names that describe the behavior; never 'works' or 'renders' Hierarchical group/test structure that reads as natural sentences — top-level group for the class, nested group for the method, test for the behavior (e.g., UserRepository → getUser → returns User when API succeeds) String interpolation for type references — use 'returns $User' not 'returns User' so renames propagate automatically Private mocks per file — declare class MockX extends Mock implements X {} with underscore prefix to prevent cross-file coupling Contained test within groups — all /tearDown calls live inside a group, never at the top level of main() Initialize mutable objects in () with late — declare late MyDep dep; then assign in so each test gets a fresh...