Auto-tools/Automation Development/QA/Automation Services/New Members

From MozillaWiki
Jump to navigation Jump to search

Welcome to the Team! Hopefully you will have been given a buddy. Your buddy will be there to answer questions where they can or direct you to the person who might know the right answer.

Start by following standard new hire info. This is the standard new hires documentation for the company and will get you mostly setup with email, your desk and all the other necessary things. This is the Mozilla Firehose so be prepared to see a lot of information!!

Make sure to join IRC and set the following channels as auto-join. #qa, #mozwebqa, #mozmill . Others will be added as you start working on projects.

Accounts

  • Create a Bugzilla account - http://bugzilla.mozilla.com
    • Under Account Information add a real name with [:ircnick] so if people need to add you to a bug its easier to find you
    • Setup bug watchers for components you have to listen for updates (project dependend)
      • Mozmill
      • Mozilla QA / Mozmill *
  • Create a wiki account on the Public Wiki
  • Create a Github account and email David Burns with details so he can add you to the Mozilla organisation
  • A Pivotal Tracker account for project tasks
  • Create a QMO account
  • Create a Litmus account and ask for the ability to create test cases

Mailing Lists

  • Sign up for the WebQA mailing list

Setting up your machine for Automation Services

  • Install an IDE that would allow you to work on a number of languages.
  • Install Git
    • OSX - sudo brew install git
    • Ubuntu - sudo apt-get install git
    • Windows - Install msysgit
  • Install Xcode from the Application Install CD included with your MacOSX
  • Install the latest Python 2.6. If on OSX you will need to update your brew formula with this Gist
  • Install Pip with the following command sudo easy_install pip
  • sudo pip install mercurial
  • sudo pip install virtualenvwrapper
  • update your ~/.bash_profile
 export WORKON_HOME=$HOME/.virtualenvs
 export PIP_VIRTUALENV_BASE=$WORKON_HOME
 source /usr/local/bin/virtualenvwrapper.sh
  • To create a new virtualenv you would do mkvirtualenv projecta --no-site-packages. "projecta" would be the name of the project you are using
 workon projecta
  • install libraries needed in the relevant virtualenv so that you don't pollute your environment. If something goes wrong you can delete the virtualenv without breaking your machine

Pivotal Tracker

We use Pivotal Tracker to track tasks that need doing. This could be at a team level(https://www.pivotaltracker.com/projects/323503) or at a Project level. Ask an admin (Henrik Skupin) to add you to the Mozilla account.

Employee Items

Unfortunately there are a couple things that community members can't get access to. These are for employees but if it should be known to everyone rest assured we will move it into the public domain!!!

Other things to read

Great! Now that you have got this far and your brain is still operational, lets get going with writing tests, helping guide other QA teams and expanding things to make the rest of QA look good!