mocktail — Claude Code skill: mocking and setup
Guidance for using Mocktail in Dart and Flutter tests: configure stubs, inspect interactions, and decide when a mock, fake, or real object fits.
MIT ★ 674 updated 2026-10-29
/plugin marketplace add evanca/flutter-ai-rules
/plugin install flutter-ai-skills@flutter-ai-rulesWhat mocktail does
The skill lays out when to keep a real object, write a small fake, or use a mock to inspect calls and arguments. It covers setting return values and errors, capturing arguments, and checking whether a method ran. Async methods use thenAnswer.
Examples show Mock and Fake classes, when stubs, and verify checks. Custom types passed to any(), captureAny(), or captureThat() need a fallback registered first. That requirement matters for non-nullable custom types; when interaction checks are unnecessary, the guidance favors a fake or real object over a mock.
What it helps with
- choose a mock, fake, or real object for a test
- stub a method to return a value or throw an error
- check how often a method ran and which arguments it received
- capture method arguments for later assertions
- register fallback values for custom argument types
Example prompts for the agent
- Help me write a Dart test with Mocktail and check how often
fetchDataruns. - Stub the async
fetchDatamethod to return a test result. - Show me how to capture the argument passed to
processand assert its value.
How to install mocktail
1Plugin marketplace
/plugin marketplace add evanca/flutter-ai-rules/plugin install flutter-ai-skills@flutter-ai-rulesThis installs the whole flutter-ai-skills plugin with all its skills
2Skills CLI (Vercel)
npx skills add evanca/flutter-ai-rules --skill mocktail -a claude-code3Manually: put the files in place
~/.claude/skills/mocktail/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/mocktail/
1Skills CLI (Vercel)
npx skills add evanca/flutter-ai-rules --skill mocktail -a codex2Manually: put the files in place
.agents/skills/mocktail/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add evanca/flutter-ai-rules --skill mocktail -a cursor2Manually: put the files in place
.cursor/skills/mocktail/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install evanca/flutter-ai-rules skills/mocktail2Manually: put the files in place
.github/skills/mocktail/SKILL.md1Skills CLI (Vercel)
npx skills add evanca/flutter-ai-rules --skill mocktail -a gemini-cli2Platform CLI
gemini skills install https://github.com/evanca/flutter-ai-rules --path skills/mocktailManually: put the files in place
.devin/skills/mocktail/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about mocktail
How do I install mocktail in Claude Code?
Add the marketplace with /plugin marketplace add evanca/flutter-ai-rules, then install the skill with /plugin install flutter-ai-skills@flutter-ai-rules.
What does the mocktail skill do?
It guides you through stubbing methods and checking interactions in Dart and Flutter tests. It also explains when a mock, fake, or real object is the right choice.
When should I register a Mocktail fallback value?
Register it before matching a custom type with any(), captureAny(), or captureThat(). The skill shows registration in setUpAll or at the start of a test.
Source text
SKILL.md · MIT
---
name: mocktail
description: "Use when creating mocks, stubbing methods, verifying interactions, registering fallback values, or choosing between mocks, fakes, and real objects (Mocktail)."
license: MIT
---
# Mocktail Skill
This skill defines how to correctly use the `mocktail` package for mocking in Dart and Flutter tests.
---
## 1. Mock vs. Fake vs. Real Object
| Use | When |
|---|---|
| **Real object** | Prefer over mocks when practical. |
| **Fake** (`extends Fake`) | Lightweight custom implementation; override only the methods you need. Prefer over mocks when you don't need interaction verification. |
| **Mock** (`extends Mock`) | Only when you need to **verify interactions** (call counts, arguments) or stub dynamic responses. |
- Never add `@override` methods or implementations to a class extending `Mock`.
- Only use mocks if your test has `verify` assertions; otherwise prefer real or fake objects.
---
## 2. Creating Mocks
```dart
class MockMyService extends Mock implements MyService {}
class FakeMyEvent extends Fake implements MyEvent {}
```
No code generation required — unlike Mockito, Mocktail uses `noSuchMethod` at runtime.
---
## 3. Registering Fallback Values
Register fallback values **before** using custom types with argument matchers. Do this in `setUpAll` or at the top of your test:
```dart
setUpAll(() {
registerFallbackValue(FakeMyEvent());
});
```
- Required for non-nullable custom types used with `any()`, `captureAny()`, or `captureThat()`.
- Register fallback values for **any** custom type used with argument matchers.
---
## 4. Stubbing
```dart
final mock = MockMyService();
// Return a value
when(() => mock.fetchData()).thenReturn('result');
// Throw an error
when(() => mock.fetchData()).thenThrow(Exception('error'));
// Dynamic/async response
when(() => mock.fetchData()).thenAnswer((_) async => 'result');
// Future<void>
when(() => mock.doWork()).thenAnswer((_) async {});
```
- Always stub async methods (returning `Future` or `Future<void>`) with `thenAnswer`.
- Stub every method you expect to be called, even if it's not the focus of your test.
---
## 5. Named Parameters
Always include **all named parameters** in both `when` and `verify` calls. Use `any(named: 'paramName')` for those you don't care about:
```dart
when(() => mock.fetch(
id: any(named: 'id'),
headers: any(named: 'headers'),
)).thenReturn(response);
```
- If a method has default values for named parameters, Mocktail still expects them all to be matched.
---
## 6. Verification
```dart
verify(() => mock.fetchData()); // called at least once
verifyNever(() => mock.fetchData()); // never called
verify(() => mock.fetchData()).called(2); // called exactly twice
```
---
## 7. Argument Matchers
```dart
// Any positional argument
when(() => mock.process(any())).thenReturn(true);
// Capture arguments for later assertions
final captured = verify(() => mock.process(captureAny())).captured;
print(captured.last);
```
- Use `any()` for positional parameters when you don't care about the exact value.
- Use `captureThat()` for conditional capturing.
- When matching string output, be aware of what `.toString()` returns for the type.
---
## References
- [Mocktail GitHub Repository](https://github.com/felangel/mocktail)
© Ivanna Kaceviča · MIT · evanca/flutter-ai-rules