Flutter Integration Tests
Add end-to-end Flutter integration tests — Flutter Driver setup, MCP-guided exploration, permanent user-flow tests
- What
- Add end-to-end Flutter integration tests — Flutter Driver setup, MCP-guided exploration, permanent user-flow tests
- Cost
- Free
- Needs
- Flutter SDK installed and a runnable app target; designed for Claude Code, Codex or a similar harness
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a Flutter integration-testing skill: configure Flutter Driver for app interaction (enableFlutterDriverExtension, ValueKey targeting on critical widgets, integration_test package) and convert MCP actions into permanent integration tests. Walks through an interactive exploration phase first — launch the app via the Dart/Flutter MCP server, inspect the widget tree, simulate taps, text entry, and scrolling — then converts those explored flows into authored, maintainable end-to-end tests with execution and profiling guidance. Distinct from the sibling Flutter skills also listed here: this one covers full user journeys across screens, while flutter-add-widget-test covers component-level WidgetTester tests and flutter-setup-declarative-routing covers go_router navigation. By @flutter, listed here with credit to its creator. Honest caveats: end-to-end tests are slower and more brittle than widget tests — reserve them for critical user flows; requires the Flutter SDK and a runnable app target. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Flutter Integration Tests is a free Muse skill for Flutter integration tests: configure Flutter Driver, enableFlutterDriverExtension, ValueKey targeting on critical widgets, integration_test package, convert MCP actions into permanent tests. Interactive exploration first, launching the app via the Dart-Flutter MCP server, inspecting the widget tree, simulating taps, text entry, scrolling, converting explored flows into maintainable tests.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 18, 2026📌 Pinned version: commit 0ef3972Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: Flutter SDK installed and a runnable app target; designed for Claude Code, Codex or a similar harness Install "Flutter Integration Tests" for me. Add end-to-end Flutter integration tests — Flutter Driver setup, MCP-guided exploration, permanent user-flow tests Repository: https://raw.githubusercontent.com/flutter/agent-plugins/0ef3972f93e2baa4156ba1cbb1e515cd53079c68/skills/flutter-add-integration-test/SKILL.md Pinned version: install the code at commit 0ef3972f93e2baa4156ba1cbb1e515cd53079c68 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file for the flutter-flutter-add-integration-test skill from the repository into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "flutter-flutter-add-integration-test". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 0ef3972 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 18, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.