
Dart Test Fundamentals
- 399 installs
- 139 repo stars
- Updated July 11, 2026
- kevmoo/dash_skills
dart-test-fundamentals is a Claude agent skill that teaches package:test structure, lifecycle setup, and dart_test.yaml configuration for developers shipping tested Dart and Flutter applications.
About
dart-test-fundamentals is an Apache-2.0 skill from kevmoo/dash_skills covering core package:test concepts for Dart and Flutter projects. It explains test and group structure, setUp and tearDown lifecycle methods, and dart_test.yaml execution settings so suites stay CI-friendly. Developers reach for dart-test-fundamentals when authoring new test files, reorganizing groups, fixing try-finally cleanup patterns, or aligning Flutter widget and integration tests with Dart testing conventions. The skill maps discovery patterns for brittle tests and documents configuration hooks teams need before merging mobile releases.
- Unit and widget test setup
- Matchers and expectations
- test package conventions
- Flutter test bootstrapping
- CI-ready test layout
Dart Test Fundamentals by the numbers
- 399 all-time installs (skills.sh)
- +10 installs in the week ending Aug 2, 2026 (Skillselion tracking)
- Ranked #653 of 2,153 Testing & QA skills by installs in the Skillselion catalog
- Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/kevmoo/dash_skills --skill dart-test-fundamentalsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 399 |
|---|---|
| repo stars | ★ 139 |
| Last updated | July 11, 2026 |
| Repository | kevmoo/dash_skills ↗ |
How do you structure Dart tests with package:test?
Write and run Dart unit, widget, and integration tests with correct matchers, setup, and CI-friendly patterns before shipping Flutter apps.
Who is it for?
Dart and Flutter developers writing or refactoring unit, widget, or integration tests who need package:test conventions and CI-ready configuration.
Skip if: Teams seeking golden-file UI snapshots, performance benchmarking, or language-agnostic testing theory without Dart specifics.
When should I use this skill?
A user writes new Dart test files, configures dart_test.yaml, or asks about test, group, setUp, or tearDown in a Flutter project.
What you get
Organized test suites, dart_test.yaml configuration, and lifecycle-safe setUp and tearDown patterns ready for CI.
- structured test files
- dart_test.yaml config
- lifecycle-safe test suites
By the numbers
- Documents 3 core areas: package:test concepts, lifecycle methods, and dart_test.yaml configuration
- Licensed Apache-2.0 in the kevmoo/dash_skills repository
Files
Dart Test Fundamentals
When to use this skill
Use this skill when:
- Writing new test files.
- Structuring test suites with
group. - Configuring test execution via
dart_test.yaml. - Understanding test lifecycle methods.
Discovery
To find candidates for improving test structure:
try-finally Cleanup
Search for tests that use try-finally for cleanup instead of addTearDown:
- Regex:
\bfinally\s*\{(Check if this is used for resource cleanup
inside a test).
Core Concepts
1. Test Structure (test and group)
- `test`: The fundamental unit of testing.
test('description', () {
// assertions
});- `group`: Used to organize tests into logical blocks.
- Groups can be nested.
- Descriptions are concatenated (e.g., "Group Description Test Description").
- Helps scope
setUpandtearDowncalls. - Naming: Use
PascalCasefor groups that correspond to a class name
(e.g., group('MyClient', ...)).
- Avoid Single Groups: Do not wrap all tests in a file with a single
group call if it's the only one.
- NOTE: DO NOT remove groups when doing a cleanup on existing code you
didn't create unless explicitly asked to. This can cause a LOT of churn in the DIFF that most engineers won't want!
- Naming Tests
test('test name here',: - Avoid redundant "test" prefixes. Use
groupinstead. - Include the expected behavior or outcome in the description (e.g.,
'throws StateError' or 'adds API key to URL').
- Descriptions should read well when concatenated with their group name.
- Named Parameters Placement:
- For
testandgroupcalls, place named parameters (e.g.,testOn,
timeout, skip) immediately after the description string, before the callback closure. This improves readability by keeping the test logic last.
test('description', testOn: 'vm', () {
// assertions
});2. Lifecycle Methods (setUp, tearDown)
- `setUp`: Runs before every
testin the currentgroup(and nested
groups).
- `tearDown`: Runs after every
testin the currentgroup. - `setUpAll`: Runs once before any test in the group.
- `tearDownAll`: Runs once after all tests in the group.
Best Practice:
- Use
setUpfor resetting state to ensure test isolation. - Avoid sharing mutable state between tests without resetting it.
3. Cleaning Up Resources
- To clean up resources created WITHIN the
testbody, consider using
addTearDown instead of a try-finally block.
Avoid:
test('can create and delete a file', () {
final file = File('temp.txt');
try {
file.writeAsStringSync('hello');
expect(file.readAsStringSync(), 'hello');
} finally {
if (file.existsSync()) file.deleteSync();
}
});Prefer:
test('can create and delete a file', () {
final file = File('temp.txt');
// Register teardown immediately after resource creation intent
addTearDown(() {
if (file.existsSync()) file.deleteSync();
});
file.writeAsStringSync('hello');
expect(file.readAsStringSync(), 'hello');
});4. Configuration (dart_test.yaml)
The dart_test.yaml file configures the test runner. Common configurations include:
Platforms
Define where tests run (vm, chrome, node).
platforms:
- vm
- chromeTags
Categorize tests to run specific subsets.
tags:
integration:
timeout: 2xUsage in code:
@Tags(['integration'])
import 'package:test/test.dart';Running tags: dart test --tags integration
Timeouts
Set default timeouts for tests.
timeouts:
2x # Double the default timeout5. File Naming
- Test files must end in
_test.dartto be picked up by the test runner. - Place tests in the
test/directory.
Common commands
dart test: Run all tests.dart test test/path/to/file_test.dart: Run a specific file.dart test --name "substring": Run tests matching a description.
Related Skills
dart-test-fundamentals is the core skill for structuring and configuring tests. For writing assertions within those tests, refer to:
- [dart-matcher-best-practices]:
Use this if the project sticks with the traditional package:matcher (expect calls).
[dart-matcher-best-practices]: https://github.com/kevmoo/dash_skills/blob/main/skills/dart-matcher-best-practices/SKILL.md
Related skills
How it compares
Use dart-test-fundamentals for package:test basics; reach for integration-test or golden-file skills when end-to-end device flows dominate.
FAQ
What does dart-test-fundamentals cover?
dart-test-fundamentals covers package:test core concepts including test and group structure, setUp and tearDown lifecycle methods, and dart_test.yaml configuration for reliable Dart and Flutter test execution in local and CI environments.
When should I use dart-test-fundamentals?
Use dart-test-fundamentals when writing new Dart test files, restructuring suites with group, configuring dart_test.yaml, or understanding lifecycle methods before shipping Flutter app changes.