QA/Execution/Web Testing/Contribute

Web Testing - Contribute!

Welcome to the Mozilla Web Testing Contribute! page, and thanks for your interest!

The purpose of this page is to provide a quick overview of and links to the various projects and testing approaches we're involved with here at WebQA.

The Team / Contact Info

Please see Web Testing for the most up-to-date contact information.

Current List of Projects

Current project list

Testing Options

New/Recent Tester

If you're new to web testing (or testing in general), you might want to start with any of the following:

• Test features
  • Nearly every project has a test plan (written by QA) which will give you a better idea of our test approach/coverage
• Verify RESOLVED FIXED bugs on the staging server for each project
• Confirm (by setting to "NEW") UNCONFIRMED bugs in each project's component in Bugzilla
• Run Litmus testcases (for our three largest projects):
  • AMO - addons.mozilla.org (project-meeting page)
  • SUMO - [support.mozilla.com support.mozilla.com] (project-meeting page)
  • SFx spreadfirefox.com (project-meeting page)

• Ad-hoc testing
  • Without much structure; feel free to try things you'd not normally do
• Browser-compatibility testing
  • We typically follow Web Development's support levels for the major browsers pretty closely
    • (Firefox 3.0.x, 3.5.x, Firefox 2.0.0.20 (limited), IE 6 (limited), IE 7 / 8, Opera, Safari, Google Chrome)

Intermediate/Advanced Tester

• Negative testing (purposefully try to break things)
  • URL manipulation
    • Replace "add" in a URL with "delete", change a key, unique ID, or hash in the URL, etc.
    • Permissions
      • Admin vs. end users; access rights
  • Invalid/large data (particularly in text/form fields)
    • 250/255, etc.
    • Null/empty-string values, ""
    • Single spaces, " "
    • Invalid characters (changes, depending on software package/config -- could include !@#$%^&*+=_-|\<>?/)

• Accessibility testing
  • Includes limited support for WAI-ARIA

Advanced/Automation/API tests:

• Security testing
  • XSS, SQL injection
    • Via JavaScript/PHP, etc.
• Selenium
  • Selenese/other language doesn't matter
  • Locations of current test scripts:
    • AMO: http://viewvc.svn.mozilla.org/vc/addons/trunk/site/app/tests/ (files ending in *.html)
    • SUMO: http://viewvc.svn.mozilla.org/vc/projects/sumo/trunk/tests/frontend/
    • SFx: http://viewvc.svn.mozilla.org/vc/projects/spreadfirefox.com/tests/
• API testing
  • AMO API

I Know What I'd Like to Help Out With; What's Next?

Great, thanks!

Here are just some basic starting points:

1. Browse the various projects
2. Find one or a couple you're interested in
3. Familiarize yourself with the project's release cycles, meeting notes, objectives, existing/needed Litmus/Selenium testcases, etc.
4. Get a feel for what you're comfortable with helping out on (New/Intermediate/Advanced)
5. Dive in, and don't hesitate to

Get in touch with us via any of the linked contact methods and if you have any questions. Thanks again!