QA/Automation/Meetings/121008: Difference between revisions

m
 
(15 intermediate revisions by 5 users not shown)
Line 14: Line 14:


= Last Weeks Action Items =
= Last Weeks Action Items =
* {{done|}} Dave: Followup on bug 773632 to get further feedback on the memory increase
* {{new|}} Henrik: Update project list/goals
* {{new|}} Henrik: Update project list/goals
** Not done yet, due to upcoming changes for our Q4 goals due to B2G


= Highlights =
= Highlights =
*
* 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}}


= Goals Overview =
= Goals Overview =
Line 23: Line 38:


= Blockers =
= Blockers =
* Bug 773116 - Need full ESX cluster set up in SCL3 or PHX for QA Team automation in 2012 Q4
* {{bug|773116}} - Need full ESX cluster set up in SCL3 or PHX for QA Team automation in 2012 Q4
* Bug 777354 - Regression in shutdown time of httpd.js (~6s) when multiple local pages have been opened (feedback from waldo)
* {{bug|777354}} - Regression in shutdown time of httpd.js (~6s) when multiple local pages have been opened (feedback from waldo)
* Bug 758187 - Write a new mozmill test for checking location sharing (feedback from :ndeakin)
* {{bug|758187}} - Write a new mozmill test for checking location sharing (feedback from :ndeakin)


= Issues =
= Issues =
* Bug 774892 - Unable to type in Firefox if it's started with focusmanager.testmode enabled on Linux
* {{bug|774892}} - Unable to type in Firefox if it's started with focusmanager.testmode enabled on Linux
* Bug 702605 - Allow interaction events to be injected into the Event Queue
* {{bug|702605}} - Allow interaction events to be injected into the Event Queue
* Bug 791960 - Rework Mozmill's sleep/waitFor methods to not spin the event loop
* {{bug|791960}} - Rework Mozmill's sleep/waitFor methods to not spin the event loop
* Bug 773632 - High results on mozmill endurance test on Mac 10.7.4_x64 since Jul 5
* {{bug|773632}} - High results on mozmill endurance test on Mac 10.7.4_x64 since Jul 5


= Softvision Updates =
= Softvision Updates =
* Finish working on the last week sprint
* Blocked bugs in [http://scrumbu.gs/t/Auto_Dev/Q4_2012/ http://scrumbu.gs/t/Auto_Dev/Q4_2012/]
** {{Bug|489474}} Write automated tests for user generated video controls
*** Alex is working on the dependency {{Bug|795831}} for the video test files
*** Got feedback for wip patch, will have a final patch after dependency is solved
* Start working on this week sprint
** {{Bug|792394}} - Replace expect with waitFor to ensure the page title matches the underlined text in /testAwesomeBar tests
*** Try to reproduce failure on Mac OS X, no luck so far
* {{Bug|790191}} Mozmill test failure /testAwesomeBar/testGoButton.js | controller.waitForPageLoad(): Timeout waiting for page loaded
** Still a blocker


= Roundtable =
= Roundtable =
* [https://wiki.mozilla.org/Auto-tools/Goals/2012Q4 Q4 Goals update] and how they affect our team goals
* 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


= Presentation / Demo =
= Presentation / Demo =
Line 66: Line 81:


==Action items==
==Action items==
* {{new|}} Henrik: Gather host/port details required by Mozmill tests for new ESX cluster
* {{new|}} Clint: Follow-up with Neil on the geolocation notification
* {{new|}} Henrik: File an IT bug to add himself as the QA contact for Mozmill,and MozBase (after checking with Jeff and Will)
* {{new|}} Henrik: Update project list/goals
canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,747

edits