QA/Execution/Meetings/2008-01-10: Difference between revisions

no edit summary
(New page: <small>« previous mtg | index | next mtg »</small> == Meeting Agenda: == * [https://b...)
 
No edit summary
 
(10 intermediate revisions by 4 users not shown)
Line 1: Line 1:
<small>[[QA/Execution/Meetings/2007-12-20|« previous mtg]] | [[QA/Execution/Meetings|index]] | [[QA/Execution/Meetings/2007-12-20|next mtg »]]</small>
<small>[[QA/Execution/Meetings/2007-12-20|« previous mtg]] | [[QA/Execution/Meetings|index]] | [[QA/Execution/Meetings/2008-01-17|next mtg »]]</small>


== Meeting Agenda: ==
== Meeting Agenda: ==
* [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=qawanted&resolution=---&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&known_name=1.9a1%2B&query_based_on=1.9a1%2B&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking1.9%2B&field0-0-1=flagtypes.name&type0-0-1=equals&value0-0-1=blocking-firefox3%2B 19 qawanted bugs] for Fx3 (tchung) 
* Fx3 update (tchung)
 
** Open Issues needing updates.  See [http://wiki.mozilla.org/Firefox3/StatusMeetings/2008-01-08#Status_of_Key_Areas_to_wrap_up_for_final_ship schrep's list]
 
** [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=qawanted&resolution=---&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&known_name=1.9a1%2B&query_based_on=1.9a1%2B&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking1.9%2B&field0-0-1=flagtypes.name&type0-0-1=equals&value0-0-1=blocking-firefox3%2B 19 qawanted bugs] for Fx3  
** [http://wiki.mozilla.org/QA/Firefox3/TestPlan#Top_Critical_issues_for_QA Top critical issues] tracking in QA
** [http://wiki.mozilla.org/QA/Firefox3/TestResults/M11 b3 testplan] in the works.


* [https://intranet.mozilla.org/QA#Q4_2007_Goals Q4 QAE goals] update? (timr)
* Firefox 2.0.0.12 update (al)
** '''UPDATE''' - Targeting jan 29th for beta
** Thunderbird is not scheduled at the moment.  (late feb is the plan)


* Fx3b2 Post mortem feedback (tchung)
* AMO update (stephend)
** '''UPDATE''' - john duinn to send out notes
** No update yet from morgamic, since yesterday's meeting status.  
** meeting will be at 1pm PST.  posted shortly.
** Tentative date for release - mid to late february
* Fx3 update (tchung)
** [http://wiki.mozilla.org/QA/Firefox3/TestPlan#Test_Areas Testplans]complete them by Q4
*** '''UPDATE''' - '''timr''' and '''tchung''' gathered verbal status on testplan.  will roll up a summary in the next firefox meeting.
*** '''martijn''' will add a testplan for Gecko test cases.


** [http://wiki.mozilla.org/QA/Firefox3/TestPlan#Review_Feedback Feedback Rollup page]
* Leaks update (tomcat)
** Ownership needed to develop test cases for Breakpad [marcia]
** [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=mlk+reporter%3Acbook Leaks found so far]
***Email sent regarding the issue but no feedback was received. Currently we should ensure before we ship that breakpad is not only installed but that it fires and that data ends up on the server. The Win Vista issue surfaced very late in the game for Beta 2, and as a result we will not have any crash feedback for that OS until someone figures out what is going on in that bug.
** create a page on devmo, on how to test leaks
**** '''DISCUSSION''' - '''sam''' to add testcases on ways to include tests for breakpad into litmus.  Will disable these tests from community.
** filming of video on how-to test for leaks for the community.   This will be done on the onsite (ran by choffman)


* TB 1.5.0.14 update (al)
* Betatesters update (jay, marcia)
** '''UPDATE''' - shipped on wed.  no plans for major updates yet.
** plans to leverage for the branch release
** Firefox 2.0.0.12 - targeting end of jan
** what is the plan for beta 3?  (jay to work on that)


* Leak Update
* [http://quality.mozilla.org/en/node/1243 Testday topic] this week on Download manager.  Please be around to assist.  (tomcat)
** '''UPDATE''' - filed 5 new leak bugs to dev teamOver the holiday, will do more testing.
** '''DISCUSSION''' - Next week, we should focus on Places.  Specifically, tagging feature.  UI issues still need addressingIdea is to get people to play with tagging more, but get eyeballs.
*** Need more instruction to users to get people to do more tagging.   (eg. converting bookmark folders to tags)


* Litmus cleanup update for Fx 3.0 (tracy)
* inLitmus? Bug Nominations - Getting test cases made for FIXED and VERIFIED bugs before next triage session (marcia)
** '''UPDATE''' - Completed restructured 3.0 areas.  eg. collaborated security tests
** Current query is here: http://tinyurl.com/2fgk9n
** cleaned up FFTs and BFTS
** '''DISCUSSION''' - be sure to go through your list and create testcases before B3 if possible.
** '''litmus admins''': keep up your feature area clean.  If you have a massive change (eg. string for Places Organizer), ask coop to change it in the backend.
** Talk to clint to see what areas of content handling are left uncovered ('''tchung''')


* Discuss bugzilla component for litmus?
* Moving relevant new test cases from FFTs to BFTs if needed (marcia)
** From coop, "Note that I'm not advocating this new component for one-off testcase writing for specific bugs, but rather for instances (e.g. Places) where we need to come up with testcases for entire feature areas.  In the interim, I've started assigning testcase-content-related to '''qa@mozilla.bugs'''."
*** '''DISCUSSION''' - could be more overhead for QAE.  unsure how this is going to be a benefit to our team for now.  Not realistic for tracking individual testcases, but no one is fully convinced why this is going to be used for.


* [http://wiki.mozilla.org/QA/Community/Betatesters_Mailing_List Betatesters alias] update (jay, marcia)
* Litmus testcase tagging (tracy)
** '''UPDATE''' - article is picked up on the press. 56 people signed up. great work guys!
** '''UPDATE''' - coop's design spec [http://wiki.mozilla.org/Litmus:Design#Testcase_Tagging here]


* Testday this week on trunk (tomcat)
* Onsite work week topics for QAE?
** '''UPDATE''' - '''jay''' followed up with top testday members, and pinged them
** Leak testing demo including how to setup debug builds (tomcat)
** '''UPDATE''' - demo firing off eggplant runs (tracy)
** in-litmus triage for team (marcia)


* Vacations.  (Update the Mozilla calendar)
-----
-----
* Other topics?
* Other topics?
* Which QAE time work for everyone?  '''UPDATE''' - lets try for 11am again
Confirmed users
6,361

edits