Repository navigation
flutter test --coverage and flutter test --watch #4719
Description
-
flutter test --coverageshould write:- two identical files, a base file and a coverage file,
- plus a file that lists the last modification times of all the test files.
-
flutter test --watchshould watch the file system of the current package.- If a file under
lib/changes, it should rerun all the tests and create a new base file and timestamp file. - If a file under 'test/' changes, it should rerun all the tests with timestamps that indicate the file changed since the base file was written.
- after
flutter test --watchruns some tests, it should merge the new coverage with the base file and overwrite the coverage file.
- If a file under
- We should document the caveats here:
- Tests that have expectations or that depend on non-test files won't be run when those files change.
- Reducing coverage won't be noticed.
- Coverage is per-line and hitting any expression on the line counts as covering the line.
Activity
[fuchsia] Place Observatory in the runner's package instead of linkin…
Hixie commentedon Sep 12, 2018
cc @aam
16 remaining items
szotp commentedon Aug 22, 2020
It looks like it won't be implemented anytime soon so I'm considering a workaround - since flutter already supports hot reload, I could add my tests as a package directly to the app as dev dependency, and re run tests on each hot reload.
EDIT: This actually works pretty well, I've made a package for other people to try it: https://github.com/szotp/hottie/
HerrNiklasRaab commentedon Oct 28, 2020
Related: Dart-Code/Dart-Code#2878
danielgomezrico commentedon Dec 10, 2020
Is there any possibility that
flutter test --watchrun only the tests related to the file that changed?I loved the behavior of https://github.com/guard/guard-test.
YazeedAlKhalaf commentedon Jul 20, 2022
can we possible have something similar to how bazel does caching of tests.
if you're familiar with running a project that has bazel, you will notice that only tests of files changed are run after the first run which runs everything.
if we integrate this into the watch flag it would make development so much faster.
matanlurey commentedon Jun 27, 2025
This feature is not planned, of course it's great that the community is able to write custom packages.
github-actions commentedon Jul 11, 2025
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.