Revision as of 16:52, 8 December 2011

Every Thursday @ 9am PDT/PST

Dial-in Information:

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

Action Items / Takeaways from Last Week

Carryover: Update jenkins with pycache settings (??)
- Marlena has some questions about this. Link to the original action item.
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
Project leads will update the Jenkins jobs with the new settings to clear the workspace
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
Update from Raymond on mobile-testing setup/infra
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
Socorro test day tomorrow. Please sign up and help.

We should add Firefox 8 support to our Grid
We need to look into a replacement for Gmail, for outbound failure emails (due to rate-limiting)
Selenium 2.15.0 is almost ready; (when) do we want it, given we just upgraded to 2.14.0?
QA-Selenium2 - Do we still want this machine as part of our grid?

Affiliates
- Test plan is moving towards a rapid release goal
- BrowserID will be introduced to staging early next week

AMO
- webdriver is merged in (working on fixes for remaining failing tests)
- modifying our BrowserID page object for general consumption
- production job for jenkins

Input
- moved to Webdriver (yay! thx davehunt & community!)
- introducing a production run using nondestructive as the py.test marker

SUMO
- 12/6 release goes out tomorrow, delay from issues
- 12/13 release in process
- #3 SUMO Questions day on 12/1 - went well
- Editing Volunteer Guidelines with mluna
Case Conductor
- no news is good news

@@ Line 9: / Line 9: @@
 = Action Items / Takeaways from Last Week  =
 *Carryover:  Update jenkins with pycache settings (??)
+**Marlena has some questions about this.  Link to the [https://wiki.mozilla.org/QA/Execution/Web_Testing/Meetings/2011-11-17 original action item.]
 *Everyone involved in automation re-read the thread and comments for:
 **Production tags