Write Dart and Flutter unit tests with package:test
Write and organize unit tests for Dart/Flutter functions, methods and classes with package:test — test file layout, groups, setUp/tearDown, matchers, async tests, Mockito DI, and the test implementation workflow
- What
- Write and organize unit tests for Dart/Flutter functions, methods and classes with package:test — test file layout, groups, setUp/tearDown, matchers, async tests, Mockito DI, and the test implementation workflow
- Cost
- Free
- Needs
- the Dart or Flutter SDK installed and a Dart/Flutter project to test — the skill is guidance the agent follows, not software to install
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @flutter's skill for writing Dart and Flutter unit tests with `package:test`: organize test files to mirror `lib/` under `test/` with the `_test.dart` suffix (`integration_test/` for integration tests); import `package:test/test.dart` (or `package:flutter_test/flutter_test.dart` for Flutter); group related tests with `group()`, define cases with `test()`, assert with `expect()` and matchers (`equals()`, `isTrue`, `throwsA()`); write async tests with plain `async`/`await`; manage setup/teardown with `setUp()`/`tearDown()`; use `package:mockito` alongside `package:test` for dependency injection; pick the runner per project type (`dart test` for pure Dart, `flutter test` for Flutter, explicit directory for integration tests). Includes a sequential test-implementation workflow with a copyable checklist and a feedback loop (run → review stack trace → fix → re-run until green), plus worked examples (a standard unit test suite; mocking with `@GenerateNiceMocks`). Honest caveats: methodology only — you need the Dart or Flutter SDK installed; the deep Mockito mock-generation guidance lives in the companion skill dart-generate-test-mocks in the same repo. BSD-3-Clause licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Write Dart and Flutter unit tests is a free skill from @flutter for writing Dart and Flutter unit tests with package:test. It mirrors lib under test with the _test.dart suffix, uses group, test, expect and matchers, handles async with async and await, manages setup and teardown, uses mockito, and picks dart test or flutter test.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 18, 2026📌 Pinned version: commit 0ef3972Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: the Dart or Flutter SDK installed and a Dart/Flutter project to test — the skill is guidance the agent follows, not software to install Install "Write Dart and Flutter unit tests with package:test" for me. It teaches my agent @flutter's unit-testing workflow: mirror lib/ under test/ with _test.dart suffix; use package:test (flutter_test for Flutter) with group()/test()/expect() and matchers; write async tests with async/await; setUp/tearDown for fixtures; Mockito for dependency injection; pick the right runner (dart test vs flutter test); follow the implementation checklist and the run → review → fix feedback loop until green. BSD-3-Clause licensed. Repository: https://raw.githubusercontent.com/flutter/agent-plugins/0ef3972f93e2baa4156ba1cbb1e515cd53079c68/skills/dart-add-unit-test/SKILL.md Pinned version: install the code at commit 0ef3972f93e2baa4156ba1cbb1e515cd53079c68 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "dart-add-unit-test". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. point the agent at the Dart/Flutter code to test; install the companion dart-generate-test-mocks skill from the same repo if you need deep Mockito mock generation). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 0ef3972 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 18, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.