QA/Fennec
Home of those who want to Propel Fennec Quality!
Milestones
Current Releases
- Native: Native Testplan
- 10.0: Testplan
Planning
What We Do
Testing Strategy
- Manual
- QA/Fennec/Waverley on the latest Nightly build on the current development branch and trunk
- Verification of overnight resolved bugs on the current development branch
- Run BFT(s)/Focused testing around areas that area affected by resolved bugs
- Weekly triage of new and unconfirmed bugs
- Bi-Monthly Testdays
- Automation
- Unique Areas of Testing
| Project | Description |
| Device Compatibility Test Plan | Tracks Tests and Full device list of compatibility with Mobile Firefox |
| Website Compatibility Test Plan | Tracks top Website compatibility with Mobile Firefox |
| Performance Benchmarking Test Plan | Tracking performance benchmarking numbers for Startup times and Page Loads |
| Mobile Addon for Unit Testing Automation | Project to run unit tests via a test-harness addon and disperse via crowdsourcing techniques |
Release Testing
Fennec Crash Reporting
Crash Reports can be seen from Socorro and they are manually being done until there doesn't need to be a person looking at the socorro crash signatures for separation (crashes that have the same signatures but are completely different crashes) or combination (for signatures that are separate signatures but are really the same crashes).
Crash reports are done mostly for the Nightly as the developers can be the most effective there. Here is an example of a crash report: Dec 26, 2011 Crash Report
What We Use
Tools
- Litmus
- Device Anywhere
- Performance Graphs
Resources
- Device Anywhere Tutorial
- Mobile (HG) Repository
- Mobile Source Code
- Fennec MXR Source Code Web-Based Viewer
- Builds
Where Do We Need Help
Test Tool Development
- Write automated testcases
- Port Automation Frameworks to WinCE
- Find, Fix, Verify UnitTest Failures
Execution
- Triage Unconfirmed Fennec Bugs
- Create Litmus testcases for bugs flagged as in-litmus?
- TestDay Promotions within Mobile Community Channels
- Write technical documentation to perform quality execution
Performance Benchmarking
Previous Performance testing
- Scratch pad of notes
- Performance Testplan
- Performance Benchmarks
Website Compatibility Testing
- Scratch pad of notes
- Web Compatibility Testplan
Sync Performance Instrumentation
Fennec sync continues to cause performance issues on first time syncing with very large amounts of data. How you can help, is to provide sync logging through a custom extension, and submit your data to the Mozilla Services team. Detailed instructions can be found here.
More historical information on the project:
- Philikon's Sync Instrumentation Research
- Blog on profiling Javascript Objects
How You Can Contact Us
If you're interested in helping out with anything below (or want to help with something else), please contact jmaher or aakashd. If you want to talk to the Mozilla Mobile Community, you can find us in our IRC Channel.
- Mailing Lists
- mobile@mozilla.com
- Newsgroups
- 3rd Party Testing (Waverley)
- Execution testplan for Smoketests & BFTs