flutter-testing-apps
Implements unit, widget, and integration tests for a Flutter app. Use when ensuring code quality and preventing regressions through automated testing.
- License 许可
- MIT
- 最近更新
- 2026-06-13
- Stars
- ★ 3
- Forks
- 1
01 前言 Front Matter
- name
- flutter-testing-apps
- description
- Implements unit, widget, and integration tests for a Flutter app. Use when ensuring code quality and preventing regressions through automated testing.
03 SKILL.md 正文
Testing Flutter Applications
Contents
Core Testing Strategies
Balance your testing suite across three categories to optimize for confidence, maintenance cost, and execution speed.
Unit Tests
Verify the correctness of a single function, method, or class.
- Mock all external dependencies.
- Do not involve disk I/O, screen rendering, or user actions.
- Execute using the
testorflutter_testpackage.
Widget Tests
Ensure a single widget's UI looks and interacts as expected.
- Provide widget lifecycle context using
WidgetTester. - Use
Finderclasses to locate widgets andMatcherconstants to verify state. - Test views and UI interactions without the full application.
Integration Tests
Validate how individual pieces work together and capture performance metrics on real devices.
- Add the
integration_testpackage as a dependency. - Run on physical devices, OS emulators, or Firebase Test Lab.
- Prioritize for routing, dependency injection, and critical user flows.
Architectural Testing Guidelines
Design for observability and testability:
- ViewModels/Providers: Unit test every provider. Test UI logic without Flutter framework dependency.
- Repositories & Services: Unit test with mocked data sources (HTTP clients, databases).
- Views: Widget test all views. Pass faked or mocked providers to isolate UI.
- Fakes over Mocks: Prefer
Fakeimplementations over mocking libraries for well-defined inputs and outputs.
Workflows
Implementing a Component Test Suite
- [ ] Create
Fakeimplementations for Repositories or Services. - [ ] Write Unit Tests for the Repository (mocking API/Database).
- [ ] Write Unit Tests for the ViewModel/Provider (injecting Fakes).
- [ ] Write Widget Tests for the View (injecting providers and Fakes).
- [ ] Write an Integration Test for the critical path.
- [ ] Review coverage and fix missing edge cases.
Running Integration Tests
- Mobile (Local):
flutter test integration_test/app_test.dart - Web: Launch ChromeDriver, then
flutter drive --driver=test_driver/integration_test.dart --target=integration_test/app_test.dart -d chrome
Examples
ViewModel/Provider Unit Test
import 'package:flutter_test/flutter_test.dart';
void main() {
group('HomeViewModel tests', () {
test('Load bookings successfully', () {
final viewModel = HomeViewModel(
bookingRepository: FakeBookingRepository()..createBooking(kBooking),
userRepository: FakeUserRepository(),
);
expect(viewModel.bookings.isNotEmpty, true);
});
});
}
View Widget Test
import 'package:flutter/material.dart';
import 'package:flutter_test/flutter_test.dart';
void main() {
group('HomeScreen tests', () {
late HomeViewModel viewModel;
setUp(() {
viewModel = HomeViewModel(
bookingRepository: FakeBookingRepository()..createBooking(kBooking),
userRepository: FakeUserRepository(),
);
});
testWidgets('renders bookings list', (WidgetTester tester) async {
await tester.pumpWidget(
MaterialApp(home: HomeScreen(viewModel: viewModel)),
);
expect(find.byType(ListView), findsOneWidget);
expect(find.text('Booking 1'), findsOneWidget);
});
});
}
Integration Test
import 'package:flutter/material.dart';
import 'package:flutter_test/flutter_test.dart';
import 'package:integration_test/integration_test.dart';
import 'package:my_app/main.dart';
void main() {
IntegrationTestWidgetsFlutterBinding.ensureInitialized();
group('end-to-end test', () {
testWidgets('tap FAB, verify counter', (tester) async {
await tester.pumpWidget(const MyApp());
expect(find.text('0'), findsOneWidget);
await tester.tap(find.byKey(const ValueKey('increment')));
await tester.pumpAndSettle();
expect(find.text('1'), findsOneWidget);
});
});
}
04 同仓库更多 Skills
hello-checker
Use this skill when asked to "verify", "check", or "validate" a file's existence and content. It provides a reliable workflow for confirming files meet their spec.
ask-skill
暂无简介
html-review-artifact
Framework-wide guidance for crafting polished human-review artifacts as markdown or HTML
converge-planning
Design a Converge playbook end-to-end. Use when the user says "plan a project", "design a playbook", "decompose into tasks", "scaffold a Converge workflow", "onboard to Converge", or asks how to write TASK.md / playbook.yml. Two entry points: plan a new playbook or update an existing one. Hand off to `/converge-control` after producing the playbook structure.
converge-control
Operate a Converge playbook end-to-end — start runs, monitor progress, narrow failures with `--select`, inspect runtime state, validate definitions, surgically reset subtrees, and stop stuck or orphaned runs. Use this skill whenever the user says "run my playbook", "execute this", "monitor the run", "converge failed", "the run is stuck", "retry failures", "babysit this playbook", "what's the status?", "show me the gantt", or asks how to use `converge run` / `--select` / `inspect` / `doctor` / `clean` / `stop`. Also use it for `HTTP 401` / `Invalid API key` failures on the first task — those are environment-not-playbook problems — and for any post-run cleanup work. Hand off to `converge-planning` if the user wants to design or restructure the playbook itself.
repair-taskts
Fix task.ts definition issues — Seed syntax, missing .build(), empty checks, import errors, TypeScript errors