QA/Execution/Meetings/2008-05-15: Difference between revisions

From MozillaWiki
< QA‎ | Execution‎ | Meetings
Jump to navigation Jump to search
 
(7 intermediate revisions by 2 users not shown)
Line 5: Line 5:
** No current hendrix-type feedback in place now
** No current hendrix-type feedback in place now
** Right now, for branch, we have to scour mozillazine, newsgroups, QMO, and blogs to look for feedback.
** Right now, for branch, we have to scour mozillazine, newsgroups, QMO, and blogs to look for feedback.
*** '''Discussion''' - some users dont know they're on the beta.  some solutions, funnel through newsgroup, or goto a webpage that sniffs your UA string, and fill out a form.


* EV server update (marcia)
* EV server update (marcia)
Line 10: Line 11:
** '''Marcia''' to follow up with Bob lord to figure out final requirements
** '''Marcia''' to follow up with Bob lord to figure out final requirements
*** Possibly a security testing summit?
*** Possibly a security testing summit?
*** '''Discussion''' - havent heard back from bob lord, '''(marcia)''' to follow up with IT after fx3.


* need a litmus server to throw permanent testcases against it ('''Stephend / Coop''' to figure out specs)
* need a litmus server to throw permanent testcases against it ('''Stephend / Coop''' to figure out specs)
Line 20: Line 22:
** We need another machine?  Figure out source code control.
** We need another machine?  Figure out source code control.


* Operating system coverage (marcia)
** Seems like there are still missing OS coverage that can hinder us from complete testing.  (eg. No one has Vista Ultimate, so parental controls is untested)
** How do we tackle every scenario accounted for?
** '''Discussion''' - for os's, just ask IT.  For a special case where you need hardware (eg. Vista ultimate), then we can make a special request.


* Limited bandwidth and proxy testing (jay, tomcat)
* Limited bandwidth and proxy testing (jay, tomcat)
Line 31: Line 37:
*** This will be a partial signoff by QA, to pre-launch for beta community
*** This will be a partial signoff by QA, to pre-launch for beta community


* Fx 2.0.0.15 update (al)
* TB / Fx 2.x update (al)
** No decision on re-spin for TBird issue - impact is not clea
** June 24th is planned release. Testing June 10th


* Leak testing update (tomcat)
* Leak testing update (tomcat)
** Leaks: Filed last week 11 new Leak Bugs .http://tinyurl.com/69dtkr -> Total Leak Bugs so far: 275
*** [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=mlk+reporter%3Acbook Open Buglist]
*** No new 1.9 blocking Bug, but a lot of Bugs related to Extensions, found also a leak in Prism [https://bugzilla.mozilla.org/show_bug.cgi?id=432545 (nsGlobalWindows Leak)]
** Assertions: Filed so far 67 (+4) [http://tinyurl.com/2urfa7 Assertion Bugs]
*** Teamwork with Devs is very effective :) see {{Bug|433374}} , fix within a day :)
** Extension JS Errors: Filed so far 43 (+5) Bugs for [http://tinyurl.com/5rnohg JS Errors/Exceptions] caused by Extensions. This Errors/Bugs are more a side effect of the Leak Testing and [https://bugzilla.mozilla.org/show_bug.cgi?id=433357#c1 Comments] show that this Bug Reporting is still useful to fix JS Error Messages in Extensions :)


* Webdev update (stephend)
* Webdev update (stephend)
Line 48: Line 62:
*** 7am-11am '''(Tomcat / Martijn)'''
*** 7am-11am '''(Tomcat / Martijn)'''
*** 11am-1pm (overlapping testers)   
*** 11am-1pm (overlapping testers)   
*** 1pm-5pm '''(Marcia / Tchung)'''
*** 1pm-5pm '''(Marcia / Tchung/Tomcat)'''


-----
-----
Other topics?
Other topics?
* Those on Ubuntu 8.0.4, running Fx Rc1, will have issues with addons. No addons offered are compatible. [marcoz]
** {{Bug|433371}} is marked for relnotes.  There is a workaround, but requires rebuilding the extensions.rdf file.

Latest revision as of 18:34, 15 May 2008

« previous mtg | index | next mtg »

Discussion Items

  • Central Feedback system for branch (abillings)
    • No current hendrix-type feedback in place now
    • Right now, for branch, we have to scour mozillazine, newsgroups, QMO, and blogs to look for feedback.
      • Discussion - some users dont know they're on the beta. some solutions, funnel through newsgroup, or goto a webpage that sniffs your UA string, and fill out a form.
  • EV server update (marcia)
    • Past discussion: IT setup server, Juanb setup the app
    • Marcia to follow up with Bob lord to figure out final requirements
      • Possibly a security testing summit?
      • Discussion - havent heard back from bob lord, (marcia) to follow up with IT after fx3.
  • need a litmus server to throw permanent testcases against it (Stephend / Coop to figure out specs)
    • Past discussion: Need some static tests for storage
    • Three things:
      • A) coop has set up a repo at mozilla/webtools/litmus/testcase_files, which gets mirrored out to https://litmus.mozilla.org/testcase_files/
      • B) Just need to come up with a directory structure within this (not sure this is the right time to have a meeting for this), and then each do C, below:
      • C) We'll need to all get CVS checkin access to this repository (to land--shouldn't have just a few people responsible for landing testcases, I don't think?), but that's an easily filed IT bug (per person). -- stephend
    • Eggplant tests need to be ran here also. currently running off bc's box
    • We need another machine? Figure out source code control.
  • Operating system coverage (marcia)
    • Seems like there are still missing OS coverage that can hinder us from complete testing. (eg. No one has Vista Ultimate, so parental controls is untested)
    • How do we tackle every scenario accounted for?
    • Discussion - for os's, just ask IT. For a special case where you need hardware (eg. Vista ultimate), then we can make a special request.
  • Limited bandwidth and proxy testing (jay, tomcat)
    • bug 23459 - (squid) – install a WWW-proxy (squid 2.0) that can be used to limit bandwidth
    • Choffman asking for more proxy testing, bandwidth throttling. Who to drive this?

Project Updates

  • Firefox 3 (tchung)
    • RC1 testing
      • Targetting early release on friday, 5/15
      • This will be a partial signoff by QA, to pre-launch for beta community
  • TB / Fx 2.x update (al)
    • No decision on re-spin for TBird issue - impact is not clea
    • June 24th is planned release. Testing June 10th
  • Leak testing update (tomcat)
    • Leaks: Filed last week 11 new Leak Bugs .http://tinyurl.com/69dtkr -> Total Leak Bugs so far: 275
    • Assertions: Filed so far 67 (+4) Assertion Bugs
      • Teamwork with Devs is very effective :) see bug 433374 , fix within a day :)
    • Extension JS Errors: Filed so far 43 (+5) Bugs for JS Errors/Exceptions caused by Extensions. This Errors/Bugs are more a side effect of the Leak Testing and Comments show that this Bug Reporting is still useful to fix JS Error Messages in Extensions :)
  • Webdev update (stephend)
  • Community update (jay)
    • Working with legal to finalize contract with http://www.advomatic.com/, who will be working on the QMO2 development project, hopefully starting before end of May.
    • Organizing QMO2 content creation project, be ready to sign up for sections of the site to gather and write content. I will be using basecamp to track progress.
    • Finishing betatesters survey design/setup, will be going live early next week.
  • Testday this week on RC1 Part 1 (tchung) is the topic moderators this week.
    • Moderator rotation list
      • 7am-11am (Tomcat / Martijn)
      • 11am-1pm (overlapping testers)
      • 1pm-5pm (Marcia / Tchung/Tomcat)

Other topics?

  • Those on Ubuntu 8.0.4, running Fx Rc1, will have issues with addons. No addons offered are compatible. [marcoz]
    • bug 433371 is marked for relnotes. There is a workaround, but requires rebuilding the extensions.rdf file.
Retrieved from "https://wiki.mozilla.org/index.php?title=QA/Execution/Meetings/2008-05-15&oldid=93451"