QA/Execution/Web Testing/WorkWeek/2011/06: Difference between revisions
< QA | Execution | Web Testing | WorkWeek/2011
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 73: | Line 73: | ||
*11:10am - 12pm: Git - use, misuse, and process | *11:10am - 12pm: Git - use, misuse, and process | ||
== Friday == | == Friday == | ||
*10am - 10:30am: Automating load & performance testing in the CI and Se2 | |||
*10:35am - 11:05am: Our mobile automation story - spikes and goals |
Revision as of 20:33, 21 June 2011
Overview
Date: | June 20th-25, 2011 |
Attendees: | Krupa, Marlena, Raymond, Dave, David, Rebecca, Matt, Stephen |
Meetings
Room:
# Mountain View, Get To Da Choppa
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
Meeting | Schedule | Topic |
Planning | Monday, June 20th | decide on an agenda for the week |
Sessions | 10-11am, 1:30-2:30pm | |
Sessions | 10-12am, 30 minute sessions | |
Sessions | 10-12am, 30 minute sessions |
Monday
Reserved for planning out the work week. Prior to the work week we used a scrumpad to capture a few ideas. http://mozqa.sync.in/mozwebqa-work-week6-20-11
Tuesday
- 10am - 11am: Q3 Goal Setting, hosted by Stephen
- 1:30pm - 2:30pm: Discuss optimizing our interactions with Waverly.
Wednesday
- 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
Thursday
- 10am - 10:30am: Upgrading our Automation env - CI coverage, adding nightlies, more browsers (Chrome, IE, Opera, Safari)
- 10:35am - 11:05am: Gamr talk hosted by David
- 11:10am - 12pm: Git - use, misuse, and process
Friday
- 10am - 10:30am: Automating load & performance testing in the CI and Se2
- 10:35am - 11:05am: Our mobile automation story - spikes and goals