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:
Install
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://github.com/flutter/agent-plugins/blob/main/skills/dart-add-unit-test/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 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.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build 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 build before installing it.