QA/Desktop Firefox/WebRTC: Difference between revisions
< QA | Desktop Firefox
Jump to navigation
Jump to search
| Line 31: | Line 31: | ||
== Weekly Sign-off == | == Weekly Sign-off == | ||
* | * [https://wiki.mozilla.org/QA/Desktop_Firefox/WebRTC/2013.45 2013-11-04 to 2013-11-08] | ||
== Meetings == | == Meetings == | ||
* [https://etherpad.mozilla.org/qa-webrtc-meeting-20130814 August 14, 2013]: Kick-off meeting with WebRTC Devs | * [https://etherpad.mozilla.org/qa-webrtc-meeting-20130814 August 14, 2013]: Kick-off meeting with WebRTC Devs | ||
Revision as of 22:10, 5 November 2013
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
Meetings
- August 14, 2013: Kick-off meeting with WebRTC Devs