QA/Fennec/Waverley/2011-07-12: Difference between revisions

From MozillaWiki
< QA‎ | Fennec‎ | Waverley
Jump to navigation Jump to search
 
(19 intermediate revisions by 9 users not shown)
Line 7: Line 7:
<i> (eg. Action items from last weeks's Take Aways) </i>
<i> (eg. Action items from last weeks's Take Aways) </i>
* <i> Kevin to review waverley test cases </i>
* <i> Kevin to review waverley test cases </i>
* <i> Anthony: needs to investigate features for Firefox 7</i>
* '''[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 ==  
== Round Table ==  
Line 17: Line 20:
** If feature wasn't verified on all platforms, please do so.
** If feature wasn't verified on all platforms, please do so.
*** For example: [https://wiki.mozilla.org/Platform/Features/RevampAboutMemory RevampAboutMemory]
*** For example: [https://wiki.mozilla.org/Platform/Features/RevampAboutMemory RevampAboutMemory]
*** Don't forget to check if there are one-off bug landings in beta and aurora.  If you happen to see bug comments with checkins on those branches, please verify the fixes on the beta and aurora branches by using keywords '''verified-beta''', '''verified-aurora''' (tchung)
* 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 ==
== Firefox Updates ==
<i> (eg. Status, top issues) </i>
<i> (eg. Status, top issues) </i>
* Mozilla (test lead)
* Mozilla (juanb, ashughes)
** Fx 6(beta1) desktop and mobile, 7(aurora), 3.6.19/5.0.1 released: Great work!
** Fx 6(beta1) desktop and mobile, 7(aurora), 3.6.19/5.0.1 released: Great work!
** Fx 6(beta2): TBD this week.
** Fx 6(beta2): TBD this week.


* Waverley (tester)
* Waverley (Andrei, George, Simona, Vlad G)
** [https://wiki.mozilla.org/DevTools/2011-07/07 Dev Tools meeting minutes]
**Test plan
***Firefox 3.6.19
****BFTs on Mac OS X 10.7 - [http://mzl.la/oYq4kA Wiki-page]
***Firefox 5.0.1
****Smoketests - [http://mzl.la/rtX53X Wiki-page]
****BFTs on Mac OS X 10.7 - [http://mzl.la/nMIxTO Wiki-page]
***Firefox 6.0 Beta
****Smoketests - [http://mzl.la/nRxwim Wiki-page]
****Feature sign-off - [http://mzl.la/ridZP6 Wiki-page]
****Brand checking - [http://mzl.la/qzTeaC Wiki-page]
***Firefox 7.0 Aurora
****Smokestests - [https://wiki.mozilla.org/QA/Firefox:7#Smoketests Wiki-page]
****Feature spot-check - [http://mzl.la/pSdNXj Wiki-page]
***Firefox 5 spot-checking on Mac OS X 10.7 - [http://bit.ly/pb6SIU Etherpad]
***Fixed bug verification across platforms - [http://bit.ly/iwrNhI  Spreadsheet]           
***Logged issues - [http://bit.ly/nnHCyj Bugzilla query]
***Bug triage - [http://bit.ly/e0wiuz Spreadsheet]
***Updated testcases in Litmus [http://bit.ly/kJBMUv Spreadsheet]
**Project tracking
***Watch QA assigned Features [http://bit.ly/lWsrWo 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 ==
== Automation Updates ==
Line 31: Line 66:
; WebQA (Selenium)
; WebQA (Selenium)
* Waverly (Teodosia, Florin)
* Waverly (Teodosia, Florin)
**Moved tasks from [https://spreadsheets.google.com/ccc?key=0Astb7g_teL8bdHFzV05LVTh1OEtOZFFSeTBhc0toUEE&hl=en&authkey=COqmu-gN&ndplr=1#gid=4 AMO Spreadsheet] to [https://www.pivotaltracker.com/projects/310523 Pivotal Tracker]
**Writing new tests for AMO
**Modifying test accordingly to the code review
* Mozilla
* Mozilla


; Desktop (Mozmill)
; Desktop (Mozmill)
* Waverley (Alex, Vlad)
* Waverley (Alex, Vlad)
* Mozilla (Anthony)
** [http://bit.ly/n1akWP ASSIGNED bug list]
** [http://bit.ly/niAllN RESOLVED bug list]
** Current tasks
*** Refactor/fix tests as needed
*** Creating restart tests for AOM (P1) [http://bit.ly/jQ58fl mozmill spreadsheet]
** 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 ==  
== Fennec Updates ==  
<i> (eg. Status, top issues) </i>
<i> (eg. Status, top issues) </i>
* Mozilla (test lead)
* Mozilla (kbrosnan)
** Beta 1 Shipped Friday
** there is a special beta 1 build from release engineering
** Beta 2 this week (we think)
** AAronMT will be the lead on Firefox 7
** kbrosnan will be the lead on Firefox 8
* Waverley (Ioana, Anna, Andreea, Nicolae)
* Waverley (Ioana, Anna, Andreea, Nicolae)
** '''Weekly Status:'''
** '''Weekly Status:'''
Line 47: Line 105:
*** run performance tests (all) against daily builds with the add-on (daily on aurora and nightly)(result are on server)
*** run performance tests (all) against daily builds with the add-on (daily on aurora and nightly)(result are on server)
*** updated 6.0 tests in Litmus and other changed ones changes made [https://spreadsheets.google.com/ccc?key=0AvuRMBSIUafjdGUzVkFTeldzSk0za0Y0Q3hTellVN0E&hl=en&authkey=CIaU1ZEL#gid=0 here]
*** updated 6.0 tests in Litmus and other changed ones changes made [https://spreadsheets.google.com/ccc?key=0AvuRMBSIUafjdGUzVkFTeldzSk0za0Y0Q3hTellVN0E&hl=en&authkey=CIaU1ZEL#gid=0 here]
*** Smoketests on Android and Maemo for Beta 1 Special. Results: [https://wiki.mozilla.org/QA/Fennec/Milestones/6.0/Beta_1_special here]
*** '''Beta 6.0b1''' Results: [https://wiki.mozilla.org/QA/Fennec/Milestones/6.0/Beta_1 here]
*** [http://bit.ly/m1FqGZ Logged issues]
*** '''Smoketests on Android and Maemo for Beta 1 Special'''. Results: [https://wiki.mozilla.org/QA/Fennec/Milestones/6.0/Beta_1_special here]
*** [http://bit.ly/LoggedBugs20110712 Logged issues]
**'''Important bugs:'''
**'''Important bugs:'''
***[https://bugzilla.mozilla.org/show_bug.cgi?id=669289 Bug 669289 - Fennec UI is unresponsive and browser becomes unusable if a restart is triggered with a single blank tab open]
***[https://bugzilla.mozilla.org/show_bug.cgi?id=669289 Bug 669289 - Fennec UI is unresponsive and browser becomes unusable if a restart is triggered with a single blank tab open]
***[https://bugzilla.mozilla.org/show_bug.cgi?id=669298 Bug 669298 - Download notification is not triggered if Fennec performs this action before it loads for the first time]
***[https://bugzilla.mozilla.org/show_bug.cgi?id=669298 Bug 669298 - Download notification is not triggered if Fennec performs this action before it loads for the first time]
**'''Questions:'''
**'''Questions / Issues:'''
*** We could not install Fennec 6.0 Beta 1 special on Gingerbread
*** A new option was added to favicon menu: Install as App. Is this a new feature? Could you tell us more about it please?


== Take Aways This Week ==
== Take Aways This Week ==
<i> (eg. Action items) </i>
<i> (eg. Action items) </i>
* Anthony to update Fx7 bug queries for bug verifications
* Reminder: verify bugs across all platforms they apply to.

Latest revision as of 15:28, 12 July 2011

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.
      • For example: RevampAboutMemory
      • Don't forget to check if there are one-off bug landings in beta and aurora. If you happen to see bug comments with checkins on those branches, please verify the fixes on the beta and aurora branches by using keywords verified-beta, verified-aurora (tchung)
  • 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)

  • Anthony to update Fx7 bug queries for bug verifications
  • Reminder: verify bugs across all platforms they apply to.