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

 
(5 intermediate revisions by 3 users not shown)
Line 34: Line 34:
*** Marionette has more active contributors than Mozmill
*** Marionette has more active contributors than Mozmill
** contra
** contra
*** First we have to figure out how to inject Marionette in default Firefox builds (see bug 836253)
*** 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)
*** 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
*** Where would we publish our test results? Our dashboard would need a rewrite or we can directly push to tbpl
**** Probably TBPL2 (Tree Herder)
**** Probably TBPL2 (Tree Herder)
* Mozmill 2.0 triage part 2


= Goals Overview =
= Goals Overview =
Line 53: Line 54:
** First results submissions to DataZilla b2g project
** First results submissions to DataZilla b2g project
** Setting up jenkins on my test PC
** Setting up jenkins on my test PC
** Tests to be submitted for review soon
** Tests submitted for review
** Once the tests are in the gaia-ui repo and more results are on DataZilla, I will give a talk about them in our meeting, write a blog post, etc.
** Once the tests are in the gaia-ui repo and more results are on DataZilla, I will give a talk about them in our meeting, write a blog post, etc.


Line 96: Line 97:
** {{bug|763461}} - Mozmill tests for cut-off elements should not report failure for scrollable direction  
** {{bug|763461}} - Mozmill tests for cut-off elements should not report failure for scrollable direction  
** {{bug|763470}} - False positive test for cut-off elements for advanced pane tabs
** {{bug|763470}} - False positive test for cut-off elements for advanced pane tabs
** {{bug|764640}} - Mozmill returns PASS/SKIP/FAIL == 0 for test_assertions.js
** {{bug|860670}} - mozmill.utils.getWindowByType fails for type: Addons:Blocklist - Fails with "Window has been found."
** {{bug|860662}} - controller.select() fails to select the option by value


{| border="1" cellpadding="2" align="center"
{| border="1" cellpadding="2" align="center"
Line 122: Line 126:
|-
|-
| {{bug|860665}} || Feedback || Henrik/Dave || controller.waitForPageLoad() fails when working with Private Browsing windows.
| {{bug|860665}} || Feedback || Henrik/Dave || controller.waitForPageLoad() fails when working with Private Browsing windows.
|-
| {{bug|827276}} || Needinfo || Alex Keybl || Test failure 'Check for updates has been completed' in /restartTests/testSoftwareUpdateAutoProxy/test2.js
|}
|}


Line 157: Line 163:


==Action items==
==Action items==
* {{new|}} %name%: %task%
* {{prev|}} Henrik - Update the goals page
* {{prev|}} Anthony: Ensure any Metro tests are suitably tagged with in-testsuite?
* {{new|}} Andreea: File bug about the broken elementslib handling with elements
canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,714

edits