agentleFS
evancaevanca/flutter-ai-rules/skills/mocktail/SKILL.md

mocktail

Skill669 starsChanged 3 months agoMITView on GitHub

Use when creating mocks, stubbing methods, verifying interactions, registering fallback values, or choosing between mocks, fakes, and real objects (Mocktail).

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 1 is distinctive, and 8 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 8

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Never add @override methods or implementations to a class extending Mock.

    line 21
  2. Very specific:

    Only use mocks if your test has verify assertions.

    line 22
  3. Very specific:

    No code generation required — unlike Mockito, Mocktail uses noSuchMethod at runtime.

    line 33
  4. Very specific:

    Always stub async methods (returning Future or Future<void>) with thenAnswer.

    line 70
  5. Very specific:

    Always include all named parameters in both when and verify calls.

    line 77
  6. Distinctive:

    If a method has default values for named parameters, Mocktail still expects them all to be matched.

    line 86
  7. Very specific:

    Use any() for positional parameters when you don't care about the exact value.

    line 111
  8. Very specific:

    Use captureThat() for conditional capturing.

    line 112
  9. Very specific:

    When matching string output, be aware of what .toString() returns for the type.

    line 113

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

UseWhen
Real objectPrefer 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

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:

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

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:

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

verify(() => mock.fetchData());             // called at least once
verifyNever(() => mock.fetchData());        // never called
verify(() => mock.fetchData()).called(2);   // called exactly twice

7. Argument Matchers

// 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.