flutter-add-integration-test Skill for Claude: What It Does and How to Install It
Makes Claude set up Flutter integration tests, try your app's screens through MCP, then save those steps as permanent tests.
- Installs
- 39.2K
- on skills.sh
- Stars
- 3.1K
- on GitHub
- Updated
- Nov 2026
- last repo commit
This is the Flutter team's skill for integration testing. Claude adds the integration_test packages, switches on the Flutter Driver extension in your app, explores the running app, then writes tests in integration_test/ and runs them with flutter drive.
It loads when you ask for integration tests, UI exploration through MCP or automated user flows. The exploration step calls tools from the Dart and Flutter MCP server, which this one-file skill does not install for you.
Good for
- Flutter developers adding end-to-end tests to an existing app
- Teams that want to try a user flow by hand through MCP and keep it as a test
- Anyone running tests on Chrome, Android or Firebase Test Lab
Install flutter-add-integration-test
Claude Code
- 1
Copy this prompt.
Install the flutter-add-integration-test skill in Claude Code. Run this command: npx skills add https://github.com/flutter/agent-plugins --skill flutter-add-integration-test Then check that it loaded and tell me how to use it.
- 2
Paste it into Claude Code. It shows the change and asks before running it.
Requires Node.js.
From its listing on skills.sh. Source.
What's in the skill
When it loads
Configures Flutter Driver for app interaction and converts MCP actions into permanent integration tests. Use when adding integration testing to a project, exploring UI components via MCP, or automating user flows with the integration_test package.
Sections in SKILL.md
- Contents
- Project Setup and Dependencies
- Interactive Exploration via MCP
- Test Authoring Guidelines
- Execution and Profiling
- Workflow: End-to-End Integration Testing
- Examples
- Standard Integration Test (integration_test/app_test.dart)
- Host Driver Script (test_driver/integration_test.dart)
- Performance Profiling Driver Script (test_driver/perf_driver.dart)
Key facts
- Author
- Flutter team
- License
- BSD-3-Clause
- Installs on skills.sh
- 39,182 (Nov 2, 2026)
- Last repo commit
- Nov 1, 2026
- What it includes
- 1 file: SKILL.md (no scripts)
What it includes
Adds test packages and the Flutter Driver extension
Adds integration_test and flutter_test as dev dependencies, calls enableFlutterDriverExtension() before runApp(), and adds Keys to key widgets so tests can find them.
Try: “Add integration testing to my Flutter app and put a key on the login button.”
Runs code ·
Project setupLaunches the app and taps through it with MCP tools
Uses launch_app, get_widget_tree, tap, enter_text, scroll and waitFor to try a user flow before writing a test. It scrolls lazy lists so hidden widgets mount first.
Try: “Launch the app, open the checkout screen and tell me which widgets have keys.”
Runs code ·
Explore through MCPCreates integration_test/<name>_test.dart
Initialises IntegrationTestWidgetsFlutterBinding, loads the app with pumpWidget, taps, calls pumpAndSettle and checks widgets with find.byKey.
Write ·
Write the testAdds test_driver/integration_test.dart
Creates the small driver file that calls integrationDriver(), which flutter drive needs.
Write ·
Host driver scriptRuns flutter drive on Chrome, web-server, Android or Firebase
Gives the flutter drive command for each target. Chrome needs chromedriver on port 4444. Firebase Test Lab needs a debug APK and a test APK, which you upload in its console.
Runs code ·
Run the testsAdds perf_driver.dart to save a scrolling timeline
Provides a driver script that summarises a timeline captured with binding.traceAction() and writes it to a file.
Write ·
Performance profilingUses driver.waitFor, tap and scroll for old tests
When you maintain or migrate old flutter_driver tests, Claude uses the driver calls instead of WidgetTester.
Write ·
Legacy flutter_driver
From the official docs
Permissions
Medium risk
The skill edits your project and taps through your running app, so it can create data if the app points at a live backend. Use a debug build with test accounts and review the diff.
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only mode
Watch out for
It drives your running app with taps and typed text
During exploration it can tap buttons and enter text. If the app talks to a real backend, those actions can create real data. Use a debug build and test accounts. github.com
It adds a test hook to your app entry point
enableFlutterDriverExtension() goes in lib/main.dart or a separate lib/main_test.dart. A separate file keeps the hook out of your normal entry point. github.com
It changes your dependencies
flutter pub add adds integration_test and flutter_test to pubspec.yaml. Review the diff before you commit. github.com
Security advisories
No published security advisories as of Nov 2, 2026.
Technical details
| Turning on read-only | No read-only mode. Use version control and a debug build. |
|---|---|
| Talks to | Package downloads when flutter pub add runs. Firebase Test Lab: the skill tells you to upload the APKs in its console |
| Sign-in and keys | SKILL.md does not mention any account or key. |
| Scopes |
|
Questions
What does the flutter-add-integration-test skill do?
It guides Claude through Flutter integration testing. Claude sets up the packages and Flutter Driver, explores your app through MCP, writes tests with the integration_test package and runs them with flutter drive.
How do I install flutter-add-integration-test?
Use the install box at the top of this page. The skill is one SKILL.md file, so there is nothing else to download. Start a new session afterwards so it loads.
Do I need the Dart and Flutter MCP server?
For the exploration step, yes. The skill names the MCP tools launch_app, get_widget_tree, tap, enter_text, scroll, waitFor and get_health. The skill folder holds only SKILL.md, so set the MCP server up separately using the Flutter guide.
Which devices can the tests run on?
The skill covers Chrome (with chromedriver), headless web, a local Android device and Firebase Test Lab on Android. Those are the targets the skill lists.
Integration test vs widget test: which skill do I want?
This skill tests whole-app flows. The same repo has a separate flutter-add-widget-test skill for component-level tests with WidgetTester, per the Flutter README.
Is flutter-add-integration-test safe?
It edits your project and runs commands, so review each step. It adds packages, edits your entry point, runs flutter drive and taps through your running app, which can create real data if the app talks to a real backend. Use a debug build and test accounts, and keep the project under version control.
Does flutter-add-integration-test work in Codex or Cursor?
The README does not list supported clients. It links to https://docs.flutter.dev/ai/get-started for installing the plugins in your preferred agent, so follow that guide for Codex or Cursor.
Information
updated Nov 2, 2026
- Repository
- flutter/agent-plugins
- Folder
skills/flutter-add-integration-test
Sources
Docs, issue trackers and discussions this page is built from.
Show all 2Hide
- flutter-add-integration-test SKILL.md · github.com
- Flutter agent-plugins README · github.com