How software that runs Wikipedia is tested
•
1 like•926 views
This document discusses test automation strategies and tools used at Wikimedia. It covers topics like communication, maintainability, browser automation, code visibility, continuous integration, test results, code reuse, speeding up tests, how to get involved, local development environments, and reasons for using Ruby. Key tools mentioned include Cucumber, page object pattern, Selenium, Sauce Labs, Git, Gerrit, GitHub, Jenkins, Bugzilla, parallel_tests, RVM, Bundler, and MediaWiki-Vagrant. The document provides an overview of Wikimedia's test automation approach across 11 pages.
More Related Content
What's hot
Viewers also liked
Viewers also liked (20)
Similar to How software that runs Wikipedia is tested
Similar to How software that runs Wikipedia is tested (20)
More from SQALab
More from SQALab (20)
Recently uploaded
Recently uploaded (20)
How software that runs Wikipedia is tested
- 19. Combinatorial explosion browser / operating system / version 4/9
- 24. Code: Git, Gerrit, GitHub git-scm.com gerrit.wikimedia.org github.com/wikimedia
- 36. Test results: Sauce Labs saucelabs.com
- 42. Code reuse 6/9
- 45. Speed 7/9
- 46. Not there yet :( github.com/grosser/parallel_tests
- 48. Help wanted! 8/9
- 50. Works at my machine! 9/9
- 56. Ruby Version Manager (RVM) Ruby versions and gemsets rvm.io
- 73. Communication: Cucumber Maintainability: page-object gem Browser automation: selenium-webdriver gem Combinatorial explosion: Sauce Labs Code reuse: mediawiki-selenium gem (Speed: parallel_tests gem) Help wanted: Ruby Works at my machine: RVM, Bundler gem
- 74. How to fail at test automation? 11/9