QA/Browser Technologies/2011-04-21: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
(5 intermediate revisions by 3 users not shown)
Line 3: Line 3:
= Discussion Items =
= Discussion Items =
* Q2 Goals
* Q2 Goals
** Look over [https://intranet.mozilla.org/QA/Q12011_QAgoals#Mobile_QA_Goals near-final draft]
** Look over [https://intranet.mozilla.org/QA/Q22011_QAgoals#Mobile_QA_Goals near-final draft]
** Update personal goals to reflect these.  Remember, goals should be '''measurable!'''
** Update personal goals to reflect these.  Remember, goals should be '''measurable!'''


Line 21: Line 21:
** Should we clone test-suites for M-c, aurora, beta?
** Should we clone test-suites for M-c, aurora, beta?
** or just clone test suites for major releases?  Q: need a way to indicate which branch the tests are being ran at.
** or just clone test suites for major releases?  Q: need a way to indicate which branch the tests are being ran at.
*** '''discussion''' we will take this offline.  A test strategy needs to be created on what test suites are ran in each branch, and not necessarily a clone of existing litmus test suites.


= Project Status  =
= Project Status  =
*Fennec  
*Fennec  
** Manual (aakash)
** Manual (aakash)
*** QA signed off on 4.0.1
*** Moving Fx5 from Aurora to Beta is still a 5-6 weeks away
*** Features and prioritization for Fx6 are still being determined
** Automation (martijn)  
** Automation (martijn)  
** Website Compatibility / Device Compatibility (aaront)
** Website Compatibility / Device Compatibility (aaront)
Line 52: Line 56:
*** Priorities Planning for Home can be found on the spreadsheet : https://spreadsheets.google.com/ccc?key=tnoZ5MAX0sUxtYo2qbssxtA#gid=7
*** Priorities Planning for Home can be found on the spreadsheet : https://spreadsheets.google.com/ccc?key=tnoZ5MAX0sUxtYo2qbssxtA#gid=7
*** Features for Home can be found : https://wiki.mozilla.org/Features/Mobile
*** Features for Home can be found : https://wiki.mozilla.org/Features/Mobile
**** ETA for all P1 2011/7/1
** Investigation into the use of Selenium has been started
** Investigation into the use of Selenium has been started
** QA Plans need to be adjusted and moved over once planning is complete
** QA Plans need to be adjusted and moved over once planning is complete: https://wiki.mozilla.org/QA/Weave_Test_Plan/FxHome -> https://wiki.mozilla.org/Home/Features/qaplan


*Jetpack (ayan)
*Jetpack (ayan)

Latest revision as of 18:47, 21 April 2011

« previous mtg | Browser Technologies Home | next mtg »

Discussion Items

  • Q2 Goals
    • Look over near-final draft
    • Update personal goals to reflect these. Remember, goals should be measurable!
  • Services QA plan
    • Engineering proposes weekly pushes to s-c on server and client
    • Tracy working on a proposal for testing (more details in Sync update below)
    • have 3 candidates in the pipeline to interview. If all goes well, i am pushing for 2 open positions.
  • Discussion on Maintaining Litmus tests for all projects
    • Should we clone test-suites for M-c, aurora, beta?
    • or just clone test suites for major releases? Q: need a way to indicate which branch the tests are being ran at.
      • discussion we will take this offline. A test strategy needs to be created on what test suites are ran in each branch, and not necessarily a clone of existing litmus test suites.

Project Status

  • Fennec
    • Manual (aakash)
      • QA signed off on 4.0.1
      • Moving Fx5 from Aurora to Beta is still a 5-6 weeks away
      • Features and prioritization for Fx6 are still being determined
    • Automation (martijn)
    • Website Compatibility / Device Compatibility (aaront)
  • Test pilot (tracy)
    • Testing 1.2pre builds. This version is almost exclusively the switch to using built Fx doorhanger notifications. We're on version pre3 as I found a couple issues that needed to be addressed. The latest being bug 651138 - The welcome page returns upon each browser start.
    • Bug 641597 - Main menu stops working after a while of using Firefox 4 RC1. It may be caused TP. That or TP may be a vector to cause it. I've seen it a few times recently but haven't been able to nail it down.
    • There are up to 5 new studies in the works, 3 from outside sources and 2 from with in the TP team.
      • Jinghua sent a proposal for study sign-off which I agreed with. However, it is yet to be documented and QA really can't handle the study sign-off load.
  • Identity (tracy)
    • No UX is planned 'til end of quarter. Need to touch base with jrconlin before this group meets again to work out QA's approach to testing this feature.
  • Jetpack (ayan)
    • SDk 1.0b5 to code freeze next week.
    • From now on, Flightdeck to be pushed to production on every other wednesday at 4pm. Code freeze previous friday.
    • Selenium scripts for flightdeck automation on github now. To be reviewed by david burns
    • Meeting with daniel (hopefully today) to discuss about load testing and other things.
  • Open Web Apps (ayan, tchung)
    • This is still being redefined. Latest i heard, development focus is shifting toward building the Open Web Apps Store.
    • Priorities are being reshifted. Meeting with Ragavan this friday at 9am

Round Table

Notes

Retrieved from "https://wiki.mozilla.org/index.php?title=QA/Browser_Technologies/2011-04-21&oldid=301575"