Closed Bug 894562 Opened 10 years ago Closed 10 years ago
Flesh out test format for Web
RTC automation HTML tests
We need to figure out what we want our tests to look like. We're going to have both HTML and C++ tests to define here.
ekr: Does Adam have a bugzilla account? Ideally I'd assign this to him.
Morphing this to cover just HTML tests. I haven't fleshed out a full WebRTC test yet, but I got the harness to run a sample test that communicates over the signalling channel: https://github.com/luser/steeplechase/blob/master/webharness/tests/sample.html
Assignee: nobody → ted
Summary: Flesh out test format for WebRTC automation tests → Flesh out test format for WebRTC automation HTML tests
bug 913446 has a patch with changes to the WebRTC Mochitest harness bits to make them runnable in Steeplechase. I was able to successfully run test_peerConnection_basicAudio.html on two separate machines with those changes. I imported that test + the harness bits with my changes into the steeplechase repo for testing: https://github.com/luser/steeplechase/commit/db84537869b8ab2c61a4259f1fa7c556ddbbe013
I haven't heard any complaints, so I'm going to call this FIXED. bug 913446 just landed on inbound, so we'll be able to easily run the existing Mochitests with only minor changes.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.