flutter-automated-testing

Goal

Generates, configures, and debugs automated tests for Flutter applications, encompassing unit, widget, integration, and plugin testing. Analyzes architectural components (such as MVVM layers) to produce isolated, mock-driven tests and end-to-end device tests. Assumes a standard Flutter project structure, existing business logic, and familiarity with Dart testing paradigms.

Instructions

1. Determine Test Type (Decision Logic)

Evaluate the user's target code to determine the appropriate testing strategy using the following decision tree:

• If verifying a single function, method, ViewModel, or Repository: Implement a Unit Test (Proceed to Step 2).
• If verifying a single widget's UI, layout, or interaction: Implement a Widget Test (Proceed to Step 3).
• If verifying complete app behavior, routing, or performance on a device: Implement an Integration Test (Proceed to Step 4).
• If verifying platform-specific native code (MethodChannels): Implement a Plugin Test (Proceed to Step 5).

STOP AND ASK THE USER: "Which specific class, widget, or flow are we testing today? Please provide the relevant source code if you haven't already."

2. Implement Unit Tests (Logic & Architecture)

Unit tests verify logic without rendering UI. They must reside in the test/ directory and end with _test.dart.

• For ViewModels (UI Layer Logic): Fake the repository dependencies. Do not rely on Flutter UI libraries.