QA: Difference between revisions

← Older edit

QA (view source)

Revision as of 21:18, 10 January 2019

1,220 bytes added , 10 January 2019

→‎Teams

Ashughes

Confirmed users

14,525

edits

@@ Line 1: / Line 1: @@
-Welcome to Mozilla Foundation Quality Assurance (MoFo QA)!
+[[File:Qa-badge.jpg|250px|left]]
-You can contact us by either [mailto:qa&#64;mozilla.org email] or on the [irc://irc.mozilla.org/qa #qa channel] of irc.
+<br><br>
+Welcome to the Mozilla QA wiki home page.
-== Who We Are ==
+We are a guild of individuals united by a common passion to make the quality of the products Mozilla creates the best it can possibly be. There are a plethora of ways to get involved and be a part of the Mozilla Quality Project to help ensure, empower, extend, and enjoy the open web. We're excited you're here to join us.
-There are thousands of Mozilla contributors who download and test nightly builds of Firefox, Thunderbird, Camino and the Mozilla Suite. The main MoFo QA team consist of:
+<br clear=all>
-====Asa Dotzler (asa)====
+= Quality Assurance Principles =
-QA lead, community lead.
+These are the foundational elements that we evaluate to judge quality for each of our projects. These are all interdependent and interrelated and the list is probably not exhaustive, but it will give you an idea of what we are passionate about.
+* Dependability - Every product should be stable and dependable
+* Delight - Doing "what it should do" is not enough. The product must delight the user with its functionality.
+* Security & Privacy - Mozilla believes very strongly that our products must put our users in control of their data and must take every step we can to ensure your security while on the web.
+* Performance - The products must meet or exceed the performance requirements we and our users demand.
+* Web Platform - Our mission is to extend, empower, and keep the web platform open for all. We do that by releasing great products that people love, which push the boundaries and capabilities of the open web ever farther.
-====Tracy Walker (tracy)====
+= Get In Touch! =
-QA engineer, smoketest guru.
+We'd love to hear from you. We hang out on Mozilla IRC (irc.mozilla.org) in the #qa channel. We use the [https://groups.google.com/forum/#!forum/mozilla.dev.quality dev-quality] mailing list for communication and discussion. Our blog is at [https://quality.mozilla.org quality.mozilla.org (also known as QMO)].
-====Sarah Liberman ([[User:Sairuh|sairuh]])====
+While you're at it, please register as a Mozillian and [https://mozillians.org/en-US/group/qa/ join us]!
-QA engineer. Sarah has been poking, prodding and playing with various Mozilla projects since 1999 (and Netscape products since 1994).
-====Jay Patel (jay)====
+= Teams =
-Talkback guru.
+We are organized into product focused areas. You can find our teams and team leads' IRC nicknames below.
+{| class="fullwidth-table" border="1"
+|-
+| style="font-weight: bold; background: #DDD; width: 15%" | QMO Team Page
+| style="font-weight: bold; background: #DDD; width: 15%" | Team Lead
+| style="font-weight: bold; background: #DDD; width: 20%" | Team Wiki
+| style="font-weight: bold; background: #DDD; width: 30%" | Primary Focus Areas
+| style="font-weight: bold; background: #DDD; width: 20%" | Primary Team IRC Channels
+|-
+| [https://quality.mozilla.org/teams/firefoxqe/ Firefox QE]
+| None at this time. Team members are embedded in Engineering Teams
+| [[QA/Firefox|QA/Firefox]]
+| Firefox browser (Desktop and Android)
+| #qa
+|-
+| [https://quality.mozilla.org/teams/test-engineering/ Firefox Test Engineering]
+| sphilp
+| [https://wiki.mozilla.org/TestEngineering https://wiki.mozilla.org/TestEngineering]
+| Firefox Test Engineering
+| #qa, #fx-test
+|-
+| [https://quality.mozilla.org/teams/web-qa/ Web and QA Services]
+| Stephend
+| [[QA/Execution/Web_Testing|QA/Execution/Web_Testing]]
+| Mozilla websites, Marketplace, QA specific sites
+| #qa, #mozwebqa
+|-
+| [https://quality.mozilla.org/teams/services/ Cloud Services QA]
+| sphilp
+| [[QA/Services|QA/Services]]
+| Mozilla Cloud Services (sync, simplepush, OAuth, Firefox Accounts etc)
+| #qa, #services-qa
+|-
+| [https://github.com/mozilla/iris Mozilla Iris]
+| Matt Wobensmith (Core)<br />Tracy Walker (Test)<br />Anthony Hughes (Deploy)
+| [[QA/Product_Integrity/Mozilla_Iris]]
+| Test automation
+| #qa-automation
+|}
-====Marcia Knous (marcia)====
+[[File:Mozilla_QA_2014_team.jpg|border|600px|2014 QA Workweek in Mountain View]]
-Project Manager and QA contributor.
+<small> The old version of this [https://wiki.mozilla.org/QA_Archived_Home_Page page is archived here]</small>
-== What We Do ==
-We currently focus most of our efforts on the Firefox and Thunderbird products. We also work with other projects such as [[SeaMonkey:Home_Page|Seamonkey]] to assist their [[SeaMonkey:QA|QA]] and [[SeaMonkey:Project_Organization|development]] teams so that we can maximize resources &mdash;such as Bugzilla and Testrunner&mdash; as well as minimize duplicated efforts.
-===Smoketests and BFT's===
-We smoketest the nightly builds of Firefox and Thunderbird (and sometimes Seamonkey), where smoketests consist of the bare-acceptance/sanity tasks of a product. We run basic functional tests (BFT's) at key points during a project cycle, notably before milestone (alpha/beta, final, etc.) releases, which are broader in scope than smoketests. The aim of a BFT is breadth, not depth, of scope, where as many of the features of a given product are touched.
-===Verifications, ad hoc usages, regressions===
-The majority of bugs filed result from ad hoc usage. Verifying such bugs is a great means of more deeply exercising the application as well as a useful way to find regressions.
-===Test development===
-Just as developers need to create, modify and maintain code, we in QA need to write, update, revamp and recreate (as needed) test plans and test cases &mdash;to ensure that what we use, test and investigate in a given application is correct and current! At present we do most of this manually, but are concurrently investigating automation tools for more repetitive, high-level tasks.
-<!-- == What We Use and QA Resources ==
-Bugzilla
-Testrunner
-Talkback
-Webpages
-== How can you help? ==
--->