Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
madteacher avatar

Flutter Testing

  • 1.4k installs
  • 105 repo stars
  • Updated May 1, 2026
  • madteacher/mad-agents-skills

flutter-testing is an agent skill that apply flutter-testing agent skill workflows from documented skill.md guidance.

About

flutter-testing is an agent skill from madteacher/mad-agents-skills that apply flutter-testing agent skill workflows from documented skill.md guidance. # 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 be Developers invoke flutter-testing during ship/testing work for testing & qa tasks. The skill documents triggers, prerequisites, and step-by-step workflows grounded in SKILL.md. Compatible with Claude Code, Cursor, and Codex agent runtimes that load marketplace skills. Review the Security Audits panel on this listing before installing in production environments.

  • You are a Flutter testing engineer for app, package, and plugin projects.
  • 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.

Flutter Testing by the numbers

  • 1,417 all-time installs (skills.sh)
  • +11 installs in the week ending Jul 29, 2026 (Skillselion tracking)
  • Ranked #488 of 2,159 Testing & QA skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Jul 29, 2026 (Skillselion catalog sync)
At a glance

flutter-testing capabilities & compatibility

Capabilities
you are a flutter testing engineer for app, pack · do not write flutter tests from memory. first in · right test layer, read the routed reference for · closest validation command. broken or flaky test · tests because they create false confidence and s
Use cases
orchestration
From the docs

What flutter-testing says it does

You are a Flutter testing engineer for app, package, and plugin projects.
SKILL.md
Do not write Flutter tests from memory. First inspect the project, choose the
SKILL.md
right test layer, read the routed reference for the scenario, then run the
SKILL.md
npx skills add https://github.com/madteacher/mad-agents-skills --skill flutter-testing

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1.4k
repo stars105
Security audit3 / 3 scanners passed
Last updatedMay 1, 2026
Repositorymadteacher/mad-agents-skills

What it does

Apply flutter-testing agent skill workflows from documented SKILL.md guidance.

Who is it for?

Developers working on testing & qa during ship tasks.

Skip if: Tasks outside Testing & QA scope described in SKILL.md.

When should I use this skill?

Apply flutter-testing agent skill workflows from documented SKILL.md guidance.

What you get

Completed testing & qa workflow aligned with SKILL.md steps.

  • corrected widget layout code
  • passing widget test suite

Files

SKILL.mdMarkdownGitHub ↗

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/, integration_test/, test_driver/, 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.

Resource Routing

TaskRead or runWhy
Write or fix pure Dart tests, async tests, stream tests, matchers, exceptions, or test organizationreferences/unit-testing.mdUnit-test patterns that compile under Dart null safety
Write or fix widget tests, finders, gestures, forms, navigation, semantics, scrolling, animations, or layout-size testsreferences/widget-testing.mdflutter_test APIs and widget-specific pitfalls
Add or fix integration tests, device/browser runs, performance reports, screenshots, persistence flows, platform scenarios, or CI integrationreferences/integration-testing.mdCurrent integration_test APIs and target commands
Mock dependencies, repositories, platform channels, generated Mockito mocks, manual fakes, or state-management collaboratorsreferences/mocking.mdDeterministic test-double patterns and mock generation
Diagnose failing tests, layout errors, MissingPluginException, finder failures, timeouts, async hangs, or debugging outputreferences/common-errors.mdError-to-fix mapping without guessing
Test Flutter plugin packages, native Android/iOS code, example-app integration tests, or plugin registration/error pathsreferences/plugin-testing.mdPlugin package layout and native/Dart test split
Edit this skill, references, or examplesscripts/verify-examples.shDeterministic smoke check for stale patterns and broken links

Mandatory Validation

  • After editing Dart tests or production code, run the narrowest relevant

command first, such as flutter test test/my_widget_test.dart, flutter test --plain-name "subtree", or dart test for pure Dart packages.

  • After adding or changing generated Mockito mocks, run

dart run build_runner build or the repository's established build command before running tests.

  • For integration tests on mobile or desktop targets, run `flutter test -d

<device-id> integration_test/<test_file>.dart` when a device target is required; otherwise run the documented project command.

  • For browser integration tests that require integrationDriver, run

flutter drive --driver=test_driver/integration_test.dart --target=integration_test/<test_file>.dart -d chrome or the project's web driver command.

  • After fixing flaky tests, run the specific test more than once or use the

repository's repeat/randomization option if one exists.

  • After editing this skill or its references, run

bash flutter-testing/scripts/verify-examples.sh.

Constraints

  • Prefer package:flutter_test/flutter_test.dart for widget and integration

tests, and package:test/test.dart only for pure Dart tests that do not need Flutter bindings.

  • Test user-visible behavior and public contracts. Do not assert private method

calls, widget internals, or incidental rebuild counts unless performance work explicitly requires it.

  • Prefer dependency injection, fake repositories, fake platform interfaces, or

MethodChannel handlers over real network, real storage, timers, permissions, or OS dialogs.

  • Do not use fixed Future.delayed waits to hide async uncertainty. Use

deterministic fakes, explicit pumps, pumpAndSettle only when animations can settle, or bounded custom pumps.

  • Do not use obsolete commands or APIs: --no-sound-null-safety,

flutter test --platform ..., tester.trace, tester.takeScreenshot, captureNamed, or flutter pub run build_runner build.

  • Do not simulate connectivity, permissions, or persistence by changing the

test surface size or by re-pumping the app with hidden state. Use explicit fakes, test hooks, or real integration targets.

Fallback

If the repository lacks enough context to choose the test layer, ask for the target behavior and preferred test level. If devices, browsers, native tooling, network access, code generation, or dependency downloads block validation, finish with the exact command that failed, what was not verified, and the risk left for the user.

Related skills

How it compares

Use flutter-testing for fast diagnosis of known Flutter test error patterns; consult Flutter layout docs when designing new responsive layouts from scratch.

FAQ

What does flutter-testing do?

Apply flutter-testing agent skill workflows from documented SKILL.md guidance.

When should I use flutter-testing?

During ship testing work for testing & qa.

Is flutter-testing safe to install?

Review the Security Audits panel on this listing before production use.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.