Numerous extensions don't appear on https://doc.wikimedia.org/cover-extensions/ because they don't have any PHPUnit tests, but they do have parser tests... Which exercise PHP code in the extensions.
Is there any way we can use these to trigger creation of PHPUnit code coverage? wrt T186850: Wikimedia-deployed extensions/skins with no PHPUnit coverage
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | cscott | T358955 Interesting code coverage in composer-coverage-patch-docker | |||
| Open | None | T315768 Can we make parser tests show as PHP test coverage? | |||
| Open | None | T345481 Migrate Parser and extension tests away from deprecated PHPUnit TestSuite subclassing |
Dupe of T184216: Figure out how to implement dynamic @covers tags? Or maybe that's a subtask of this.
As part of the test parallelization / PHPUnit 10 (?) work, I think someone was working on generating a static test harness from the parser test file, which would then make the @covers nondynamic, I think:
T345481: Migrate Parser and extension tests away from deprecated PHPUnit TestSuite subclassing