QA/Fennec: Difference between revisions

Jump to navigation Jump to search

QA/Fennec (view source)

Revision as of 20:20, 4 September 2012

4,131 bytes removed ,  4 September 2012
m
→‎Current Projects
mNo edit summary
Line 63: Line 63:
  | [https://wiki.mozilla.org/Releases/#Firefox_16 August 28th, 2012 (beta).]
  | [https://wiki.mozilla.org/Releases/#Firefox_16 August 28th, 2012 (beta).]
  |- valign="top"
  |- valign="top"
  | [[QA/Ownership|Feature Ownership]]
  | [https://docs.google.com/spreadsheet/ccc?key=0AhE7m4JB2j6tdGVKQlRHUnFWVEZXNFFJbHo0RVpQMmc Feature Ownership]
  | colspan="3" | Testing, Planning, and Bug Triage of new and stable Firefox features
  | colspan="3" | Testing, Planning, and Bug Triage of new and stable Firefox features
  |}
  |}


 
=Community Contribution=
=== Release Testing ===
'''Anyone can participate.''' There are several ways in which '''YOU''' can participate:
* [https://wiki.mozilla.org/Mobile/Releases/Release_Checklist Mobile Release Checklist]
* File bugs
 
* Triage bugs (confirm existing bugs and assign them to the right buckets)
=== Fennec Crash Reporting ===
* Help test new features
Crash Reports can be seen from [https://crash-stats.mozilla.com/products/FennecAndroid Socorro] and they are manually being done until there doesn't need to be a person looking at the socorro crash signatures for separation (crashes that have the same signatures but are completely different crashes) or combination (for signatures that are separate signatures but are really the same crashes).
* Write test cases
 
* Plan new features testing
Crash reports are done mostly for the Nightly as the developers can be the most effective there.
* Help others who want to get involved.
Here is an example of a crash report:
[https://wiki.mozilla.org/index.php?title=QA/Fennec/crash_rep_26Dec2011 Dec 26, 2011 Crash Report]
 
== What We Use ==
 
 
=== Tools ===
; Litmus
* [http://litmus.mozilla.org/ Fennec Test Runs] - A Manual test repository of execution tests for Mobile Firefox.  Consisted of smoketests, BFTs, and latest feature coverage.
; Automation
* [https://wiki.mozilla.org/Auto-tools/Projects/Robocop Robocop] - With advent of NativeFennec, a new framework was needed to test the UI of the Mobile Browser. Robotium was identified as a useful framework to take advantage of, but is not complete. Robocop incorporates all of Activity, Instrumentation, and Robotium Classes to inject events into the new Java front-end of Fennec.
 
; Device Anywhere
* [http://wiki.mozilla.org/QA/Fennec/DeviceAnywhere DeviceAnywhere] - A virtual set of Android devices for assorted device coverage when you physically dont have on.  Great for testday coverage, regression hunting, and device specific bug investigation.
 
; 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 ===
* [https://etherpad.mozilla.org/fennec-perf-ts-take2 Current Instructions on Performance Testing]
 
==== Previous Performance testing ====
* Scratch pad of [http://etherpad.mozilla.com:9000/3nS0MfR7yx notes]
* [[QA/Fennec/PerformanceBenchmark|Performance Testplan]]
* [https://spreadsheets.google.com/ccc?key=0AocUyLHteCtSdDJrNkZFaE1kUktlUGItRktJXzB5ZVE&hl=en&authkey=CLz_9McK#gid=1 Performance Benchmarks]
 
=== Website Compatibility Testing ===
* Scratch pad of [http://etherpad.mozilla.com:9000/3nS0MfR7yx notes]
* [[QA/Fennec/WebsiteCompatibility|Web Compatibility Testplan]]
 
=== Sync Performance Instrumentation ===
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]].
<p>
More historical information on the project:
* 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 ==
AaronMT
canmove, Confirmed users
2,398

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/467588"

Navigation menu