OOPP and Responsiveness

OOPP is coming together nicely and as we move from finding basic problems like crashes and hangs, I'd like for us to take a look at little look at performance. We don't have a clear way to compare performance between Firefox 3.6 and the 1.9.3a3pre nightlies, for example, when using plugins, but if there's any perceived change in responsiveness I would like your help in calling it out. Just to remind you, OOPP works in Windows and Linux trunk nightlies. So far our testing has involved trying out sites with popular plugins to see if they crash and checking what the user interaction i

Mozilla QA account on AMO?

Hey All, Quick question, but is there a reason why we don't use a Mozilla QA account on AMO for any of our extensions ? I'd like to create one and post it as an author if possible. Thanks, Aakash

Documentation for Shared Modules now available

Hi, For everyone who is working with Mozmill and uses our Shared Modules I will have good news. In the last couple of days I was working to get a complete documentation for all of our existent Shared Modules. It was quiet a lot of work but now we have some shiny pages with good explanations for each of the classes and helper functions. Bookmark the following URL to have it always handy: https://developer.mozilla.org/en/Mozmill_Tests/Shared_Modules Cheers, -- Henrik Skupin QA Execution Engineer Mozilla Corporation

Bugday for regressionwindow-wanted keyword on Feb. 25, 2010

Please join Mozilla QA for a Bugday for regressionwindow-wanted keyword on Feb. 25, 2010 (9:00am PST - 3:00pm PST) 1) Teach the Mozillla QA Community how to find and address bugs with "regressionwindow-wanted" keyword requests 2) As a community, significantly reduce the number of open "regressionwindow-wanted" requests for Firefox product Please see details at https://wiki.mozilla.org/QA/Community/Bug_Day/Feb_25_2010 Hope to see you there, Tracy

qawanted Bugday on Feb. 11, 2010

Please join Mozilla QA for a qawanted Bugday on Feb. 11, 2010 (9:00am PST - 3:00pm PST) It's been a while since Mozilla QA as hosted a Firefox bugday. We want to see if getting these rolling again is a worthwhile effort. I believe successful Bugdays are two-fold: 1) Teach Mozillla QA Community members how to do whatever task is at hand for that session such that individuals feel comfortable and confident doing that task at their leisure in the future. 2) As a group, significantly reduce the number of open bugs in the list we're working on for that Bugday session. Hope

Testdays this Week: Out of Process Plugins

Greetings! Please join us this Tuesday, Wednesday and Friday between 9am and 1pm (PDT) when we will be holding multiple testdays to test out-of-process plugin support which has landed recently on the nightlies on Windows and Linux. We want to iron out as many wrinkles as possible as we prepare to include this feature in the near future. You'll find a testing guide with instructions here: https://wiki.mozilla.org/Plugins/OOPP_Testing What: OOPP (out of process plugins) Testdays When: Tuesday <http://quality.mozilla.org/events/20http://quality.mozilla.org/events/2010/feb/09/te

News about Mozmill testing

Hi, I want to give a short heads-up about ongoing work for Mozmill tests for Firefox in the Mozilla QA group. Anyone who is interested can read through the following two articles: * We run daily Mozmill tests against the latest versions of Firefox: http://www.hskupin.info/2010/01/29/daily-automated-mozmill-test-runs-in-the-qa-lab/ * FOSDEM takes place next weekend in Brussels (Belgium). Everyone who has interests can join my talk: http://www.hskupin.info/2010/02/01/mozmill-talk-at-fosdem-2010/ Best, -- Henrik Skupin QA Execution Engineer Mozilla Corporation

Running of Tests on SeaMonkey2.0 Split Up

[Re-posting http://home.kairo.at/blog/2010-01/running_of_tests_on_seamonkey2_0_split_u to newsgroups] One thing is closely following after the other, now that I have synched up even the master configuration the the SeaMonkey buildbots with what Firefox has. First I got L10n nightlies triggering again (and in a much better way, actually), then they did even gain automated updates, and after that I started experimenting with running what we call "packaged tests". What that means is that all files for running our test suites get packaged up and uploaded to FTP, from where a

Automated Updates for Localized SeaMonkey Trunk Nightlies

[re-post of http://home.kairo.at/blog/2010-01/automated_updates_for_localized_seamonke - FYI] I've been working on this for a few days now - and with some teak of last night it finally started working: Localized nightlies for SeaMonkey "trunk" (i.e. those from http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-comm-central-trunk-l10n/) now get automated updates, just like the US English ones do! Of course, you'll only get an update if one is available, but string changes in Mozilla or SeaMonkey areas should not pose problems, our build system "merges" locali

Firefox 3.6 Launch Thursday

Hi everyone, Firefox 3.6 is officially shipping Thursday morning, and I just wanted to thank all of you who have been helping to make this possible especially on the QA side of things, from attending our regular test days, confirming bug reports and reporting new problems to helping us spot check the beta releases. I look forward to the positive reviews on Firefox 3.6 and to your continued participation in the project as we move on to the next version of Firefox. Thank you! juanb Mozilla QA

Fwd: Firefox Lorentz Coordination Meeting: Wed Jan 13 @ 1PM PT

FYI, In case you missed this note.. For anyone interested in electrolysis updates, weekly meetings will begin this wednesday. Update your calendars. Tony -------- Original Message -------- Subject: Firefox Lorentz Coordination Meeting: Wed Jan 13 @ 1PM PT Date: Mon, 11 Jan 2010 17:12:05 -0500 From: Benjamin Smedberg <benjamin@smedbergs.us> Newsgroups: mozilla.dev.planning,mozilla.dev.tech.plugins Followup-To: mozilla.dev.planning We are going to hold a weekly Firefox Lorentz coordination meeting on Wednesday at 1PM PT (2100 UTC). The purpose of these meetings is to coord

Fx3.6 RC1 Testing

This is it. This will be the first release candidate for Firefox 3.6. Builds are being generated and we should have them ready to test by tomorrow morning, Pacific time. The release approach hasn't been officially agreed upon, but I think we are going to release to beta users after a short cycle, and during this beta period we will be completing more extensive tests. The tentative time-line is as follows: * Build team generates builds overnight (Jan 5) * Builds and updates available by *Wednesday morning (Mountain View time) * * Spot checks start as soon as builds are ready

Thunderbird Bugzilla Triage day Thursday 2010-01-07

Dear contributors, and contributors wannabe to the Calendar, Seamonkey and Thunderbird projects, The Thunderbird QA team is hosting a online "virtual" event in order to keep the bug database in shape. The idea is to read bugs, ask questions on the bugs. Make sure the bug is filed in the right component etc .... We are having a event to make it easier for people who want to participate to be able to, so they'll find people online to help them, answer the questions new comers might have. To participate you'll need : * an account on bugzilla (1) * a web browser (2) * time Ta

Firefox Mobile Meetup in Mt. View - January 13, 2010

Please join us for our first meetup of the New Year - you can read all the details here: http://quality.mozilla.org/events/2010/jan/13/firefox-mobile-meetup-mountain-view-january-13-2010 Please RSVP to marcia@mozilla.org if you plan on attending. Thanks!

QMO landing page needs an update

While talking with Tomcat some days ago he pointed me to the new getting involved page on mozilla.org. There are a couple of new users who were coming via this page to QMO. Sadly our landing page is outdated and we should really update its content to reflect our current work and major project. Please check the following bug for ongoing work and a discussion: https://bugzilla.mozilla.org/show_bug.cgi?id=534231 Henrik -- Henrik Skupin QA Execution Engineer Mozilla Corporation

Testday for Seamonkey 2.0 next Friday, December 11th!

The MozQA community is holding a Testday on Friday, December 11th, for users interested in the use, development and/or testing of Seamonkey 2.0! We're going to have Robert Kaiser, the lead for SeaMonkey available to help users test the new project, learn how to report out the results of the tests and just generally chat about the project with the community via IRC Chat (channel #testday on irc://irc.mozilla.org). So, if you're interested, come on by anytime between 7AM to 5PM PDT that Friday! For more information, please go to http://quality.mozilla.org/events/2009/dec/11/testday-te

Official Fennec Repository for Maemo Users

Hey Mozilla QA Community, The Release team has set up a repository system for nightly versions of fennec! If you're interested in getting a nightly update on your maemo-powered devices, take a look at the following blog post to get set up: http://stechz.com/2009/official-fennec-repository-available-for-n900/ Thanks, Aakash

ff mouse wheel problem

Hi, I have encountered a firefox problem over the last few releases of fedora linux. I switched to slackware and the problem is not prevalent. Now I try Mandriva and I can see the same problem. Here goes (current setup Mandriva 2010 free, Gnome desktop and ff 3.5.3, PC sharing KVM switch with other PCs): I access a website and I click onto a link. I scroll down the page. When I use the mouse wheel to scroll back up I am expecting just that. However the results are unpredictable. Most times the mouse wheel action is similar to pressing the BACK button and the browser returns to the pr

Firefox 3.6 Beta revision 3 testing

We are looking for volunteers to help us spot check these candidate builds. We have a wiki page ready where you can sign up for some of the tasks. It should be a short QA cycle involving spot checks across platforms as well as updates checks. We are hoping to finish all of these tests by tomorrow (Tue) noon, so we can ship by the evening. https://wiki.mozilla.org/Releases/Firefox_3.6Br3/Test_Plan Let us know if you can participate or if you have any questions. juanb Mozilla QA

QA Status Notes - 11/11/2009

QA status notes this week: http://quality.mozilla.org/blogs/qa-meeting-notes-11112009

Debugging tp4 freeze?

How can I debug a freeze on tp4? __FAILbrowser frozen__FAIL on Windows: http://tinderbox.mozilla.org/showlog.cgi?log=MozillaTry/1257945362.125794 6499.9099.gz&fulltext=1 unrecognized output format on Linux without any usual cycle output: http://tinderbox.mozilla.org/showlog.cgi?log=MozillaTry/1257944443.125794 5140.24069.gz&fulltext=1 -- Henri Sivonen hsivonen@iki.fi http://hsivonen.iki.fi/

Fwd: Firefox 3.6b2 build1 - linux, mac, wince, and signed win32 builds available

We have builds available for testing. If you have time to help out spot check this ASAP please sign up in the wiki: https://wiki.mozilla.org/Releases/Firefox_3.6Br2/Test_Plan#Test_Results The intention is to complete these tasks by today. Let me know if you have any questions as to how to participate. juanb -------- Original Message -------- Subject: Firefox 3.6b2 build1 - linux, mac, wince, and signed win32 builds available Date: Sun, 8 Nov 2009 23:05:10 -0800 (PST) From: Nick Thomas <nthomas@mozilla.com> To: release-drivers <release-drivers@mozilla.org> Sign

Firefox 3.6 Beta revision 2 testing

We will be spinning Firefox 3.6 Beta revision 2 candidate builds within the next day or so. We are looking for volunteers to help us spot check these builds. Please take a look at the following wiki page where you can sign up for some tasks: https://wiki.mozilla.org/Releases/Firefox_3.6Br2/Test_Plan#Test_Results This will be a short QA cycle involving mostly spot checks across platforms as well as some updates checks. Let me know if you can participate or if you have any questions. juanb Mozilla QA

Mobile QA: Fennec Beta 5 Candidate Builds are Available and being Tested

Hey All, The Fennec QA team has begun testing candidate builds for Fennec Beta 5. For those that are interested in checking out the builds, head over to http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mobile-1.9.2/ and download/install the following builds on your n810's and n900's: fennec_1.0b5_armel.deb xulrunner_1.9.2b2pre-20091104071136_armel.deb To follow what the Fennec QA team is doing for the next couple of days, take a look at: https://wiki.mozilla.org/QA/Fennec1.0/ReleaseTest/1.0Maemo_Beta5 Thanks, aakashd

Results from 2-day Mozmill Testscripting Testday

The Mozilla QA Community came out in full force again for both days of our unprecidented 2-day testday event. This was the first time we have ever tried to run a test day spanning 48 hours. The test day itself was preceeded by a Mozmill Workshop taught by myself at Seneca College on Friday. We had a few new faces as well as some returning community members help out. Here are the highlights: * Had a max of 33 people in the testday channel at its peak * Major contributors include Aleksej, Mavericks, christine, merike, AaronMT, palan, and gmccreight * 12 Bugs filed (htt

Self correcting software :: Do we know about it ?

Please read http://www.technologyreview.com/computing/23821/ They seem to have tested this on Firefox. Has any one know more details ? Thanks Murali

Need help repro'ing bug 509560 for Firefox 3.6!

We need help reproducing a bug from anyone with a few moments. The bug is 509560. It involves the crash reporter having a problem sending the crash report to the server. We need to find additional flash crash test cases and see if the crashes get reported. Looks like we can also use crashme on certain flash pages and maybe see the problem. This is a major concern related to the 3.6 release. Any hep would be greatly appreciated!

In-litmus flags for SUMO and AMO now available

We now have |in-litmus| flags for bugs needing testcases in both the SUMO (support.mozilla.com) and AMO (addons.mozilla.org) projects; flag away! To use: simply flag as |in-litmus?| if you're unsure whether a test exists; we'll triage and either add a comment (preferably with a Litmus testcase ID #), and/or flag it as + or -, depending on whether a test exists or is not needed, respectively. (Sprinkle liberally - probably coming soon for other projects too (the ongoing ones)) - Stephen

Proposal: Changing the way we handle Not Doable Mozmill test scripts

Hi folks, Whimboo and I chatted back and forth about how we currently handle/track not-doable test scripts in Mozmill. Specifically, we were talking about the "File | Save Page As | Web Page Complete" test. This test is considered not-doable because Mozmill has no way to access system-level dialogs at the moment. The way we currently track progress is with a Google Spreadsheet. This spreadsheet basically assigns a bug number to a test case ID. However, in the case of not-doable tests, we simply don't file a bug on it and mark it as not-doable in the spreadsheet. Whil

Meetup Reminder: Open Mike with Mozilla Interns

When: Wednesday, October 28, 2009 @ 6:30pm Where: Seneca College, York University Campus (room T1009), Toronto, ON This event is a meet-up of sorts. Many of you may already be aware of the Mozilla Meet-up format. For the benefit of those who have not experienced a Mozilla Meet-up, it basically involves a group of people (large, small, from varying backgrounds) getting together to discuss a particular topic. It usually begins with some sort of presentation followed by a free-for-all Q&A session. My meet-up will be no different. As the name implies, we'll be having an open discussi

How to sync Mozmill tests with Litmus testcase additions, updates, and removals

Hi, Now that we are updating a lot of Litmus tests especially for the 3.6 release I would ask everyone who adds, changes, or removes a litmus test to inform me about this action so I can sync our Mozmill scripts with the current Litmus status. When we do not start that we will end up in a complete mixture of covered and uncovered areas. It's really hard for me to discover this information from the daily reports because they still miss two important rows (product, subgroup) for test updates and which makes my life hard to check each day. Please think about our automation process

3.6b1(build2) plan for today

We are nearly done with the smoke tests, and we should spend today and tomorrow with the BFTs. At the moment no one has signed up for the BFTs from what I can see in the wiki. Reply to this email asap if you can help with these. https://wiki.mozilla.org/Releases/Firefox_3.6b1/Test_Plan If you can't commit to spending a few hours on the BFT, you can help out with l10n spot checks and top add-ons testing, for example. We'll be on #qa to answer any questions. juanb Mozilla QA

SeaMonkey 2.0 RC2 pre-testing - help wanted!

Hi everyone, The next step is done and now we have SeaMonkey 2.0 RC2 builds available, with updates being live on the betatest channel. We hope this will be the final RC, and would be happy about another fast round of testing them before we push the builds out to a wider range of people on the beta channel. All builds are available in 20 languages including US English, the packages are available in the win32, mac, and win32 subdirectories of http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/2.0rc2-candidates/build2/ Please use the builds for any usage patterns you c

Community QA mail list?

Should we have a community oriented qa or testing mail list? From time to time we considered making qa@m.o an open list. But generally this was a hypothetical question. Currently there are some sensitive conversations that happen on qa@m.o Now we have at least one community member that would like to be more involved including being part of email exchanges between testers. We have some precedence for this, like the mozwebqa mail list. On the other hand, many teams use the news groups/google groups for this and don't have a mail list. So... options: 1) Make qa@m.o ope

New QA Activity Reports on QA dashboard

Hello MozQA, Please go to the URL http://people.mozilla.com/~mnandigama/dashboard.html and please check the 'QA' link in the "QA Bug Activity" section of the Left Navigation bar. After you click the 'QA' link, you would be presented with a bunch of graphs and links below the graphs. The graphs are generated by QA engineer. For each QA engineer, you will see TWO graphs. The TOP graph shows the counts of blocker and non-blocker bugs filed by the QA engineer starting from -24 Weeks till this week, grouped by week. The BOTTOM graph displays the count of comments made by QA

3.6 pre not working with GMX

Can't log into my GMX.com account.

Testday Reminder: Reporting Website Compatibility with Fx3.5 this Week!

Hey Mozilla Community! Our second website testing project test day event of 2009 is coming up on Friday, October 16th from 7AM to 5PM PDT. It'll be a day completely devoted to exploring/testing/playing the new project and learning about what they do and how they do it! To get started, just head over to the project page on QMO: http://quality.mozilla.org/website-testing ....and start participating at any time! We've still making some changes to the testday logistics for this sort of project and would love to hear your feedback about what you think of it during the day. For more i

A QAC blog

Hi all, First of all Henrik had given a link about a weekly status update on what you guys work on or areas where you guys are working on and I sadly lost it (or its there in the whole pile of stuff that's called my inbox ) . So can somebody give me the link again, sorry . Incidentally can/does somebody post the link everytime there's new stuff on the weekly wiki. I don't know whether this is already done or not but it would be nice to have some kind of feed going (think Atom/RSS) so people who are interested to atleast know can sign up and get those updates. For som

Testday: Test-scripting with MozMill 1.2

Hey Mozilla QA Community! I'm super excited for something aakashd and I have conjured up for October 29th-30th! In conjunction with the Free Software and Open Source Software conference at Seneca College, the MozQA community is holding a two-day Testday on Thursday, October 29th and Friday, October 30th for users interested in the use, development and/or testing of Mozmill! I'm going to be leading a workshop, Thursday, for those interested in getting MozMill set-up and running on their machines. Afterward, we'll have a two-day Testday for those that not only have questions, but a

"Number of Fixes by Developer" Metrics

Damon Sicore maintained a cool set of graphs some time ago that was built using few external frameworks. * QGoogleVisualizationAPI by Thomas Sch=E4fer which is a PHP wrapper around Google Visualization APIs. * Simplepie.inc package which is a cool feed reader framework in PHP. * Couple of nifty home made PHP scripts. The framework has fallen out of use sometime ago. So, Damon has asked our team to revive it. It is revived now and the graphs are getting generated from the framework. Please have a look in the "Fixes by Dev Group" section of http://people.mozilla.com/

Simpler test-cases

Hi all, I read the whole 'verified' thread . One of the things which stuck me was simpler test-cases. I can relate with many test-cases where I had no clear idea what resource or things I need to do. Lemme give an example. While testing one of the tests was downloading anything from the web multiple times, then go to incognito/private browsing mode and download few things again. Now, at that point in time I was confused by what to download. Normally one download files, one downloads pictures etc. whatever on the web, but when suddenly one is supposed to be downloading some

Test Pilot Surveys, Testdays and the Mozilla QA Community

Hey mozQA Community, We now have a tentative Testday planned for 12/4 on combining the Mozilla QA Community and Test Pilot together to hopefully answer a question (or set of related questions) to find out how we test and/or how we can test better. With that said, this is tentative only because there's no real idea set up for this Testday. This is where our community comes in as I'd like to use this e-mail in a chain with those that might have some ideas as to formulate a proposal (i.e. question/set of questions) to do on 12/4. For more information, check out their proposal wiki here: htt

List of all PENDING reviews report

Please find enclosed the list of all pending reviews grouped by 'Assigned Reviewer'. http://people.mozilla.com/~mnandigama/allPendingReviews.html This list also includes the list of all pending reviews for approved blockers for 1.9.2 and Firefox3.6 as well. This is report is available at http://people.mozilla.com/~mnandigama/blockerReviews.html Original request for this report is credited to Benjamin Smedberg followed by Damon Sicore. Thanks Murali

Some bugs for QMO

Hi all, A newbie trying to involve himself with testing. During the course of these tests came across and used QMO Add-on quite a bit. I had been meaning to write for sometime now. While playing/using it came to realize that while its a great tool it could get some more usability love so mainstream people could use it and also give better feedback as well. The bugs have been put up at the bugzilla within the QMO Addon component. Please go through them and do whatever you feel is the best. One question though, if I have some issue or need help on a specific test-case is

Reminder: 3.6 Bug Verifications

This is a reminder that as we approach code freeze for beta 1 we need to be spending time every day verifying bugs in the areas we own. You'll find a list of bugs needing verification at the bottom: https://wiki.mozilla.org/QA/Firefox3.6/TestPlan In addition, if your name is next to a feature in the table, please try to have the test plan ready as soon as possible, especially if it is a new feature with new UI that requires Litmus tests, because we are going to need those tests to leverage the community in the following weeks. juanb

Improve tracking of failed tests vs fixed bugs, so that attention is quickly called to possible regressions

https://litmus.mozilla.org/common_results.cgi?status=fail seems like it would be useful at first glance, but drilling down, you find that the signal-to-noise is pretty bad. I think this could be more useful if we looked at failures for a test since the last time a bug was "fixed" affecting what the test is measuring, in other words, adding a "failed tests from last fixed bug" metric to the reports. Currently, getting this information would be time consuming, requiring drilling down to each failed test, finding the relevant bugs, getting dates for when they were fixed, and then sea

Date Change for Live Testing Meetup - Moved to Wednesday, September 23

The meetup that was scheduled for this Wed, September 16 has been moved to September 23. http://quality.mozilla.org/events/2009/sep/16/firefox-36-pre-feature-explorationlive-testing-event has all the details. Hope to see you there.

MozQA Facebook Group moved to a Page!

Hey MozQA Community, The Mozilla QA Community has a facebook page associated with it for the past week or so ( located here: http://www.facebook.com/pages/Mozilla-QA/122167964300?ref=search&sid=6000202.4081432383..1 ). I'm deciding to now update the group and probably delete/remove it within a month's time as it's a lot of work to update compared to a page...and people have had complaints about the amount of testday spam they've been receiving. I tried asking a friend to move the users that are associated with our group to the become "fans" of our page instead, but was told that they ad

About fixed bug counts in Firefox 3.5

I am working on a set of retrospective bug metrics on Firefox 3.5 release. When I run queries on the Bugzilla DB dump, I get a total of 3551 bugs fixed in FF3.5 of which 1853 bugs have blocking flag set on them [ the 1853 bugs also contain 102 security bug fixes ]. I find only a handful of DUPLICATE, WONTFIX, WORKSFORME, INVALID state bugs in the 3551 total. On a positive note, it shows that we have a great system in place that is helping bug filers to not file bugs that are duplicates or frivolous. On the other side it may also indicate that, for bugs that are closed with above

Code Coverage Data trends graph.

Please find enclosed Code Coverage Data trends graph here. This little graph contains a lot of visual information if you play with it correctly. http://people.mozilla.org/~mnandigama/coveragedatatrends.html You can select two distinct views :: Bubbles or Bars In the Bubbles view : Select Colors [ Right hand side drop down menu ] to be Unique and Size to be [ Coverage ]. This will make bubbles size inflate or deflate based on coverage changes. Please pick X-Axis to be Order:Alphabetical Then press the Play button at the bottom left . You can do similar things with '