QA/StaffMeetings/QA-Staff-05-25-2011: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(36 intermediate revisions by 16 users not shown)
Line 15: Line 15:
== Desktop Firefox (Juan)  ==
== Desktop Firefox (Juan)  ==
* Fx.Next
* Fx.Next
**  
** nightly-aurora (fx6) merge: builds expected out today
** new beta build (fx5b3): go-to-build Friday, expected ship out.
* Crash Investigation
* Crash Investigation
**
** https://wiki.mozilla.org/CrashKill has breakdown for all channels(nightly, aurora, beta).
** [https://wiki.mozilla.org/Platform/2011-05-24#Stability_Report Stability Report for this week]


== Maintenance and Security (Al)  ==
== Maintenance and Security (Al)  ==
* Firefox 3.6.18
* Firefox 3.6.18
**  
** Work is continuing and checkins are occurring more quickly.
** Still set to release on June 21 with Firefox 5.
* Firefox 3.5.x
* Firefox 3.5.x
**  
** There are no more 3.5.x releases. Three cheers. We've done an advertised major update to Firefox 4.0.1 for these users.
* Firefox 4.0.2
* Firefox 4.0.2
**  
** There are currently no plans for 4.0.2 unless there is a chemspill. Firefox 5 is the next release for 4.0.1 users.


== Browser Technologies (Tony)  ==
== Browser Technologies (Tony)  ==
Line 31: Line 34:
**  
**  
*Fennec (aakash)  
*Fennec (aakash)  
**  
** Expecting builds for MobiFx 5.0 Beta 3 that incorporate backouts
** Features are landing for 6.0 and QA is beginning testing their features there
** Nightly is on 7.0a1 now
*Sync (Tracy)
*Sync (Tracy)
** Client train was moved up one day this week (pushed to m-c on Monday) to make sure changes made it for the Aurora merge.
** Client train was moved up one day this week (pushed to m-c on Monday) to make sure changes made it for the Aurora merge.
Line 38: Line 43:
** [https://wiki.mozilla.org/Firefox/Features/Instant_Sync Instant Sync] feature, targeted for Fx7, will proceed once devs complete work on [https://wiki.mozilla.org/Services/Sync/FxSync/DeathToUnknownError DeathToUnknownError]  
** [https://wiki.mozilla.org/Firefox/Features/Instant_Sync Instant Sync] feature, targeted for Fx7, will proceed once devs complete work on [https://wiki.mozilla.org/Services/Sync/FxSync/DeathToUnknownError DeathToUnknownError]  
** Server push for next Monday will be done on Tuesday instead because of the US holiday.
** Server push for next Monday will be done on Tuesday instead because of the US holiday.
*Load Testing (Owen)
** Working with ops team to develop a plan for load testing sync
** Furthering development on current grinder scripts to hit more functions with more accurate usage patterns.
** Detailed plans exist here: https://wiki.mozilla.org/index.php?title=QA/Sync/Test_Plan/grinder_tests
*Test pilot (tracy)
*Test pilot (tracy)
** 1.2 is getting closer with pre6 build, but some minor fixes are still needed.   
** 1.2 is getting closer with pre6 build, but some minor fixes are still needed.   
*Identity (tracy)
*Identity (tracy)
** Still on security hold.
** Still on security hold.
*Jetpack(?)
*Jetpack(tchung)
**  
** Handed FlightDeck off to webdevQA
** No ownership atm for jetpack sdk
*Firefox Home (nhirata)
*Firefox Home (nhirata)
** Researching on various automation strategies
** Researching on various automation strategies
Line 58: Line 68:
*
*
=== AMO  ===
=== AMO  ===
*  
*[http://tinyurl.com/3lymljv AMO 6.0.10] went live on 05/19. This release included support for Bulk compatibility check which is a huge deal for the new Firefox release model.
*[http://tinyurl.com/3h2nlyj AMo 6.0.11] is scheduled for 05/25.
 
=== Engagement Projects  ===
=== Engagement Projects  ===
*
 
*[https://wiki.mozilla.org/QA/Execution/Web_Testing/Web_Hero_Facebook_tab_update Webhero release] planned for 5/31
*[http://goo.gl/GypV0 Mark Up 1.0 release] planned for 5/31
 
=== Input  ===
=== Input  ===
*  
 
*[https://bugzilla.mozilla.org/show_bug.cgi?id=658700 3.5, 3.5.1, and 3.5.2] milestones pushed last week
*[https://bugzilla.mozilla.org/show_bug.cgi?id=658031 4.0 milestone] release on 5.26.11, [http://goo.gl/Th6cx 4.0 bug list], two blockers [https://bugzilla.mozilla.org/show_bug.cgi?id=659516 bug 659516] and [https://bugzilla.mozilla.org/show_bug.cgi?id=659733 bug 659733]
 
=== Mozilla.com ===
=== Mozilla.com ===
* [http://bit.ly/ip149p 2.6] milestone
* [http://bit.ly/ip149p 2.6] milestone shipping next week 5/31


=== MDN  ===
=== MDN  ===
*[http://bit.ly/iBJTWK 0.9.5] milestone
*[http://bit.ly/iBJTWK 0.9.5] milestone shipping 6/7


===Spark ===
===Spark ===
* [http://bit.ly/joUWY5 2.0] milestone
* Working on [http://bit.ly/joUWY5 2.0] milestone which might ship next week


=== Socorro  ===
=== Socorro  ===
*  
 
*[http://goo.gl/jtaL2 1.7.8 milestone] slipped from 5.26.11 to 5.31.11
 
=== SUMO  ===
=== SUMO  ===
* Added a test for creating/editing/previewing/deleting a [https://github.com/mozilla/sumo-tests/pull/7 Knowledge Base Article]
*[http://moxie.jamessocol.com/bugstats/sumo/2.8.4 2.8.4 release] on 5/24
*[http://moxie.jamessocol.com/bugstats/sumo/2.9 2.9 release] on 5/31
* planning a community test day for Users&Groups/Private Messaging


=== WebQA Automation  ===
=== WebQA Automation  ===
Line 81: Line 103:
* Waverly helping out with Test day and looking at AMO
* Waverly helping out with Test day and looking at AMO
==== AMO ====
==== AMO ====
* Test Day yesterday, patches are pending at the moment
* Test Day yesterday, [https://github.com/mozilla/Addon-Tests/pulls patches are pending] at the moment
 
==== Input ====
*
==== MDN ====
==== MDN ====
*
*
==== Mozilla.com ====
==== Mozilla.com ====
*
*
==== Socorro ====
* Matt/David to work through test-template updates for [http://qa-selenium.mv.mozilla.com:8080/job/socorro/lastCompletedBuild/testReport/ failing tests]
==== SUMO ====
==== SUMO ====
*
* Added a test for creating/editing/previewing/deleting a [https://github.com/mozilla/sumo-tests/pull/7 Knowledge Base Article]


== Community (Marcia)  ==
== Community (Marcia)  ==
Line 96: Line 123:
* Video Work
* Video Work
** Reviewing some footage from Whistler Summit (Marco Zehe Accessibility)
** Reviewing some footage from Whistler Summit (Marco Zehe Accessibility)
** Reviewing the "Making Mozilla Better" video with intent of updating the content to match changes in the product.
*QMO.next (Al):
*QMO.next (Al):
** [http://mozilla.focalcurve.com/qmo/ QA Site refresh]
** Work in in progress for [http://mozilla.focalcurve.com/qmo/ QMO Site refresh] for theme.
** Meeting with Ryan Snyder on progress and timeline on Thursday.
** Meeting with Eric Meyer to go over second round of potential Achievement badges for QMO.


== Test Automation (Henrik)  ==
== Test Automation (Henrik)  ==
===General===  
===General===  
*  
* Mozmill Dashboard: Please check the [http://etherpad.mozilla.com:9000/mozmill-dashboard-elasticsearch feature list] for the dashboard rewrite and add proposals or ask questions
* Tests / Shared Modules: Henrik is working on getting any issue of the Add-ons API solved as quick as possible - we don't want to block Softvision
* Shadow Server: Still waiting for the SSL certificates to improve our security tests
 
===Mozmill===  
===Mozmill===  
*  
* Mozmill 1.5.4 process is slower but we will get interim beta releases with any important bug fixes which block us from writing tests for the Discovery Pane
* Mozmill 2 is getting closer; release can happen by end of this quarter
 
===Project updates===
===Project updates===
;[https://wiki.mozilla.org/QA/Mozmill_Test_Automation/Shared_Modules_Refactor API Refactoring]
;[https://wiki.mozilla.org/QA/Mozmill_Test_Automation/Shared_Modules_Refactor API Refactoring] (Geo)
*  
* Owen Coutts has joined project part-time, will be assisting in module refactoring and test porting to help us make our quarterly goal.


; Mozmill Tests for the Discovery Pane of the Addons Manager (ashughes)
; Mozmill Tests for the Discovery Pane of the Addons Manager (Anthony)
*  
* 4 / 10 tests on file are in development


; [[QA/Mozmill_Test_Automation/Endurance_Tests|Endurance Tests]]
; [[QA/Mozmill_Test_Automation/Endurance_Tests|Endurance Tests]] (Dave)
*
* Issue with restarting Firefox between tests. {{bug|658395}}
* Updated [[QA/Mozmill_Test_Automation/Endurance_Tests/Documentation|Documentation]]
* Several patches in the queue to improve reporting. {{bug|656404}}, {{bug|657347}}, {{bug|658572}}
* Currently working on getting Endurance Tests working with Firefox 6.0. {{bug|656869}}


; [https://wiki.mozilla.org/QA/Mozmill_Test_Automation/On_Demand_Update_Testing On Demand Updates]
; [https://wiki.mozilla.org/QA/Mozmill_Test_Automation/On_Demand_Update_Testing On Demand Updates] (Geo)
*  
* Problem with daemons hanging overnight has been identified; combo of machine sleeping and inactive socket timeout. Fix is in progress.
* Otherwise, was successfully used in the 5.0b2 release (yay!)


===Events===
===Events===
Line 122: Line 161:
= Discussion Items  =
= Discussion Items  =
* Org Proposal - Matt
* Org Proposal - Matt
* (tchung) How to handle bugzilla tracking of fixed and verified bugs in rapid release branch?  (aurora, beta)
** one idea, is to get BMO to add "verified" to status-firefox-N flag
** We can track them with status-firefox5=fixed and other bugzilla magic: See [https://bugzilla.mozilla.org/buglist.cgi?list_id=343580&field0-0-0=cf_status_firefox5&query_format=advanced&type0-0-0=equals&value0-0-0=fixed example]: where bugs have been marked as fixed in firefox 5. (juanb)
** another, use whiteboards (eg. [verified-in-beta])


= Notes, Takeaways and Action Items  =
= Notes, Takeaways and Action Items  =

Latest revision as of 21:04, 25 May 2011

« previous mtg | QA Staff Home | next mtg »

QA Staff Meeting Notes May 25, 2011

New Hires

Upcoming Test Events

  • Friday, May 27th: Regression-window Bugday (abillings)

Project Status

  • Overview (2 min brief update)

Desktop Firefox (Juan)

Maintenance and Security (Al)

  • Firefox 3.6.18
    • Work is continuing and checkins are occurring more quickly.
    • Still set to release on June 21 with Firefox 5.
  • Firefox 3.5.x
    • There are no more 3.5.x releases. Three cheers. We've done an advertised major update to Firefox 4.0.1 for these users.
  • Firefox 4.0.2
    • There are currently no plans for 4.0.2 unless there is a chemspill. Firefox 5 is the next release for 4.0.1 users.

Browser Technologies (Tony)

  • Issues
  • Fennec (aakash)
    • Expecting builds for MobiFx 5.0 Beta 3 that incorporate backouts
    • Features are landing for 6.0 and QA is beginning testing their features there
    • Nightly is on 7.0a1 now
  • Sync (Tracy)
    • Client train was moved up one day this week (pushed to m-c on Monday) to make sure changes made it for the Aurora merge.
    • Sync hardware outage caused .5% of total users to be affected. Tracked in bug 659399
    • Sync discovery bug 618913 merged to m-c to aurora. However, the main function of linking to information from "Learn More" is broken. That bug 659335 should be fixed shortly.
    • Instant Sync feature, targeted for Fx7, will proceed once devs complete work on DeathToUnknownError
    • Server push for next Monday will be done on Tuesday instead because of the US holiday.
  • Load Testing (Owen)
  • Test pilot (tracy)
    • 1.2 is getting closer with pre6 build, but some minor fixes are still needed.
  • Identity (tracy)
    • Still on security hold.
  • Jetpack(tchung)
    • Handed FlightDeck off to webdevQA
    • No ownership atm for jetpack sdk
  • Firefox Home (nhirata)

WebQA (Stephen)

AMO

  • AMO 6.0.10 went live on 05/19. This release included support for Bulk compatibility check which is a huge deal for the new Firefox release model.
  • AMo 6.0.11 is scheduled for 05/25.

Engagement Projects

Input

Mozilla.com

  • 2.6 milestone shipping next week 5/31

MDN

  • 0.9.5 milestone shipping 6/7

Spark

  • Working on 2.0 milestone which might ship next week

Socorro

SUMO

WebQA Automation

  • Test Day yesterday. Post Mortem on David's blog
  • Waverly helping out with Test day and looking at AMO

AMO

Input

MDN

Mozilla.com

Socorro

  • Matt/David to work through test-template updates for failing tests

SUMO

Community (Marcia)

  • Upcoming Testdays/BugDays/Meetups
  • Video Work
    • Reviewing some footage from Whistler Summit (Marco Zehe Accessibility)
    • Reviewing the "Making Mozilla Better" video with intent of updating the content to match changes in the product.
  • QMO.next (Al):
    • Work in in progress for QMO Site refresh for theme.
    • Meeting with Ryan Snyder on progress and timeline on Thursday.
    • Meeting with Eric Meyer to go over second round of potential Achievement badges for QMO.

Test Automation (Henrik)

General

  • Mozmill Dashboard: Please check the feature list for the dashboard rewrite and add proposals or ask questions
  • Tests / Shared Modules: Henrik is working on getting any issue of the Add-ons API solved as quick as possible - we don't want to block Softvision
  • Shadow Server: Still waiting for the SSL certificates to improve our security tests

Mozmill

  • Mozmill 1.5.4 process is slower but we will get interim beta releases with any important bug fixes which block us from writing tests for the Discovery Pane
  • Mozmill 2 is getting closer; release can happen by end of this quarter

Project updates

API Refactoring (Geo)
  • Owen Coutts has joined project part-time, will be assisting in module refactoring and test porting to help us make our quarterly goal.
Mozmill Tests for the Discovery Pane of the Addons Manager (Anthony)
  • 4 / 10 tests on file are in development
Endurance Tests (Dave)
On Demand Updates (Geo)
  • Problem with daemons hanging overnight has been identified; combo of machine sleeping and inactive socket timeout. Fix is in progress.
  • Otherwise, was successfully used in the 5.0b2 release (yay!)

Events

Discussion Items

  • Org Proposal - Matt
  • (tchung) How to handle bugzilla tracking of fixed and verified bugs in rapid release branch? (aurora, beta)
    • one idea, is to get BMO to add "verified" to status-firefox-N flag
    • We can track them with status-firefox5=fixed and other bugzilla magic: See example: where bugs have been marked as fixed in firefox 5. (juanb)
    • another, use whiteboards (eg. [verified-in-beta])

Notes, Takeaways and Action Items

Today

  • Add notes here

Last Meeting

  • Introductions: Owen started this week. Geo is his mentor. Welcome!
  • Meetup Tonight: Selenium, 6:30pm, more greeters welcome.
  • Go-no-go criteria from QA
    • What will constitute this criteria? (geo) - Work in progress. Draft this week. (juanb)
  • Vacation: Matt, May 28- June 18th
    • Organizational changes in the teams to be articulated before then. (mevans)
  • Scrumpad: We depend on this information day-to-day, and it's becoming more important to others.
    • Leads responsible to update the highlights by Friday.
    • Any other pertinent information like other meetings' notes would be useful
  • Use of Pivotal for tracking purposes. Cameron presented a brief intro to the system he uses to keep track of his projects.
    • Check it out and see if it meets your needs. You are encouraged to use it, and we could make a decision to adopt it in a few weeks. (mevans)
  • Contributor inquiries responses: How do we go forward?
    • Any mail client solution to do automated responses is good for now. (juanb)
    • Figure out an interim solution to this. (juanb, mevans, et al interested)