QA/Fennec/iOS: Difference between revisions

From MozillaWiki
< QA‎ | Fennec
Jump to navigation Jump to search
Line 63: Line 63:
=Resources=
=Resources=
==== Reference Links ====
==== Reference Links ====
* This is a list of all the features being considered for development across products in the near future: https://wiki.mozilla.org/Mobile/Firefox_for_iOS.
* Project overview, definition, phases and further descriptions available on the project page here: https://wiki.mozilla.org/Mobile/Firefox_for_iOS
* Current [https://docs.google.com/a/mozilla.com/spreadsheets/d/1rfhMbw2zR6OmL8gSo_Nz3YuEVbNnHpFGZTvV2DX90fc/edit#gid=0 working document for the browser functionality] is available to Mozilla employees only initially whilst the definition gets locked down.


==== Additional Resources & Tips ====
==== Additional Resources & Tips ====

Revision as of 18:57, 2 March 2015

Overview

The team focuses on testing current and upcoming releases of Firefox on iOS. Some of our responsibilities include qualifying builds prior to a maintenance or milestone release. Some of the responsibilities include, but are not limited to:

  • Verifying bugs using a triage strategy
  • Running basic functional tests and smoke tests - mostly manual; but automated in the near future
  • Running our manual test suites on localized builds
  • Making sure web content is viewable, acceptable and ready for consumption in Firefox for iOS

In addition to qualifying builds prior to a release, we perform ongoing tasks on the development branches to ensure no major problems get uplifted as we merge changes to the next branch. For example, on a daily basis we:

  • Confirm new unconfirmed bugs
  • Verify bugs on development branches
  • Engage community and new volunteers in helping improve Firefox through test day events
  • Interact with developers to help them test the features they implement
  • Perform exploratory testing on new features while on development branch
  • Write test cases in Moztrap for new features
  • Monitor crashes to assess stability
  • File and track new crasher bugs as they appear
  • Manage web compatibility testing through community involvement or crowdsourcing companies that help in testing different iOS device configurations and top-site testing

All of which help assess the quality of individual new features as well as the Firefox version as a whole.

Team Details

The team is lead by Aaron Train who coordinate testing of their respective areas among several MoCo employees and community volunteers. Traditionally new features are tested by several MoCo QA employees. Anyone is welcome and encouraged to participate.

Team Members and Assignments

Name Contact Availability Project Assignments
Aaron Train atrain@mozilla.com MoCo Employee (full time) Lead - New features testing coordination.

QA Current Release Test Plans

Community Contribution

Anyone can participate. There are several ways in which YOU can participate:

  • File bugs
  • Triage bugs (confirm existing bugs and assign them to the right buckets)
  • Help test new features
  • Write test cases
  • Plan new features testing
  • Help others who want to get involved.

How You Can Contact Us

If you're interested in helping out with anything below (or want to help with something else), please contact us. We hang out on irc.mozilla.org in the channel #qa and in #mobile.

Download Firefox for iOS

The easiest and most simplest way to help us by using Firefox for iOS. One can download Firefox for iOS on our temporary XCode integration server and installing it on your iOS device. Note that installation capability are currently limited to provisioned and certified devices.

Resources

Reference Links

Additional Resources & Tips