full_coverage
1.0.0, released 4 years ago by flutterando.com.br
Generates a dummy test file importing all Dart files to ensure accurate code coverage reports.
What it does
It finds all Dart files in specified directories like lib and creates a dummy test file that imports them all. This ensures that coverage tools register all files, even those not explicitly imported by other tests.
AI-written summary of version 1.0.0, based on the package's README and metadata. Report an inaccuracy
Use it when
- You want accurate code coverage reports that include untested files.
- You use coverage tools that only track files triggered by actual test imports.
Skip it when
- You manually manage comprehensive test imports for coverage.
- You do not use code coverage tools in your project.
Strengths
- Automates the creation of a comprehensive coverage test file.
- Supports ignoring specific files using patterns.
Weaknesses
- Relies on shell execution and global activation.
- Not documented beyond basic script execution.
Setup
- Kind
- Pure Dart
- Effort
- Low
- Code generation
- No
- Direct dependencies
- 2
Activated globally via pub and run as a command-line script.
dart pub global run full_coverageAlternatives
Packages that do the same job and could replace full_coverage.
- patrol_cli
Command-line tool to run and debug Patrol UI tests on multiple platforms
89Compare - bdd_widget_test
Generate Flutter widget tests from Gherkin feature files
88Compare - coverde
A CLI tool for optimizing test execution and manipulating code coverage trace files.
71Compare - fluttersdk_dusk
Flutter E2E test driver for LLM agents and CLI via VM Service extensions without a test harness.
77Compare
Works with
Packages commonly used together with full_coverage: ones it builds on, ones built on it, and its own family.