View source for QA/Browser Technologies/JulyWorkWeek2011

= Overview  =

{|
|-
| style="width: 15%" | 
| style="width: 85%" | 
|- valign="top"
| '''Date:''' 
| June 20th-25, 2011
|- valign="top"
| '''Attendees:''' 
| Tbd
|- valign="top"
| '''What:''' 
| Browser Technologies QA Workweek
|}

= Meeting Space =

Offsite: Half moon bay
Onsite: Zombocom
 
= Agenda  =

{| class="fullwidth-table" style="width: 939px; height: 139px;"
|-
| style="background: rgb(239, 239, 239); width: 25%; font-weight: bold" | Schedule 
| style="background: rgb(239, 239, 239); width: 25%" | '''Meeting''' 
| style="background: rgb(239, 239, 239); width: 50%" | '''Topic'''
|- valign="top"
| Monday
| Planning<br> 
| [[#Monday|topics'''<br>''']]
|- valign="top"
| Tuesday<br> 
| Offsite
| [[#Tuesday|topics'''<br>''']]
|- valign="top"
| Wednsday, morning<br> 
| Offsite 
| [[#Wednesday|topics'''<br>''']]
|- valign="top"
| Thursday<br> 
| Sessions 
| [[#Thursday|topics]]'''<br>'''
|- valign="top"
| Friday<br> 
| None Scheduled 
| [[#Friday|topics]]'''<br>'''
|}

== Monday  ==

Breakdown for the week.  Start a idea scrumpad, lay out the expectations
http://mozqa.sync.in/bt-work-week-july-2011

== Tuesday  ==

*8am: Mobile Waverley Call [https://wiki.mozilla.org/QA/Fennec/Waverley/2011-07-19 (Notes)]
*9am : Large Group Introduction & Discussions
*10am: Mobile Discussion / Services Work Session
*11am: Mobile Discussion / Services Work Session
*12pm - 12:45pm: Lunch
*1pm: Mobile Discussion / Services Work Session
*2pm: Services Discussion / Mobile Work Session
*3pm: Services Discussion / Mobile Work Session
*4pm: Services Discussion / Mobile Work Session
*5pm: Half Moon Bay fun, Group Picture

== Wednesday  ==

*9am: Continued Discussions
*10am: Continued Discussions
*11am: Pack up, clean, head out
*12pm: Lunch someplace, head back to office

== Thursday ==

*12pm: Lunch for Aakash
*2pm: BT Project demo,  (video recorded, 10 Fwd)

== Friday  ==

*10am - 10:30am: Automating load &amp; 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  ==

[[https://docs.google.com/document/d/1iRjaQlm24khgPoAJpSMifCTae0Fd2-524DGWcVODSOA/edit?hl=en_US full meeting minutes]] 

=== uTest  ===

*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.

=== Waverly ===

*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  ==

[[https://docs.google.com/document/d/1xIp1-6ix6pi4EayOC1eZ-j8ShyqNHj2_nwdrUyK8J4E/edit?hl=en_US 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  ==

[[https://docs.google.com/document/d/1wDq70o6bmDWOcLFZoD1J7BWsw5rmls9mM3InNHCqtW8/edit?hl=en_US full meeting minutes]]

=== Git  ===

*Stephen &amp; 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

=== Garmr  ===

*pip installable 
*https://github.com/AutomatedTester/Garmr 
*meant to check security items on our security check list - https://wiki.mozilla.org/WebAppSec/Secure_Coding_QA_Checklist

== Friday's Notes<br>  ==

[[https://docs.google.com/document/d/1c4Rk4DjoTUjnUUBhRnNfUQqOWZezHcequm6lVXXgX6Q/edit?hl=en_US 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 &amp; Aurora 
**doing this cleanly would be a nice contribution to the community
**Ensure Se supports Nightly &amp; 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