This testbed: https://github.com/fippo/testbed provides a good test of WebRTC interoperability. It would make sense to run it automatically at a low frequency to ensure that we are not introducing regressions that prevent basic communication between different browsers. I spent some time with a Taskcluster loaner this morning, and it is possible to run the tests in that environment. I think it makes sense to run these tests as a Tier-3 job whenever changes under e.g. /media/webrtc and /dom/webrtc are committed. To start with, Linux running Firefox and Chrome would be fine. We can expand to Windows after that is working. Treeherder isn't really the best interface for viewing these results if we're running the tests infrequently. We'll probably want to write a dashboard that scrapes the results and presents them in a nicer fashion.
This is a P1 bug without an assignee. P1 are bugs which are being worked on for the current release cycle/iteration/sprint. If the bug is not assigned by Monday, 28 August, the bug's priority will be reset to '--'.
Roxana has been working on this one.
Assignee: nobody → rrobotin
Mass change P1->P2 to align with new Mozilla triage process
Priority: P1 → P2
I'll finish this up.
Assignee: rrobotin → dminor
Rank: 17 → 25
Priority: P2 → P3
Hi Dan, Here you can find all the details, with example, about the reporting I've done on testbed: https://docs.google.com/a/mozilla.com/document/d/1S6JV716s4UV1mzcJQrAPexzju62PiNgUMeXpTSPOe00/edit?usp=sharing. Please feel free to comment on the details. Thank you
You need to log in before you can comment on or make changes to this bug.