Testing
evanca/flutter-ai-rules
A skill your agent uses when writing or reviewing Flutter/Dart tests (unit, widget, golden), fixing flaky tests, adding coverage, or choosing between unit and widget tests.
Write, fix, review, debug, and validate Flutter tests for apps, packages, and plugins.
Install Flutter Testing
$ npx skills add MADTeacher/mad-agents-skills --skill flutter-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install MADTeacher/mad-agents-skills flutter-testing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/MADTeacher/mad-agents-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/flutter-testing .claude/skills/flutter-testing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "flutter-testing" agent skill from https://github.com/MADTeacher/mad-agents-skills/tree/main/flutter-testing into .claude/skills/flutter-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flutter-testing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/MADTeacher/mad-agents-skills/tree/main/flutter-testingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add MADTeacher/mad-agents-skills --skill flutter-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install MADTeacher/mad-agents-skills flutter-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MADTeacher/mad-agents-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/flutter-testing .agents/skills/flutter-testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "flutter-testing" agent skill from https://github.com/MADTeacher/mad-agents-skills/tree/main/flutter-testing into .agents/skills/flutter-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flutter-testing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add MADTeacher/mad-agents-skills --skill flutter-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install MADTeacher/mad-agents-skills flutter-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MADTeacher/mad-agents-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/flutter-testing .cursor/skills/flutter-testing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "flutter-testing" agent skill from https://github.com/MADTeacher/mad-agents-skills/tree/main/flutter-testing into .cursor/skills/flutter-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flutter-testing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/MADTeacher/mad-agents-skills.git --path flutter-testing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add MADTeacher/mad-agents-skills --skill flutter-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install MADTeacher/mad-agents-skills flutter-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MADTeacher/mad-agents-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/flutter-testing .gemini/skills/flutter-testing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "flutter-testing" agent skill from https://github.com/MADTeacher/mad-agents-skills/tree/main/flutter-testing into .gemini/skills/flutter-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flutter-testing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install MADTeacher/mad-agents-skills flutter-testingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add MADTeacher/mad-agents-skills --skill flutter-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/MADTeacher/mad-agents-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/flutter-testing .github/skills/flutter-testing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "flutter-testing" agent skill from https://github.com/MADTeacher/mad-agents-skills/tree/main/flutter-testing into .github/skills/flutter-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flutter-testing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add MADTeacher/mad-agents-skills --skill flutter-testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install MADTeacher/mad-agents-skills flutter-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MADTeacher/mad-agents-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/flutter-testing .opencode/skills/flutter-testing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "flutter-testing" agent skill from https://github.com/MADTeacher/mad-agents-skills/tree/main/flutter-testing into .opencode/skills/flutter-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flutter-testing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
flutter-testing- GitHub stars
- 110
- Token cost
- ~1.5k tokens
- SKILL.md length
- 681 words
- Files
- 8 (incl. scripts, references)
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- MIT
At a glance
Write, fix, review, debug, and validate Flutter tests for apps, packages, and plugins.
- Works in 5 steps: Inspect the project before changing… → Choose the test layer → Read only the reference files needed for… → …
- Adding unit tests
- SKILL.md covers Principle 0, Workflow, Resource Routing and Mandatory Validation, plus 2 more sections
- Runs Shell scripts from its folder; calls flutter, dart and bash
What it does
Flutter Testing is an agent skill from MADTeacher/mad-agents-skills. 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, buildrunner mock generation, device integration testing, web integration testing, or flaky Flutter tests.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including scripts and reference files (for example `references/common-errors.md`, `references/integration-testing.md` and `references/mocking.md`).
It sits in Testing & QA, covering Cross-platform mobile apps, Integration testing and Unit testing. It works with Flutter and Dart. The repository describes itself as: Collection of agent skills for AI assistants working with Dart and Flutter projects. The licence is MIT.
When your agent uses it
- Adding unit tests
- Integration tests
- Mocktail test doubles
- Accessibility checks
Example prompts
- “/flutter-testing”
Requirements
- A Bash shell
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Inspect the project before changing tests: pubspec.yaml, existing test/,
- Choose the test layer
- Read only the reference files needed for the chosen scenario.
- Implement the smallest deterministic test or test fix using the project's
- Run mandatory validation. If validation cannot run, report the exact blocker
What it can do on your machine
Read from SKILL.md and the folder at commit 2fb67e3. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
flutterdartbash
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Flutter Testing loads about 1.5k tokens when it runs, and up to ~20k if it reads all its reference files. Until then it costs about 118 tokens; SKILL.md has 681 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from MADTeacher/mad-agents-skills at commit 2fb67e3, republished under its MIT licence (© MADTeacher). 681 words, ~1,536 tokens.
Download SKILL.mdSave it as
.claude/skills/flutter-testing/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.- name
- flutter-testing
- description
- 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.
- metadata.author
- Stanislav [MADTeacher] Chernyshev
- metadata.version
- 2.0
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
- Inspect the project before changing tests:
pubspec.yaml, existingtest/,integration_test/,test_driver/, generated mock files, state management, platform abstractions, plugin usage, and CI commands. - 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.
- Read only the reference files needed for the chosen scenario.
- Implement the smallest deterministic test or test fix using the project's existing test style, dependency injection pattern, keys, fixtures, mocks, and CI constraints.
- Run mandatory validation. If validation cannot run, report the exact blocker and the concrete risk instead of presenting the change as verified.
Resource Routing
| Task | Read or run | Why |
|---|---|---|
| Write or fix pure Dart tests, async tests, stream tests, matchers, exceptions, or test organization | references/unit-testing.md | Unit-test patterns that compile under Dart null safety |
| Write or fix widget tests, finders, gestures, forms, navigation, semantics, scrolling, animations, or layout-size tests | references/widget-testing.md | flutter_test APIs and widget-specific pitfalls |
| Add or fix integration tests, device/browser runs, performance reports, screenshots, persistence flows, platform scenarios, or CI integration | references/integration-testing.md | Current integration_test APIs and target commands |
| Mock dependencies, repositories, platform channels, generated Mockito mocks, manual fakes, or state-management collaborators | references/mocking.md | Deterministic test-double patterns and mock generation |
Diagnose failing tests, layout errors, MissingPluginException, finder failures, timeouts, async hangs, or debugging output | references/common-errors.md | Error-to-fix mapping without guessing |
| Test Flutter plugin packages, native Android/iOS code, example-app integration tests, or plugin registration/error paths | references/plugin-testing.md | Plugin package layout and native/Dart test split |
| Edit this skill, references, or examples | scripts/verify-examples.sh | Deterministic smoke check for stale patterns and broken links |
Show full SKILL.md (322 more words)Show less
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", ordart testfor pure Dart packages. - After adding or changing generated Mockito mocks, run
dart run build_runner buildor 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>.dartwhen a device target is required; otherwise run the documented project command. - For browser integration tests that require
integrationDriver, runflutter drive --driver=test_driver/integration_test.dart --target=integration_test/<test_file>.dart -d chromeor 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.dartfor widget and integration tests, andpackage:test/test.dartonly 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.delayedwaits to hide async uncertainty. Use deterministic fakes, explicit pumps,pumpAndSettleonly 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, orflutter 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.
© MADTeacher, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 7 other files (scripts, references) in flutter-testing of MADTeacher/mad-agents-skills.
- SKILL.md
- references/common-errors.md
- references/integration-testing.md
- references/mocking.md
- references/plugin-testing.md
- references/unit-testing.md
- references/widget-testing.md
- scripts/verify-examples.sh
Open the folder on GitHubat commit 2fb67e3
Compare with similar skills
Flutter Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Flutter Testing this skillMADTeacher/mad-agents-skills | 110 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Testingevanca/flutter-ai-rules | 647 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Flutter Add Integration Testabdulmominsakib/localmind | 261 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Flutter Testing Appsbtwld/superdeck | 129 | — | ~2.2k | Automated safety check: Pass | BSD-3-Clause | |
| Test Guidelinesgetsentry/sentry-dart | 873 | — | ~3.1k | Automated safety check: Pass | MIT | |
| Flutter TesterFNOSP/FlyNarwhal | 495 | — | ~1.4k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
Flutter Add Integration Test
abdulmominsakib/localmind
Configures Flutter Driver for app interaction and converts MCP actions into permanent integration tests.
Flutter Testing Apps
btwld/superdeck
Implements unit, widget, and integration tests for a Flutter app.
- Official
Test Guidelines
getsentry/sentry-dart
Enforce Sentry Dart/Flutter SDK test conventions for naming, structure, and fixtures.
Flutter Tester
FNOSP/FlyNarwhal
A skill your agent uses when creating, writing, fixing, or reviewing tests in a Flutter project.
Bloc
VeryGoodOpenSource/vgv-ai-flutter-plugin
Best practices for Bloc state management in Flutter/Dart, covering Cubit versus Bloc, event and state naming, sealed classes with Equatable, the Page/View split with BlocProvider, BlocBuilder…
More from MADTeacher/mad-agents-skills
All 11 skills in this repoFlutter Internationalization
MADTeacher/mad-agents-skills
Add, fix, audit, and maintain Flutter internationalization with gen-l10n, ARB files, AppLocalizations, flutterlocalizations, intl formatting, plural/select messages, RTL support, locale-specific…
Flutter Networking
MADTeacher/mad-agents-skills
Implement, fix, debug, review, or refactor Flutter networking code for HTTP/REST APIs, WebSocket realtime flows, authentication and token refresh, request headers, timeouts, retries, JSON parsing…
Agents Md Generator
MADTeacher/mad-agents-skills
Create, generate, update, repair, trim, or split minimal AGENTS.md files for repository roots and confirmed nested modules using progressive disclosure.
Dart Drift
MADTeacher/mad-agents-skills
Build, fix, audit, and migrate Drift persistence in Dart CLI, server-side, and non-Flutter desktop apps.
Flutter Duit Bdui
MADTeacher/mad-agents-skills
Integrate, fix, review, migrate, test, or debug Duit / flutterduit backend-driven UI in Flutter applications.
Flutter Adaptive UI
MADTeacher/mad-agents-skills
Build, fix, review, and validate adaptive or responsive Flutter UIs for mobile, tablet, desktop, web, large screens, foldables, and mixed input devices.
Related
Categories
Questions about Flutter Testing
What does Flutter Testing do?
Write, fix, review, debug, and validate Flutter tests for apps, packages, and plugins. Flutter Testing is an agent skill from MADTeacher/mad-agents-skills. Write, fix, review, debug, and validate Flutter tests for apps, packages, and plugins.
When should I use Flutter Testing?
Flutter Testing fits situations like: adding unit tests; integration tests; mocktail test doubles; accessibility checks.
How do I install Flutter Testing in Claude Code?
Run `npx skills add MADTeacher/mad-agents-skills --skill flutter-testing -a claude-code`. Or copy the skill folder (flutter-testing in MADTeacher/mad-agents-skills) into .claude/skills/flutter-testing in your project. Claude Code loads it when a task matches its description.
How do I install Flutter Testing in Codex?
Run `npx skills add MADTeacher/mad-agents-skills --skill flutter-testing -a codex`. Or copy the skill folder (flutter-testing in MADTeacher/mad-agents-skills) into .agents/skills/flutter-testing in your project. Codex loads it when a task matches its description.
Can I use Flutter Testing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add MADTeacher/mad-agents-skills --skill flutter-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/flutter-testing, .gemini/skills/flutter-testing, .github/skills/flutter-testing and .opencode/skills/flutter-testing in your project.
What does Flutter Testing need to run?
Going by SKILL.md and its folder, Flutter Testing needs a shell for the scripts in its folder and the command-line tools its instructions call (flutter, dart and bash). Our summary lists: A Bash shell.
Does Flutter Testing access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Flutter Testing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Flutter Testing use?
Flutter Testing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Flutter Testing use?
About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 18k tokens, read only when the agent opens those files.
What are the alternatives to Flutter Testing?
Skills that share tags, products or a category with Flutter Testing: Testing (evanca/flutter-ai-rules, 647 stars), Flutter Add Integration Test (abdulmominsakib/localmind, 261 stars), Flutter Testing Apps (btwld/superdeck, 129 stars) and Test Guidelines (getsentry/sentry-dart, 873 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Flutter Testing?
MADTeacher (a GitHub user) maintains it in MADTeacher/mad-agents-skills, which has 110 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on May 1, 2026.
Source: MADTeacher/mad-agents-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.