Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

No coverage when running in watch mode

See original GitHub issue

🐛 Bug Report

when I run jest --watch, I see unknown coverage.

To Reproduce

see Link repo.

Expected behavior

show correct coverage.

Link to repl or repo (highly encouraged)

jest-watch-coverage-bug

Run `npx envinfo --preset jest`

Paste the results here:

System:
    OS: macOS 10.14
    CPU: x64 Intel(R) Core(TM) m3-6Y30 CPU @ 0.90GHz
  Binaries:
    Node: 9.10.1 - /usr/local/bin/node
    npm: 6.4.1 - /usr/local/bin/npm
  npmPackages:
    jest: ^23.6.0 => 23.6.0

Issue Analytics

State:
Created 5 years ago
Reactions:65
Comments:39 (2 by maintainers)

Top GitHub Comments

28reactions

abierbaumcommented, Jul 13, 2019

I was able to get everything working fine by simply starting jest with watchAll. Then if I want to see the coverage for a single test I just use ‘p’ to match the pattern of the file name. Works great. Just confusing to know to use watchAll.

22reactions

EmilyRosinacommented, Nov 15, 2019

Seems like it’s back to not working for me, unsure if a release broke it or something, no idea 🤷‍♀️.

I can confirm what others say though --watch doesn’t work, --watchAll does. It’s a pita, but at least it works.