Write Flutter Tests
Write and extend Dart/Flutter unit (bloc/cubit), widget, and Patrol E2E tests using bloc_test, mocktail, page objects, and project templates. Use when asked to write, add, update, fix, or refactor Flutter tests or test setup.
Install
$ agentstack add skill-wreos-flutter-cursor-plugin-write-flutter-tests ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-wreos-flutter-cursor-plugin-write-flutter-tests) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Write Flutter Tests
Use this skill as the single entry point for Flutter test work.
Workflow
- Detect scope: widget test vs bloc/cubit test vs Patrol E2E test.
- If the repo has shared test setup helpers (for example
TestEnv,pumpApp), reuse them. - Load only the needed guide:
- Widget:
widget-tests.md - Bloc/Cubit:
bloc-tests.md - Integration/E2E (Patrol):
integration-tests.md
- Apply shared constraints from
../../rules/flutter-test-best-practices.mdc. - Start from the matching template:
../../templates/widget_test_template.dart../../templates/bloc_test_template.dart../../templates/integration_test_template.dart
- Run only impacted tests and fix failures.
- Prefer behavior-first assertions:
- user action -> observable outcome,
- expected branch visible + conflicting branch hidden,
- avoid synthetic-only style assertions unless style is the requirement.
Description Format
- Event tests:
WHEN user taps THEN - State tests:
GIVEN THEN - Never write:
WHEN widget is pumped/WHEN page is built
Progressive Disclosure
- Keep this file short.
- Put implementation detail in:
widget-tests.mdbloc-tests.mdintegration-tests.md../../docs/test-environment-setup.md
Guardrails
- Prefer deterministic tests over time-dependent assertions.
- Keep test setup local unless shared helpers already exist.
- Avoid broad snapshot/golden assertions unless explicitly requested.
- Do not present sample test snippets as completed repository changes without file-level confirmation.
Required output
- Test type selected and why.
- Files created/updated.
- Test commands run and results.
- Flakiness risks or missing coverage notes.
- Next test to add (single highest-value gap).
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Wreos
- Source: Wreos/flutter-cursor-plugin
- License: MIT
- Homepage: https://docs.flutter.dev/ai/get-started
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.