View source for QA/Execution/Web Testing/Meetings/2011-12-01

<small>[https://wiki.mozilla.org/QA/Execution/Web_Testing/Meetings/2011 previous mtg] | [https://wiki.mozilla.org/QA/Execution/Web_Testing QA/Execution/Web Testing/ Web QA Home] | [https://wiki.mozilla.org/QA/Execution/Web_Testing/Meetings/2011-11-24 next mtg] </small> 

Every Thursday @ 9am PDT/PST 

Dial-in Information: 

650-903-0800 or 650-215-1282 x92 Conf# 303 (US/INTL)<br> 1-800-707-2533 (pin 369) Conf# 303 (US) 

= Action Items / Takeaways from Last Week  =
*Project leads will update the Jenkins jobs with the new settings 
*Continue discussion about versions in Python package dependencies on mailing list until next week 
*Continue the discussion about markers on the mailing list until the group takes a decision 
**Should we use @destructive / @nondestructive marks?
**For AMO we will use temporary marks until the final decision
*Project leads decide if you want to use branches for running test on different environments [production/development]
*Raymond to ping Berada from Google(should we use Hub or Jenkins)
**Didn't get a response.
*Like to have someone answer https://bugzilla.mozilla.org/show_bug.cgi?id=702605#c2, so we can try to move it right along - stephend
**Comment the blocking bug, make sure it will be handled on the triage meeting 
**[Stephen] add more info to clarify what BHAG means
*BHAGS -- what do we want WebQA to be/look like/do, in 2012?:
**http://www.slideshare.net/wadekar/b-h-a-g1
**http://www.sitepoint.com/how-to-create-a-big-hairy-audacious-goal/
***Brainstorm notes, here: https://mozqa.etherpad.mozilla.org/Web-QA-BHAGs-2012
****Add your ideas to the brainstorm notes

= Discussion Items / Updates  =
*Pass over notes from Google Bite project team conversations - mbrandt

= Project Status / goals for next week (keep it brief)  =

*Affiliates 
** Slipping this weeks release to next Wednesday. Waiting for strings to land. 
** Creating an automation plan with the team. Currently automation is near zero on both webdev and webqa's side.
*AMO
**App Developer preview is scheduled to go live on 12/8.
**AMO devs spent time QAing the site and we found some good issues.
**Webdriver branch is ready to be merged aiming for it to be completed by next QA Meeting
**Production tags have been added to the webdriver branch
**Demo of webdriver tests will take place in apps meeting on December 12, will be repeated in the WebQA meeting on Dec. 15
*Input
**Webdev is working through the recent spate of tracebacks and is running our Se tests.
*Jetpack Builder (aka FlightDeck)
*Mozilla.com
** ship [http://bit.ly/tqm7ZX 4.9] milestone
*Mozillians
** Super hot and active project
** Automation is really helping get releases out.
*MDN
** shipped [https://bugzilla.mozilla.org/show_bug.cgi?id=706255 1.6.1] on Tuesday. Working on [http://bit.ly/rSmHki 1.7]
*Socorro 
** (Zac) I have spent a bit of time refactoring code and bringing it up to mozwebqa's high standards. Thanks to Alin and other Ro team for reviewing the pulls for me
** Socorro onsite next week
*SUMO 
** [http://moxie.jamessocol.com/bugstats/sumo/2011-11-29 11/29 release] went out
** [http://moxie.jamessocol.com/bugstats/sumo/2011-12-06 12/6 release] in process
** #3 SUMO Questions day on 12/1 - these have been going really well
** Building out Volunteer Guidelines with mluna
*Case Conductor
** Manual test cases testrun built out

= Time off / Out-of-office  =
* mbrandt in San Francisco office next week for Socorro onsite - Tuesday and Wednesday (12/6 & 12/7)

= Takeaways and Action Items  =

*Next meeting: https://wiki.mozilla.org/QA/Execution/Web_Testing/Meetings/2011-12-08
*Chair: Rebecca
*Carryover:  Update jenkins with pycache settings (??)
*Everyone involved in automation re-read the thread and comments for:
**Production tags
**python package dependencies
*Automation Leads should play with py.test2.2 with negation
*Raymond will move the android vm to qa-selenium and will post an email to selenium *developers group and cross-post to mozwebqa