Brooks, I'm not sure as I'm unable to reproduce it. I just did the exact same thing and here are my results which include coverage data:
Here's the run configuration for that test run:
I did have to run "npm install" to ensure that the "Jest package" selected above is available, and of course I also ensured that the "@types/jest" and "@types/node" JavaScript libraries are enabled for the project:
See if you have yours configured in the same fashion. If not, does changing the config resolve the issue? If that doesn't do it, you might need to report it to JetBrains since the Jest test runner and code coverage stuff is part of their JavaScript plugin.
Regards,
Scott Wells