Glorious merge of code coverage and testem configuration

Gill, Avtar agill at
Wed Jan 17 15:59:44 UTC 2018

Awesome work, Tony and everyone else :)

> This will be invaluable to us in CI, and will shortly be a part of the automated builds run on each pull request. 

While the coverage info is being reported for pull requests and other branch activity it’s unsurprisingly buried among other output:

A couple quick searches for how to share coverage reports using the GitHub statuses API brought up two services:

Both have free plans for open source projects. At a glance it looks like Codecov has more polished documentation. I omitted Jenkins plugins since Fluid’s instance doesn’t run jobs for PR branches.

There most likely are alternatives out there. Is anyone aware of other options?


> On Jan 16, 2018, at 11:17 AM, Antranig Basman <Antranig.Basman at> wrote:
> I'm happy to report the merge of a major and significantly useful pull request from Tony Atkins which adds long-awaited and much needed code coverage and testem drivers to Infusion. As well as providing amalgamated coverage reports derived from both our browser and node-based tests, it provides an all-in-one testem driver that will execute all such tests in all available browsers and node.js.
> This will be invaluable to us in CI, and will shortly be a part of the automated builds run on each pull request. It will be important in future reviews to ensure that new work has good coverage, coverage of existing work does not degrade, and that we should work steadily to bring areas of old implementation up to reasonable standards of coverage (e.g. branch coverage of about 90% represents a reasonable baseline. For example we have interestingly poor coverage of jquery.keyboard-a11y.js via automated tests.
> The coverage reports are generated automatically by running "npm test" and can be accessed in the newly generated "reports" directory. Machine-readable summaries of the coverage are produced in "coverage".
> Let us all join in congratulating ADTKINS on almost a year of steering this pull request to a successful conclusion. Similar work is in progress for GPII projects but looks like it will be blocked by moving those projects over to a "monorepo" structure.
> Cheers,
> Antranig
> _______________________________________________________
> fluid-work mailing list - fluid-work at
> To unsubscribe, change settings or access archives,
> see

More information about the fluid-work mailing list