Page MenuHomePhabricator

Try to hook up xenon logs to coverage reports to get a list of most executed non-covered code
Closed, ResolvedPublic


To help prioritizing writing tests, we could try hooking up the xenon logs used to generate flamegraphs (, build a list of most called functions, and then figure out which of those are not covered.

Event Timeline


I think this is actually going to be pretty useful, e.g. shows pretty obvious suggestions for improvement across ResourceLoader related code.

Because of the way the xenon logs work, it has a heavier bias towards entrypoint functions (e.g. MediaWiki::run()), but once those are covered they won't get in the way :)