Thank you for checking out Mozilla's Addon-Tests test suite. Mozilla and the Mozwebqa team are grateful for the help and hard work of many contributors like yourself. The following contributors have submitted pull requests to Addon-Tests:
We love working with contributors to fill out the Selenium test coverage for Addon-Tests, but it does require a few skills. You will need to know some Python, some Selenium and you will need some basic familiarity with Github.
If you know some Python, it's worth having a look at the Selenium framework to understand the basic concepts of browser based testing and especially page objects. Our suite uses Selenium WebDriver.
If you need to brush up on programming but are eager to start contributing immediately, please consider helping us find bugs in Mozilla Firefox or find bugs in the Mozilla web-sites tested by the WebQA team.
To brush up on Python skills before engaging with us, Dive Into Python is an excellent resource. MIT also has lecture notes on Python available through their open courseware.The programming concepts you will need to know include functions, working with classes, and some object oriented programming basics.
While we take pains to keep our documentation updated, the best source of information is those of us who work on the project. Don't be afraid to join us in irc.mozilla.org #mozwebqa to ask questions about our Selenium tests. Mozilla also hosts the #mozillians chat room to answer your general questions about contributing to Mozilla.
This repository contains Selenium tests used to test the website addons.mozilla.org.
Mozilla maintains a guide to running Automated tests on our QMO website:
This wiki page has some advanced instructions specific to Windows:
Before you will be able to run these tests you will need to have Python 2.6 installed.
Tests are run using the py.test library. You will find examples here for running all of the tests, tests in one file and running a single test.
WebDriver does not need a Selenium Server or Grid to run so these examples bypass this step and just use the --driver command.
An example of running all tests without a Selenium Server:
py.test --driver=firefox --credentials=/credentials.yaml
An example of running all of the tests in one file:
py.test --driver=firefox --credentials=/credentials.yaml tests/test_details_page.py
An example of running one test in a file:
py.test --driver=firefox --credentials=/credentials.yaml tests/test_details_page.py -k test_that_external_link_leads_to_addon_website
If running on a Mac, skip tests which require 'native' support:
py.test --driver=firefox --credentials=/credentials.yaml -m 'not native'
Depending on the platform you're running the tests on, run only the tests in the mobile or desktop directories:
py.test --driver=firefox --credentials=/credentials.yaml ./tests/desktop py.test --driver=firefox --credentials=/credentials.yaml ./tests/mobile
For information about running tests against a Selenium Grid or moz-grid-config see the section in this document about setting up moz-grid-config.
The mozwebqa plugin has advanced command line options for reporting and using browsers. See the documentation on davehunt's pytest mozwebqa github:
While most of us have had some experience using virtual machines, virtualenv is something else entirely. It's used to keep libraries that you install from clashing and messing up your local environment. After installing virtualenv, installing virtualenvwrapper will give you some nice commands to use with virtualenvwrapper.
Moz-grid-config is a project containining our Selenium Grid configuration. It uses Apache Ant to run the Selenium hub or node to the configuration defined in the yaml files.
We recommend git cloning the repository for a couple of reasons:
- The commands to launch a node or hub are all pre-configured and as simple as typing
- The paths to browser binaries and nodes can be stored in configuration (yaml) files
- It contains a jar file of the latest Selenium in it's lib directory
(If you prefer to download Selenium it's own, you can do that from here) You will need to make sure that the name of your Firefox application matches one of the names in moz-grid-config/grid_configuration.yml. As an example: even though Firefox typically installs without a version number in the name, moz-grid-config requires it to be named "Firefox ".app on mac.
If you want to get involved and add more tests then there's just a few things we'd like to ask you to do:
- Use the template files for all new tests and page objects
- Follow our simple style guide
- Fork this project with your own GitHub account
- Add your test into the "tests" folder and the necessary methods for it into the appropriate file in "pages"
- Make sure all tests are passing and submit a pull request with your changes
This software is licensed under the MPL 2.0:
This Source Code Form is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, You can obtain one at http://mozilla.org/MPL/2.0/.