|mediawiki/extensions/GettingStarted : master||Delete Ruby Selenium tests|
|integration/config : master||Do not run Ruby and/or Selenium jobs for GettingStarted|
|mediawiki/extensions/GettingStarted : master||WIP The first sample Selenium test in Node.js|
|Open||None||T139740 Port Selenium tests from Ruby to Node.js|
|Open||None||T174594 Global Collaboration: Migrate browser tests from Ruby to node.js|
|Resolved||zeljkofilipin||T180224 Port GettingStarted Selenium tests from Ruby to Node.js|
- Mentioned In
- T214382: Gem::InstallError: watir requires Ruby version >= 2.3.0.
T92156: Cucumber tests for GettingStarted
T198409: Set up CI for running Node.js+Selenium tests for repositories that have Ruby+Selenium tests
T183162: Patches in Gerrit deleting Selenium+Ruby tests for repositories that still have them
T183160: Sample code in Node.js for repositories that still have Selenium+Ruby tests
T139740: Port Selenium tests from Ruby to Node.js
@Etonkovidova @SBisson @Mooeypoo @Catrope I would like to make an exception and migrate this one, since it is actively monitored by @phuedx and I, and the test has caught a serious outage in the account creation workflow (though the response to that should have been better).
There is only one test, though it has some unusual behavior (to bypass the CAPTCHA).
@JTannerWMF "working" on it by deleting Ruby Selenium tests and Jenkins jobs that run them. :)
I'm acutally done with that, but I'm hesitant to delete jobs and tests from the GettingStarted repository until somebody from the Growth team at least gives a +1 to the related commits: