mobile-automation
Mobile Automation guides E2E testing and UI verification for Flutter apps using dart-mcp and Marionette MCP. Launch apps on iOS simulators, verify UI elements, run mock scenarios without a Bridge server, or execute full end-to-end flows with Bridge integration for real Claude Code sessions.
Mobile Automation automates Flutter app UI testing and E2E verification through dart-mcp and Marionette MCP tools.
AI-generated summary based on this skill's SKILL.md
Install
K9i-0/ccpocket/mobile-automation · repository language: Dart
git clone https://github.com/K9i-0/ccpocket
cp -r ccpocket/.claude/skills/mobile-automation ~/.claude/skills/mobile-automationFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How to automate flutter UI verification?
Mobile Automation enables Flutter app UI testing automation through dart-mcp and Marionette MCP integration. You can launch apps on iOS simulators, verify UI elements programmatically, validate interactions, and automate widget testing workflows. The skill supports both mock scenarios for isolated component testing and full end-to-end flows when Bridge server integration is configured for real Claude Code sessions.
What is E2E testing flutter apps simulator with Mobile Automation?
Mobile Automation performs end-to-end testing with Bridge server integration, allowing you to test Flutter apps on iOS simulators with full workflow automation. You can verify UI elements, validate user interactions, and execute complete app flows. The skill also supports mock preview testing to validate UI components and behaviors without requiring a backend or Bridge server connection.
Can Mobile Automation test flutter UI changes without a backend?
Yes, Mobile Automation supports mock scenarios and UI component testing without a backend. You can run isolated widget tests, validate UI elements, and verify component behaviors using mock data. This allows you to test Flutter app UI changes and interactions independently, then scale to full end-to-end testing with Bridge server integration when needed.
How does Mobile Automation handle flutter app regression testing?
Mobile Automation automates Flutter app regression testing through UI verification workflows and interaction automation. You can capture and validate UI states, verify element behaviors, and run automated widget tests to detect unintended changes. The skill integrates with dart-mcp and Marionette MCP to enable screenshot automation and behavior verification across simulator sessions.
What testing scenarios does Mobile Automation support for Flutter?
Mobile Automation supports multiple Flutter testing scenarios: automated UI element validation on iOS simulators, end-to-end workflows with Bridge server integration, mock component testing without backend dependencies, widget interaction automation, and app behavior verification. You can combine these approaches—start with isolated mock tests, then execute full end-to-end flows within real Claude Code sessions.
Is Mobile Automation open source and what license applies?
Mobile Automation is released under the MIT license, making it open source and freely available for both commercial and personal use. The MIT license permits modification, distribution, and private use with minimal restrictions, supporting collaborative development and integration into other projects.
SKILL.md
rendered from the published skill — quoted content, verbatim
Mobile Automation
dart-mcp と Marionette MCP を使ったFlutterアプリのUI検証・E2E自動化ガイド。
デフォルト設定
特別な指示がない限り、以下をデフォルトとして使う:
- デバイス: iOSシミュレーター（
flutter devicesで確認し、iPhone Simulator を選択） - Bridge ポート:
8766（テスト用。本番の8765と分離してテストできる） - プロジェクトルート: リポジトリルート（
git rev-parse --show-toplevelで取得） - アプリルート:
<プロジェクトルート>/apps/mobile
ユーザーが実機やポート8765を指定した場合はそちらに従う。
サブエージェント活用
E2E検証は e2e-verifier サブエージェント に委譲すると効率的。独立したコンテキストで検証するため、実装バイアスなく客観的に動作を確認できる。
Agent tool で e2e-verifier サブエージェントを起動:
subagent_type: e2e-verifier
プロンプト:
---
アプリが起動済みです。以下の検証を実施してください。
## 検証内容
[検証したい項目を記述]
## 接続情報
- VM Service URI: [wsUri]
- PID: [pid]
日本語で回答してください。
---
使い分け:
- 単純なUI確認（要素の存在チェック、1-2画面の確認）→ 直接MCP操作
- 包括的なE2E検証（複数画面のフロー、回帰テスト）→ e2e-verifier サブエージェントに委譲
アプリ起動ワークフロー
Step 1: デバイス確認
flutter devices
出力からシミュレーターのデバイスIDを確認する（例: 1A2B3C4D-5E6F-...）。
Step 2:
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
.claude/skills/mobile-automation/SKILL.md