test-driven-development
Write tests first, watch them fail, then implement minimal code to pass.
dart-generate-test-mocks
Define and generate mock objects for external dependencies using package:mockito and build_runner. Use when unit testing classes that depend on complex external services like APIs or databases.
Full skill instructions
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.
http.Client) through class constructors.Uri objects using Uri.parse(string).Configure the pubspec.yaml file with the necessary testing and code generation packages.
package:http) using dart pub add http.dart pub add dev:test dev:mockito dev:build_runner.import 'package:http/http.dart' as http;.Use package:mockito and build_runner to automatically generate mock classes for fixed scenarios and behavior verification.
@GenerateNiceMocks annotation (preferable to @GenerateMocks to avoid missing stub exceptions).MockSpec<Type>() objects..mocks.dart extension.build_runner to generate the mock files: dart run build_runner build.Isolate the system under test using the generated mock objects. Use package:test to structure the test suite.
when(mock.method()).thenReturn(value) for synchronous methods.thenAnswer((_) async => value) for methods returning a Future or Stream. Never use thenReturn for asynchronous returns.verify(mock.method()).called(1) to check exact invocation counts.any, anyNamed, or captureAny for flexible verification.Use the following checklist to implement and verify mocked unit tests.
http.Client).target_test.dart) and add @GenerateNiceMocks([MockSpec<Dependency>()]).part or import directive for the generated .mocks.dart file.dart run build_runner build to generate the mock classes.group() and test().when().verify() and assert outcomes using expect().dart test.If tests fail or build_runner encounters errors:
dart test or dart run build_runner build.@GenerateNiceMocks.ArgumentError, change thenReturn to thenAnswer.build_runner fails, ensure the .mocks.dart import matches the file name exactly.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,
);
});
});
}
Write tests first, watch them fail, then implement minimal code to pass.
Enforce verification commands before claiming work completion, fixes, or test passes—no success assertions without fresh evidence.
Dispatch fresh subagents per task with two-stage review (spec compliance, then code quality) in the current session.
Evaluate code review feedback with technical rigor before implementing, avoiding performative agreement and blind implementation.
Test-driven documentation for creating reusable agent techniques, patterns, and reference guides.
Structured workflow for completing development branches with test verification and merge/PR options.
Browser automation with 40+ commands for navigation, interaction, form filling, and web testing.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Comprehensive reference guide for writing, debugging, and maintaining Playwright tests across all testing types and scenarios.
End-to-end Solana development with framework-kit, @solana/kit, Anchor programs, and local testing.
ab testing
Build custom Expo development clients for testing native code on physical devices via EAS Build or locally.
Opus.ai: Revolutionize Your Web Experience
Build a no-code AI app in minutes.
An IDE for code migration from legacy to modern frameworks through coding agents.
Automate CGI animation in live-action scenes
Branded artistic QR-code concepts
Launch a website in seconds with AI.
Streamline Your Coding Experience with AI Code Helper
Convert any screenshot or design to clean code.