Thank you for checking out Mozilla's Marketplace 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 Marketplace-Tests:
https://github.com/mozilla/marketplace-tests/contributors
We love working with contributors to fill out the Selenium test coverage for Marketplace-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 marketplace-dev.allizom.org.
Mozilla maintains a guide to running Automated tests on our QMO website:
https://quality.mozilla.org/docs/webqa/running-webqa-automated-tests/
This wiki page has some advanced instructions specific to Windows:
https://wiki.mozilla.org/QA_SoftVision_Team/WebQA_Automation
###You will need to install the following:
If you have cloned this project already then you can skip this! GitHub has excellent guides for [Windows][GitWin], [MacOSX][GitMacOSX] and [Linux][GitLinux]. [GitWin]: http://help.github.com/win-set-up-git/ [GitMacOSX]: http://help.github.com/mac-set-up-git/ [GitLinux]: http://help.github.com/linux-set-up-git/
Before you will be able to run these tests you will need to have [Python 2.6][Python] installed. [Python]: http://www.python.org/download/releases/2.6.6/
Install pip (for managing Python packages):
sudo easy_install pip
If you don't already have one, sign up for a GitHub account.
If you visit the project page while signed into your GitHub account, you will see an option to Fork the repository. If you think you might want to contribute to the project, create a Fork so that you have a copy you can experiment with.
On your computer, clone the repository (your own if you forked, or the mozilla one if not). The URL for cloning is close to the top of the GitHub project page.
Be sure to retrieve the git submodules by issuing this command at the project root:
git submodule update --init
####Virtualenv and Virtualenvwrapper (Optional/Intermediate level) 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.
If you are using virtualenv, create and activate the virtualenv, then run the following in the project root:
pip install -r requirements.txt
If you are not using virtualenv, run the following in the project root to install dependencies globally:
sudo pip install -r requirements.txt
You will need persona credentials for the site being tested. Get the URL being tested from mozwebqa.cfg in the project root, sign up for that site, and enter the credentials in a yaml file (see credentials.yaml in the project root). To avoid version control conflicts, you may want to store your credentials files separately from your source code.
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 non-destructive tests:
py.test --driver=firefox --credentials=/path/to/credentials/credentials.yaml
An example of running all of the tests in one file:
py.test --driver=firefox --credentials=/path/to/credentials/credentials.yaml tests/mobile/test_details_page.py
An example of running one test in a file:
py.test --driver=firefox --credentials=/path/to/credentials/credentials.yaml tests/mobile/test_details_page.py -k test_details_page_for_an_app
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 or run
py.test --help
Prerequisites: Java Runtime Environment, Apache Ant
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
ant launch-huborant launch-node - 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/.