Page MenuHomePhabricator

Provide (pre-merge) code coverage reports on patchsets
Closed, ResolvedPublic


I'd really love part of the CI pipeline to say

"With this patch, VisualEditor coverage is 64.3% (up 0.1%)."

Maybe with a link to a the full coverage report for that patchset on that master.

Event Timeline

hashar triaged this task as Low priority.Jun 5 2015, 9:58 PM
hashar set Security to None.

Change 237234 had a related patch set uploaded (by Krinkle):
build: Enable json format in karma-coverage

Change 237234 merged by jenkins-bot:
build: Enable json-summary format in karma-coverage

hashar changed the task status from Open to Stalled.Oct 6 2015, 12:34 PM
hashar added a subscriber: hashar.

Until we have a data store to expose the generated files ( T101545: Provide infrastructure to store files by project/branch post-merge to compare with pre-merge ). There is not much we can do on this task.

I wrote to be able to do per-patch coverage reports without any complex storage things (which I initially tried and got very lost in).

Here it is hooked up to jenkins:

I'm not really sure how to get jenkins-bot on Gerrit to say custom text from the job result.

Change 407588 had a related patch set uploaded (by Legoktm; owner: Legoktm):
[integration/config@master] Run phpunit patch coverage for MediaWiki in "coverage" pipeline

Change 407588 merged by jenkins-bot:
[integration/config@master] Run phpunit patch coverage for MediaWiki in "coverage" pipeline

Legoktm changed the task status from Stalled to Open.Feb 2 2018, 8:43 AM
Legoktm claimed this task.
This comment was removed by Krinkle.

For the most part this is done for PHP. Follow-up tweaks/improvement are tracked in individual tasks in phpunit-patch-coverage and Continuous-Integration-Infrastructure.