QA/Execution/Web Testing/WorkWeek/2011/06

From MozillaWiki
Jump to: navigation, search


Date: June 20th-25, 2011
Attendees: Krupa, Marlena, Raymond, Dave H., Vishal, David B., Rebecca, Matt B., Stephen, Matt E.
What: WebQA Workweek UnCon

Meeting Space


# Mountain View, Get To Da Choppa

Vidyo & Dial in (on request):

# 650-903-0800 or 650-215-1282 x92 Conf# 303 (US/INTL) 
# 1-800-707-2533 (pin 245) Conf# 245 (US)
# if you desire to dial in please let us know, by default we won't be using the phone or vidyo


Schedule Meeting Topic
Monday, 6.20.11 Planning
decide on an agenda for the week
Tuesday, 10-11am & 1:30-2:30pm
Sessions topics
Wednsday, 10-12am
Sessions topics
Thursday, 10-12am
Sessions topics
Friday, 10-12am
Sessions topics


Reserved for planning out the work week. Prior to the work week we used a scrumpad to capture a few ideas.


  • 10am - 11am: Q3 Goal Setting, hosted by Stephen
  • 1:30pm - 2:30pm: Discuss optimizing our interactions with Waverly.


  • 10am - 10:30am: Tools & planning for load testing - JMeter, etc
  • 10:35am - 11:05am: Improving our interactions with the community - better test days, etc
  • 11:10am - 11:40am: Increasing our interviewing skillz - what do we need to be more successful
  • 11:40 - 12pm: Dave's Automating Pacman prezo


  • 10am - 11am: Git - use, misuse, and process
  • 11:00am - 11:30am: Gamr talk hosted by David
  • 11:30am - 12pm: Dave Hunt's Helicopter talk


  • 10am - 10:30am: Automating load & performance testing in the CI and Se2
  • 10:35am - 11:05am: Our mobile automation story - spikes and goals

Action Items

Items that the group felt would merit followup on

Tuesday's Notes

[full meeting minutes]


  • Krupa, Rebecca, and Matt to work on getting a checklist for uTest projects things we need their testers to adhere to, and whether they file directly in Bugzilla, etc.


  • Assign one tester to:
    • AMO
    • Socorro
  • Process outline for utilizing Waverly
    • daily standups
    • Office hours
    • Point them to the Guidelines
    • WebQA point person for automation needs in Tuesday 8am
    • Get Matt the point person and ask for a direct meeting invite for that contact person
  • Team to try using GitHub issues, talk to someone who’s using it
    • Raymond said to ask Dietrich

Wednesday's Notes

[full meeting minutes]

Load Testing

  • Stephen to talk to Justin Lazarao about the load-testing cluster
  • Stephen to talk to James Bonacci
  • Investigate multi-node JMeter?
  • Can trigger JMeter from a simple ant script in CI

Thursday's Notes

[full meeting minutes]


  • Stephen & Matt B. to create a visual diagram of the git clone/branch/merge/review process.
  • Team members can consider sitting through test reviews with one another to learn from one another.
  • Use Pivitol Tracker
  • Stephen to talk to Dave Dash and see about co-developing a fuzzing tool a la PowerFuzzer


Friday's Notes

[full meeting minutes]

Our Automation Env

  • remove the blocker dependency, get Se2 running
  • finding a project that we can try out BrowserMob with, and do a trial run
  • Need a real strategy for the environments that we need to support
    • we should be using Webtrends+anticipated users’ platforms (we want to support other platforms for conversion)
  • Grid 2 is again a dependency/blocker
  • Nightly, Aurora, Beta, RC FF
    • need to explore an automated way to upgrade Nightly & Aurora
    • doing this cleanly would be a nice contribution to the community
    • Ensure Se supports Nightly & Aurora envs
  • Latest Chrome, Safari (limited/non-existent Selenium support at present), Opera (you’re welcome Esteban)
  • Linux, OSX, Win XP, Vista?,Win 7
  • Consider Android, iPad, iPhone envs
  • explore targeting specific platforms with Se (Firefox x on Windows x, etc.) -- granularity with environments for test runs
  • Look at resurrecting an Ubuntu Linux environment for Selenium
  • What about Mac OS X Lion support? Do we want to maintain dual environments?
    • Which testruns run in Snow Leopard, which run in Lion? Do we want a blend of both?
    • Modify the current environment string to differentiate between the two versions