patrol-e2e-testing
Use when writing E2E/integration tests, testing native interactions like permissions or system dialogs, capturing UI regressions, or validating cross-platform behavior (Patrol 4.x).
npx skills add evanca/flutter-ai-rules --skill patrol-e2e-testing --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Patrol E2E Testing Skill Design, implement, and run end-to-end (E2E) tests using Patrol 4.x in Flutter projects. ## When to Use Use this skill when: * A new screen or user flow needs E2E test coverage. * A feature interacts with native components (permissions, notifications, system dialogs, deep links). * A UI bug should be captured as a regression test. * Cross-platform behavior (Android / iOS / Web) must be validated. * Setting up Patrol in a new or existing Flutter project. ## Setup Follow the official Patrol documentation for installation and project initialization: [https://patrol.leancode.co/documentation#setup](https://patrol.leancode.co/documentation#setup) Key Patrol conventions: * Add `patrol` as a dev dependency. * Place tests in `patrol_test/`. * Name test files with a `_test.dart` suffix. * Execute tests with `patrol test`. ## Workflow Follow these steps when implementing or updating Patrol tests. ### 1. Identify the user journey Break the feature into: * **Actions**: taps, scrolls, input, navigation, deep links. * **Observable outcomes**: visible text, screen changes, enabled buttons, dialogs. Rules: * One test per primary (happy-path) journey. * Separate tests for
- When to Use
- Setup
- Workflow
- 1. Identify the user journey
- 2. Structure the Patrol test
- 3. Handle native dialogs
- 4. Selector & interaction quick reference
- 5. Running Patrol tests
- 6. Stabilization patterns
- Output requirements
- Quality bar
patrol test patrol develop -t integration_test/my_test.dart patrol test --target patrol_test/login_test.dart patrol test --device chrome patrol test --device chrome --web-headless true patrol test --tags android
What does the patrol-e2e-testing skill do?
Use when writing E2E/integration tests, testing native interactions like permissions or system dialogs, capturing UI regressions, or validating cross-platform behavior (Patrol 4.x).
How do I install it?
Run `npx skills add evanca/flutter-ai-rules --skill patrol-e2e-testing --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From evanca/flutter-ai-rules, a repository with 604 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.