
dart-generate-test-mocks
Define and generate mock objects for external dependencies using package:mockito and buildrunner. Use when unit testing classes that depend on complex external services like APIs or databases.
- Installs
- 14.4K
- Last 24h
- +186
- Trending rank
- #1286
- Security
- Pass
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/flutter/agent-plugins --skill dart-generate-test-mocks- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads dart-generate-test-mocks automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
Security audits
Independent scans of the skill's instructions and bundled files.
SKILL.md
The instructions your agent reads when the skill is triggered.
Testing and Mocking Dart Applications
Contents
- Structuring Code for Testability
- Managing Dependencies
- Generating Mocks
- Implementing Unit Tests
- Workflow: Creating and Running Mocked Tests
- Examples
Structuring Code for Testability
Design Dart classes to support dependency injection. Isolate complex external dependencies (like API clients or databases) so they can be replaced with mock objects during testing.
- Inject external services (e.g.,
http.Client) through class constructors. - Represent URLs strictly as
Uriobjects usingUri.parse(string). - Utilize Dart's object-oriented features (classes, mixins) to define clear interfaces for external interactions.
Managing Dependencies
Configure the pubspec.yaml file with the necessary testing and code generation packages.
- Add runtime dependencies (e.g.,
package:http) usingdart pub add http. - Add testing dependencies using
dart pub add dev:test dev:mockito dev:build_runner. - Import HTTP libraries with a prefix to avoid namespace collisions:
import 'package:http/http.dart' as http;.
Generating Mocks
Use package:mockito and build_runner to automatically generate mock classes for fixed scenarios and behavior verification.
- Always use the
@GenerateNiceMocksannotation (preferable to@GenerateMocksto avoid missing stub exceptions). - Place the annotation in the test file, passing a list of
MockSpec<Type>()objects. - Import the generated file using the
.mocks.dartextension. - Execute
build_runnerto generate the mock files:dart run build_runner build.
Implementing Unit Tests
Isolate the system under test using the generated mock objects. Use package:test to structure the test suite.
- Stubbing: Configure mock behavior before interacting with the system under test.
- Use
when(mock.method()).thenReturn(value)for synchronous methods. - CRITICAL: Always use
thenAnswer((_) async => value)for methods returning aFutureorStream. Never usethenReturnfor asynchronous returns.
- Use
- Verification: Assert that the system under test interacted with the mock object correctly.
- Use
verify(mock.method()).called(1)to check exact invocation counts. - Use argument matchers like
any,anyNamed, orcaptureAnyfor flexible verification.
- Use
Workflow: Creating and Running Mocked Tests
Use the following checklist to implement and verify mocked unit tests.
Task Progress
- 1. Identify the external dependency to mock (e.g.,
http.Client). - 2. Inject the dependency into the target class constructor.
- 3. Create a test file (e.g.,
target_test.dart) and add@GenerateNiceMocks([MockSpec<Dependency>()]). - 4. Add the
partorimportdirective for the generated.mocks.dartfile. - 5. Run
dart run build_runner buildto generate the mock classes. - 6. Write the test cases using
group()andtest(). - 7. Stub required behaviors using
when(). - 8. Execute the target method.
- 9. Verify interactions using
verify()and assert outcomes usingexpect(). - 10. Run the test suite using
dart test.
Feedback Loop: Test Failures
If tests fail or build_runner encounters errors:
- Run validator: Execute
dart testordart run build_runner build. - Review errors: Check for missing stubs, mismatched argument matchers, or syntax errors in the generated files.
- Fix:
- If a mock method throws an unexpected null error, ensure you used
@GenerateNiceMocks. - If an async stub throws an
ArgumentError, changethenReturntothenAnswer. - If
build_runnerfails, ensure the.mocks.dartimport matches the file name exactly.
- If a mock method throws an unexpected null error, ensure you used
- Repeat until all tests pass.
Examples
High-Fidelity Mocking and Testing Example
1. System Under Test (lib/api_service.dart)
import 'dart:convert';
import 'package:http/http.dart' as http;
class ApiService {
final http.Client client;
ApiService(this.client);
Future<String> fetchData(String urlString) async {
final uri = Uri.parse(urlString);
final response = await client.get(uri);
if (response.statusCode == 200) {
return jsonDecode(response.body)['data'];
} else {
throw Exception('Failed to load data');
}
}
}
2. Test Implementation (test/api_service_test.dart)
import 'package:test/test.dart';
import 'package:mockito/annotations.dart';
import 'package:mockito/mockito.dart';
import 'package:http/http.dart' as http;
import 'package:my_app/api_service.dart';
// Generate the mock class for http.Client
@GenerateNiceMocks([MockSpec<http.Client>()])
import 'api_service_test.mocks.dart';
void main() {
group('ApiService', () {
late ApiService apiService;
late MockClient mockHttpClient;
setUp(() {
mockHttpClient = MockClient();
apiService = ApiService(mockHttpClient);
});
test('returns data if the http call completes successfully', () async {
// Arrange: Stub the async HTTP GET request using thenAnswer
when(mockHttpClient.get(any)).thenAnswer(
(_) async => http.Response('{"data": "Success"}', 200),
);
// Act
final result = await apiService.fetchData('https://api.example.com/data');
// Assert
expect(result, 'Success');
// Verify the mock was called with the correct Uri
verify(mockHttpClient.get(Uri.parse('https://api.example.com/data'))).called(1);
});
test('throws an exception if the http call completes with an error', () {
// Arrange
when(mockHttpClient.get(any)).thenAnswer(
(_) async => http.Response('Not Found', 404),
);
// Act & Assert
expect(
apiService.fetchData('https://api.example.com/data'),
throwsException,
);
});
});
}
FAQ
What does the dart-generate-test-mocks skill do?
Define and generate mock objects for external dependencies using package:mockito and buildrunner. Use when unit testing classes that depend on complex external services like APIs or databases.
How do I install dart-generate-test-mocks?
Run npx skills add https://github.com/flutter/agent-plugins --skill dart-generate-test-mocks in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/dart-generate-test-mocks/ (personal) or .claude/skills/dart-generate-test-mocks/ (project).
Which AI agents can use dart-generate-test-mocks?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is dart-generate-test-mocks safe to install?
Security partners have reviewed it: Gen Agent Trust Hub passed; Socket passed; Snyk passed. As with any skill, read the SKILL.md and bundled scripts before installing.
Who maintains dart-generate-test-mocks?
It is published by flutter in flutter/agent-plugins. It has 14,416 recorded installs.
More from flutter/agent-plugins
flutter-apply-architecture-best-practices
flutter/agent-plugins
Architects a Flutter application using the recommended layered approach (UI, Logic, Data). Use when structuring a new project or refactoring for scalability.
flutter-build-responsive-layout
flutter/agent-plugins
Use LayoutBuilder, MediaQuery, or Expanded/Flexible to create a layout that adapts to different screen sizes. Use when you need the UI to look good on both mobile and tablet/desktop form factors.
flutter-fix-layout-issues
flutter/agent-plugins
Fixes Flutter layout errors (overflows, unbounded constraints) using Dart and Flutter MCP tools. Use when addressing "RenderFlex overflowed", "Vertical viewport was given unbounded height", or similar layout issues.
flutter-add-widget-test
flutter/agent-plugins
Implement a component-level test using WidgetTester to verify UI rendering and user interactions (tapping, scrolling, entering text). Use when validating that a specific widget displays correct data and responds to events as expected.
flutter-add-integration-test
flutter/agent-plugins
Configures Flutter Driver for app interaction and converts MCP actions into permanent integration tests. Use when adding integration testing to a project, exploring UI components via MCP, or automating user flows with the integrationtest package.
flutter-setup-declarative-routing
flutter/agent-plugins
Configure MaterialApp.router using a package like gorouter for advanced URL-based navigation. Use when developing web applications or mobile apps that require specific deep linking and browser history support.
Popular testing & qa skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
grilling
mattpocock/skills
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
migrate-to-shoehorn
mattpocock/skills
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
run-train
lllllllama/rigorpilot-skills
Rigor Train skill for deep learning research repositories. Use when a documented or selected training command should be run conservatively for startup verification, short-run verification, full kickoff, or resume, with command, config, seed, log, checkpoint, status, and metric evidence written to standardized trainoutputs/. Do not use for environment setup, exploratory sweeps, speculative idea implementation, or end-to-end orchestration.
test-driven-development
obra/superpowers
Use when implementing any feature or bugfix, before writing implementation code
finishing-a-development-branch
obra/superpowers
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work