|Resolved||Legoktm||T146970 Create pretty landing page at https://doc.wikimedia.org/cover/|
- Mentioned Here
- T101544: Provide (pre-merge) code coverage reports on patchsets
T101545: Provide infrastructure to store files by project/branch post-merge to compare with pre-merge
T179054: Generate clover.xml for labs/tools/heritage
rGOJS3fb557533436: build: Use source maps in coverage report
rCICF62119a37df15: Publish clover.xml files for machine-readable coverage information
Also unicodejs and visualeditor put their coverage in a subdirectory called Chrome 57.0.2987 (Linux 0.0.0) (or whatever version of Chromium was used) - we need to figure out a way to disable that too.
Hmm. Why use this clover XML file rather than the existing machine-readable JSON coverage files? Is there a task explaining why?
clover is a standardized format that is common between jenkins, phpunit and istanbul (js). nosetests (python) supports a different standard xml format that we can probably convert into clover (see T179054). While istanbul's JSON format is documented, it's not standardized and would require having different code to parse the results - I'd rather just use clover everywhere.