Just released an npm package!

I’ve just released an npm package. There was something that always bothered me at work when the team pushed changes to an official brand of our repos. The thing is that the tool we use for CI has a coverage threshold of 80%. However, it was difficult for the team to know how much we had. We have two types of CI jobs at work:

1. For pull requests.
2. For integration with a develop/master branch.

As mentioned, there is this rule of over 80% but the thing is, it only ran for the 2nd scenario. There was no way the devs would know that the build would fail in the PR phase because this check was not performed. (Unfortunately the team was not allowed to make changes to those integration jobs.)

Well, this is over now. I came to think that this did not make much sense at all so I created this npm package which I called testaged-coverage. I sounds funny but catchy at the same time. Enjoy it.

If you want to know more about it, you can check it out here https://www.npmjs.com/package/testaged-coverage.