Summary

For a large project which hasn't established or conformed to code coverage requirements yet, the code coverage results output can be significant. When trying to iterate on a particular test with heft test --watch for example, you have to constantly scroll up past what could be pages of output to see what made the test fail.

Code coverage probably also adds time to the test iteration cycle. (Of course one should assess coverage before finalizing the code, but it may be slowing down test iteration process.)

To work around this, one can add "coverageReporters": ["none"] to a jest.config.json. However, local code changes for this sort of thing are not great (e.g. risk to accidentally commit it, and extra time spent to avoid that). It would be great if we could accomplish the same thing temporarily with a command-line option like --skip-code-coverage.

Repro steps

• With a project that has unit tests and produces a lot of code coverage report output...
• Break a couple tests.
• heft test --watch
• Try to fix a test (make a code change and save it).
• Look at the --watch output change. Look for what failed your test(s)...

Expected result:
Easy to continue iterating on remaining broken tests.

Actual result:
Have to constantly scroll up past all the code coverage output to tackle the immediate task.