SeaMonkey/QA

Seamonkey QA Call to Action

As we approach our first Seamonkey release, we need to ensure that the suite is tip-top shape. To make this possible, we need members of the Seamonkey community to help with quality assurance by testing current builds to identify and report bugs and by help sorting out bugs that have already been filed.

In preparation for this first release, we need as many testers as possible to download and use Mozilla 1.8 beta 1 or recent nightly trunk builds. You should check Bugzilla to see if any bugs have already been reported, and (if not) file a new bug. We are particularly interested in regressions (bugs which did not exist in Mozilla 1.7), so mark these bugs with the regression keyword to bring them to developers' attention.

We also need to identify previously reported bugs that need to be fixed before our release. There is a list of recent unconfirmed bugs that need to be triaged. You should ensure that the bugs are in the appropriate component, and (if enough information is available) confirmed or marked as duplicate, works for me, invalid, or wontfix. If not enough information is available, add a comment in the bug asking the reporter for the information needed. Once the bugs are properly triaged, we'll be able to see what bugs need to be fixed before a first release, and what issues need to be reported in the release notes.

Seamonkey vs. Gecko bugs

There are two major classes of bugs you might find in the Seamonkey Suite:

• Front-end bugs: These bugs occur in the user-interface part of the code, and might include problems with bookmarks, autocomplete or the download manager. These bugs should be filed under one of the Mozilla Application Suite components.

• Back-end bugs: These bugs occurs in code that operates behind the scenes, and might include problems with web page rendering, networking or printing. These bugs should be filed under one of the core Gecko components, which are shared with other Mozilla applications, including Firefox and Thunderbird.

If you're not sure of the appropriate component or even product, that's ok. We'll move it to the right component, but filing in the right component will speed up the process of getting your bug fixed and save our time, so please try to find the most appropriate component.

More QA Resources

• Helping with QA provides a good overview of the various tasks for people getting involved in QA.

• Mozilla's QA Home Page provides more information for QA members, including resources for specific parts of suite (browser, Gecko, mail, etc).

• #seamonkey generally has a few developers or experienced QA folks that can help you getting started with bug reporting or triage.