Drive towards full coverage

[mhdawson]

Next steps
1- Blog post to point to the issues we have open to encourage external help.

[mhdawson]

@JckXia has a draft for the blog post, will send to rest of team members through email to discussion/review.

[mhdawson]

Link with blog post for commenting/editing https://docs.google.com/document/d/1uqy-DGRks6RMO3xPVx1Iyywk7h6rSdGg/edit

[KevinEady]

@KevinEady to investigate adding a coverage badge to the root README.md.

[mhdawson]

Badge is now on README.md

[KevinEady]

Next step: Create a "condensed report" which analyzes why some coverage paths are not taken and present this to team for triage.

[KevinEady]

• Investigate why coverages is lower than expected: is it possible that coverages are being overwritten? Coverages are stored on the filesystem when the process runs (ends?). Could it be the case that since we use subprocesses, a subprocess' test results get overridden when the parent process' finishes?
• Improve coverage report with experimental runs node-addon-api#1525