When to use / when NOT to use
- •Use during active feature work for quick feedback.
- •Do not use as your only CI gate for release PRs.
Preconditions (tools, versions, repo state)
- •Flutter installed.
- •Test directory exists.
Workflow (DISCOVER → PLAN → EXECUTE → VERIFY → REPORT)
- •DISCOVER: detect changed files and test availability.
- •PLAN: decide targeted tests to run.
- •EXECUTE: run changed tests; optionally run full suite.
- •VERIFY: capture completion and key failures.
- •REPORT: summarize targeted/full results.
Exact commands and expected signals
bash
skills/flutter-test-focus/scripts/run.sh --dry-run skills/flutter-test-focus/scripts/run.sh --verify-only skills/flutter-test-focus/scripts/run.sh --execute
Success: targeted tests discovered/executed and report produced. Failure: missing Flutter toolchain or no test setup.
If it fails (checklist)
- •Ensure
test/exists. - •Validate command in local Flutter environment.
- •Run full
flutter testif diff-based detection is empty.
Final report template
- •Changed test files detected.
- •Targeted run status.
- •Full suite status (if run).
- •Next actions.