TestEngineering/UI: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 83: Line 83:
'''[http://docs.google.com/Doc?id=df5tpx98_12m3w7d6hm Project checklist (template)]'''
'''[http://docs.google.com/Doc?id=df5tpx98_12m3w7d6hm Project checklist (template)]'''


#L1: [[Update:Remora Meeting Notepad|AMO 5.2]]  
#L1: [[Update:Remora Meeting Notepad|AMO 5.2]]
#L1: [[https://wiki.mozilla.org/QA/Execution/Web_Testing/AMO/5.0.9_Collector_Test_Plan AMO 5.0.9 Collector test plan]] - Help Wanted!  
#L1: [[https://wiki.mozilla.org/QA/Execution/Web_Testing/AMO/5.0.9_Collector_Test_Plan AMO 5.0.9 Collector test plan]] - Help Wanted!  
#L1: [[Support/SUMOdev Meeting Notepad#Next_releases|SUMO 1.4]]  
#L1: [[Support/SUMOdev Meeting Notepad#Next_releases|SUMO 1.4]] - [https://wiki.mozilla.org/QA/Execution/Web_Testing/SUMO/Test_Plan Test Plan]
#L1: [https://intranet.mozilla.org/index.php?title=ProjectFennec Fennec pages] - [https://intranet.mozilla.org/ProjectFennec/Beta_Websites/Test_Plan Test Plan] -- '''[https://bugzilla.mozilla.org/show_bug.cgi?id=502088 Master tracking bug]'''
#L1: [https://intranet.mozilla.org/index.php?title=ProjectFennec Fennec pages] - [https://intranet.mozilla.org/ProjectFennec/Beta_Websites/Test_Plan Test Plan] -- '''[https://bugzilla.mozilla.org/show_bug.cgi?id=502088 Master tracking bug]'''
#L1: [https://wiki.mozilla.org/Website/Sprints/PluginProblem Plugin-upgrade page] - [https://bugzilla.mozilla.org/show_bug.cgi?id=391433 main plugin-updating bug] - [https://wiki.mozilla.org/Website/Sprints/PluginProblem/Test_Plan test plan]
#L1: [https://wiki.mozilla.org/Website/Sprints/PluginProblem Plugin-upgrade page] - [https://bugzilla.mozilla.org/show_bug.cgi?id=391433 main plugin-updating bug] - [https://wiki.mozilla.org/Website/Sprints/PluginProblem/Test_Plan test plan]

Revision as of 08:53, 16 October 2009

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)

tmzmoz@gmail.com
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)

Q4 project list

Project checklist (template)

  1. L1: AMO 5.2
  2. L1: [AMO 5.0.9 Collector test plan] - Help Wanted!
  3. L1: SUMO 1.4 - Test Plan
  4. L1: Fennec pages - Test Plan -- Master tracking bug
  5. L1: Plugin-upgrade page - main plugin-updating bug - test plan
  6. L1: Mozilla.com 3.6
  7. L1: Mozilla.com optimization
  8. L?: 5Years
  9. L1: Funnelcake
  10. L3: Mozilla CRM Test Plan
  11. L2: Mozilla Developer Center
  12. 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

Metrics

http://people.mozilla.com/~mnandigama/dashboard.html

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.

Selenium/PHP Scripts

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