Fennec is growing up fast and will be on its own before we know it.  Just last month, we released Beta1 for the Maemo platform, and this month we will get Alpha1 for Windows Mobile released.  These are huge steps in the right direction.  This creates a great opportunity to develop testcases and automation.
 
Currently we have a well over one hundred litmus (manual) test cases defined.  This number has been slowly growing over the last few months and will continue to grow.  Have you tried running a set of test cases on a small device?  It is not very easy when you are used to running on a desktop browser, but these are very important testcases to run since they really exercise the browser in it's native environment.  We still need testcases, specifically ones that reference integration with a specfic device (hardkeys, common UI elements, installation, upgrade, uninstall) as well as percieved usability and performance.
 
The big hole we have is automation.  We have already ported the Firefox unittests to Maemo, but there are a lot of bugs to be fixed and a pending integration into the tinderbox automation framework.  We also need to port the tests to run on Windows Mobile (WinCE) which is a much larger project, but a chance to make very large contributions.
 
The big push we are working on in the next couple months is to add automated cases to exercise the Fennec UI.  Now that the product is starting to stabalize, we need to catch up and get some real automation for all the hard work the dev team has been doing.
 
Interested in helping out, pick one of these projects:

• Fennec Preferences
• Fennec Panning / Zoom
• Fennec Download Manager
• Fennec Awesome Bar

• Maemo Mochitest Failures
• Maemo Chrome Failures
• Maemo Reftest Failures