Management and Communication

Project Updates

• Add yourself to the list of Team Members
• Weekly Scrum Pads

Meetings

• Weekly Waverly meeting
• Bi-weekly Desktop Automation meeting (optional)

IRC

• #mozmill on irc.mozilla.org (use SSL)

Mailing Lists

• mozmill-dev - Mozmill Developer mailing list hosted on Google
• Use internal Waverly mailing list to communicate active work to managers

Bug watchers

• mozmill-tests@mozilla-qa.bugs - Mozmill Tests (required)
• mozmill-automation@mozilla-qa.bugs - Mozmill automation scripts (optional, but proposed)
• mozmill-crowd-extension@mozilla-qa.bugs- Mozmill Crowd extension (optional)
• mozmill-result-dashboard@mozilla-qa.bugs- Mozmill Dashboard (optional)

Spreadsheets

• Mozmill Test Coverage (Send proposed email address to Henrik)

Mozmill

First Steps

• Install Mozmill
• Get familiar with the handling of our Mozmill Tests
• Clone the mozmill-automation repository

Hardware and Environments

• It is important to have hardware or VMs available which cover test-runs on all of our supported platforms (Windows, Linux, OS X)
• Test developing should be done on Linux and OS X due to better debugging capabilities
• Use whatever text editor you like

Tasks

Test Creation

• Identify areas of work with Vlad irc: vladmaniac and Anthony irc: ashughes
• Current status in tracked in the Google Spreadsheet
• Follow the steps as given on the project page
• Review Process
  • Review: Vlad, Alex, Anthony (ask for availability on IRC for a fast process)
  • Super-Review: Anthony

Shared Modules / UI map

• If necessary existing shared modules or ui maps have to be enhanced to allow access to specific elements and back-end features of a component
• Review Process
  • Review: Henrik, Geo or any other QA Automation services team member

Fixing broken Tests

• Daily checks of our dashboards: daily/release, crowd
• Follow the steps as given on the project page
• Review Process
  • Review: Vlad irc: vladmaniac, Alex irc: AlexLakatos
  • Super-Review: Anthony irc: ashughes

Additional Information

• Henrik will be available throughout the day (European time) to help out at any time
• Automation team members from Softvision will be flexible, so Desktop and WebQA can help out each other
• Each Mozmill test covers exactly one test on Litmus (make sure the test is accurate before starting to work on it - re-check with group owner if necessary)
• When tests have been updated always test them across platforms and with the automation test-run script from the mozmill-automation repository.
• Don't forget to update the Litmus tests which are connected to Mozmill tests of the same Branch
• If you have to disable a Litmus test please follow those steps.
• Obey the Style Guide for Mozmill tests.
• We do not add new Mozmill tests to older branches, only for Nightly and Aurora. Only test fixes will be allowed to land on older branches.