QA/Execution/Meetings/2009-11-18: Difference between revisions

From MozillaWiki
< QA‎ | Execution‎ | Meetings
Jump to navigation Jump to search
 
(25 intermediate revisions by 6 users not shown)
Line 1: Line 1:
<small>[[QA/Execution/Meetings/2009-11-04|« previous mtg]] | [[QA/Execution/Meetings|index]] | [[QA/Execution/Meetings/2009-12-02|next mtg »]]</small>
<small>[[QA/Execution/Meetings/2009-11-04|« previous mtg]] | [[QA/Execution/Meetings|index]] | [[QA/Execution/Meetings/2010-01-13|next mtg »]]</small>


= Discussion Items =  
= Discussion Items =  
* How are you measuring Quality?
* How are you measuring Quality?
** [https://intranet.mozilla.org/forum/comments.php?DiscussionID=843&page=1#Item_14 Clint's post]
** [https://intranet.mozilla.org/forum/comments.php?DiscussionID=843&page=1#Item_14 Clint/Juan's post]
** Questions to ponder:
** Questions to ponder:
*** Discuss measurable goals within your own project of "quality"
*** Discuss measurable goals within your own project of "quality"
*** Supporting multiple releases is unevitable.  What an we tweak to ease this transition?
*** Supporting multiple releases is unevitable.  What an we tweak to ease this transition?
*** What would extra resources on your project do for you?
*** What would extra resources on your project do for you?
**** '''Discussion'''
**** Project leaders to come up with a list of things working/not working
**** What can be done to improve it?
**** Take the list and how can we create a release criteria
**** Look into a tool for Mining data through hendrix, trending on common words
**** This will help with QA prioritization of projects
**** We are looking for a measurement to assess quality of your projects, then we can collaborate into a common document


* [https://intranet.mozilla.org/QA/Q409 QA allhands agenda]
* [https://intranet.mozilla.org/QA/Q409 QA allhands agenda]
Line 14: Line 21:
* Remote access to Lab Machines (marcia, raymond)
* Remote access to Lab Machines (marcia, raymond)
** update?
** update?
* Crash Kill QA Page
** will be tomorrow sorted for releases for less confusion ;) - Tomcat


= Project Updates =
= Project Updates =
* Firefox 3.0x, 3.5x (abillings)
* Firefox 3.0x, 3.5x (abillings)
** Update?
** We are waiting for last checkin for 1.9.1 (a week late but a regression was found).
** Last 1.9.0 checkins are in.
** First builds for 1.9.1 and 1.9.0 on 11/30. Bug verification until then.
* Firefox 2.0.0.20 to 3.0.15 MU
** Build made bits without warning last Wednesday.
** Al is roughly halfway through MU testing with Rich Profiles.


* Firefox 3.6 (juanb)
* Firefox 3.6 (juanb)
** update?
** Beta3 signoff
** Scheduling for RC coming soon. Resources will be required. High priority.


* Tegra (marcia)  
* Tegra (marcia)  
Line 35: Line 51:


* WebQA (stephend)
* WebQA (stephend)
** update?
** Doing a [https://bugzilla.mozilla.org/show_bug.cgi?id=529600 small AMO push] to address a few regression from AMO 5.3
** Working through [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED;classification=Other;query_format=advanced;bug_status=RESOLVED;component=getpersonas.com;product=Websites;target_milestone=2.0 GetPersonas.com 2.0 bugs]
** Working on [https://wiki.mozilla.org/AMO:Meeting_Notes AMO 5.4]
** Working on [https://wiki.mozilla.org/Support/SUMOdev_Meeting_Notepad#Next_releases SUMO 1.5]


* Weave Sync (tracy)
* Weave Sync (tracy)
Line 43: Line 62:


* Mozmill Testcase automation (henrik)
* Mozmill Testcase automation (henrik)
** update?
** Mozmill 1.3 has been released yesterday (blog post to come by tomorrow)
** Software update tests have been finished ([http://www.hskupin.info/2009/11/18/automated-software-update-tests-with-mozmill/ blog post])
** Current Status [http://spreadsheets.google.com/ccc?key=pAP5Y5AH3-Tl-wRoNgBujUQ&hl=en Spreadsheet]:
*** Smoketests: Blocked (9), Assigned (1), Fixed (23 - 68%), Not Doable (3 - 8%)
*** BFT: Blocked (11), Assigned (14), Fixed (69 - 32%)[+3], Not Doable (26) => Target Q4 (~105)
*** FFT: Blocked (12), Assigned (15), Fixed (80)


* QMO & Community (marcia, aakashd)
* QMO & Community (marcia, aakashd)
Line 62: Line 86:


= Round Table =
= Round Table =
Individuals' ideas of what is and what isn't working as well as ideas on how to improve.
* '''Update''': individual notes have been moved to [https://wiki.mozilla.org/QA/Execution/Meetings/2009-11-18/MeasuringQuality Measuring Quality] page
We'll summarize these and discuss at the next meeting.
#[https://wiki.mozilla.org/QA/Execution/Meetings/2009-11-18/MeasuringQuality aakash]
#[https://wiki.mozilla.org/QA/Execution/Meetings/2009-11-18/MeasuringQuality abillings]
#[https://wiki.mozilla.org/QA/Execution/Meetings/2009-11-18/MeasuringQuality juanb]
#[https://wiki.mozilla.org/QA/Execution/Meetings/2009-11-18/MeasuringQuality henrik]
#[https://wiki.mozilla.org/QA/Execution/Meetings/2009-11-18/MeasuringQuality marcia]
#[https://wiki.mozilla.org/QA/Execution/Meetings/2009-11-18/MeasuringQuality tchung]
#[https://wiki.mozilla.org/QA/Execution/Meetings/2009-11-18/MeasuringQuality timr]
#[https://wiki.mozilla.org/QA/Execution/Meetings/2009-11-18/MeasuringQuality tracy]
#[https://wiki.mozilla.org/QA/Execution/Meetings/2009-11-18/MeasuringQuality et al]

Latest revision as of 17:36, 29 January 2010

« previous mtg | index | next mtg »

Discussion Items

  • How are you measuring Quality?
    • Clint/Juan's post
    • Questions to ponder:
      • Discuss measurable goals within your own project of "quality"
      • Supporting multiple releases is unevitable. What an we tweak to ease this transition?
      • What would extra resources on your project do for you?
        • Discussion
        • Project leaders to come up with a list of things working/not working
        • What can be done to improve it?
        • Take the list and how can we create a release criteria
        • Look into a tool for Mining data through hendrix, trending on common words
        • This will help with QA prioritization of projects
        • We are looking for a measurement to assess quality of your projects, then we can collaborate into a common document
  • Remote access to Lab Machines (marcia, raymond)
    • update?
  • Crash Kill QA Page
    • will be tomorrow sorted for releases for less confusion ;) - Tomcat

Project Updates

  • Firefox 3.0x, 3.5x (abillings)
    • We are waiting for last checkin for 1.9.1 (a week late but a regression was found).
    • Last 1.9.0 checkins are in.
    • First builds for 1.9.1 and 1.9.0 on 11/30. Bug verification until then.
  • Firefox 2.0.0.20 to 3.0.15 MU
    • Build made bits without warning last Wednesday.
    • Al is roughly halfway through MU testing with Rich Profiles.
  • Firefox 3.6 (juanb)
    • Beta3 signoff
    • Scheduling for RC coming soon. Resources will be required. High priority.
  • Tegra (marcia)
    • Tested Firefox 3.6 B3. Results on wiki
    • Continued testing of nightly builds
    • Still many issues with Flash not playing on various sites
  • Fennec (aakashd)
    • Next Fennec-related Testday will be on 12/4 on Weave Beta
    • Began planning for fennec quality in 2010
      • Planning on adding a bunch of components within Fennec Product (nothing finite as of yet) for Bugzilla
    • String Guide for localizers on Litmus
    • Dougt mentioned spec testing for geolocation for Opera
  • Weave Sync (tracy)
    • Weave 1.0b1 released
    • creating test cases for Litmus
    • Weave testday scheduled for Dec. 4th
  • Mozmill Testcase automation (henrik)
    • Mozmill 1.3 has been released yesterday (blog post to come by tomorrow)
    • Software update tests have been finished (blog post)
    • Current Status Spreadsheet:
      • Smoketests: Blocked (9), Assigned (1), Fixed (23 - 68%), Not Doable (3 - 8%)
      • BFT: Blocked (11), Assigned (14), Fixed (69 - 32%)[+3], Not Doable (26) => Target Q4 (~105)
      • FFT: Blocked (12), Assigned (15), Fixed (80)
  • QMO & Community (marcia, aakashd)
    • Testdays
    • Meetups
      • No meetup this month, will resume in December.
      • Have ideas for two upcoming meetups: Weave and Mobile
  • Accessibility (marcoz)
    • Still fighting top crashers as in bug 525579. That bug is fixed in principal, but had a few logic errors that needed folllow-up bug 529442 which we're dealing with now.
    • Also tracking and fixing other bug reports that were harvested from the new analysis tools. These are a huge help!
  • QA Metrics ( Murali )
    • Gap analysis report is almost ready.
      • New report includes codecov% from Linux,Mac , Reg bugs, Sec bugs, Gen bugs and patchsets for each file.

Round Table

Individuals' ideas of what is and what isn't working as well as ideas on how to improve.

We'll summarize these and discuss at the next meeting.

  1. aakash
  2. abillings
  3. juanb
  4. henrik
  5. marcia
  6. tchung
  7. timr
  8. tracy
  9. et al