Revision as of 12:15, 5 January 2012

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

Q1 goals; for reference, the WebQA BHAGs we started to brainstorm
- We should also keep the list of tentative projects + current projects' Q1 goals in mind
Work week (when, where?)
- Mountain View or San Francisco, February 20th - 24th
We should add Firefox 9 support to moz-grid-config, and be running most jobs on at least that (and finally get around to setting and using the config in Jenkins for this purpose)
Selenium 2.16.0 is out; I think we want to take a look at it
Upcoming events:
- Selenium Camp in Kiev (25th February) http://seleniumcamp.com/
- Selenium Conference in London (16-18 April) http://www.seleniumconf.org/
We need to monitor the Selenium nodes
- Currently only 5 running (2 Mac, 2 VMs, 1 Android)
- Less nodes means slower/failing testruns.
- Starting/restarting nodes takes very little time.

Affiliates
- Moved en-US/ now uses BrowserID
- Technical debt: we have zero automation on this project
  - https://github.com/mozilla/affiliates-tests and https://github.com/mozilla/Affiliates-Tests/pull/6 ? ^^^

AMO
- work through code reviews form contributors
- marketplace tests in their own repo

Input
- Created a production Jenkins job
- Q1 the project will likely see active development again

@@ Line 20: / Line 20: @@
 ** Selenium Camp in Kiev (25th February) http://seleniumcamp.com/
 ** Selenium Conference in London (16-18 April) http://www.seleniumconf.org/
+* We need to monitor the Selenium nodes
+** Currently only 5 running (2 Mac, 2 VMs, 1 Android)
+** Less nodes means slower/failing testruns.
+** Starting/restarting nodes takes very little time.
 = Project Status / goals for next week (keep it brief)  =