QA/Desktop Firefox/WebRTC

See: https://wiki.mozilla.org/Media/WebRTC/Testing for background on automated testing.

Basic Topology

The basic topology should include two separate machines on separate networks, each with their own NAT. We have some flexibility about which NAT, but for concreteness, I suggest a pair of Apple Airport Express NATs. I.e., the following topology:

The following test series should be run, with one machine on each network with Nightly.

Endpoints

• Firefox Nightly <-> Firefox Nightly
• Firefox Nightly <-> Chrome Stable
• Firefox Nightly <-> Chrome Canary

Platforms

• Desktop (Windows, Mac, Linux)
• B2G (Unagi, Peak)
• Android

AppRTC

Conduct a call for no less than 5 minutes with apprtc resulting in no lag, no freezing, no audio or video delays, no degradation in quality from the previous revision.

WebRTC.ME

Conduct a call for no less than 1 minute using webrtcme resulting in minimal lag and freezing.

WebRTC Landing

Run the WebRTC-Landing tests with no failures.

Testing

Weekly Sign-off

Conduct a 10 minute 1:1 call via apprtc.webrtc.org using Firefox Nightly (Win/Mac/Lin) to Firefox Nightly (Win/Mac/Lin), with no other process running, should be clear and accurate (no delays, no artifacts, no crashes or hangs, no degradation in audio or video quality). Issues found should be compared against Chrome before reporting to Bugzilla.

2013-11-11 to 2013-11-15

• Testing
  • Windows XP -> Windows 7
  • Windows 7 -> Mac OSX 10.9
  • Mac OSX 10.9 -> Ubuntu 13.10
  • Ubuntu 13.10 -> Windows XP
• Bugs Reported:
• Bugs Confirmed:
• Bugs Verified:

Bug Triage

FIXED Bugs

The following tracks verification of WebRTC bug fixes. As you verify a bug fix please list it below.

Verified Fixes

UNCONFIRMED Bugs

The following tracks confirmation of WebRTC unconfirmed bugs. As you confirm a bug exists please list it below.

Confirmed Bugs

Meetings

• August 14, 2013: Kick-off meeting with WebRTC Devs