QA/Fennec/Waverley/2011-07-12

Meeting Notes for <date/year>

Welcome

(eg. headcount, updates with staffing, vacation/away time)

Take Ways From Last Week

(eg. Action items from last weeks's Take Aways)

  • Kevin to review waverley test cases
  • [DONE] Anthony: needs to investigate features for Firefox 7
    • Still need to work with Firefox team to improve communication -- Fx7 Flight Tracking page was not updated until day before merge -- this will be an area of "continuous improvement"
    • I'll update the overall testplan every Wednesday, following the Platform and Firefox meetings, with feature status' conveyed from those meetings
    • If you've already signed up to own a feature for Fx7, please be in touch with your feature developer and project manager on at least a weekly basis to get a status update

Round Table

  • Noting more goodness in FF 6 test documentation (matt)
    • Panorama_Groups_On_Demand
      • Bug 595601 George
        • Excellent comment for bug verification!
  • FF 6 Feature verfication (matt)
    • If feature wasn't verified on all platforms, please do so.
  • Daily Stand-up (ashughes)
    • Started last Friday doing a daily stand-up with Waverley via the Firefox and Automation etherpads -- it's just a top-level section
      • Waverley reports issues, blockers, and questions
      • Mozilla reports tasks to be completed and answers those issues, blockers and questions
    • Not doing physical 1:1 yet -- will start if/when needed -- etherpad section seems to be working well so far

Firefox Updates

(eg. Status, top issues)

  • Mozilla (juanb, ashughes)
    • Fx 6(beta1) desktop and mobile, 7(aurora), 3.6.19/5.0.1 released: Great work!
    • Fx 6(beta2): TBD this week.
  • Waverley (Andrei, George, Simona, Vlad G)
    • Dev Tools meeting minutes
    • Test plan
    • Project tracking
      • Watch QA assigned Features Spreadhsheet
      • Reviewed commented bugs
    • Questions
      • Should fixed bugs verification be done on Core and Toolkit products, besides Firefox?
      • Should we focus on Ubuntu 10.10 or Ubuntu 11.04? (automation tests are run under Ubuntu 11.04)
      • Once Mac OS X 10.7 is launched does it have a higher priority than Mac OS X 10.6?

Automation Updates

(eg. Status, top issues)

WebQA (Selenium)
  • Waverly (Teodosia, Florin)
  • Mozilla
Desktop (Mozmill)
  • Waverley (Alex, Vlad)
    • ASSIGNED bug list
    • RESOLVED bug list
    • Current tasks
    • Issues so far
      • Lack of API for places makes those tests very low priority for now
      • Add-on compatibility issues force us to skip some tests for aurora and default branch (will need manual testing for those branches unless we come up with compatible add-ons in the Discovery Pane sections)
    • Questions
      • What is to be done with litmus tests which cannot be 100% covered by mozmill? Should we take those and do what it can be done or leave them by to decide later? What about reporting these kind of situations?
      • ANSWER: Deal with these on a case by case basis by calling them out in the daily standup section of the Etherpad -- Anthony will make the decision on each case
      • What about API change/updates requests? Should we modify shared modules locally and upload along with patches? Or: file a bug, change the API, wait for that to land then upload test? We have done both sides so far. Finally, should we request Anthony or Henrik for the API changes?
      • ANSWER: If it's a small couple line change to an existing API method, include it with your test patch. If it's a new method file a bug for Henrik, CC me, mark it blocking your test, and make a note of it in the daily stand-up section of the etherpad
  • Mozilla (ashughes)
    • We now have 8 P1 Add-ons Manager BFTs to automate -- focus on those once you have finished up any open Discovery Pane and Places tests
    • I'll work with Dave Hunt this week to identify Endurance tests -- would like to see Vlad and Alex contribute 2 tests each

Fennec Updates

(eg. Status, top issues)

Take Aways This Week

(eg. Action items)