Auto-tools/Automation Development/Meetings/130422: Difference between revisions

Auto-tools/Automation Development/Meetings/130422 (view source)

1,401 bytes added , 22 April 2013

canmove, Confirmed users, Bureaucrats and Sysops emeriti

4,714

edits

@@ Line 21: / Line 21: @@
 = Roundtable =
-* TBD
+* How to implement Metro tests, as it looks like we will majorly be blocked on missing event actions in Mozmill. Should we consider Marionette instead?
+* [henrik] Really awful proposal - Shall we drop work on Mozmill and start with Marionette for tests?
+** pro arguments
+** Only a few tests are using complex mouse events like drag&drop, and we do not support touch events at all in Mozmill
+** Marionette gets injected in the system process as extra library and doesn't have to be build as extension, which even is not supported for all products (e.g native web apps don't allow add-ons to be installed)
+** W3C compliance by using the web driver protocol (http://www.w3.org/TR/2013/WD-webdriver-20130117/)
+** Tests can even be run on mobile (Android, B2G)
+** Tests can be written in different languages (e.g. Python) and allow us to write system integration tests because we are not in the browser scope anymore
+** Support for (remote) debugging
+** Changes of getting a much broader community around desktop testing
+* contra
+** First we have to figure out how to inject Marionette in default Firefox builds (see bug 836253)
+** Existing Mozmill tests would have to be transformed or we keep and run them in parallel (some tests would even be not necessary anymore due to new browser chrome tests)
+** Where would we publish our test results? Our dashboard would need a rewrite or we can directly push to tbpl
 = Goals Overview =