Confirmed users
14,525
edits
QA/Desktop Firefox/WebRTC: Difference between revisions
→Routine Manual Testing Tasks
(→B2G) |
|||
| Line 5: | Line 5: | ||
need a person. The goal should be to find ways to automate this work. | need a person. The goal should be to find ways to automate this work. | ||
=== 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 16: | Line 15: | ||
The following test series should be run, with one machine on each network with Nightly. | 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 | Conduct a call for no less than 5 minutes with [http://apprtc.webrtc.org apprtc] resulting in no lag or freezing. | ||
=== 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 === | === WebRTC Landing === | ||
Run the [http://mozilla.github.com/webrtc-landing WebRTC-Landing tests] | Run the [http://mozilla.github.com/webrtc-landing WebRTC-Landing tests] with no failures. | ||
== Other Tasks == | == Other Tasks == | ||