Confirmed users
46
edits
SeaMonkey/QA: Difference between revisions
m
style cleanup
(→Seamonkey QA Call to Action: Mention that testers should enable talkback) |
m (style cleanup) |
||
| Line 3: | Line 3: | ||
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. | 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 [http://www.mozilla.org/releases/ Mozilla 1.8 beta 1] or [http://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/latest-trunk/ recent nightly trunk builds]. | In preparation for this first release, we need as many testers as possible to download and use [http://www.mozilla.org/releases/ Mozilla 1.8 beta 1] or [http://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/latest-trunk/ recent nightly trunk builds]. Also, please enable the [http://www.mozilla.org/quality/qfa.html Talkback Quality Feedback Agent] to send information back to developers so they can fix crash bugs. If you find a problem, check [https://bugzilla.mozilla.org/ Bugzilla] to see if your [http://www.mozilla.org/quality/help/beginning-duplicate-finding.html bug has already been reported], and (if not) [http://www.mozilla.org/quality/bug-writing-guidelines.html 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 [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Mozilla%20Application%20Suite&version=Trunk&version=unspecified&version=Other+Branch&bug_status=UNCONFIRMED&chfieldfrom=-60d&chfieldto=Now&chfield=%5BBug%20creation%5D&order=bugs.bug_id recent unconfirmed bugs] that need to be [http://www.mozilla.org/quality/help/bugzilla-privilege-guide.html 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. | We also need to identify previously reported bugs that need to be fixed before our release. There is a list of [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Mozilla%20Application%20Suite&version=Trunk&version=unspecified&version=Other+Branch&bug_status=UNCONFIRMED&chfieldfrom=-60d&chfieldto=Now&chfield=%5BBug%20creation%5D&order=bugs.bug_id recent unconfirmed bugs] that need to be [http://www.mozilla.org/quality/help/bugzilla-privilege-guide.html 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. | ||