Currently only files loaded at runtime are reported in the lcov reports. This means if a file is not loaded at all, it may be excluded from coverage data in IDEs/reporting tools (instead of being treated as 0% coverage). This makes it harder to notice uncovered code if the entire file is uncovered.
Some other tools have flags to allow collecting coverage of all files so that the lcov file is complete:
It would be nice to have something similar for Dart. While we could just report 0s for all files, having the same behaviour across all tools would mean duplicating that, whereas handling it in pkg:coverage would only require they pass a flag.
Currently only files loaded at runtime are reported in the lcov reports. This means if a file is not loaded at all, it may be excluded from coverage data in IDEs/reporting tools (instead of being treated as 0% coverage). This makes it harder to notice uncovered code if the entire file is uncovered.
Some other tools have flags to allow collecting coverage of all files so that the lcov file is complete:
It would be nice to have something similar for Dart. While we could just report 0s for all files, having the same behaviour across all tools would mean duplicating that, whereas handling it in
pkg:coveragewould only require they pass a flag.