MANAGEMENT AND COMMUNICATION

Project Updates

Hot Projects

Meetings

• Weekly QA Meeting

• • Wednesdays, 8:30am Pacific Time
  • Telephone:
  • 650-903-0800 or 650-215-1282 x92 Conf# 99779 (US/INTL)
  • 1-800-707-2533 (pin 369) Conf# 99779 (US)
  • Vidyo Room: QA-Desktop
  • Vidyo Guest URL
  • Agenda and notes: etherpad

IRC

• #qa on irc.mozilla.org
• #mobile on irc.mozilla.org

Mailing Lists

• firefox-qe@mozilla.com
• dev-quality@mozilla.com
• dev-platform@mozilla.com

Blogs

• most contributers have blogs and a lot of information can be found out by watching these blogs
• list of most important blogs:
  • Planet Mozilla – http://planet.mozilla.org
  • QMO Community - http://quality.mozilla.org/community
  • QMO News - http://quality.mozilla.org/category/qmo-news/
  • Planet Firefox - http://planet.firefox.com/

REGULAR CYCLE QA FENNEC TEAM SCHEDULING

BETA TESTING DETAILS

1. Beta 1 & 8 testing (week 1 & 5)

• Process and documents
  • Create the Testplan and test runs for the current beta build
  • Run Smoketests - basic functions covered - 2 x ARMv7 tablet, 2 x ARMv7 phone API 11, 1 x ARMv7 phone API 9 and x86 phone

Testing Matrix:

• • Check Android Permissions - ARMv7 tablet, phone and x86
  • Bug Verification - verify all introduced fixes
  • L10 Spot Check - check that the main parts of the app are localized
  • Run Appthwack - API 11

2. Beta 2,6,10 testing (week 2,4,6)

• Process and documents
  • Create the Testplan and test runs for the current beta build
  • Run Smoketests - basic functions covered - 2 x ARMv7 tablet, 2 x ARMv7 phone API 11, 1 x ARMv7 phone API 9 and x86 phone
  • Check Android Permissions - ARMv7 tablet, phone and x86
  • Bug Verification - verify all introduced fixes
  • L10 Spot Check - check that the main parts of the app are localized
  • Results Beta 2
  • Results Beta 6
  • Results Beta 10

3. Beta 4 testing (week 3)

• Process and documents
  • Fennec Features tracking
  • Create the Testplan and test runs for the current beta build
  • Run Smoketests - basic functions covered - 1 x ARMv7 tablet, 1 x ARMv7 phone API 11, 1 x ARMv7 phone API 9, and x86 phone
  • Check Android Permissions - ARMv7 tablet, phone and x86
  • Bug Verification - verify all introduced fixes
  • L10 Spoot Check - check that the main parts of the app are localized
  • Run Appthwack - API 11
  • Run BFTs - all features tests covered
  • Results Beta 4

3. Beta features sign-off (week 5)

• Process and documents
  • Feature owners monitor new fixes + perform additional testing (weeks 1 -> 5)
  • Feature owners analyze remaining issues and do a final assessment on quality of the Beta features
  • Feature owners send final sign-off email for Beta features to dev leads & Kairo & Lawrence? (Friday week 5 or Monday week 6 latest)

4. Aurora Signoff (week 1)

• Process and documents
  • Create the Testplan and test runs for the current beta build
  • Run Smoketests - basic functions covered - 1 x ARMv7 tablet, 1 x ARMv7 phone API 11, 1 x ARMv7 phone API 9, and x86 phone
  • Check Android Permissions - ARMv7 tablet, phone and x86
  • Bug Verification - verify all introduced fixes
  • L10 Spot Check - check that the main parts of the app are localized
  • Run Appthwack - API 11
  • Run BFTs - all features tests covered
  • Results Beta 4

5. Release Candidate (week 6)

• Process and documents
  • Create the Testplan and test runs for the current beta build
  • Run Smoketests - basic functions covered - 2 x ARMv7 tablet, 3 x ARMv7 phone and x86 phone
  • Check Android Permissions - ARMv7 tablet, phone and x86
  • Bug Verification - verify all introduced fixes
  • L10 Spot Check - check that the main parts of the app are localized
  • Run Appthwack - API 11
  • Results RC

GENERAL TASKS DETAILS

1. Bug Verification

• Branches: Nightly, Aurora, Beta

2. Bug Investigations

• NI/ Regression Window wanted

3. Bug Triage

4. Feature testing

• Channel
  • Nightly - https://wiki.mozilla.org/QA/Fennec/42
    • Nightly - Draft documentation is created and Exploratory is performed to shake out most bugs
  • Aurora - https://wiki.mozilla.org/QA/Fennec/41
    • Aurora - Test Plan is created, Test Cases are created and Run
  • Beta - https://wiki.mozilla.org/QA/Fennec/40
    • Beta - Bug Verification for additional fixes, and final Exploratory/Regression testing
• Owners are assigned to each feature as early as possible
• Owners are responsible for testing and signing off on their features

5. Component Watch

• Major components split among team members
• Owners will cover: triage of new Unconfirmed bugs, investigation of bugs, and verification of fixes in certain area
• Considered a lower priority area with not much time spent on it

6. SmokeTesting & Exploratory

• Nightly
• Aurora

Automation using Robocop

• Robocop is a java based testing framework. Robocop is an extention of the Android Robotium test tool with features needed to perform automation on Firefox for Android builds.
• Here is a small walktrough to setup the enviroment and start running the automated tests
• Resources where you can read more about how to set up the enviroments, run and create automated tests using Robocop:
  • Installing Mercurial
  • Getting Firefox sourse code
  • Setup build enviroment
  • Building Firefox and running tests
  • Robocop info
  • Robotium API
  • Writing Tests
  • Existing Robocop tests
  • Simple instructions on who to create a patch file
• Here is some information about writing Robocop tests.
• Here is a set of guidelines that need to be followed in order to receive a positive review on a patch
• Here is a quick guide in setting up a pandaboard in order to run automation on it