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.

Weekly Sign-off

• Spend 2 days each week testing a 10 minute 1:1 call for clarity, accuracy, and performance (issues found should be compared against Chrome before reporting to Bugzilla)
• Spend 1/2 day each week verifying bug fixes
• Spend 1/2 day each week confirming reported bugs

2013-11-11 to 2013-11-15

• Testing
  • [result] Caller Endpoint -> Callee Endpoint

• Bugs Reported:
• Bugs Confirmed:
• Bugs Verified:

Previous Weeks

• link to reports from previous weeks

Meetings

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