AMO Automation
This page contains information for the addons.mozilla.org automation project.
Link to our style guide
If you'd like to chat with us, we mainly hang out in #mozwebqa at irc.mozilla.org
On Migrating to Selenium Webdriver
Currently, our tests are written in selenium using the rc api and we are currently migrating them to webdriver. Here is a messy paste from our internal document on the switch: (If you want it prettier, feel free to edit.)
Reasons for switching to webdriver: We need the ability to write automated tests for mobile as soon as possible. Addons has a huge reliance on "hover" events which cannot be tested at all with Selenium-RC
- What it looks like in Github:
- Everything we've been writing in AMO has been merged directly into the master branch. We've created an addtional "webdriver" branch in the addons-tests repository where we will begin changing the page objects over to webdriver syntax.
- New tests or changes can be migrated to the webdriver branch with using git cherry-pick.
- In order to maintain velocity, we will not be using pull requests until we've built up a few page objects and working tests. Activity can be easily monitored through commits: https://github.com/mozilla/Addon-Tests/commits/webdriver .
- To maintain code quality and communication on the project, we will be doing more pair programming.
- How this affects Infrastructure:
Currently, native events are not supported for webdriver in mac but they work just fine for windows, which is the main user base for Firefox. As a result, tests in the webdriver branch will be run against windows VM's running Pivotal Tracker: We will add stories to pivotal as we work on them Create your own stories We expect more structure will emerge for creating pivotal stories as we continue through the switch
