QA/Meetups/Results

QA meetup Testing Results, 4/22/09

Attendees

Please list your name and email address so we can properly credit you for finding issues!

• marcia, marcia@mozilla.org
• craig, reg . mozilla at excel4x . com
• Cheng (Cww) cwang@mozilla.com <-- E-mail me about anything that should get documentation or that new Firefox or Firefox 3.5 users might want to know about or if anything was confusing about 3.5.
• Jefferson Scher (jscher2000), 20 tests with no serious problems!
• Mark Wong (markwong.mtw@gmail.com), 9 tests without major problems
• dean, dean@sos.com, 11 tests with problems noted
• Vijay, vijay.bulusu@yahoo.com - 10 tests on cookies with no problems.

                               - Memory leak. Started at around 40M and ended 100M

• Dwi Taniel (dwichandra -> dc@dwichandra.info), 20+ tests no problem. But, before running the tests, I experienced a one-timer crash when switching from private to non-private browsing. Well done folks! I surely will attend the next meetup (and any marketing meetup)

Bugs Filed in Bugzilla

• https://bugzilla.mozilla.org/show_bug.cgi?id=489753 - Crash when going from private browsing to non-private browsing

Issues noted

craig: running AVG 8.0; surf safe add-in manager does not show updates but with surf safe enabled, cannot type in URLs; clicking on existing URLs works; known: bug 475653

craig: when installing new build 3.5b4, if firefox is already running, installer reports that Shiretoko is already running, but does not clearly advise as to how to proceed or offer to close application. Also, Shiretoko was not running, firefox 3.0 was running - so this is confusing

craig: error console reports: (not sure what page causes this) Error: document.getElementById("twitter_update_list") is null Source File: http://twitter.com/javascripts/blogger.js Line: 1

craig: Error: Permission denied for <http://uac.advertising.com> to call method Location.toString on <http://www.amazon.com>.

dean: On Linux, starting private browsing causes the location bar to end up blank rather than showing "about:privatebrowsing". bug 486858

dean: On Mac OSX, if Firefox crashes during a private browsing session, when Firefox is restarted, the previous session (not private browsing) is restored, but the cookies from the private browsing session have not been removed and are persistent and still available to a new private browsing session. I don't know the desired behavior in this instance.

Comments about event

Awesome!