Wikimedia Release Engineering Team

This is the team responsible for Release Engineering/Management and QA at the Wikimedia Foundation. We predominately use the QA mailing list along with conversations on the appropriate IRC channels (especially, , , and ).

= Status =

= Quarterly Reviews =
 * February 2014
 * November 2013
 * August 2013

= Backlog/Wishlist =

We maintain a list of projects that would be great to have done, but are not on our roadmap in in the near term. See the wishlist here.

= Meetings =

See /Meetings for notes from the Showcase meetings of the Release and QA Team.

= Quarterly Progress =

Feb - Apr '14 Goal Progress
See the WMF Engineering 13-14 goals page for the yearly view.


 * Process through all (useful) pain points from the Dev/Deploy review session (Greg)
 * Scap incremental improvements
 * 1) Refactor existing scap scripts to enhance maintainability and reveal hidden complexity of current solution (Bryan)
 * 2) create matrix of tool requirements per software stack (MW, Parsoid, ElasticSearch) (Greg)
 * 3) Use above matrix to add/fix functionality in scap (or related) tooling for ONE software stack, prioritized by cross stack use (Bryan)
 * Use the API to create test data for given tests at run time. (Jeff, Chris, Željko)
 * Create the ability to test headless (Željko, Jeff, Chris)
 * Run versions of tests compatible with target test environments (Chris, all)
 * Make database(s) in Beta Cluster emulate production (set up db slaves) (Antoine)

Antoine

 * Complete integration of browsertests for VisualEditor
 * One build worked and triggered two successful scenario!!
 * Train Zeljkof on Jenkins Job Builder script
 * Zeljkof started on it. Will pair with him to finish up.
 * Help migrating Cloudbees Jenkins template to JJB YAML templates
 * Zeljkof started on it. Will pair with him to finish up.

Dec-Feb Goal Progress
See the WMF Engineering 13-14 goals page for the yearly view.


 * - Browser tests managed in feature repos with feature teams (Chris, Zeljko, Jeff, Rummana)
 * - Successfully managed the first release of MediaWiki in conjunction with our outside contractor (Greg, Antoine)
 * - More comprehensive quarter assessments of postmortems (Greg)
 * - Create process documentation for ideal test/deployment steps (Greg, Reedy, Chris, and others)
 * Automated API integration tests in important areas (Chris, Zeljko, Jeff, Rummana, Antoine, also with Mark Holmquist)
 * - UploadWizard
 * - Parsoid / VisualEditor
 * - ResourceLoader

Greg

 * do post Dev and Deploy process review follow up
 * post images to Commons - - included in commons:Category:Wikimedia_Foundation_software_development
 * send one email with list of grouped red-cards
 * send off first email on first topic (make it a good one)
 * Create plan to evaluate progress on postmortem/retrospective actions
 * archive/put on wikitech missing post-mortems -
 * https://wikitech.wikimedia.org/wiki/Incident_documentation/20140203-LVS
 * create BZ whiteboard entry to track retrospective bugs -
 * RT something or other?

Antoine

 * Complete integration of browsertests for VisualEditor
 * Train Zeljkof on Jenkins Job Builder script
 * Help migrating Cloudbees Jenkins template to JJB YAML templates

Chris

 * Refactor tests to use API article creation
 * Continue creating a suite of tests for local environments
 * Requires the API gem in mediawiki-selenium 1.20


 * Finish headless Xvfb integration
 * In Jenkins, investigate pulling master branch for beta labs builds but pull release branch for test2wiki builds
 * Follow up on ResourceLoader error reporting

Jeff

 * New task: Create browser test for VisualEditor availability on production wikis
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=60797
 * Add browser tests for using VisualEditor via Mobile UI
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=60290
 * Continuing to work getting Jenkins (CloudBees) versions of VE automated tests from red to green
 * Clean-up work on browser test for the "Nearby" page for the Mobile team
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=58720
 * Working on a request from Antoine to setup Visual Editor browser test triggers
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=53691
 * Continuing work on adding browser tests for outstanding VE regression items
 * https://www.mediawiki.org/wiki/Quality_Assurance/VisualEditor_browser_regression_test_backlog

Greg

 * Prep for Dev and Deploy process meeting (Jan 22nd)
 * Create baseline flowchart of dev/deploy documentation for use in the January in-person meeting -
 * the chart
 * refinements (ie: suggestions from Chris) -
 * write up final agenda/notes, share before meeting (clean up notes from Robla) -
 * make physical version of flowchart -
 * do post-review followup -
 * Create plan to evaluate progress on postmortem/retrospective actions
 * archive/put on wikitech missing post-mortems -
 * create BZ whiteboard entry to track retrospective bugs -

Antoine

 * For January: got to prepare myself for the MediaWiki summit (two weeks left + one week summit)
 * Mostly focused on CI (Zuul upgrade, new jenkins jobs..) last week.
 * ✅ Parsoid self update on beta cluster via a Jenkins job.
 * See 'Parsoid update' on the CI dashboard https://integration.wikimedia.org/dashboard/
 * ✅ Parsoid job migrated to new repos mediawiki/services/parsoid and mediawiki/services/parsoid/deploy
 * VE browser tests from Gerrit. Waiting for them to be passing with (a fresh wiki + phantomjs)
 * ✅ mediawiki/extensions.git out of sync since Jan 2nd

Chris

 * Bring about monitoring uploads in production with existing test, with failure messages emailed to QA staff Željko and Antoine to discuss hiding the password properly.
 * Create a suite of local bare-wiki tests to use PhantomJS in WMF Jenkins
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=60347
 * Only one existing test under/qa/browsertests passes in a bare wiki
 * Use the API to create test data (e.g. a wiki page) on a target wiki Jeff working on https://gerrit.wikimedia.org/r/#/c/106548/ .  Jeff and Chris paired Jan 24 to make progress. Commit is pending unexpected auth issue:  https://bugzilla.wikimedia.org/show_bug.cgi?id=60407
 * Continue contributing code and review to Mobile tests paired with Arthur on https://gerrit.wikimedia.org/r/#/c/106833/, etc.
 * Continue contributing code and review to Flow tests Reported/fixed upstream Selenium bug, continuing...
 * Monitor fatal errors in beta labs, send email alerts
 * merged a monitor script, needs to be cron'd/puppet'd

Jeff

 * New task: add browser tests for using VisualEditor via Mobile UI
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=60290
 * Worked with Aaron Arcos to create initial browser test for MultimediaViewer repo
 * Creating scripts for adding new wiki users and articles via Mediawiki API
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=58939
 * Continuing to work getting Jenkins (CloudBees) versions of VE automated tests from red to green
 * Clean-up work on browser test for the "Nearby" page for the Mobile team
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=58720
 * Working on a request from Antoine to setup Visual Editor browser test triggers
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=53691
 * Continuing work on adding browser tests for outstanding VE regression items
 * https://www.mediawiki.org/wiki/Quality_Assurance/VisualEditor_browser_regression_test_backlog

Greg

 * Create baseline flowchart of dev/deploy documentation for use in the January in-person meeting -
 * the chart
 * Create plan to evaluate progress on postmortem/retrospective actions

Antoine

 * jenkins job for VisualEditor / Parsoid (reporting to James F / Gabriel Wicke)
 * making sure a change in VE or in Parsoid does not break the other since they are tightly coupled
 * ✅ parsoid init script doesn't play well when run over ssh
 * Worked on, wrote an upstart job to wrap around parsoid server + logrotate configuration
 * browser tests in Gerrit.
 * ✅ First with ULS cause it is simpler, pairing with Zeljkof and i18n team
 * Second MobileFrontend https://gerrit.wikimedia.org/r/#/c/97497/
 * later VisualEditor
 * ✅ polishing up the mw release tarball job (was )

Slowdowns:
 * deployed bunch of favicons for Google Code-in
 * helped on gwtoolset, an extension to mass import materials from museum libraries
 * bunch of CI changes to make jobs running in parralel

Chris

 * Get everyone interested in API testing and monitoring pulling together: Multimedia + Jenkins + QA
 * Met with Mark Holmquist and Aaron Aarcos Dec 5
 * Progress: https://bugzilla.wikimedia.org/show_bug.cgi?id=58555
 * Test is merged and is pending adding to Jenkins https://gerrit.wikimedia.org/r/#/c/102603/
 * Move login method to shared code (Željko working on this right now), demonstrate improved pass rates pairticularly for IE
 * In process, interim commit is https://gerrit.wikimedia.org/r/#/c/100579/
 * Upgraded login method and corrected other issues affecting IE pass rate, builds are significantly more green, will pass on benefit to other repos when consolidated
 * Concrete steps for Mobile QA after Michelle's departure
 * Chris to support automation effort, Chris/Jeff/Rummana to contribute as requested, e.g. post-deployment checking
 * Chris is monitoring the backlog of mingle cards for tests immediately. Next step is to collaborate with Mobile devs for regression tests like https://gerrit.wikimedia.org/r/#/c/103761/
 * Browser test coverage for Flow
 * Coverage ongoing
 * Continuing working with S on refinements

Jeff

 * Creating scripts for adding new wiki users and articles via Mediawiki API
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=58939
 * Continuing to work getting Jenkins (CloudBees) versions of VE automated tests from red to green
 * Clean-up work on browser test for the "Nearby" page for the Mobile team
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=58720
 * Working on a request from Antoine to setup Visual Editor browser test triggers
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=53691
 * Continuing work on adding browser tests for outstanding VE regression items
 * https://www.mediawiki.org/wiki/Quality_Assurance/VisualEditor_browser_regression_test_backlog

Rummana

 * Regular exploration testing on betalabs and test2
 * Verifying each week's VE deployment
 * Verifying resolved bugs
 * Verifying new copy-paste implementation
 * Track the already reported bugs on bugzilla and changing their status accordingly

= Check-ins = These are here just for historical reasons, we no longer use this format.
 * /Checkin-20131202
 * /Checkin-20131119
 * /Checkin-20131105
 * /Checkin-20131008
 * /Checkin-20130924
 * /Checkin-20130917
 * /Checkin-20131022
 * /Checkin-20130910
 * /Checkin-20130903