Personal tools

QA/Fennec/WebRTC/Dogfood

From MozillaWiki

Jump to: navigation, search

Contents

Intro

We plan to ship WebRTC support for Firefox for Android in version Fx24 which is currently in beta. Our target audience for this release are Developers and we want to make their experience with Firefox on Android is as stable and high fidelity as possible.

Set Up

The focus of dogfooding for FxA is Android to Android devices, we need to cover this matrix
  • FxA Beta 24 - FxA Beta 24
  • Chrome 29 - Chrome 29 <== why? because we really want to compare and contrast the experience with FxA
  • Chrome 29 - FxA Beta 24
Install the Firefox for Android build you intend to use for testing
Make the most of Mobility
  • We are fairly confident about things working well with residential WiFi, we need a *variety* of network configs
    **What happens in the SF office?
    • What happens in the Portland office?
    • What happens in the Toronto office?
    • Hotel wifi networks
    • Coffeehouse wifi networks
    • Airport wifi networks
    • Data plans (3G, 4G)

Make the call!!

Navigate to one of these pages with your browser to make Video/Audio Calls

Capturing Logs

Nightly

  • adb shell am start -a android.activity.MAIN -n org.mozilla.fennec/.App --es env0 NSPR_LOG_MODULES=mediamanager:5,signaling:5,mediastreamgraph:6,mtransport:5

Beta

  • adb shell am start -a android.activity.MAIN -n org.mozilla.firefox_beta/.App --es env0 NSPR_LOG_MODULES=mediamanager:5,signaling:5,mediastreamgraph:6,mtransport:5

Test Results Log

Post your results here and file a bug with any issues http://mzl.la/157L9U8
  • Recording carrier-to-carrier combinations that work (or don't) is really helpful data
  • If using WiFi, specifying your router model is also helpful (for both passing and failing cases)
  • If you have a really crappy experience, try speedof.me
  • If your connection completely fails, try desktop: you can use nightly, aurora or beta
  • Considerations: How did the call establish? How was the video latency? Audio latency?


Caller Browser, Device Callee Browser, Device Location Caller 1 Location Caller 2 Call Length Notes
Firefox 24 (Android, Samsung Galaxy S4) Firefox 24 (Android, HTC One) Kind Grind, Santa Cruz Starbucks, San Diego 3 min Caller: video was tiny on talky.io but and v were clear
Callee: Ditto, call was great until we tried to add a 3rd person
Firefox 26 (Android, Galaxy Nexus) Firefox 26 (Android, Galaxy Nexus) SF office, SF SF office, SF 5 min On talky.io, experience was similar between caller and callee - video and audio were very delayed and fuzzy, essentially unusable. Perhaps worth noting that we were sharing the same WiFi network. Also, callee crashed (Bug 910964). Marginally better but still unusable experience on 24 (sans crash).
Caller:
Callee:
Caller:
Callee:
Caller:
Callee:
Caller:
Caller:
Caller:
Callee:
Caller:
Callee:
Caller:
Callee:
Caller:
Callee:
Caller:
Callee:
Caller:
Callee:
Caller:
Callee:
Caller:
Callee:
Caller:
Callee:
Caller:
Callee:
Caller:
Callee:
Caller:
Callee:
Caller:
Callee:
Caller:
Callee:
Caller:
Callee:
Caller:
Callee:
Caller:
Callee:
Caller:
Callee:
Caller:
Callee:
Caller:
Callee: