QA/Fennec: Difference between revisions

From MozillaWiki
< QA
Jump to navigation Jump to search
No edit summary
 
(143 intermediate revisions by 9 users not shown)
Line 1: Line 1:
Home of those who want to Propel Fennec Quality!
= Overview =
The team focuses on testing current and upcoming releases of Firefox on Android. Some of our responsibilities include qualifying builds prior to a maintenance or milestone release. Some of the responsibilities include, but are not limited to:


== Milestones ==
* Verifying bugs using a triage strategy
* Current - 1.0 Maemo: [https://wiki.mozilla.org/QA/Fennec1.0/TestPlan Testplan]
* 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 Android


== Planning ==
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:
* [https://wiki.mozilla.org/QA/Fennec/Planning/2010 2010]


== What Do We Do? ==
* Confirm new unconfirmed bugs
* Verify bugs on development branches like Aurora and Beta
* 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 the Aurora branch
* Write test cases in [http://moztrap.mozilla.org Moztrap] for new features
* Monitor [http://crash-stats.mozilla.com/ crash-stats] to assess stability
* File and track new crasher bugs as they appear in crash-stats
* Manage web compatibility testing through community involvement or crowdsourcing companies that help in testing different Android 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.


=== Community Projects ===
= Team Details =
* [https://wiki.mozilla.org/QA/TestDay/ Testdays]
The team is lead by both Kevin Brosnan and 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.


=== Release Testing ===
* Lead - [mailto:kbrosnan@mozilla.com Kevin Brosnan (:kbrosnan)]
* Lead - [mailto:atrain@mozilla.com Aaron Train (:aaronmt)]


== What Do We Need Help With ==
== Team Members and Assignments ==
{| class="fullwidth-table"
| style="background:#EFEFEF; width:30%" | '''Name'''
| style="background:#EFEFEF; width:30%" | '''Contact'''
| style="background:#EFEFEF; width:10%" | '''Availability'''
| style="background:#EFEFEF; width:30%" | '''Project Assignments'''
|-
|Aaron Train
|[mailto:atrain@mozilla.com atrain@mozilla.com]
|MoCo Employee (full time)
|Lead - New features testing coordination.
|-
|Kevin Brosnan
|[mailto:kbrosnan@mozilla.com kbrosnan@mozilla.com]
|MoCo Employee (full time)
|Lead - New features testing coordination.
|-
|}


=QA Current Release Test Plans=
{| class="fullwidth-table"
| style="background:#EFEFEF; width:25%" | '''Project Test Plan'''
| style="background:#EFEFEF; width:25%" | '''Description'''
| style="background:#EFEFEF; width:25%" | '''Scope'''
| style="background:#EFEFEF; width:25%" | '''Timeframe'''
|- valign="top"
|[https://wiki.mozilla.org/QA/Fennec/31 Firefox for Android 31]
| QA activities revolving around Firefox Aurora in the time frame for Firefox 31 final release.
| [https://wiki.mozilla.org/Mobile/Roadmap#Firefox_31_.28Beta.29 Features in Firefox for Android 31]
| [https://wiki.mozilla.org/Releases/#Upcoming_Releases Upcoming Releases]
|- valign="top"
|[https://wiki.mozilla.org/QA/Fennec/32 Firefox for Android 32]
| QA activities revolving around Firefox Nightly in the time frame for Firefox 32 final release.
| [https://wiki.mozilla.org/Mobile/Roadmap#Firefox_32_.28Aurora.29 Features in Firefox for Android 32]
| [https://wiki.mozilla.org/Releases/#Upcoming_Releases Upcoming Releases]
|- valign="top"
|[https://wiki.mozilla.org/QA/Fennec/33 Firefox for Android 33]
| QA activities revolving around Firefox Nightly in the time frame for Firefox 32 final release.
| [https://wiki.mozilla.org/Mobile/Roadmap#Firefox_33_.28Nightly.29 Features in Firefox for Android 33]
| [https://wiki.mozilla.org/Releases/#Upcoming_Releases Upcoming Releases]
|- valign="top"
| [https://docs.google.com/spreadsheet/ccc?key=0AhE7m4JB2j6tdGVKQlRHUnFWVEZXNFFJbHo0RVpQMmc Feature Ownership]
| colspan="3" | Testing, Planning, and Bug Triage of new and stable Firefox features used till Firefox for Android 30
|}


=== Test Tool Development ===
=Community Contribution=
* Write automated [https://wiki.mozilla.org/Mobile/Fennec_TestDev#Areas_to_focus_on testcases]
'''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.


=== Execution ===
== How You Can Contact Us ==
* Create Litmus testcases for bugs flagged as [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=in-litmus%3F%20Mobile in-litmus?]
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.
* [https://wiki.mozilla.org/QA/TestDay/ TestDay] Promotions within Mobile Community Channels
* Mailing Lists
** [https://mail.mozilla.org/listinfo/android-mobile-nightly-testers Firefox for Android (Mobile Nightly Testers)]
* Newsgroups
** [http://groups.google.com/group/mozilla.dev.platforms.mobile/topics mozilla.dev.platforms.mobile]
** [http://groups.google.com/group/mozilla.dev.quality/topics mozilla.dev.quality]


== What Do We Use? ==
=== Download Firefox for Android ===
The easiest and most simplest way to help us by using Firefox for Android. One can download Firefox for Android on [https://play.google.com/store/apps/details?id=org.mozilla.firefox Google Play] and installing it on your Android device.


 
=Resources=
=== Tools ===
==== Reference Links ====
* [https://addons.mozilla.org/en-US/mobile/addon/13954 QA Companion]: Currently allows users to painlessly report bugs if they don't have a desktop on hand.
* This is a list of all the features being considered for development across products in the near future: https://wiki.mozilla.org/Features.
* Manual Testing:  
** To be specific this is the list of potential [https://wiki.mozilla.org/Features/Mobile mobile Firefox features] being considered.
** Litmus [https://litmus.mozilla.org/run_tests.cgi?test_run_id=35 Fennec 1.0 Test Run]
* You can find a list of features to be shipped in the coming milestones: https://wiki.mozilla.org/Firefox/Flight_Tracking
** Litmus [https://litmus.mozilla.org/run_tests.cgi?test_run_id=48 Fennec 1.0 Localizer Test Run]
 
=== Resources ===
* [http://hg.mozilla.org/mobile-browser/ Fennec HG] Repository
* [http://mxr.mozilla.org/mobile-browser/ Fennec MXR Source Code] Web-Based Viewer
* Builds
** [http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mobile-trunk/ Trunk Nightly Builds]
** [http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/ Hourly Tinderbox Builds]
** [http://l10n.mozilla.org/dashboard/?tree=fennec10x Fennec L10n] Dashboard

Latest revision as of 19:25, 28 April 2016

Overview

The team focuses on testing current and upcoming releases of Firefox on Android. 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 Android

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 like Aurora and Beta
  • 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 the Aurora branch
  • Write test cases in Moztrap for new features
  • Monitor crash-stats to assess stability
  • File and track new crasher bugs as they appear in crash-stats
  • Manage web compatibility testing through community involvement or crowdsourcing companies that help in testing different Android 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 both Kevin Brosnan and 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.
Kevin Brosnan kbrosnan@mozilla.com MoCo Employee (full time) Lead - New features testing coordination.

QA Current Release Test Plans

Project Test Plan Description Scope Timeframe
Firefox for Android 31 QA activities revolving around Firefox Aurora in the time frame for Firefox 31 final release. Features in Firefox for Android 31 Upcoming Releases
Firefox for Android 32 QA activities revolving around Firefox Nightly in the time frame for Firefox 32 final release. Features in Firefox for Android 32 Upcoming Releases
Firefox for Android 33 QA activities revolving around Firefox Nightly in the time frame for Firefox 32 final release. Features in Firefox for Android 33 Upcoming Releases
Feature Ownership Testing, Planning, and Bug Triage of new and stable Firefox features used till Firefox for Android 30

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.

Download Firefox for Android

The easiest and most simplest way to help us by using Firefox for Android. One can download Firefox for Android on Google Play and installing it on your Android device.

Resources

Reference Links