Bonus points if it has a cute name.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | zeljkofilipin | T91669 Make browser tests voting for all repos of WMF deployed code | |||
| Resolved | zeljkofilipin | T55697 [EPIC] trigger browser tests from Gerrit (tracking) | |||
| Resolved | • Jhernandez | T104315 [GOAL]: Set up testing environments that run browser tests on all patches. | |||
| Resolved | Jdlrobson | T100293 [EPIC] Run browser tests against every MobileFrontend/Gather patch | |||
| Resolved | Jdlrobson | T101334 Setup Gerrit account and labs instance for a bot for mobile |
Event Timeline
Comment Actions
I'm setting up gather-browser-tests.eqiad.wmflabs (http://gather-browser-tests.wmflabs.org/) as we speak
Todo:
- install public key on instance
- install git review
- install GerritCommandLine
- Get browser tests up and running
Comment Actions
Ok MediaWiki is setup in /srv/mediawiki/
Gather and MobileFrontend installed
Vector skin setup.
GerritCommandLine installed to /srv/mediawiki/GerritCommandLine
Added it to bin so you can run gerrit.py from anywhere.
barrybrowsertestbot is setup and from gather-browser-tests.eqiad.wmflabs can communicate with Gerrit.
TODO:
Setup an account for browser tests
Setup phantomjs driver
Gets tests running and passing green.
Comment Actions
Okay "User:Mr Selenium" is now live on http://gather-browser-tests.wmflabs.org/
Phantomjs is installed (took forever fyi)
gem installed bundles in both MobileFrontend and Gather directory
ran bundle install from tests/browser directory in Gather and MobileFrontend tests directory
(had to install apt-get install ruby-dev)
Am running a browser test build as we speak on Gather. I think we can call this done.
Note: I suspect the settings for the browser tests (public/private key etc) are all tied to my account. We can either switch these to sudo user or create a user specific for this.
Comment Actions
@Jdlrobson: Can we create a new user? User accounts are cheap and, I find, useful for limiting scope of development tasks.
Comment Actions
What do you mean by new user?
There are two users here - one the mediawiki user for browser tests and two the user for the bot that can review.
Alas the latter is not so cheap.
I envision one box per browser test build which means the user problem goes away (this makes life easier for managing dependencies).
Comment Actions
What do you mean by new user?
We can either switch these to sudo user or create a user specific for this.
I was saying "the latter".