jest: Jest is "stuck" on only generating coverage for tested files, instead of all files

🐛 Bug Report

I recently setup codecov, and then setup jest to generate coverage reports for it.

Initially, it was setup to collect coverage from all files via the jest config (see below).

Later, I wanted to have a separate jest command minus the coverage report, so I moved the collect coverage command from the jest options to the cli (see below).

After doing this, jest no longer gives coverage for the entire src folder, but only for the files tested. Okay, no problem, I’ll just undo this change.

Here’s where I am getting frustrated - no attempts to revert this seem to work. I can revert to the previous config, and it no longer works for all files, only the ones being tested. Same config, different results. I’ve tried running it with --clearCache or --no-cache and neither work. I’ve tried creating a whole new config, one with coverage and one without, and then just running the base command, and that doesn’t work either.

When running, it takes much longer than it used, displays the ‘generating coverage for untested files’ message, and then still only returns the coverage for tested files only.

To Reproduce

I had a config with the following (this worked fine):

with a command that looked like this:

I removed the collectCoverage and collectCoverageFrom options from the jest config, and created a separate command that looked like this:

I realize now that the above command never worked for all files. Regardless, after reverting to the original setup, jest no longer works the way it used to, and is instead “stuck” on just reporting coverage for the tested files only. Even though it displays the “generating coverage for untested files” message.

Expected behavior

I would expect that when coverage is set to true, and collectCoverage is passed a glob for all files in the repo, that the generated coverage report would be for all files. I would expect this behavior to be consistent.

Run npx envinfo --preset jest

Paste the results here:

System:
    OS: macOS 10.14.4
    CPU: (4) x64 Intel(R) Core(TM) i5-6267U CPU @ 2.90GHz
  Binaries:
    Node: 8.12.0 - ~/.nvm/versions/node/v8.12.0/bin/node
    Yarn: 1.7.0 - /usr/local/bin/yarn
    npm: 6.4.1 - ~/.nvm/versions/node/v8.12.0/bin/npm
  npmPackages:
    jest: ~24.1.0 => 24.7.1