-
Notifications
You must be signed in to change notification settings - Fork 344
Closed
Labels
in coverageRelates to collecting code coverage when running Dart/Flutter testsRelates to collecting code coverage when running Dart/Flutter testsin testingRelates to test execution of Dart/Flutter tests for end usersRelates to test execution of Dart/Flutter tests for end usersis enhancementAn enhancement or improvement that should be listed in release notes but is not a bug fix.An enhancement or improvement that should be listed in release notes but is not a bug fix.
Milestone
Description
This was requested on Discord by @RedPhœnix:
I’d like to exclude certain folders from the coverage results (for example, my
lib/l10n/generatedfolder), but I haven’t found a way to do that yet. Is this currently possible, or is there a workaround someone could recommend?
I think there are a few ways this could be supported:
- Natively by VS Code, which just drops the coverage and computes totals excluding it
- By Dart-Code, which also just drops the coverage before reporting to VS Code
- By
dart test/flutter testwhere it doesn't collect the coverage in the first place
@liamappelbe what are your thoughts on (3)? It would be nicer (and perhaps faster) if we this coverage wasn't collected for these files in the first place, but it might be that the difference is negligible and we should just drop it in Dart-Code.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
in coverageRelates to collecting code coverage when running Dart/Flutter testsRelates to collecting code coverage when running Dart/Flutter testsin testingRelates to test execution of Dart/Flutter tests for end usersRelates to test execution of Dart/Flutter tests for end usersis enhancementAn enhancement or improvement that should be listed in release notes but is not a bug fix.An enhancement or improvement that should be listed in release notes but is not a bug fix.