How do I install the Flutter Testing skill?

Run npx skillmds@latest add comeonoliver/flutter-testing in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Flutter Testing safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Flutter Testing?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Flutter Testing free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Flutter Testing?

ComeOnOliver (@comeonoliver) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Flutter Testing by comeonoliver — Agent Skill

Name: Flutter Testing
Rating: 4.2 (5 reviews)
Author: ComeOnOliver

Flutter Testing

Unit, widget, and integration testing with robots, widget keys, and Patrol. Use when writing Flutter unit tests, widget tests, or integration tests with Patrol. (triggers: **/test/**.dart, **/integration_test/**.dart, **/robots/**.dart, lib/core/keys/**.dart, test, patrol, robot, WidgetKeys, patrolTest, blocTest, mocktail)

ComeOnOliver Updated Sep 8, 2026 61 repo stars

File contents

Flutter Testing Standards

Priority: P0 (CRITICAL)

Core Rules

Test Pyramid: Unit > Widget > Integration.
Naming: should <behavior> when <condition>.
AAA: Arrange, Act, Assert in all tests.
Shared Mocks: test/shared/ only — no local mocks.
File Placement: _integration_test.dart ONLY in integration_test/.
Robot-First: ALL UI assertions/interactions via Robot pattern (e.g., CheckoutRobot) — never raw find.*/expect() in test body.

Widget Testing & Mocking

Setup: Use TestWrapper.init() in setUpAll and tester.pumpLocalizedWidget(...).
Mocking: Use GetIt registration of Mock BLoCs in setUpAll if created internally. Use blocTest for BLoC logic and whenListen for state transitions.
Stubbing: Always stub bloc.state and bloc.stream in setUp. Prohibit any() / anyNamed().
Async: Use settle: false for loading or stream states to verify mid-process transitions.

Robot Pattern

All interactions and assertions belong in *Robot (e.g., expectFirstOrderVisible()).
Symmetric: every expectXxxVisible() needs expectXxxNotVisible() pairs.
Widget tests: include a pumpScreen(bloc:, settle:) helper.
Widget Keys: Use WidgetKeys constants from lib/core/keys/ — never inline Key('string').

Integration Testing

Use patrolTest with IntegrationAuthHelper.loginOrSkip($) for authenticated flows.
Use $.native.tap() or $.native.* for native interactions (e.g., system dialogs).
Create a robot: final robot = OrdersRobot($.tester) — share the same class as widget tests.
Only $.native.* and navigation helpers may remain inline in the test body.

Anti-Patterns

No inline Key: Use WidgetKeys constant. No any(): Use typed matchers.
No local mocks: Use test/shared/. No missing bloc stub: Stub state + stream.
No test-body logic: Move find.*/expect() to robot. No raw find in integration tests.
No _integration_test.dart in test/: Rename or merge.
No unused imports: Remove v_dls when robots handle assertions. Check Material import needs.
No happy-path-only: Add Edge cases group. No one-sided assertions: Add expectNotVisible pairs.
No unchecked text casing: Verify .toUpperCase(), .tr() in source.

---name: flutter-testingdescription: Unit, widget, and integration testing with robots, widget keys, and Patrol. Use when writing Flutter unit tests, widget tests, or integration tests with Patrol. (triggers: **/test/**.dart, **/integration_test/**.dart, **/robots/**.dart, lib/core/keys/**.dart, test, patrol, robot, WidgetKeys, patrolTest, blocTest, mocktail)---# Flutter Testing Standards## **Priority: P0 (CRITICAL)**## Core Rules1. **Test Pyramid**: Unit > Widget > Integration.2. **Naming**: `should <behavior> when <condition>`.3. **AAA**: Arrange, Act, Assert in all tests.4. **Shared Mocks**: `test/shared/` only — no local mocks.5. **File Placement**: `_integration_test.dart` ONLY in `integration_test/`.6. **Robot-First**: ALL UI assertions/interactions via **Robot pattern** (e.g., `CheckoutRobot`) — never raw `find.*`/`expect()` in test body.## Widget Testing & Mocking- **Setup**: Use `TestWrapper.init()` in `setUpAll` and `tester.pumpLocalizedWidget(...)`.- **Mocking**: Use **GetIt registration** of Mock BLoCs in `setUpAll` if created internally. Use **blocTest** for BLoC logic and **whenListen** for state transitions.- **Stubbing**: Always stub **bloc.state** and **bloc.stream** in `setUp`. Prohibit `any()` / `anyNamed()`.- **Async**: Use **settle: false** for loading or stream states to verify mid-process transitions.## Robot Pattern- All interactions and assertions belong in `*Robot` (e.g., `expectFirstOrderVisible()`).- Symmetric: every `expectXxxVisible()` needs **expectXxxNotVisible()** pairs.- Widget tests: include a `pumpScreen(bloc:, settle:)` helper.- **Widget Keys**: Use **WidgetKeys** constants from `lib/core/keys/` — never inline `Key('string')`.## Integration Testing- Use **patrolTest** with **IntegrationAuthHelper.loginOrSkip($)** for authenticated flows.- Use **$.native.tap()** or `$.native.*` for native interactions (e.g., system dialogs).- Create a robot: `final robot = OrdersRobot($.tester)` — share the same class as widget tests.- Only `$.native.*` and navigation helpers may remain inline in the test body.## Anti-Patterns- **No inline Key**: Use `WidgetKeys` constant. **No `any()`**: Use typed matchers.- **No local mocks**: Use `test/shared/`. **No missing bloc stub**: Stub `state` + `stream`.- **No test-body logic**: Move `find.*`/`expect()` to robot. **No raw find in integration tests**.- **No `_integration_test.dart` in `test/`**: Rename or merge.- **No unused imports**: Remove `v_dls` when robots handle assertions. Check Material import needs.- **No happy-path-only**: Add `Edge cases` group. **No one-sided assertions**: Add `expectNotVisible` pairs.- **No unchecked text casing**: Verify `.toUpperCase()`, `.tr()` in source.

Frequently asked questions