previous mtg | Web QA Home | next mtg

Meeting Details

Please see our public calendar for all upcoming events and meetings.

Our regular team meeting occurs every Thursday @ 9am Pacific

• Vidyo: WebQA (8824)
• IRC: #mozwebqa
• Notes: Archive, Template

Action Items / Takeaways from Last Week

• Takeaways:
• Action Items:
  • Stephen to delegate removing Beta and Aurora environoments on most nodes; leave them only on one
    • Not done -- someone please take this!
  • Marlena to let us know when Scott Barber has responded about performance testing
    • Marlena got an email, need to know budget- this has morphed into a new action item listed below.
  • Matt to add other members of the team to the WebQA Pivotal Tracker, as admins (done)
  • 2nd floor computer lab - find home for qa-selenium7 and the Android devices (tegra boards & ics phones) - stephend/raymond
    • Not done -- on the back-burner
  • Marlena to work with Raymond on setting up the Google Galaxy Nexus phones to the Grid
    • done thanks to Raymond & Dave for helping Marlena
  • Stephen to talk to Chris More/morgamic about getting more up-front involvement/information about re-orgs that affect QA
    • Spoke to him -- it's complicated right now due to their re-org, but visibility is there
  • Stephen to talk to Clint/Tony about Q2 goals, and what we're looking for
    • Clint not yet, Tony in same boat as us, will write up goals and submit to Bob
    • We submitted goals in old format to Bob last quarter and he said it was fine, but mtg yesterday he said it wasn't fine- so it's not clear. We'll do ones we're sure about and make sure that's the right direction.
  • Stephen to talk to Raymond to get Pivotal tasks for remaining Mozilla.com automation needs
    • Not done

Discussion Items / Updates

• Q2 goals
  • Official goals are here: https://intranet.mozilla.org/2012Q2Goals
  • Brainstorm them here: https://mozqa.etherpad.mozilla.org/mozwebqa-Q22012-Goals
    • WebDev's Q2 draft goals: https://etherpad.mozilla.org/webdev-q2-2012
    • Start filling out https://wiki.mozilla.org/QA/Execution/Web_Testin/Goals/2012/Q2
    • Stephend did look at goals, need to add airmozilla & engagement projects [list has been updated]. Apps will be added also. Want to give what we have to Bob and get his reaction before putting more. Can meet if we want to discuss more- ideally after Bob looks at what we have. We're aiming to go for cautious rather than ambitious. Bob doesn't want normal work as a goal, he also doesn't want goals you don't think you'll meet.
• Jenkins Backup
  • The basic restore procedure has been documented here https://wiki.mozilla.org/QA/Execution/Web_Testing/Automation/Selenium_Grid#Jenkins_Backup
    • Dave is contributing some ideas to the awkward step of restoring the plugins.
    • Zac: A couple of steps might change to make it more robust. We now have a daily backup and steps for restoring Jenkins. Task completed!
• Project coverage
  • Selenium Conf participants - if you need coverage for a project during the conference let the team know.
• Automation project coverage discussion:
  • Right now the onus of fixing a project is on the project lead, even if they are in a diff time zone. Need to balance this out in a way similar to the engagement projects. Don't want a prescriptive thing, but need a method to provide coverage by those available when project leads are offline. Reason: there was a flightdeck push with a failure. It was a prob relating to code and they wanted to know about the flightdeck tests and no one was familiar with them. Would like to see some discussions on this.
  • we have a need for people, esp. in Mtn View timezone who can watch & fix failing tests. Lots of coverage in Europe. It seems like on Mtn View side there is so much going on it's hard to consistently keep an eye on the build while planning new tests, going to meetings, etc. A suggestion on the AMO side was having a rotation for someone who only pays attention to the build during certain periods of time. It could allow someone to focus on the builds without having divided attention.
  • This was easier when there were fewer projects. Everyone is having more projects and more meetings.
  • Could encourage devs to really take a look at tests. People like jsocol and other devs are really interested in looking at our tests.
  • Some of our projects it'll require a cultural change, which is a positive direction- sounds like the right path to go down [to have devs help]
  • Devs have offered in the past to help.
  • marlenac: I know I have an action item to talk to addon devs about this. There are probably other opportunities to do this on other projects.

Engagement Project Status

If you've worked on an engagement project in the last week, enter your name, the project name, and time spent in hours (estimated).

• Betafarm - 24 hrs rbillings

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

• Affiliates
  • No release scheduled for this week
• AMO
  • CI for AMO mobile tests...yay!
  • New tests from contributors Pengsu and Victor...yay!
  • Pull request is in the queue for a smarter login...yay!
• Marketplace
• Input
• Jetpack Builder (aka FlightDeck)
• Mozilla.com
  • No release this week
• Mozillians
  • [rel:04/04/2012] scheduled to be released this week
  • hot new UI with responsive design
  • mbrandt: struggling with mozillians, not asking for team coverage, but the team is struggling with quality and it's taking a lot of my focus. Really trying to help them out- but it's taking away from pull requests and other duties. Am sure that there's nothing others can do to help with this.
• Mozilla Reps
  • 0.2 shipped today
• MDN
  • pushed on 04/04
• Socorro
  • Successful Milestone 4 release on 4/4/2012
  • zac: Thanks to alin- did a lot of work on socorro, takes 8 min to run the suite but that is too long, have an etherpad to work on cleaning up tests. Probably do it in the next couple of days.
• SUMO
  • no updates
• MozTrap
  • Yay new name! Yay 1.0 release! blog post about it here has more info.
• Wiki
  • no updates
• REMO
  • stephend: pushed mozilla reps 2.0 this morning, still hoping to find a community person to take over as leader

Community Update

• We discussed quarterly goals Goals etherpad
• We discussed using Pivotal Tracker for community tasks
• Community meeting notes
• We discussed upcoming events like MozCamps, and the possibility of doing them in the US.
• Decided that another QMO meeting is needed as the last one left people in two minds: either that we should keep QMO and make it better or that we should get rid of it.

Time off / Out-of-office

• Stephen to be in London from 14-22
• Raymond to be in London from 13-22
• Zac working remotely 11-13
• Bebe 12 - 17 April PTO
• Alin 17 - 18 April PTO
• April 16 is a National Holiday in Romania

Takeaways and Action Items

• Takeaways:

• Action Items:
  • Stephen to delegate removing Beta and Aurora environoments on most nodes; leave them only on one
    • Not done -- someone please take this!
  • marlenac will send info to stephend from Scott Barber, but doesn't have exact prices, know it'll take more than a day
  • 2nd floor computer lab - find home for qa-selenium7 and the Android devices (tegra boards & ics phones) - stephend/raymond
    • Not done -- on the back-burner
  • Stephen to talk to Raymond to get Pivotal tasks for remaining Mozilla.com automation needs
    • Not done
  • retornam needs to list what needs to be done for [mozilla.com] and put items into Pivotal Tracker or send an email to get what is needed.
  • Add goals for any upcoming projects if you know about ones not on the list. Can update goals list directly & then tell stephend.
  • Help needed: team could help complete the last 1% of automation for Mozillians.
  • If team sees Tobbi online, give him support for working on Mozillians

• Next owner: retornam
• Next week's meeting notes: mbrandt