MozillaWiki

QA/StaffMeetings/QA-Staff-02-01-2012: Difference between revisions

Page Discussion

QA/StaffMeetings/QA-Staff-02-01-2012 (view source)

Revision as of 00:05, 4 February 2012

9,908 bytes added ,  4 February 2012
→‎QA Org Items
 
(46 intermediate revisions by 15 users not shown)
Line 14: Line 14:
== QA Org Items ==
== QA Org Items ==
* New Hires & Interviews
* New Hires & Interviews
** item
** three new community members currently onboarding to work with B2G on Emulator (hopefully test automation):
***Vlad Maniak  (irc vmaniac, email: unchiu_maniac@yahoo.com)
***Leandra Largo LMLARGO@fortlewis.edu
***Rafael Tso RLTSO@fortlewis.edu
* Upcoming Events
* Upcoming Events
** item
** item
* PTOs
* PTOs
**  
** marcia taking some time off during week of February 27
** mbrandt taking birthday pto on February 6th


== Discussion Items  ==
== Discussion Items  ==


* Several items from the last meeting were not discussed: See https://wiki.mozilla.org/QA/StaffMeetings/QA-Staff-01-25-2012#Discussion_Items
* [https://wiki.mozilla.org/QA/StaffMeetings/QA-Staff-01-25-2012#Discussion_Items Several items] from the last meeting were not discussed: See
* [https://wiki.mozilla.org/Privacy/Friends#Functional_Areas Mozilla Privacy Lead] role needs to be filled:  - any volunteers?
* [https://wiki.mozilla.org/Privacy/Friends#Functional_Areas Mozilla Privacy Lead] role needs to be filled:  - any volunteers?
* No more All Hands meetings?
* No more All Hands meetings?
* How does QA get more connected to and represented at some of the works weeks that are going on?
* How does QA get more connected to and represented at some of the work weeks that are going on?
** Snappy
** Snappy
** Firefox
** Firefox
* (DavidB) Check out [http://powerball.theautomatedtester.co.uk powerball] and try a simple [http://people.mozilla.org/~jmaher/power-ball-10.xpi addon] to earn points for bugs you file and comment on.


== QA Team Updates  ==
== QA Team Updates  ==


=== Desktop Firefox (Juan)  ===
=== Desktop Firefox (Juan)  ===
* Fx.Next
* Fx.Next
** Firefox 11 (ashughes)
** Firefox 11 (ashughes)
Line 40: Line 46:
** Firefox 13 (ashughes)
** Firefox 13 (ashughes)
*** moving to Nightly Tuesday
*** moving to Nightly Tuesday
* Crash Investigation
* Stability/Crash Investigation
** [https://wiki.mozilla.org/Releases/Firefox_10/RRRT RRRT page]  created for Firefox 10 release
** [https://wiki.mozilla.org/Releases/Firefox_10/RRRT RRRT page]  created for Firefox 10 release
** [https://wiki.mozilla.org/Platform/2012-01-31#Stability_Report Stability Report] for this week
** [https://wiki.mozilla.org/Platform/2012-01-31#Stability_Report Stability Report] for this week
** Will most likely do a CrashKill Brown Bag in the next few weeks.
** CrashKill team working on an idea for a crash newsletter
* Maintenance and Security (ashughes)
* Maintenance and Security (ashughes)
** Firefox 3.6.*
** Firefox 3.6.*
Line 49: Line 57:
*** Released 10.0 (first ESR), 10.1 timeline TBD
*** Released 10.0 (first ESR), 10.1 timeline TBD
** Sign up for the new [https://wiki.mozilla.org/QA/Desktop_Firefox#Security_Triage_Team Security Triage team] if you want to help verify security fixes in the Beta releases
** Sign up for the new [https://wiki.mozilla.org/QA/Desktop_Firefox#Security_Triage_Team Security Triage team] if you want to help verify security fixes in the Beta releases
* Apps - Desktop (jsmith)
** Mobile World Congress desktop/mobile testing - can the apps run?
*** [https://mozqa.etherpad.mozilla.org/59 Test Plan] established in line with demo
*** Demo date: February 23rd, 2012
** Initiated Apps Dashboard plan construction (KPIs, Goals, Data Sources)


=== Browser Technologies (Tony)  ===
=== Browser Technologies (Tony)  ===
*(Please fix this section of the template!)
*(Please fix this section of the template!)
** Anyone can edit, feel free!
** Anyone can edit, feel free!
** Yay! where is the template?


*Issues
*Issues
**  
**
*Fennec (AaronMT/KBrosnan)  
*Fennec (AaronMT/KBrosnan)  
**  
** Preparing for Firefox 11 beta 2 release
** Wrapping up test plans for features
** assisting with Graphics testing GLlayers/Gralloc
** Sync testing
** Beta blocking bug verification
** Crash Report:
** Crash Report:
*** Skia fix in 1/31/2012 (top crash); should be in today's build.
*** Skia fix in 1/31/2012 (top crash); should be in today's build.
Line 64: Line 82:
*** Locale Testing (TBD)
*** Locale Testing (TBD)
*Sync (Tracy)
*Sync (Tracy)
**  
** Daily sync triage now for android
** focus is on dataloss testing, large profiles, and bug verifications for beta
*Test pilot (tracy)
*Test pilot (tracy)
**  
** nothing new
*Sync Server (jbonacci/jrgm)
*Sync Server (jbonacci/jrgm)
**Change/Maintenance Windows
**Change/Maintenance Windows
Line 72: Line 91:
***https://intranet.mozilla.org/Services/Ops/ChangeWindow_20120125
***https://intranet.mozilla.org/Services/Ops/ChangeWindow_20120125
***https://intranet.mozilla.org/Services/Ops/ChangeWindow_20120126
***https://intranet.mozilla.org/Services/Ops/ChangeWindow_20120126
***https://intranet.mozilla.org/Services/Ops/ChangeWindow_20120130  
***https://intranet.mozilla.org/Services/Ops/ChangeWindow_20120130
***https://intranet.mozilla.org/Services/Ops/ChangeWindow_20120205
**Focus
**Focus
***Upcoming Change/Maintenance windows: Sanity testing of Prod, as needed
***Upcoming Change/Maintenance windows: Sanity testing of Prod, as needed
***Upcoming Deployments: Stage and Prod testing, as needed  
***Upcoming Deployments: Stage and Prod testing, as needed  
*BrowserID (jbonacci/jrgm)
*BrowserID (jbonacci/jrgm)
**Current Release
**Current Release: Train 19: Bug 719243 - QA and deploy BrowserID train-2012.01.18 to production
***Train 19: Bug 719243 - QA and deploy BrowserID train-2012.01.18 to production
***This train has been signed off
****This train will be completed by mid-day tomorrow (Wednesday)
**Upcoming Release: Train 20: Bug 723755 - QA and deploy BrowserID train-2012.02.02 to production
****Focus right now is on load test debug and testing support for primaries
**https://intranet.mozilla.org/Services/Ops/ChangeWindow_20120201
****Push to Production is schedule for Wednesday afternoon, after which time QA will verify primary support.
***Focus for this release will be on continued test of primary support and initial support for localization
**Upcoming Release
***First-round language support: en-US and about 39 others (!)
***Train 20
****Focus for this release will be on continued test of primary support and initial support for localization
****First-round language support: en-US, and others TBD
**Student to help QA this Semester
**Student to help QA this Semester
***Zak Valteau from Fort Lewis College in Co will be working with as as part of his project requirements for his Open Source Development class.
***Zak Valteau from Fort Lewis College in CO will be working with us as part of his project requirements for his Open Source Development class.
*Jetpack(?)
*Jetpack(?)
**  
**  
Line 95: Line 112:
** 2nd Draft of UI Designs are in
** 2nd Draft of UI Designs are in
** Pancake Blog Out
** Pancake Blog Out
*B2G/WebAPIs (jhammink)
**now have working bug triage etherpad https://etherpad.mozilla.org/B2G-Bug-Triage-1-31 updating weekly
**Boot to Gecko Landing page on MDN: https://developer.mozilla.org/en/Mozilla/Boot_to_Gecko
**Use-Cases/test cases for MWC demo; exploratory/manual testing in progress
**Onboarding 3 new community members
**begining automation telephony toward QEMU


=== WebQA (Stephen)  ===
=== WebQA (Stephen)  ===
* Affiliates
** [http://www.openprobe.blogspot.com/ Rajeev Bharshetty] is the new community QA Lead on the project
** Successful release on 02/01; push [[bug 722478]]
* AMO
* AMO
**[http://cl.ly/3M040y3A3N2D1o3n262E AMO 6.4.0] is going live 02/03.
**Paypal test is merged
**Paypal test is merged
**MPL2 License is merged
**MPL2 License is merged
Line 104: Line 131:
** Careers is on hold from one bug, release TBD
** Careers is on hold from one bug, release TBD
* Input
* Input
**
** Hand-off meeting, Zac Campbell is the new QA Lead on the project
** Project is still in maintenance mode
** Test automation still seeing trouble due to staging hardware, [[bug 664318]]
** TellUsMore project is taking precedence over Input at the moment
* Mozilla.com
* Mozilla.com
**
** shipped Firefox 10 website updates
* Mozillians
** The team is working through hardware/env issues with IT to get a stable dev environment.
* MDN
* MDN
**
** shipped 2.2 this week
* Socorro
* Socorro
**
** Successful 2.4.1 release; push [[bug 723185]]
*SUMO
*SUMO
**[http://moxie.jamessocol.com/bugstats/sumo/2012-01-31 1/31] release went out - users are at 25% for Elastic search
**[http://moxie.jamessocol.com/bugstats/sumo/2012-01-31 1/31] release went out - users are at 25% for Elastic search
Line 129: Line 161:
** Friday, February 3rd: [https://etherpad.mozilla.org/testday-20120203 Firefox 11b1] (ashughes)
** Friday, February 3rd: [https://etherpad.mozilla.org/testday-20120203 Firefox 11b1] (ashughes)
** Friday, February 10th: OPEN, who wants to take it? contact ashughes
** Friday, February 10th: OPEN, who wants to take it? contact ashughes
** Friday, February 17th: Test day for Open Web Apps Mobile World Congress Preparation - Open to take?
* Video Work
* Video Work
**  
**  
Line 150: Line 183:
=== QA Automation Service (Henrik, David)  ===
=== QA Automation Service (Henrik, David)  ===
* General
* General
**
** Selenium 2.18 has been released
** [https://addons.mozilla.org/firefox/addon/memchaser/ MemChaser 0.1.1] has been released (blog post will follow)
** [https://addons.mozilla.org/en-US/firefox/addon/mozmill-crowd/ Mozmill Crowd 0.1.5] has been released
*Mozmill
*Mozmill
**
** Mozmill 1.5.8 has been released
** Mozmill 1.5.9 is waiting for a released


====Project updates====
====Project updates====
; Prototype of a Fennec Driver (DavidB)
; DTC
*
* Henrik has found a big bug in JSBridge in Mozmill and bisected Python for a fix. Bug now with A*Team


; New Members and Mentors Pages
; On-Demand system for release Builds (Geo)
*
* Proof of Concept system staged in MV
 
* Modifications in progress for administrative scripts to allow easier differentiation between x32/x64 machines and other selections.
; CI system for daily and l10n Firefox Builds (Henrik)
*
 
; Selenium Grid (DavidB)
*


; [https://wiki.mozilla.org/QA/TCM Case Conductor]
; [https://wiki.mozilla.org/QA/TCM Case Conductor]
*
* Slipping a little on release of 0.8 version of CC.
** Expect release 2/10
** Still will release 1.0 this quarter.  May pare down features a bit to make it happen.
* Working with IT to get setup for the new build on caseconductor.allizom.org.
** since it's pure Django now, it's a different (though simpler) setup.
* Talked with Ubuntu and am working on how Case Conductor can address their testing needs
* Talked with BITE team from uTest (former Google guys) about their tools and how we can share ideas on Case Conductor.
* Added support for OWA


== Notes, Takeaways and Action Items  ==
== Notes, Takeaways and Action Items  ==


=== Today ===
=== Today ===
* Add notes here
* Add new community members to QA org section as we onboard them
**
** Make sure they join the Mozillians phonebook as well
* Install and give feedback on the [http://people.mozilla.org/~jmaher/power-ball-10.xpi Powerball extension] that David Burns talked about
* Are we following up after Test Day to see how things went?
** Trimming the checklist?
 
=== Last Meeting ===
=== Last Meeting ===
* Action Items
* Action Items
**
**
=== Notes ===
<pre>
QA _ meeting : 02 03 2012
Mobile work week : jmaher + dburns was talking about how to try to get more community involvement
jmaher = addon
dburns = l10n
need a system to have a tasking system : images / system
powerball : http://powerball.theautomatedtester.co.uk/
- dburns : proof of concept in powerbolt
links
Collect points to help compete against each other
stack overflow + microsoft w/ visual studio do a similar thing
try it and see if it's worth it : viop viop viop.
in the next 2 weeks would be great to have feedback
We got through releasing 10... looks like a pretty darn good release.  no chemspill.  Kudos to firefox team
Highlights, desktop all in the wiki
- see any problems, file bugs.
- Mobile : wiki stuff.  beta
- Sync server side catching on backlog deployment <voip voip>
- focus on l10n next release
- student helping out.
Pancake
- iOS tablet beta version coming out this quarter
- rest on wiki
B2G:
https://developer.mozilla.org/en/Mozilla/Boot_to_Gecko
- marrionette for test automation
- onboarding 2 community members
- nice notes on how to get up with B2G
- Fort Lewis College students
Apps:
- Jason: getting ready for MWC
- demo scripts, and coverage
- cover testcases for this area ; cell phones
- trying to get manual coverage right now; automation to come
: Case Conductor?  -> apps testing -> case conductor in sufficient shape?  Not today.  Maybe next friday
slipped about a week
- manual tests should be put in litmus.  put them out in community and track it
- most of them are prototypes; flow is not necessarily right for litmus/maybe etherpad
- date and when it was run.
- Apps automation, doing great job.  Services.
WebQA
- shout outs
- stuff on wiki
- no bugs on AMO
Community:
- Henrik : just arrived at FOSDEM
- MozCamp Latin America
- Tech Talk @ Brown
- Ashughes : Mic doesn't work
- can review comments
- trying to hook up community in QA
- trying to put names for onboarding
- have them join mozillians phonebook (for rewards and stuff)
Automation Services:
0.1 : gc/cc addon
- mozmill release
- Henrik bisected python (read wiki on DTC)
- Case conduxtor?
- cam working with IT; migrating data
- talk to ubuntu for their needs
- complex system
- talked to utest that is working on Byte Project : records what you do and place into case conductor
- google web apps support
- next friday: looking to sign off
Geo : On-Demand system for release Builds (Geo)
Round Table:
-    Add new community members to QA org section as we onboard them
-        Make sure they join the Mozillians phonebook as well
-    Install and give feedback on the Powerball extension that David Burns talked about
Used to be really badly silo'ed.
don't get flavor of it if people don't talk about it.
see value in talking about it... at least highlights
"ah crap, I need help"; "This is cool!" should be covered in the meetings
as long as we keep it efficient
top 3 things... don't have to have 3... say the Zinger; don't worry about eh stuff.
Mailing list
- we do an auto reply and then we jump on it if they reply.
- we haven't had anyone reply to auto reply.
- did the page get redesigned?  No.
- what do we do with it?
- we would like to personally reply or make it more personal; any proposal would be great
- we haven't moved to that system
- we started there and it wasn't rewarding
- but maybe we didn't try enough things to make it friendly?
- ideas are welcome; start a thread in QMO or by mail?
- send an email about that
- Valerie is workign with Juan.  Friendliness is important
- need to talk to legal about that.
- Juan to send out email with history etc. and some ideas.
- maybe by wednesday (community meeting)
Test Day 1/20
- reflections
- reflected on what happened from 1/20.
- was a bit of a hassle
- test day was about test api / writing automation
- past test day w/ automation : if we are doing test automation test days, we need to reapproach
- setup time + different systems make it hard for it.
- more complicated than running basic tests and verifications becomes harder
- maybe we should do automation test days in parallel rather than bite into basic tests/verifications
- much harder to get pure community to help out
- Take away : make sure we address the right audience
- documentation is out of date, should be better for more platforms, etc.
- documentation needs to be cleaned up
- do we have adequate feedback taht the doc needs update?
- follow up test days?  Any process to review how things went?
-> Tchung to put up a proposal
- it takes a lot of prep work for automation test days
- opportunities to reduce this?
- we don't have it done frequently enough?  figuring out what emails to send, etc.
- ashughes put a checklist together.  It is pretty long
- Not too difficult; just individuals don't do it freq. it takes a while to do
- other data points?
- edge case/ "real" bugs?
- can we automate the checklist?  we can try non automation?  trim down the check list
- take it from both ends; we have an automation services team... might as well get some benefits from it
- need to trim the "fat" from the checklist
- we have limited success with socorro
- before the test day, having dev buy in ... it helps out a lot
- helps to off load the stress
- VM ?
- Al was maintaining the isos.
- Geo going to do the same; once every 6 months - getting installs in place for windows; reactivate based on different hardware
- release or prerelease of a new browser : if it does trigger a hardware, etc.
- QMO handoff done
- quite a few threads: different visibility between QA, browser id team, discussion on mailing list
- Privacy lead role
- what does it entail?
- not sure: tabled that one
- need clarifications
- summary : if there's a privacy issue, conduit for legal?  part time role?
- liason for the team
- no all hands meeting?
- mentioned in hall way convo?  is that the case? 
- how do we get more connected in the larger company sense?
- brown bag w/ metrics, etc. as example
- will QA be involved?
- yes.
</pre>
Jhammink
Confirmed users
151

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/393914...394162"