TestEngineering/UI

From MozillaWiki
Jump to navigation Jump to search

Slides from my 6/24/2009 presentation at Mozilla HQ

The Team / Contact Info

How to reach us:

Name
Email Address
Project(s)
Interests / specialties
Raymond Etornam Agbeame
retornam@mozilla.com
Spread Firefox, School of Firefox, AMO...

Milos Dinic (Milos)
milos@mozilla-srbija.org
AMO, SUMO...

Stephen Donner
stephend@mozilla.com
AMO, SUMO, School of Firefox, Mozilla.com

Vishal Kamdar
vkamdar@mozilla.com
SUMO, Spread Firefox...

Tom Ellins (TMZ)

tmz@mozilla-srbija.org
SUMO...

Krupa Raj
kraj@mozilla.com
AMO, Creative Collective, SUMO, Mozilla Service Week

Tanner Young
mozilla@alyoung.com
AMO...

I Want to Help -- How Do I? / What Do You Need?

  • Please see our Volunteer page, and don't hesitate to contact us if you'd like to know more or help out!

Meetings

Currently, meetings are at 1 pm PDT on Thursdays.

Phone call details:

  • California: 650-903-0800 then extension 92
  • Toronto: 416-848-3114 then extension 92
  • Toll-free: 800-707-2533 then password 369
  • Skype (free): +18007072533 then password 369

Then, enter the conference number: 303#

Please mute your microphone as long as you are not saying anything to prevent feedback and other noise in the conference. Thank you!

irc.mozilla.org: #mozwebqa

2009

Current Projects

Project Schedules -- please use this calendar to help slot in your project (Gantt Chart)

Project checklist (template)

  1. L1: AMO 5.0.9
  2. L1: [AMO 5.0.9 Collector test plan] - Help Wanted!
  3. L1: SUMO 1.3
  4. L3: Creative Collective - Test Plan
  5. L1: Fennec pages - Test Plan -- Master tracking bug
  6. L1: Plugin-upgrade page
  7. L1: Partner pages - [Test Plan] (On hold until June)
  8. L1: Mozilla.com optimization
  9. L1: Community Store <- bug list (sporadic releases)
  10. L2: Mozilla Service Week 2009 - Test Plan
  11. L2: School of Firefox - Test Plan
  12. L1: Funnelcake
  13. L3: Mozilla CRM Test Plan
  14. L3: GetPersonas.com - we work off bugs, primarily

** Don't forget to make yourself familiar with the latest Firefox release schedules, as we might be doing work involved with them **

Staging Servers

What we do

Depending on the level of support:

  1. Browser compatibility testing of content rendering/functionality
    1. See WebDev's support levels
  2. Accessibility testing
    1. Cynthia online test
  3. Basic automation via Selenium IDE
  4. Code inspection via online, automated tools, such as
    1. W3C Link checker
    2. Doctype validation (if necessary)
  5. Basic Functionality Testing

What we currently don't do

  1. Load testing
  2. Performance testing
  3. API testing (but contact us if you need it, and we'll try to find a resource)

Our Support Levels for your Project

Please read through our support levels when proposing a new project for us.

Summary of test coverage

Please read through our summary of test coverage document, which defines various levels of test coverage for in-progress projects.

Resources

Community Outreach

References