Page MenuHomePhabricator

Establish performance budgets for tests of each area of code, and report (later, auto-skip) suites that take too long
Open, NormalPublic0 Story Points


Initial finger-in-the-air proposal:

AreaLimit per-testLimit per-repoLimit overall
PHP unit tests5 ms1 s30 s
PHP integration tests50 ms5 s60 s
JS unit tests1 ms1 s10 s
JS integration tests500 ms5 s60 s
System (browser) tests2 s10 s60 s

Relevant tasks:

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJun 17 2019, 9:17 PM

For the reporting, as well as in-line with test results to be effective there should probably be some form of regular update on how well we are collectively doing, and what areas of the code have particularly heavy tests.

greg triaged this task as Normal priority.Jul 23 2019, 8:50 PM
Krinkle moved this task from Inbox to Checkers on the MediaWiki-Core-Testing board.Sep 4 2019, 5:48 PM