QA/Fennec: Difference between revisions

From MozillaWiki
< QA
Jump to navigation Jump to search
 
(32 intermediate revisions by 6 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 Releases'''
* Running basic functional tests and smoke tests - mostly manual; but automated in the near future
* 10.0: [https://wiki.mozilla.org/QA/Fennec/Milestones/10.0 Testplan]
* Running our manual test suites on localized builds
* 9.0: [https://wiki.mozilla.org/QA/Fennec/Milestones/9.0 Testplan]
* Making sure web content is viewable, acceptable and ready for consumption in Firefox for Android
* 8.0: [https://wiki.mozilla.org/QA/Fennec/Milestones/8.0 Testplan]
* 7.0: [https://wiki.mozilla.org/QA/Fennec/Milestones/7.0 Testplan]


{{hidden
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:
|Past Releases
|
* 6.0: [https://wiki.mozilla.org/QA/Fennec/Milestones/6.0 Testplan]
* 5.0: [https://wiki.mozilla.org/QA/Fennec/Milestones/5.0 Testplan]
* 2.0: [https://wiki.mozilla.org/QA/Fennec/Milestones/2.0 Testplan]
* 1.1: [https://wiki.mozilla.org/QA/Fennec/Milestones/1.1 Testplan]
* 1.0: [https://wiki.mozilla.org/QA/Fennec1.0/TestPlan Testplan]
|headerstyle=background:#dddddd
}}


== Planning ==
* Confirm new unconfirmed bugs
* [https://wiki.mozilla.org/QA/Fennec/Planning/2011 2011]
* Verify bugs on development branches like Aurora and Beta
* <s>[https://wiki.mozilla.org/QA/Fennec/Planning/2010 2010]</s>
* 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


== What We Do ==
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.


=== Testing Strategy  ===
* Lead - [mailto:kbrosnan@mozilla.com Kevin Brosnan (:kbrosnan)]
; Manual
* Lead - [mailto:atrain@mozilla.com Aaron Train (:aaronmt)]
*[[QA/Fennec/Waverley]] on the latest [nightly.mozilla.org/mobile.html Nightly build] on the current development branch and trunk
*Verification of overnight resolved bugs on the current development branch
*Run BFT(s)/Focused testing around areas that area affected by resolved bugs
*Weekly triage of [http://bit.ly/qbtF9O new and unconfirmed bugs]
*[http://quality.mozilla.org/ Bi-Monthly Testdays]


; Automation
== Team Members and Assignments ==
* [https://wiki.mozilla.org/User:MarkFinkle/RunningTests Browser Chrome, Reftests, Crashtests, Talos Performance Tests]
{| 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.
|-
|}


; Unique Areas of Testing:
=QA Current Release Test Plans=
{| class="fullwidth-table"
{| class="fullwidth-table"
|-
| style="background:#EFEFEF; width:25%" | '''Project Test Plan'''
| style="background:#EFEFEF; width:33%" | '''Project'''  
| style="background:#EFEFEF; width:25%" | '''Description'''
| style="background:#EFEFEF; width:66%" | '''Description'''
| style="background:#EFEFEF; width:25%" | '''Scope'''
|- valign="top"
| style="background:#EFEFEF; width:25%" | '''Timeframe'''
| [https://spreadsheets.google.com/ccc?key=0AhE7m4JB2j6tdEJFZ3NoZkRoRTM3TTRpQll3UjZLYnc&hl=en&authkey=CPiPp9IK#gid=4 Device Compatibility Test Plan]
|- valign="top"
| Tracks Tests and Full device list of compatibility with Mobile Firefox
|[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.
| [[QA/Fennec/WebsiteCompatibility|Website Compatibility Test Plan]]
| [https://wiki.mozilla.org/Mobile/Roadmap#Firefox_31_.28Beta.29 Features in Firefox for Android 31]
| Tracks top Website compatibility with Mobile Firefox
| [https://wiki.mozilla.org/Releases/#Upcoming_Releases Upcoming Releases]
|-
|- valign="top"
| [https://spreadsheets.google.com/ccc?key=0AocUyLHteCtSdDJrNkZFaE1kUktlUGItRktJXzB5ZVE&hl=en&authkey=CLz_9McK#gid=1 Performance Benchmarking Test Plan]
|[https://wiki.mozilla.org/QA/Fennec/32 Firefox for Android 32]
| Tracking performance benchmarking numbers for Startup times and Page Loads
| 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/QA/Browser_Technologies/Mobile_Unit_Testing_Addon Mobile Addon for Unit Testing Automation]  
| [https://wiki.mozilla.org/Releases/#Upcoming_Releases Upcoming Releases]
| Project to run unit tests via a test-harness addon and disperse via crowdsourcing techniques
|- 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.
=== Release Testing ===
| [https://wiki.mozilla.org/Mobile/Roadmap#Firefox_33_.28Nightly.29 Features in Firefox for Android 33]
* [https://wiki.mozilla.org/Mobile/Releases/Release_Checklist Mobile Release Checklist]
| [https://wiki.mozilla.org/Releases/#Upcoming_Releases Upcoming Releases]
 
|- valign="top"
=== Fennec Crash Reporting ===
| [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
== What We Use ==
|}
 
 
=== Tools ===
; Litmus
* [http://litmus.mozilla.org/ Fennec Test Runs]
 
; Device Anywhere
* [http://wiki.mozilla.org/QA/Fennec/DeviceAnywhere DeviceAnywhere]  
 
; Performance Graphs
* [http://graphs.mozilla.org/ Performance Graphs]
 
=== Resources ===
; Device Anywhere Tutorial
* [http://wiki.mozilla.org/QA/Fennec/DeviceAnywhere Device Anywhere Tutorial]
 
; Mobile (HG) Repository
* [http://hg.mozilla.org/mozilla-central/ mozilla-central]
 
; Mobile Source Code
* [http://mxr.mozilla.org/mozilla-central/source/mobile/ Fennec MXR Source Code] Web-Based Viewer
 
; Builds
* [http://nightly.mozilla.org/mobile.html Mobile Nightly Builds]
* [http://ftp.mozilla.org/pub/mozilla.org/mobile/tinderbox-builds/ Hourly Tinderbox Builds]
* [https://l10n-stage-sj.mozilla.org/?tree=fennec10x Fennec L10n Dashboard]
 
== Where Do We Need Help ==
 
=== Test Tool Development ===
* Write automated [https://wiki.mozilla.org/Mobile/Fennec_TestDev#Areas_to_focus_on testcases]
* Port [https://wiki.mozilla.org/Mobile/Fennec_Automation Automation] Frameworks to WinCE
* Find, Fix, Verify [https://wiki.mozilla.org/Mobile/Fennec_TestDev#Other_TestDev_related_todo.27s UnitTest] Failures
 
=== Execution ===
* Triage [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced;bug_status=UNCONFIRMED;product=Fennec Unconfirmed] Fennec Bugs
* Create Litmus testcases for bugs flagged as [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=in-litmus%3F%20Mobile in-litmus?]
** [https://wiki.mozilla.org/QA/Execution/Litmus/Ownership Fennec Component Ownership in Litmus]
* [https://wiki.mozilla.org/QA/TestDay/ TestDay] Promotions within Mobile Community Channels
* Write [http://wiki.mozilla.org/QA/Fennec/TechDocQueue technical documentation] to perform quality execution
 
=== Performance Benchmarking ===
* Scratch pad of [http://etherpad.mozilla.com:9000/3nS0MfR7yx notes]
* [[QA/Fennec/PerformanceBenchmark|Performance Testplan]]


=== Website Compatibility Testing ===
=Community Contribution=
* Scratch pad of [http://etherpad.mozilla.com:9000/3nS0MfR7yx notes]
'''Anyone can participate.''' There are several ways in which '''YOU''' can participate:
* [[QA/Fennec/WebsiteCompatibility|Web Compatibility Testplan]]
* File bugs
 
* Triage bugs (confirm existing bugs and assign them to the right buckets)
=== Sync Performance Instrumentation ===
* Help test new features
Fennec sync continues to cause performance issues on first time syncing with very large amounts of data.  How you can help, is to provide sync logging through a custom extension, and submit your data to the Mozilla Services team.  Detailed instructions can be found [[QA/Fennec/Sync_Performance_Collection|here]].
* Write test cases
<p>
* Plan new features testing
More historical information on the project:
* Help others who want to get involved.
* Philikon's [https://wiki.mozilla.org/User:Philikon/SyncInstrumentation Sync Instrumentation Research]
* Blog on [http://philikon.wordpress.com/2011/03/09/javascript-perf-avoid-creating-objects-2/ profiling Javascript Objects]


== How You Can Contact Us ==
== How You Can Contact Us ==
If you're interested in helping out with anything below (or want to help with something else), please contact [http://quality.mozilla.org/user/21/contact jmaher]  or [http://quality.mozilla.org/user/1342/contact aakashd]. If you want to talk to the Mozilla Mobile Community, you can find us in our [http://widget.mibbit.com/?settings=1b10107157e79b08f2bf99a11f521973&server=irc.mozilla.org&channel=%23mobile IRC Channel].  
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.
 
* Mailing Lists
* Mailing Lists
** mobile@mozilla.com
** [https://mail.mozilla.org/listinfo/android-mobile-nightly-testers Firefox for Android (Mobile Nightly Testers)]
* Newsgroups
* Newsgroups
** [http://groups.google.com/group/mozilla.dev.platforms.mobile/topics mozilla.dev.platforms.mobile]
** [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]
** [http://groups.google.com/group/mozilla.dev.quality/topics mozilla.dev.quality]
* 3rd Party Testing (Waverley)
 
** [https://wiki.mozilla.org/QA/Fennec/Waverley Execution testplan] for Smoketests & BFTs
=== 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=
==== Reference Links ====
* This is a list of all the features being considered for development across products in the near future: https://wiki.mozilla.org/Features.
** To be specific this is the list of potential [https://wiki.mozilla.org/Features/Mobile mobile Firefox features] being considered.
* You can find a list of features to be shipped in the coming milestones: https://wiki.mozilla.org/Firefox/Flight_Tracking

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

Retrieved from "https://wiki.mozilla.org/index.php?title=QA/Fennec&oldid=1130225"