QA/Browser Technologies/2012-02-23: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 14: Line 14:
* How to handle maple fixed bugs?  (fennec team discussion)
* How to handle maple fixed bugs?  (fennec team discussion)
** <strike>Tony's suggestion is comment in bugs on latest maple builds, and use whiteboard "verified-maple".  Then reverify after it lands on M-C later. </strike>
** <strike>Tony's suggestion is comment in bugs on latest maple builds, and use whiteboard "verified-maple".  Then reverify after it lands on M-C later. </strike>
** '''discussion''' wait until maple merges on m-c, then verify fixes, regressions and qawanted bugs afterwareds.
** '''discussion''' wait until maple merges on m-c, then verify fixes, regressions and qawanted bugs afterwards.


* Next Testdays Plans?
* Next Testdays Plans?
Line 30: Line 30:
** [https://mozqa.etherpad.mozilla.org/mozbtech-communityPlan Etherpad] of ideas
** [https://mozqa.etherpad.mozilla.org/mozbtech-communityPlan Etherpad] of ideas
** wiki cleanup, new projects for QMO, etc..
** wiki cleanup, new projects for QMO, etc..
** '''update''' list of actionable tasks broken down for this quarter.  See Notes below.


* Case conductor status (cam)
* Case conductor status (cam)

Revision as of 20:02, 23 February 2012

« previous mtg | Browser Technologies Home | next mtg »

Discussion Items

  • Top issues for your projects (team summary)
    • update maple branch (GL testing) has lots of development, and introducing regressions. This is a day to day project
    • MWC demos need to be in solid shape. backup plan is to use phone cards, and offline access off the SD card. There are still a handful of blocking bugs bug 729277
    • triaging of blocker bugs for beta and release. this determines the timeline (Sync and Maple are biggest areas)
    • Android Sync, still waiting for content provider for passwords
    • addon sync had a blocker bug for new accounts, but fixed in latest train
    • sync server side, more projects are going to be ready for testing (sync server 2.0 api - dev environment, no frontend, no database, token server - need staging environment built)
    • BrowserID still has localization issues, can't sign in on nightly/aurora only. bug 730015
    • Q: Are we still on track to rewrite the authentication work for BrowserID? No answer yet
  • How to handle maple fixed bugs? (fennec team discussion)
    • Tony's suggestion is comment in bugs on latest maple builds, and use whiteboard "verified-maple". Then reverify after it lands on M-C later.
    • discussion wait until maple merges on m-c, then verify fixes, regressions and qawanted bugs afterwards.
  • Next Testdays Plans?
    • Persona (ack! still hate typing this word...): march 9th
      • new UI, localization, have a primary server eyedee.me
    • Fennec GL merge to M-C nightly testday: Date TBD sometime after mwc)
      • include Android Sync work landed
      • (aaron) follow up with when the GL merge happens from dev
    • Pancake: defer to next quarter? only ipad beta is shipping
  • MozCamp: Buenos Aires? (AaronMT)
    • (tony) follow up with bob
  • Community projects update (tracy)
    • Etherpad of ideas
    • wiki cleanup, new projects for QMO, etc..
    • update list of actionable tasks broken down for this quarter. See Notes below.
  • Case conductor status (cam)
    • Awaiting IT to bring the staging environment up (this week)
    • New testcases can be created directly
    • See Case Conductor User Guide
    • Cam: will be requesting
    • give feedback through bugzilla (MozillaQA::Case Conductor)

Project Status

  • Highlights
    • MWC testing is top focus for fennec this week
    • BrowserID is depoying a train this week
    • Sync landed a handful of patches
    • B2G workweek this week in france
    • We'll be talking about community work tomorrow in BT meeting
  • Fennec (Kevin/Aaron)
    • Native
      • Focused on MWC demo testing on the Maple branch
      • Triage is ongoing
        • keywords are going away
        • will be going to traditional flags, watch for a blog post for blassy
    • XUL
    • Stability (nhirata)
    • MWC (nhirata)
      • work being done to make sure that MWC web apps + a build from nightly build is stable for the demo
      • So far 2/19/2012 is the fall back; Currently testing today's build, cleaning up bugs. Most likely going to use 2/23 as the MWC candidate for nightly. Maple still needs at least tomorrow's build.
      • Web API is also getting fixed up with due date of 2/23 noon PDT
  • Sync (Tracy)
    • testing Android code drop .5
    • working on automation in sikuli
    • preparing videos for community engagement.
    • s-c client train around Add-on sync bug fix bug 712542 rolled to m-c yesterday.
  • Test pilot (tracy)
    • nothing for QA this week
  • Sync Server (jbonacci/jrgm)
    • Testing continues as needed for any Sync Server deployments and Change/Maintenance Windows.
    • Test scripts are in progress for running curl against rfkelly's Sync 2.0 setup
    • QA test planning in in progress for the following projects:
      • MetLog
      • BiPostal
      • Sync 2.0 with Token Server
  • BrowserID (jbonacci/jrgm)
    • Actively working on Train 21 in Stage:
      • Bug 727995 - QA and deploy BrowserID train-2012.02.16 to production
      • Main focus on this train, again, is support for primaries, UX, localization
  • Pancake (nhirata)
    • QA work semi onhold until after MWC

Round Table

Notes

Retrieved from "https://wiki.allizom.org/index.php?title=QA/Browser_Technologies/2012-02-23&oldid=400669"