Changes between Version 2 and Version 3 of 104hackathon/webrtc

Mar 21, 2019, 8:11:42 AM (6 months ago)



  • 104hackathon/webrtc

    v2 v3  
    1 == Info is coming ==
     1== WebRTC Interop (KITE) and Compliance (WPT) testing ==
    3 Interesting links:
     3* Goals
     4  * Fix browsers to support Simulcast 1.0 better,
     5  * thus passing more compliance tests,
     6  * and interoperate better with other browser, and here specifically with SFUs
     8* Champion(s)
     9  * Harald Alvestrand <harald at>,
     10  * "Dr Alex" Gouaillard <alex.gouaillard at>
     12* Browser vendors with Staff on site to fix on-the-fly
     13  * Google (Harlad, ...)
     14  * Apple (Youenn F.)
     15  * Mozilla (Nils O., ...)
     16  * Microsoft (Nikita)
     18* SFU Vendors with staff on site to fix on-the-fly
     19  * Janus (lorenzo)
     20  * Jitsi (emil, boris, or saul)
     21  * meedoze (Sergio)
     22  * others ?
     24* Project(s)
     25  * Add more tests to the Web Platform Tests suite for webrtc 1.0 Simulcast API Compliance
     26  * Add more tests to the KITE webrtc 1.0 simulcast interop test suite
     27  * Specifically Test browser interoperability with SFUs and MCUs in Simulcast Mode
     28  * FIx browsers, rince, repeat
     29  * fix SFUs, rince repeat
     31Specifically for this event, we created a GitHub repository with two automated kite interoperability tests.
     33One test is a "typical" SFU test: KITE-Janus-Test is provided, which can be easily adapted to test any SFU, and should be the starting point for SFU developers wanting to automatically test against all the browser configuration CoSMo will provide for testing that week end.
     35One test, "KITE-Simulcast-Test", was specifically developed to test browser compliance. An app which sends simulcast to a special SFU based on meedoze, and receives back a given stream back depending on interaction with the UI is provided. It allows to test in loopback mode with a single browser (since simulcast is only sender side anyway), and all stream selection logic is made through UI button which makes it easily instrumented through KITE. The different simulcast features are not tested directly but indirectly (if I can select and receive a stream at a specific configuration it means the SFU receives them well and can differentiate them). The medooze simulcast loopback page, used by e.g. Apple for testing  is hosted here:
     37We plan to extend and complete this document over the hackathon with each and every new tests the SFU vendors will propose, or modified browsers the browsers vendor will provide:
     40Interesting links and prerequisite reading:
    541* KITE:
    642* Web Platform Tests: