QA/Browser Technologies/2011-09-08

From MozillaWiki
Jump to: navigation, search

« previous mtg | Browser Technologies Home | next mtg »

Discussion Items

  • New Hires!
    • John Hammick, Mobile Tech Lead, Sept 12
    • John Morrison, QA Services server-side, Oct 10ish
  • New Waverley resources for Services, 1 day a week
    • Ioana Buchnar, Browser ID
    • Mihaela V, Client Sync
  • QA Whiteboard discussion (qa+/-)
    • should we adopt this for fennec?
  • Firefox profiles and shared sync accounts (tracy)
    • last time
      • Having set profiles [small|med|large] for Sync Staging. How do we want to organize and store this data?
        • Services needs this since we need large sets of complicated setup
        • Manufactured versus personal?
  • Fennec
    • Keeping up with Features and Testplans. Concerns?
  • Last time
  • BT Topics for QA workweek in Sept
    • Suggestions? See scrumpad for current ideas
    • discussion
      • how to collaborate more cross team testing across products? (eg. browserID and openWebApp store, Pancake)
        • how do we coordinate those dependencies across efforts? Test systems?
      • an update on technologies of various projects, advertise the tools to development, lightning talk. (all hands or qa internal)
      • What is QA's automation's strategy for other teams to request/plan tooling and infrastructure? (have a team member attend the QA automation team meetings)
      • Having set profiles [small|med|large] for Sync Staging. How do we want to organize and store this data?
        • Services needs this since we need large sets of complicated setup
        • Manufactured versus personal?


Project Status

Fennec (kevin, aaron)

  • 7.0b5 expected to go-to-build today (Aaron)
  • Looking for feedback/improvements toward future beta status showcasing - started example (Aaron)

Automation (martijn)

Fixing editor/libeditor/ tests

  • Wait for WaitForFocus patch from Joel, which fixes timeouts
  • Still trying to write a patch to support WaitForClipboard events in e10s, which fixes a bunch of other timeouts
  • Move test_bug366682 to mochitest chrome (this is done, need 1 simple change, then it can be checked in)

Other

Sync

Client (Tracy)

  • Last two client trains have had minor delays, but proceeded to run.
  • I am behind on test suite cleanup. Targeting finish by next train on the 20th.
  • Waverly resource to help with train testing on services-central beginning 9/20.
  • Making break through in Mozmill automation of Sync account setup. But hitting plenty of speed bumps; currently stuck at clicking the Continue button once all account information has been entered.
  • Sync QA tips and tricks video targeted for rough cut completion by end of QA work week 9/21. Then hand over to Rainer for final cut polish work.
  • Bi-weekly triage sessions have been productive. The UNCONFIRMED client bug list has been reduced to ~50 bugs. 90% of those remaining have a creation date older than 7 months.

Server (James)

  • Train 4 of the very large "train of trains" finally went out a couple weeks off schedule.
  • The Services OPs team has gone into "lockdown" for the next coupld of weeks to get some infrastructure work done.
  • Plans are moving forward to reconfigure our Sync Server VM and an incoming desktop system so that they can both be used for QA testing, tools development, and automation.

Load/Automation Testing (jabonaci)

  • Sync Server, TPS, and Funkload setups will continue once the ordered Linux desktop arrives.

Test pilot (tracy)

  • jono continues to work on next versions for mobile and desktop.

BrowserID (james)

  • Work continues on Train #5 for BrowserID (09/01/2011).
  • Dev continues to work on adding support for IE, mobile, plus working with UX team to redesign desktop and mobile UI flows.
  • Next train is on hold due to resource issues around All Hands and QA Work Week.
  • Waverley resource has been made available for help with testing the weekly trains.

Pancake (Naoki)

  • Brownbag last week
  • QA testing occurred from .2 to .12 within the last 2 weeks
  • about to ship internally to Mozilla but not externally.

Round Table

Notes

nhirata's raw notes

- Over the weekend than during the week ; true offsite for QA
- Topics to discuss at the bottom
- As far as All Hands: expectations?  Anything expected for QA during all hands?
	- up to individuals
	- all hands set and haven't looked through that yet, haven't seen our sessions
	- webQA
	- set up an etherpad to indicate : 'going here' 'this looks cool' 'spread out'
	- anything that we should be aware of ; 
	- anything that we should be there for support or do we just spread out to whatever is relevant
- action item : mevans: look through and point out for slotted ones to attend
- want to get broad QA coverage to promote
- want to have something to talk about cross product work, cross browser, cross operating systems and get feedback from developers
- discuss organizations
- bird of a feather sessions when we arrive; whole blocks of rooms to gather
- if we have BoaF (Birds of a feather) , need to make sure dev is signed up
- any questions?
	- nhirata, jbonacci's first time
	- what to expect?  talk offline
	- look for email from mevans

- have fun!
- concert on monday and winery
- BrowserID team demo at all hands
- hard to look at : pdf for every day has 2 sessions to look at; bring up the 

New hires : welcome
 - John Hammick : automation frameworks; background mameo meego, nokia; gui automation framework.  skype cert starting next week
	- bring in processes, guidance, ways to improve it, spending some time with automation needs for mobile; client side/api automation
	- working with clint's group, has already contacted mobile QA for facebook; located in MV; Cameron will be working with him/mentor
 - John Morrison : signed him beginning of last month ; recommended by lots of folks, netscape. 
 	- referred; senior services for server side testing; apis sync automation working with james
 	- web API; b2g; etc.  Oct 10ish due to visa; onsite in MV
 - 2 from Waverly FF team to help with BT;     Ioana Buchnar, Browser ID + Mihaela V, Client Sync 
 	- James + Tracy already giving them test plan etc.
 - QA Whiteboard discussion (qa+/-) for bug triage
 	- qa+/qa?/qa- take the gaps between feature pages and individual bugs that do not constitute a feature page
 	- 100 % for tracking bugs are qa+
 	- another piece : taking back the qa contact field
 		- met with asa; met with bmo; it's being worked on.  maybe in a couple of weeks
 	- does everyone have to take their qa contacts?
 		- separate from watch
 	- bugzilla plugin that allows for watch fields.  That's what's being used
 	- doing another way for watched components
 	- mentioned by Marcia about the bug 684088
 	- process already : hg commit logs, review list, etc.
 	- ahughes attended meeting; asa explained triage bugs which landed, etc. see ahughes email
 - doing this for client side services bugs somewhat already
 - are we going to go ahead with fennec? or wait
	- questions for whiteboard?
	- need for tracking things that landed
	- no replies to the objections
	- questions?  who sets them?  during which part of the bug process?
	- we are setting them in the triage for aurora, beta
	- expired when QA takes action (verified fixed as example)
	- it's not clear that you want to take off that entry
	- proposed that we don't take it off?  keep it there until the bug 
	- do they expire?  qa+ ?  no one pays attention to it?  Are we following up on them?
	- possible "handful of oops?  we didn't get to it that release"?
	- if something has shipped, then attention may expire?
	- maybe it shouldn't because it has become part of the product
	- once it ships; it would be helpful for investigation purposes
	- if regression occurs; mozilla dev doesn't like reopen bugs, file a new bug.  most other places reopen the bug
	- that process is independent of qa+/qa- etc.
	- owner of qa+/qa- is QA.
	- services they do it differently.  Dev is using that whiteboard
	- not too much differently.  fix the bug, and then dev will mark qa- if qa can't test due to back end change that can't be verified etc.
	- Services is not using the full capabilities of the qa+, qa-
	- Does it matter who controls it?
		- Firefox, Fennec = QA
		- Services = dev
	- let's try to be consistent and adopt this
	- action item : juan : wiki page so that people understands what's going on with qa+/-; how to do triage based on asa's instructions
	- qa work week : socialize process : whack out the bugs!
	- once we establish this, we have consistent queries across products
	- test plan has consistent bugzilla queries
- ffx profiles and shared account sync
	- we want profile testing (why Juan is joining us today)
	- how do we approach this?
	- do we store it in the profile?
	- do we save it? download it?
	- stored on production server?
	- store it local?  or sitting on cloud?
	- need baseline of accounts
	- syncing would mean that it would keep growing
	- we should store that and set off
	- we need old accounts that grows
	- new account to grow quickly
	- lots of testing requires new account
	- do we have generation tools?
	- we need to talk to dev for profiles
	- mock up data or real data?  mock up data
	- template approach?  new account set to template in the cloud?
	- server download and set the zip file locally?
	- live profiles that you can mount which grow over time
	- third option is generation tools to create profiles; random bookmarks, history etc.
	- how do we get this?
	- scope out for qa work week?
	- this is something that affects the teams that use profiles
	- what's difference between profile versus accounts?
		- profiles need to start and then you can sync up to the account
	- need to have stuff staying in stage
		- exisiting accounts don't get mucked up
		- need to have stored profiles
		- medium account, large account, large profiles etc.
	- same account from the same profile
	- stick it on staging, production, etc.
	- if we need to wipe it we can go back to the file system
	- need requirements that need to be flushed
		- who drives the spec?
	- action item : tracy will take the requirements ; jbonacci to work with tracy due to browser id
	- get input form ffx and fennec, and a-team (a-team good source)
	- see what you can come up with next week, and move on from there
- bullet point for fennec
	- features and test plans
	- get a sense; fine at the moment; waverly is willing to step up
	- how we tackle the tablet ui; lots of bugs and fixes ; major feature for 9
	- concerned about timing
	- sign off time for features/test plan
	- don't have all data with bugs landing at last minute
	- sept 27th merge date isn't moving; we can count on that
	- better way to keep track of QA sign off?
	- QA deadline?  iterate as we go?  don't want to bleed into the merge date
	- changes are going to go in until merge date due to rapid dev
	- dev will be more in triage mid way through of aurora
	- we have to push on Thomas
	- what do we need to call it feature sign off
	- unclear when/where we're finished testing
	- be aggressive that are issues that are blocking
	- anything from ffx for feature sign off?
		- the procedure has been to follow nightly
		- test cases/testing aurora
		- beta is stability
		- people will continuously checkin until merge
		- as long as people take a look around the changes we are ok week to week.
	- is that the only influx of things of asignments?
		- push logs
		- may apply to fennec; status meeting notes; is that in the list of things?
		- we catch that before it's announced
		- some are big/some are small; are we tracking through dashboard?
		- recorded in spreadsheet by component; they are tracked in that way
		- softvision people have been saying what they have tested in that cycle
		- they list some of the bugs that they found, but not all the bugs in all components
		- need to make this more explicit : we are paying attention to it ; who owns it.
- Fennec:
	- read the wiki
	- martijn: same
		- doing test on mochi
		- no eta on blocker (need more information from henrik for elastic searches; need to talk to henrik before work week)
		- concern for missing quarterly due to blocker (due to work week)
		- action item : martijn: approach w/ email to henrik with questions; cc tony
	- monthly newsletter : more towards Android community
		- QA is doing bi weekly newsletter
		- worth looking at coordinations; maybe every other week following ahughes?; don't want to overlap with qa newsletter
		- mobile newsletter? - can expand more towards b2g and web api
		- Android newsletter? - > change it to be more mobile not just feenec
		- test specific ? 
		- Not just test specific; 
		- main reason for it : ADUs channels, current stage : Hot issues
- Sync :
 - see wiki: Bullet points
- Pancake :
 - possible demo at all hands
 - no timeline in when it's going public
- Rounds Tables:
 - none

Addendum/Followups

From the desk of jbonacci 

Just an update for those interested in the BrowserID demo that will happen during All Hands.
I made the assumption it would be as part of a session, but I was wrong!
It will take place during the Keynote!

According to Ben Adida (and I quote): "...during the keynote, either before or after lunch, not sure..."

Also, David Ascher has created an external site for all the sessions and other activity around the All Hands.

Here (must have a Twitter account to login): http://lanyrd.com/2011/mozilla-all-hands-september

Here is the BrowserID page set up by Dan Mills: http://lanyrd.com/2011/mozilla-all-hands-september/shfgt/

Action Items:

  • action item : martijn: approach w/ email to henrik with questions; cc tony
  • action item : mevans: look through and point out for slotted ones to attend
  • action item : juan : wiki page so that people understands what's going on with qa+/-; how to do triage based on asa's instructions
  • action item : tracy will take the requirements ; jbonacci to work with tracy due to browser id
  • action item : nhirata to work in coordination with ahughes for mobile newsletter
Retrieved from "https://wiki.mozilla.org/index.php?title=QA/Browser_Technologies/2011-09-08&oldid=347932"