The document summarizes Mozilla's web testing practices. It introduces the testing team and the technologies, tools, and techniques they use. It discusses common challenges like different environments, legacy browsers, and tight schedules. It also outlines their approach to automated and manual testing and provides examples of areas that are good candidates for each.

1. Testing Mozilla Web Properties Stephen Donner 6/24/2009

2. Meet the Team Stephen Donner - [email_address] Krupa Raj - [email_address] Raymond Etornam Agbeame - [email_address]

3. Technologies we test AJAX Drupal Spread Firefox QMO Apache .htaccess - bug 478952 Open-source search engines Sphinx (SUMO) TikiWiki (SUMO is its biggest consumer) Media types Ogg Flash .swf vs. .flv

4. Tools We Use Firebug Web Developer toolbar Live HTTP Headers SQL Injection Selenium IDE RC VMWare Fusion Acunetix W3C

5. Gotchas Staging server vs. production Different environments Configs (permissions, etc.) Application versions Caching Memcache NetScaler / Zeus DB setups Slave vs. master Replication lag Legacy browsers / non-standard configs IE 6, anyone? JavaScript disabled

6. Gotchas, part 2 Partner integration GetSatisfaction reCaptcha Mozilla Service Week Add-on promotions Fashion Your Firefox

7. Pain Points Tight schedules Quarterly goals from other parts of the org Lack of clear specs Wireframes vs. mockups (vs. full user-interaction testing) Project direction / ownership Out-of-band testing requests Ops/IT - hardware failure, new-technology evals, regression-testing of new hardware

8. Automated vs. Manual Testing Balance need to rapidly execute/ship vs. long-term stability Ramp-up cost Can't automate everything Quite a few projects are one-off (time investment) Impact Mozilla Fashion Your Firefox Operation Firefox Good automation candidates Search APIs (services.addons.mozilla.org) Static content Headers/footers/legal/privacy policies/EULAs Login / logout / registration/ forgotten password Exception of Captcha systems

9. Grades / Levels of Testing Acceptance check Full Functionality Test Regression testing Basic Functionality Test (Exhaustive list: http://www.softwaretestinghelp.com/types-of-software-testing/ )

10. What we use Selenium for Verify page titles Verify content pieces (text, links, images) Pagination Search terms persist in textfields ~ 15 commands

11. Example of manual testing Mozilla Service Week (http://mozillaservice.org)

12. Selenium demo AMO Basic Functionality Test AMO Search

13. How can you help? Vet content Test browser compatibility Sanity check our testing Write unit tests

14. Resources Public mailing list: [email_address] Homepage: https://wiki.mozilla.org/QA/Execution/Web_Testing IRC channel: irc.mozilla.org/webqa

15. Questions? Comments? Suggestions?

16. Thanks for your interest!