QA/Desktop Firefox/WebRTC: Difference between revisions
< QA | Desktop Firefox
(80 intermediate revisions by 6 users not shown) | |||
Line 1: | Line 1: | ||
See: https://wiki.mozilla.org/Media/WebRTC/Testing for background on automated testing. | 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, | The basic topology should include two separate machines on separate networks, | ||
each with their own NAT. We have some flexibility about which NAT, but | each with their own NAT. We have some flexibility about which NAT, but | ||
Line 13: | Line 9: | ||
[[File:topoplogy.png]] | [[File:topoplogy.png]] | ||
* Platforms | 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 [http://apprtc.webrtc.org 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 [http://webrtcme.herokuapp.com/r/ webrtcme] resulting in minimal lag and freezing. | |||
== | === WebRTC Landing === | ||
Run the [http://mozilla.github.com/webrtc-landing WebRTC-Landing tests] with no failures. | |||
== Known Issues == | |||
* {{bug|936034}} - Sound is distorted on one side on 1:1 call | |||
* | |||
=== | == Meetings == | ||
* [https://etherpad.mozilla.org/qa-webrtc-meeting-20130814 August 14, 2013]: Kick-off meeting with WebRTC Devs | |||
* | |||
Latest revision as of 19:27, 7 February 2014
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.
Known Issues
- bug 936034 - Sound is distorted on one side on 1:1 call
Meetings
- August 14, 2013: Kick-off meeting with WebRTC Devs