proposal: New File Coverage Threshold

As a user - it would be really great to be able to specify a coverage threshold for new files. That way if new files are added to the project we can assert that we’re adding tests in a meaningful way - while being able to manage our legacy code that may not be as tested alongside of it.

The diff for new file coverage is already being made - so in theory - it wouldn’t be difficult to take those numbers and fail the check if they fall under any given percentage.

[ArtiomTr]

I want to finish a big refactor before adding new features - it will be easier to review the code and predict possible drawbacks.

[ArtiomTr]

Hello @therynamo,

The v2 version uses slightly different approach - it uses threshold from the jest configuration file. Jest does not support threshold for the “new” files, so it’s hard to implement this feature.

The goal of this action is to work with as tiny configuration as possible. I could add a new option for the action, but this could potentially confuse users - all thresholds are passing on the local test run, but failing on the ci.

So if you have an idea how to implement this, without confusing users too much - I would love to hear it!