testing

Use blocTest from the bloc_test package to verify state transitions. Mock the repository with mocktail, stub its methods in build, call the cubit method in act, and assert the expected sequence of emitted states in expect.

Default to unit tests for pure Dart logic, repositories, and cubits using test and bloc_test. Use widget tests with flutter_test and WidgetTester when verifying UI rendering, gesture handling, or widget interaction.

Create a class extending Mock that implements the repository interface, then stub methods with when and thenAnswer. Call registerFallbackValue in setUpAll for custom types passed to any(), and mock at the repository boundary rather than the HTTP layer.

Tests that only confirm mocked behavior without exercising real logic cannot catch regressions. Each test should drive a real class under test, such as a cubit, and assert its actual outputs or state transitions rather than the mock's return value.

Mirror the lib folder structure under the test directory, with one test file per source file named <source_file>_test.dart. Group tests by feature subfolders such as cubit, view, and model, and wrap tests in group blocks named after the class under test.