- From: Harald Alvestrand <hta@google.com>
- Date: Thu, 19 Jul 2012 11:08:13 +0200
- To: Odin Hørthe Omdal <odinho@opera.com>
- Cc: public-webrtc-testsuite@w3.org
- Message-ID: <CAOqqYVFc7d+hzvU-bHUn59oU+-a-8LTw2jzdLeB1G_8F_61HEQ@mail.gmail.com>
The current chrome WebRTC integration tests live in src/chrome/test/functional in the Chromium source repository - webrtc_call.py is the starting point (or was when I went on vacation...) It may be entertaining to check it out! On Thu, Jul 19, 2012 at 11:16 AM, Odin Hørthe Omdal <odinho@opera.com>wrote: > On Wed, 18 Jul 2012 13:13:02 +0200, Harald Alvestrand < > harald@alvestrand.no> wrote: > >> Just testing that the list works for me. And because it's so quiet here! >> > > *crickets* ... > > > > No, it works :P > > So, tests for WebRTC is no straight forward thing to start on. And the > other testsuite mailing lists that have easier tests are not exactly run > down by people contributing and discussing tests either. > > I'm very interested in how people see us testing WebRTC though. I think W3 > can run Python in the common test repo, and for the client side "test" it'd > be very very benificial to use testharness.js. I would've thought we'd need > to build a server that you do setup and teardown via a HTTP interface, and > tell it what to do. > > Looking at the websocket tests may also be helpful, as they're also kinda > lowlevel. I haven't done any of that, I'm merely interested. :-) > > -- > Odin Hørthe Omdal (Velmont/odinho) · Core, Opera Software, > http://opera.com > >
Received on Thursday, 19 July 2012 10:16:49 UTC