(copied from bug 26908 comment 8)
Here's a few points (likely in this order, but some may be re-ordered, postponed or or skipped)
Init QUnit
Point 1a: Add QUnit as a module in core
Point 1b: Look over modules prepare where needed to be more easily
testable (ie. functions that should but don't have a return values. like mw.config.set which can fail or succeed, this is tested but nothing returned..)
Point 2: Create a basic (neutral) environment where QUnit will be running.
Point 3: Go through core modules created/maintained by Wikimedia developers (mediawiki.js, jquery.client.js, .. but not jquery.cookie). Review line by line, and make sure there's suffecient test suits for everything.
Extend / Integrate QUnit
Point 4: Create a nice way for extensions to state that a module should be
loaded on Unit-test page and register a js file with qunit tests which should
be executed.
Point 5: Figure out what needs to be done to make a QUnit test page into a
TestSwarm-able thing through SVN sending periodic tests to clients – without
requiring users to have a TestSwarm - a vanilla QUnit page should stay
available.
Distributed javascript testing / aka TestSwarm compatibility
Point 6: Set up a local TestSwarm
Point 7: Set up at Toolserver (if possible).
Wikimedia
- Install somewhere in WMF (probably a wmf-like wiki running trunk, perhaps
multiple wikis (one on trunk, one of wmfbranch) see [1])
Point 10: IRC Bot reporting breakages ?
Krinkle
[1] http://www.mediawiki.org/wiki/WMF_Projects/Virtualization_cluster
Version: unspecified
Severity: normal