As a wikibase developer I want to use the nodejs test framework so that I only have 1 selenium test framework to think about.
As the WMF I want to use the nodejs test framework in wikibaselexeme so that all wmf deployed extensions are consistent.
As release engineering I want to remove all ruby selenium jobs so that more CI time is available for other jobs.
# Jenkins jobs to setup
[x] mediawiki/core: master: Selenium: run Wikibase repo tests [[ https://gerrit.wikimedia.org/r/c/mediawiki/core/+/441051 | 441051 ]]
[x] integration/config: master: Run qunit-selenium Jenkins job for Wikibase [[ https://gerrit.wikimedia.org/r/c/integration/config/+/441195 | 441195 ]]
[x] mediawiki/extensions/Wikibase: master: Start a very basic nodejs browser test [[ https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Wikibase/+/438000 | 438000 ]]
# Features to migrate
**Impact & Priority**
There is no specific point in time when the migration should happen (i.e. does not have happen immediately).
The WMDE is no longer supporting the ruby framework so if it does break we will be on our own and then forced to make fixes / migrate before Wikibase development can continue.
The ruby tests do not run as part of the mediawiki core gate-submit jobs, although the node ones will. Having our tests run with the core gets submit tests will eliminate breakages caused by core changes.
Convert all ruby features to be run as part of the node JS selenium tests.
A test framework example can probably be taken from WikibaseLexeme which already includes node browser tests.
- No ruby test features exist in the Wikibase git repo code base
- All features that did exist have been converted to the node js system
- The "mwext-mw-selenium-composer-jessie" jenkins job that runs on Wikibase git code changes in gate-submit no longer runs on them
- All other files & docs relating to the ruby tests have been removed from the Wikibase git repo