We should up the Equivset test coverage to 100%
Description
Details
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
Increase Test Coverage to 100% | mediawiki/libs/Equivset | master | +600 -139 |
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | • TBolliger | T166816 Epic ⚡️ : Accuracy improvements to anti-spoof tools across multiple pertinent tools | |||
Resolved | dbarratt | T174195 More extensive unit testing for AntiSpoof | |||
Resolved | dbarratt | T178704 Enforce that Equivset Test Coverage Remains at 100% | |||
Resolved | dbarratt | T177667 Get Equivset Test Coverage to 100% | |||
Resolved | dbarratt | T174197 Split off AntiSpoof equivset generation and string normalization into its own library |
Event Timeline
Change 383498 had a related patch set uploaded (by Dbarratt; owner: Dbarratt):
[mediawiki/libs/Equivset@master] Increase Test Coverage to 100%
@Legoktm is there anyway to enforce (with Jenkins) that we maintain 100% code coverage?
Whatever we put into the "composer test" command gets run by jenkins. So if there's a way to make phpunit or something else complain when coverage isn't 100% that would be the recommended way.
@Legoktm uhh... we need Xdebug in Jenkins. :(
15:33:49 Warning: The Xdebug extension is not loaded
15:33:49 No code coverage will be generated.
Following up on the IRC ping.
xdebug is installed via Debian packages which should enable it by default an ini file. We have a task to stop loading xdebug since that slow down PHP T175028. To generate coverage we would thus invoke php with: php -d extension=xdebug.so.
AFAIK xdebug is still enabled. If it is not that is a bug I guess. Do you have a Gerrit change and job name that shows the issue?
Here's the patch: https://gerrit.wikimedia.org/r/#/c/383498/
and the failure: https://integration.wikimedia.org/ci/job/composer-package-php55-jessie/520/console
Change 383498 merged by jenkins-bot:
[mediawiki/libs/Equivset@master] Increase Test Coverage to 100%