TestEngineering/UI: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 101: Line 101:
| [http://widget.mibbit.com/?settings=1b10107157e79b08f2bf99a11f521973&server=irc.mozilla.org&channel=%23addons #addons]
| [http://widget.mibbit.com/?settings=1b10107157e79b08f2bf99a11f521973&server=irc.mozilla.org&channel=%23addons #addons]
| Krupa
| Krupa
| https://addons-dev.allizom.org/ (trunk/master)
| https://addons-dev.allizom.org/
| [http://qa-selenium.mv.mozilla.com:8080/view/AMO%20Tests/ CI]
| [http://qa-selenium.mv.mozilla.com:8080/view/AMO%20Tests/ CI]



Revision as of 18:19, 6 October 2014

Web QA Overview

Through a variety of tools and approaches, Web QA aims to ensure high quality web applications, of both external and internal applications and websites.

Get Involved

We'd love to have your help in testing our many projects! Are you looking for a way to contribute?

  • Contributor levels - This is the place to take a first look at what we have to offer, and how to help the team.

Community Outreach

Contact Us

Meetings

Please see our public calendar for all upcoming events and meetings.

Our regular team meeting occurs every Thursday @ 9am Pacific

Meeting Notes

Meeting details

Please see our public calendar for all upcoming events and meetings.

Our regular team meeting occurs every Thursday @ 9am Pacific

Meetings by year

I have something I need tested -- now what?

  1. We'd really appreciate it if you could sync up with the Web Production team; letting them know ahead of time on something you're working on helps us all get in-sync with the project, and shortens turnaround time
  2. Communicate with us! Send an email directly to rbillings or stephend or the mozwebqa mailing list with your ask. Our team is a lot smaller, and we're juggling a lot of balls. This means that we need you to ask us directly for what you need, and give us some head's up. Specifically we need at least a few days notice if there is something time-sensitive that needs testing.
  3. File a bug in Bugzilla, under the product Testing, and component "WebQA", asking us to test your site/application.  assigning to "mozwebqa@mozilla.org", and I'll be sure to assign it to the right person, or make sure the team tests
  4. In the bug, please let us know of any pertinent schedules, deadlines, requirements, limitations, etc.  Also, pointing us to design documentation or specs, such as mockups/HTML cuts/wireframes, etc. would be immensely helpful
  5. Please also list any third-party developers/firms we'll have to work with, to get the potential issues we might have found, addressed.  (And please make sure they have a Bugzilla account, too.)
  6. How to get a project in automation


Team Details

We welcome community members to join us and take on tasks and responsibilities; please see our quality.mozilla.org page for more information/to engage.

Team Members and Assignments

Name Email Address Availability Project Assignments / Interests
Rebecca Billings rbillings@mozilla.com Employee One and Done PM, Web Engagement projects, Mozilla.com, SUMO, MozTrap, QMO
Matt Brandt mbrandt@mozilla.com Employee Firefox OS, Socorro, Affiliates, Mozillians, Firefox Health Report, Plugin Check, Webmaker, Bouncer, +automation
Stephen Donner stephend@mozilla.com Employee Manager
Andrei Hutusoru andrei.hutusoru@softvision.ro Contractor Automation
Krupa Raj kraj@mozilla.com Employee AMO/Mozilla Marketplace lead
Bob Silverberg bsilverberg@mozilla.com Employee Automation

Web QA Project List

Project (page/bug) Testing IRC Lead/contact Staging server(s) Jenkins URL
Add-ons Automation
Manual
#addons Krupa https://addons-dev.allizom.org/ CI
Affiliates Automation #affiliates Team https://affiliates-dev.allizom.org CI
Bouncer Automation #stubby Team, Matt http://download.allizom.org CI
Marketplace Firefox OS Automation
Automation
Manual
#mozwebqa Team https://marketplace.allizom.org/ CI
Mozilla.org Automation #www Rebecca http://www-dev.allizom.org CI
Mozillians Automation
Manual
#commtools Matt https://mozillians-dev.allizom.org CI
Mozilla Developer Network (MDN) Automation #mdndev Rebecca https://developer-dev.allizom.org/en-US/ CI
MozTrap Automation
Manual
#moztrap Team https://moztrap.allizom.org/ CI
MozWebQA Dashboard Automation #mozwebqa Team . .
One and Done Test Automation
Project Automation
#mozwebqa Rebecca, Bob http://oneanddone.allizom.org/ CI
Plugin Check . #plugincheck Matt http://www-dev.allizom.org/en-US/plugincheck/ .
QMO Automation #qa Team . CI
Reps Automation #remo Team http://reps.allizom.org/ CI
Snippets Automation #snippets Team http://snippets.stage.mozilla.com CI
Socorro Automation #socorro Matt / Stephen (backup) https://crash-stats.allizom.org CI
SUMO Automation
Manual
#sumodev Team http://support.allizom.org/ CI
Webmaker Automation #webmaker Team https://webmaker.mofostaging.net/ CI
wiki.mozilla.org Automation #mozwebqa Team, Glenn Howard, Stephen Lester https://wiki.allizom.org CI

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

Current Projects + Webdev Processes

Test Plan Template and Project Checklist

Web Engagement Projects

Team Goals

Next Team Work Week

QA PTO Calendar

New Hires (useful chiefly for paid Mozilla folks)

Some useful information about getting started is available here.

Automation

See our Automation page for details of Web QA's automation efforts.

Resources

Support Levels

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

Performance and Load-Testing Tools

Useful Tools

Security

Infrastructure / Server Info

Tips and Pointers

Mozwebqabot - Our IRC Bot

See our Mozwebqabot info page for details of Web QA's friendly IRC bot.

Reference Links

Presentation Slide Archives