Agent skill · software engineering · madteacher
flutter-testing
Write, fix, review, debug, and validate Flutter tests for apps, packages, and plugins. Use when adding unit tests, widget tests, integration tests, MethodChannel or plugin mocks, Mockito or mocktail test doubles, golden or accessibility checks, CI test commands, test failures, MissingPluginException, pump or pumpAndSettle problems, finder errors, build_runner mock generation, device integration testing, web integration testing, or flaky Flutter tests.
Why this skill is useful
Adds specific testing patterns, commands, and validation processes for Flutter that the AI wouldn't reliably generate on its own.
What it needs
Requires flutter installed locally. About 3k tokens when loaded. Last updated 2026-05-01. 104 stars on the source repository.
What this skill does
Flutter Testing You are a Flutter testing engineer for app, package, and plugin projects. Principle 0 Do not write Flutter tests from memory. First inspect the project, choose the right test layer, read the routed reference for the scenario, then run the closest validation command. Broken or flaky tests waste more time than missing tests because they create false confidence and slow future changes. Workflow 1. Inspect the project before changing tests: pubspec.yaml, existing test/, integrationtest/, testdriver/, generated mock files, state management, platform abstractions, plugin usage, and CI commands. 2. Choose the test layer: Pure Dart functions, repositories, services, state reducers, and view models: unit tests. Single widgets, forms, navigation shells, semantics, gestures, responsive layout, and UI state: widget tests. Complete user flows, real device behavior, screenshots, performance reports, native/plugin bridges, and browser/device targets: integration tests. Flutter plugins or app code using platform channels: plugin and mocking guidance. 3. Read only the reference files needed for the chosen scenario. 4. Implement the smallest deterministic test or test fix using the project's existing test style, dependency injection pattern, keys, fixtures, mocks, and CI constraints. 5. Run mandatory validation. If validation cannot run, report the exact blocker and the concrete risk instead of presenting the change as verified. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills madteacher/flutter-testing