Tomcat's Blog

Hi Mozilla Community!

We now have a Firefox 4 Beta 10 candidate available for testing.

We would like your help in testing the build and identifying any possible regressions or issues. You can read all about the release here: http://www.mozilla.com/en-US/firefox/beta/

What to Test/Where to Get Builds:

*Please see http://www.mozilla.com/en-US/firefox/all-beta.html – there are direct links to the builds on that page.

Please hammer on these builds mercilessly to make sure that things work well!

Read the Release Notes

* Please also make sure to read the which detail the known issues and describe the complete list of changes in this version. You can find the Release Notes here – http://www.mozilla.com/en-US/firefox/4.0b10/releasenotes/

*Some cool things to try:
** Windows 7 Users only: Try out the sites listed at the bottom of this page: https://wiki.mozilla.org/Platform/GFX/Direct2DDemo
** Try out Firefox Panorama!
** Try out Firefox Sync! Sync to your Android or iPhone!
** Try out the Feedback button!
** Make sure to go to Mozilla Plugin Check http://www.mozilla.com/en-US/plugincheck/ to verify you are running the latest version of Flash and other plugins.
** Explore some other focus areas: https://wiki.mozilla.org/Releases/Firefox_4b10/Test_Plan#Focus_Areas

How to Report Feedback:
(1) File a bug in Bugzilla. *Note in the comment if it is a regression from a previous release. Things to remember when filing a bug:
(a) Always include the Build ID that you tested on. If you type about: in the URL bar, this will give you the Build ID.
(b) Always include clear Steps to Reproduce the bug
(c) Always check to see if your bug has already been filed.
(d) Use the regression keyword if it indeed a regression from a previous release.
(e) If you happen to crash, please submit your crash information! This helps us continually improve the product. Please also include the Breakpad Crash ID in the bug. You can get the crash ID by typing about:crashes in the URL bar.
(f) If you tend to run with lots of extensions, try starting Firefox in Safe Mode before filing to bug to see if the problem persists.

(2) If you don’t wish to file a bug, report issues through the Firefox Feedback button, http://feedback.mozilla.org or through the mozilla.feedback.firefox.prerelease newsgroup (also available on Google Groups). However, we prefer bugs as feedback is easier to track.

Thanks in advance to all of you for helping test Firefox and making it the browser of choice for millions of people all over the world!

Thanks,
-Tomcat
Team Mozilla QA

Testing of Nightly builds is a very important QA task and helps us track down regression bugs early.

This is essential to ensuring quality releases of Firefox and Firefox Mobile and we are very thankful for your work (testing, filing bugs, checking regression ranges). Our Firefox Community rocks!

To assist you better with Mobile nightly build testing and to inform you about current focus areas where Mozilla QA is working on (for example important landings of current features) we have created a new mailing lists especially for Mobile User of our Firefox Mobile Nightly Builds:

For Firefox Mobile Nightly Testers on the Android Platform: https://mail.mozilla.org/listinfo/android-mobile-nightly-testers
For Firefox Mobile Nightly Testers on the Maemo Platform: https://mail.mozilla.org/listinfo/maemo-mobile-nightly-testers

Please sign up for this mailing lists if you are interested in hearing about the latest details on Nightly Firefox Mobile build testing.

Thanks,
-Tomcat