agentleFS
hjdspacehjdspace/SpaceCode/.agents/skills/dart-collect-coverage/SKILL.md

dart-collect-coverage

Skill4 starsChanged 4 months agoMITView on GitHub

Collect coverage using the coverage packge and create an LCOV report

  • Reads credentials

5 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use dart-use-doc-examples and dart-write-documentation.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • flutterSkill

    dart-use-doc-examples

    How to inject external code examples into Dartdoc using the {@example} directive, and how to filter those files using #hide, #region, and #endregion tags.

    Also in 3 projects that use this

  • flutterSkill

    dart-write-documentation

    Rules and formatting guidelines for writing Dart /// API documentation and doc comments. Use when documenting Dart code, writing doc comments for any Dart declaration (libraries, classes, methods, variables, etc.), or when instructed to follow the Effective Dart documentation guidelines.

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. About 0 are common, 7 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Unit Tests: Verify individual functions, methods, or classes.

    line 21
  2. Very specific:

    Component/Widget Tests: Verify component behavior, layout, and interaction using mock objects (package:mockito).

    line 22
  3. Distinctive:

    Integration Tests: Verify entire app flows on simulated or real devices.

    line 23
  4. Distinctive:

    Follow this sequential workflow to add the coverage package, execute tests, and generate an LCOV report.

    line 35
  5. Very specific:

    Add the coverage package as a dev_dependency to your project.

    line 43
  6. Distinctive:

    If working in a standard Dart project:

    line 45
  7. Distinctive:

    If working in a Flutter project:

    line 50
  8. Very specific:

    Use the bundled test_with_coverage script.

    line 56
  9. Very specific:

    Verify that the coverage/ directory was created in the project root.

    line 65
  10. Very specific:

    Ensure coverage/coverage.json (raw data) and coverage/lcov.info (formatted report) exist.

    line 66
  11. Very specific:

    If coverage is missing for specific files, ensure they are imported and executed by your test files, or add // coverage:ignore-file if they …

    line 67
  12. Distinctive:

    If you require granular control over the VM service, isolate pausing, or need branch/function-level coverage, use the manual collection …

    line 71
  13. Very specific:

    Ensure your pubspec.yaml reflects the coverage package strictly under dev_dependencies.

    line 103
  14. Distinctive:

    Use ignore directives to prevent generated code or untestable edge cases from lowering coverage scores.

    line 119

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Implementing Dart and Flutter Test Coverage

Contents

  • Testing Fundamentals
  • Coverage Directives
  • Workflow: Configuring and Generating Coverage Reports
  • Workflow: Advanced Manual Coverage Collection
  • Examples

Testing Fundamentals

Structure your test suites using the standard Dart testing paradigms. Use package:test for Dart projects and flutter_test for Flutter projects.

  • Unit Tests: Verify individual functions, methods, or classes.
  • Component/Widget Tests: Verify component behavior, layout, and interaction using mock objects (package:mockito).
  • Integration Tests: Verify entire app flows on simulated or real devices.

Coverage Directives

Exclude specific lines, blocks, or entire files from coverage metrics using inline comments. Pass the --check-ignore flag during formatting to enforce these directives.

  • Ignore a single line: // coverage:ignore-line
  • Ignore a block of code: // coverage:ignore-start and // coverage:ignore-end
  • Ignore an entire file: // coverage:ignore-file

Workflow: Configuring and Generating Coverage Reports

Follow this sequential workflow to add the coverage package, execute tests, and generate an LCOV report.

Task Progress Checklist:

  • 1. Add coverage as a dev_dependency.
  • 2. Execute the automated coverage script.
  • 3. Validate the LCOV output.

1. Add Dependencies

Add the coverage package as a dev_dependency to your project. Do not add it to standard dependencies.

If working in a standard Dart project:

dart pub add dev:coverage

If working in a Flutter project:

flutter pub add dev:coverage

2. Collect Coverage and Generate LCOV

Use the bundled test_with_coverage script. This script automatically runs all tests, collects the JSON coverage data from the Dart VM, and formats it into an LCOV report.

dart run coverage:test_with_coverage

Note: If working within a Dart workspace (monorepo), specify the test directories explicitly (e.g., dart run coverage:test_with_coverage -- pkgs/foo/test pkgs/bar/test).

3. Feedback Loop: Validate Output

Run validator -> review errors -> fix:

  1. Verify that the coverage/ directory was created in the project root.
  2. Ensure coverage/coverage.json (raw data) and coverage/lcov.info (formatted report) exist.
  3. If coverage is missing for specific files, ensure they are imported and executed by your test files, or add // coverage:ignore-file if they are intentionally excluded.

Workflow: Advanced Manual Coverage Collection

If you require granular control over the VM service, isolate pausing, or need branch/function-level coverage, use the manual collection workflow.

Task Progress Checklist:

  • 1. Run tests with VM service enabled.
  • 2. Collect raw JSON coverage.
  • 3. Format JSON to LCOV.

1. Run Tests with VM Service

Execute tests while pausing isolates on exit and exposing the VM service on a specific port (e.g., 8181).

dart run --pause-isolates-on-exit --disable-service-auth-codes --enable-vm-service=8181 test &

2. Collect Raw Coverage

Extract the coverage data from the running VM service and output it to a JSON file.

dart run coverage:collect_coverage --wait-paused --uri=http://127.0.0.1:8181/ -o coverage/coverage.json --resume-isolates

Optional: Append --function-coverage and --branch-coverage to gather deeper metrics (requires Dart VM 2.17.0+).

3. Format to LCOV

Convert the raw JSON data into the standard LCOV format.

dart run coverage:format_coverage --packages=.dart_tool/package_config.json --lcov -i coverage/coverage.json -o coverage/lcov.info --check-ignore

Examples

Example: pubspec.yaml Configuration

Ensure your pubspec.yaml reflects the coverage package strictly under dev_dependencies.

name: my_dart_app
environment:
  sdk: ^3.0.0

dependencies:
  path: ^1.8.0

dev_dependencies:
  test: ^1.24.0
  coverage: ^1.15.0

Example: Applying Ignore Directives

Use ignore directives to prevent generated code or untestable edge cases from lowering coverage scores.

// coverage:ignore-file
import 'package:meta/meta.dart';

class SystemConfig {
  final String env;

  SystemConfig(this.env);

  // coverage:ignore-start
  void legacyInit() {
    print('Deprecated initialization');
  }
  // coverage:ignore-end

  bool isProduction() {
    if (env == 'prod') return true;
    return false; // coverage:ignore-line
  }
}

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.