Flutter自动化测试指南：单元测试、部件测试、集成测试与插件测试全解析

flutter-testing by flutter/skills

1,000 周安装量

808 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/flutter/skills --skill flutter-testing

开发 Flutter 测试

🇨🇳中文介绍

flutter-automated-testing

目标

为 Flutter 应用程序生成、配置和调试自动化测试，涵盖单元测试、部件测试、集成测试和插件测试。分析架构组件（如 MVVM 层），以生成隔离的、基于模拟的测试和端到端的设备测试。假设为标准 Flutter 项目结构，存在业务逻辑，并熟悉 Dart 测试范式。

说明

1. 确定测试类型（决策逻辑）

评估用户的目标代码，使用以下决策树确定合适的测试策略：

如果验证单个函数、方法、ViewModel 或 Repository： 实现 单元测试（继续步骤 2）。
如果验证单个部件的 UI、布局或交互： 实现 部件测试（继续步骤 3）。
如果验证完整应用在设备上的行为、路由或性能： 实现 集成测试（继续步骤 4）。
如果验证平台特定的原生代码（MethodChannels）： 实现 插件测试（继续步骤 5）。

停止并询问用户： "我们今天要测试哪个具体的类、部件或流程？如果尚未提供，请提供相关的源代码。"

2. 实现单元测试（逻辑与架构）

单元测试在不渲染 UI 的情况下验证逻辑。它们必须位于 test/ 目录下，并以 _test.dart 结尾。

对于 ViewModels（UI 层逻辑）： 模拟 Repository 依赖。不要依赖 Flutter UI 库。

import 'package:test/test.dart'; // 在此处导入你的 ViewModel 和模拟类

void main() { group('HomeViewModel 测试', () { test('成功加载预订', () { final viewModel = HomeViewModel( bookingRepository: FakeBookingRepository()..createBooking(kBooking), userRepository: FakeUserRepository(), );

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

3. 实现部件测试（UI 组件）

部件测试验证 UI 渲染和交互。它们必须位于 test/ 目录下，并使用 flutter_test 包。

使用 WidgetTester 来构建部件。
使用 Finder 来定位元素（find.text()、find.byKey()、find.byWidget()）。
使用 Matcher 来验证存在性（findsOneWidget、findsNothing、findsNWidgets）。

import 'package:flutter/material.dart'; import 'package:flutter_test/flutter_test.dart';

void main() { testWidgets('HomeScreen 显示标题并处理点击', (WidgetTester tester) async { // 1. 设置模拟类和 ViewModel final bookingRepository = FakeBookingRepository()..createBooking(kBooking); final viewModel = HomeViewModel( bookingRepository: bookingRepository, userRepository: FakeUserRepository(), );
```
// 2. 构建部件树
await tester.pumpWidget(
  MaterialApp(
    home: HomeScreen(viewModel: viewModel),
  ),
);

// 3. 查找器
final titleFinder = find.text('Home');
final buttonFinder = find.byKey(const Key('increment_button'));

// 4. 断言
expect(titleFinder, findsOneWidget);

// 5. 交互
await tester.tap(buttonFinder);
await tester.pumpAndSettle(); // 等待动画/状态更新完成

expect(find.text('1'), findsOneWidget);
```
}); }

4. 实现集成测试（端到端）

集成测试在真实设备或模拟器上运行。它们必须位于 integration_test/ 目录下。

确保 pubspec.yaml 的 dev_dependencies 中包含 integration_test。
初始化 IntegrationTestWidgetsFlutterBinding。

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' as app;

void main() { IntegrationTestWidgetsFlutterBinding.ensureInitialized();

group('端到端应用测试', () { testWidgets('完整流程：点击 FAB 并验证计数器', (WidgetTester tester) async { // 加载完整应用 app.main(); await tester.pumpAndSettle();
```
  // 验证初始状态
  expect(find.text('0'), findsOneWidget);

  // 查找并点击 FAB
  final fab = find.byKey(const ValueKey('increment'));
  await tester.tap(fab);
  
  // 触发一帧
  await tester.pumpAndSettle();

  // 验证状态变化
  expect(find.text('1'), findsOneWidget);
});
```
}); }

5. 实现插件测试（原生与 Dart）

如果测试插件，测试必须覆盖 Dart 和原生通信。

Dart 端： 模拟平台通道并调用插件的公共 API。
原生端： 指导用户在相应的目录中编写原生测试：
- Android: android/src/test/ (JUnit)
- iOS/macOS: example/ios/RunnerTests/ (XCTest)
- Linux/Windows: linux/test/ (GoogleTest)

6. 验证与修复（反馈循环）

向用户提供运行生成测试的确切命令：

单元/部件测试：flutter test test/your_test_file.dart
集成测试：flutter test integration_test/your_test_file.dart

停止并询问用户： "请使用上面的命令运行测试并粘贴输出。如果测试失败，请提供堆栈跟踪，以便我分析失败原因并生成修复方案。"

单一事实来源： 不要在测试中重复状态。始终使用模拟类来隔离外部依赖（Repositories、Services），以确保被测试单元的独立性。
部件中无逻辑： 编写部件测试时，假设部件是"哑"的。所有业务逻辑都应通过 ViewModel/Controller 的单元测试来验证。
文件命名： 所有测试文件必须以 _test.dart 结尾。
Pump 与 PumpAndSettle： 使用 tester.pump() 来推进单帧。仅在等待动画或异步 UI 更新完成时，严格使用 tester.pumpAndSettle()。
不可变性： 将测试数据模型视为不可变的。为状态更改创建新实例，而不是修改现有的模拟数据。
不要使用 dart:mirrors： Flutter 不支持反射。依赖代码生成（例如 build_runner、mockito、mocktail）来进行模拟。

🇺🇸English

flutter-automated-testing

Goal

Generates, configures, and debugs automated tests for Flutter applications, encompassing unit, widget, integration, and plugin testing. Analyzes architectural components (such as MVVM layers) to produce isolated, mock-driven tests and end-to-end device tests. Assumes a standard Flutter project structure, existing business logic, and familiarity with Dart testing paradigms.

Instructions

1. Determine Test Type (Decision Logic)

Evaluate the user's target code to determine the appropriate testing strategy using the following decision tree:

If verifying a single function, method, ViewModel, or Repository: Implement a Unit Test (Proceed to Step 2).
If verifying a single widget's UI, layout, or interaction: Implement a Widget Test (Proceed to Step 3).
If verifying complete app behavior, routing, or performance on a device: Implement an Integration Test (Proceed to Step 4).
If verifying platform-specific native code (MethodChannels): Implement a Plugin Test (Proceed to Step 5).

STOP AND ASK THE USER: "Which specific class, widget, or flow are we testing today? Please provide the relevant source code if you haven't already."

2. Implement Unit Tests (Logic & Architecture)

Unit tests verify logic without rendering UI. They must reside in the test/ directory and end with _test.dart.

For ViewModels (UI Layer Logic): Fake the repository dependencies. Do not rely on Flutter UI libraries.

import 'package:test/test.dart'; // Import your ViewModel and Fakes here

void main() { group('HomeViewModel tests', () { test('Load bookings successfully', () { final viewModel = HomeViewModel( bookingRepository: FakeBookingRepository()..createBooking(kBooking), userRepository: FakeUserRepository(), );
```
  expect(viewModel.bookings.isNotEmpty, true);
});
```
}); }
For Repositories (Data Layer Logic): Fake the API clients or local database services.

import 'package:test/test.dart'; // Import your Repository and Fakes here

void main() { group('BookingRepositoryRemote tests', () { late BookingRepository bookingRepository; late FakeApiClient fakeApiClient;
```
setUp(() {
  fakeApiClient = FakeApiClient();
  bookingRepository = BookingRepositoryRemote(apiClient: fakeApiClient);
});

test('should get booking', () async {
  final result = await bookingRepository.getBooking(0);
  final booking = result.asOk.value;
  expect(booking, kBooking);
});
```
}); }

3. Implement Widget Tests (UI Components)

Widget tests verify UI rendering and interaction. They must reside in the test/ directory and use the flutter_test package.

Use WidgetTester to build the widget.
Use Finder to locate elements (find.text(), find.byKey(), find.byWidget()).
Use Matcher to verify existence (findsOneWidget, findsNothing, findsNWidgets).

import 'package:flutter/material.dart'; import 'package:flutter_test/flutter_test.dart';

void main() { testWidgets('HomeScreen displays title and handles tap', (WidgetTester tester) async { // 1. Setup Fakes and ViewModel final bookingRepository = FakeBookingRepository()..createBooking(kBooking); final viewModel = HomeViewModel( bookingRepository: bookingRepository, userRepository: FakeUserRepository(), );

4. Implement Integration Tests (End-to-End)

Integration tests run on real devices or emulators. They must reside in the integration_test/ directory.

Ensure integration_test is in dev_dependencies in pubspec.yaml.
Initialize IntegrationTestWidgetsFlutterBinding.

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' as app;

void main() { IntegrationTestWidgetsFlutterBinding.ensureInitialized();

group('End-to-End App Test', () { testWidgets('Full flow: tap FAB and verify counter', (WidgetTester tester) async { // Load the full app app.main(); await tester.pumpAndSettle();
```
  // Verify initial state
  expect(find.text('0'), findsOneWidget);

  // Find and tap the FAB
  final fab = find.byKey(const ValueKey('increment'));
  await tester.tap(fab);
  
  // Trigger a frame
  await tester.pumpAndSettle();

  // Verify state change
  expect(find.text('1'), findsOneWidget);
});
```
}); }

5. Implement Plugin Tests (Native & Dart)

If testing a plugin, tests must cover both Dart and Native communication.

Dart Side: Mock the platform channel and call the plugin's public API.
Native Side: Instruct the user to write native tests in the respective directories:
- Android: android/src/test/ (JUnit)
- iOS/macOS: example/ios/RunnerTests/ (XCTest)
- Linux/Windows: linux/test/ (GoogleTest)

6. Validate and Fix (Feedback Loop)

Provide the user with the exact command to run the generated test:

Unit/Widget: flutter test test/your_test_file.dart
Integration: flutter test integration_test/your_test_file.dart

STOP AND ASK THE USER: "Please run the test using the command above and paste the output. If the test fails, provide the stack trace so I can analyze the failure and generate a fix."

Constraints

Single Source of Truth: Do not duplicate state in tests. Always use fakes or mocks for external dependencies (Repositories, Services) to isolate the unit under test.
No Logic in Widgets: When writing widget tests, assume the widget is "dumb". All business logic should be tested via the ViewModel/Controller unit tests.
File Naming: All test files MUST end with _test.dart.
Pump vs PumpAndSettle: Use tester.pump() for single frame advances. Use tester.pumpAndSettle() strictly when waiting for animations or asynchronous UI updates to complete.
Immutability: Treat test data models as immutable. Create new instances for state changes rather than mutating existing mock data.
Do not usedart:mirrors: Flutter does not support reflection. Rely on code generation (e.g., build_runner, mockito, mocktail) for mocking.

Weekly Installs

1.0K

Repository

flutter/skills

GitHub Stars

808

First Seen

Mar 4, 2026

Security Audits

Gen Agent Trust HubPass SocketPass SnykPass

Installed on

codex981

github-copilot977

opencode977

cursor977

gemini-cli976

kimi-cli975

React 组合模式指南：Vercel 组件架构最佳实践，提升代码可维护性

103,800 周安装

// 2. Build the Widget tree
await tester.pumpWidget(
  MaterialApp(
    home: HomeScreen(viewModel: viewModel),
  ),
);

// 3. Finders
final titleFinder = find.text('Home');
final buttonFinder = find.byKey(const Key('increment_button'));

// 4. Assertions
expect(titleFinder, findsOneWidget);

// 5. Interactions
await tester.tap(buttonFinder);
await tester.pumpAndSettle(); // Wait for animations/state updates to finish

expect(find.text('1'), findsOneWidget);

Flutter自动化测试指南：单元测试、部件测试、集成测试与插件测试全解析

🇨🇳中文介绍

flutter-automated-testing

目标

说明

1. 确定测试类型（决策逻辑）

2. 实现单元测试（逻辑与架构）

相关 Skills

3. 实现部件测试（UI 组件）

4. 实现集成测试（端到端）

5. 实现插件测试（原生与 Dart）

6. 验证与修复（反馈循环）

约束

🇺🇸English

flutter-automated-testing

Goal

Instructions

1. Determine Test Type (Decision Logic)

2. Implement Unit Tests (Logic & Architecture)

3. Implement Widget Tests (UI Components)

4. Implement Integration Tests (End-to-End)

5. Implement Plugin Tests (Native & Dart)

6. Validate and Fix (Feedback Loop)

Constraints

最新 Skills