[no-Jira] Include files with zero coverage in the coverage report #867
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I noticed that we have some components with zero test coverage. Because none of the lines are hit, jest isn't aware of them and doesn't include them in the coverage report. This PR adds the
collectCoverageFromconfig to explicitly include all TypeScript files in the coverage report so that our code coverage reports more accurately reflect reality.I moved a few files to make sure that we aren't including test utilities in code coverage or excluding files that should have code coverage.
This PR will inevitably reduce code coverage but only because our code coverage report was falsely inflated before.
Checklist: