|
|
| Line 64: |
Line 64: |
| * Default QA for Mozmill / Mozbase? | | * Default QA for Mozmill / Mozbase? |
| * {{Bug|791960}} - Rework Mozmill's sleep/waitFor methods to not spin the event loop - How do we want to proceed? | | * {{Bug|791960}} - Rework Mozmill's sleep/waitFor methods to not spin the event loop - How do we want to proceed? |
| * Experience in our development of the first WebRTC tests
| |
| ** Initial landing of Makefiles should be handled by our own to ensure an as fast as possible landing ({{bug|795367}})
| |
| *** Consider multiple iterations due to try failures
| |
| *** Take into account that no real devices will be available for build bot machines (faked media)
| |
| ** It is hard to write tests for APIs which are changing drastically
| |
| *** Faked media patch landed Tuesday last week (earlier no in-tree tests were possible)
| |
| *** Handling of prefed-off features (tests will have to take the pref into account)
| |
| ** Usage of common modules to ease the writing of tests
| |
| *** Creating a PeerConnection object and establishing the connection is quite complex
| |
| *** Handling of default settings for each test
| |
| ** Test creation
| |
| *** Lots of features have still not been implemented - figured out while coding on tests
| |
| ** Results
| |
| *** Even no tests have been checked in yet, we identified a couple of bugs like {{bug|798323}}, {{bug|798873}}
| |
|
| |
|
| = Presentation / Demo = | | = Presentation / Demo = |