How MediaWiki, software that runs Wikipedia, is tested
summary
MediaWiki test automation uses cucumber for readable specs, page objects for maintainability, and Ruby with rvm/bundler to pin environments; a MediaWiki Vagrant box (Puppet provisioned) spins up a headless instance with Firefox forwarded for local debugging, while Jenkins and Sauce Labs run cross‑browser suites. Repositories live in Gerrit with a GitHub mirror, builds are public, three core testers plus interns/volunteers maintain it, and the setup is working in production.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:04Wikipedia
- 2:17Communication
- 4:25Login page
- 5:59Machine Pro
- 7:42Bundler
- 9:10Vagrant
- 12:56Jenkins
- 13:18Selenium
- 13:41Browsers
- 14:38Visibility
- 15:48Reporting
- 18:01Mailing list
- 20:01Twitter
- 21:58Why Ruby
- 24:29Easy Task List
- 25:25Connect Jenkins and Sauce Labs
- 26:16Test repository
related talks
42mTesting in production for fun and profit
37mKeeping trust: Testing documentation as part of a continuous integration process
35mWordPress Acceptance Testing: Solved
44mSelenium and Cucumber
28mBuilding an automated testing suite...
24mAutomated Visual Regression & Accessibility Testing
29mUsing Selenium and Cucumber to test a healthcare information system
27mAutomated Web Acceptance Testing with Behat