Hi, All:

As many of you know, I am a strong believer in using tests to improve the
quality of our work and to improve the speed at which we can safely make
changes.  A key part of this is code coverage reports, which show us what
is tested and what isn't every time we (or the CI builds) run the tests.

In the interest of making it easier to make all of this a part of our daily
practice, I have been preparing pull requests against our core repositories
that add code coverage reporting.  We now have a complete set at least of
those I planned to do myself:

   - The initial universal PR <https://github.com/GPII/universal/pull/508>
   has been merged.
   - The Infusion PR <https://github.com/fluid-project/infusion/pull/822>is
   under review.
   - The windows PR <https://github.com/GPII/windows/pull/131> still needs
   to be picked up.
   - I have just created a PR for the linux repo
   <https://github.com/GPII/linux/pull/94>, which needs to be picked up.
   - A follow-up universal PR to address various "anomalies" in the code
   coverage reports <http://issues.gpii.net/browse/GPII-2486> will be
   created shortly.

I will be out of the office for three weeks starting on Saturday, but would
love to get these merged in early September.  As with the previous
universal PR, CI tests will not pass for the linux PR until the job
definition is updated.  Once the CI job is updated, the smaller number of
windows pulls in flight will appear to have failing jobs until they can
merge in the changes from this pull.  We should discuss the timing of the
CI config update when I return.

In the mean time, I need your help to confirm that the reports are
consistent, accurate, and complete.   If you work on one of the above
frequently, please do check the PRs for sample code coverage reports, and
comment on the PRs if you notice anything that needs review.  You're also
of course welcome to try checking out the branches and running the tests
yourselves.

Thanks,


Tony
_______________________________________________
Architecture mailing list
[email protected]
http://lists.gpii.net/mailman/listinfo/architecture

Reply via email to