= Mission =
Building private, secure, user controlled cloud services that bring user delight and utility in a multi-screen world.
=Team Details=
The Services QA team is committed to qualifying products and releases through client-server testing. Consisting of Client and server product testers, we also plan to diverge into performance and load testing in staging and production environments.
== Team Members and Assignments ==
{| class="fullwidth-table"
|-
| style="background:#EFEFEF; width:30%" | '''Name'''
| style="background:#EFEFEF; width:30%" | '''Contact'''
| style="background:#EFEFEF; width:10%" | '''Availability'''
| style="background:#EFEFEF; width:30%" | '''Project Assignments'''
|-
| Edwin Wong
| edwong at mozilla.com
| MoCo Employee (full time)
| Cloud Services QA Manager
|-
| John Morrison
| jrgm at mozilla.com
| MoCo Employee (full time)
| Cloud Services QA
|-
| James Bonacci
| jbonacci at mozilla.com
| MoCo Employee (full time)
| Cloud Services QA
|-
| [[User:Kthiessen|Karl Thiessen]]
| kthiessen at mozilla.com
| MoCo Employee (full time)
| Cloud Services QA
|-
| Peter DeHaan
| pdehaan at mozilla.com
| MoCo Employee (full time)
| Cloud Services QA
|}
=Current Status=
[https://etherpad.mozilla.org/services-qa-projects etherpad version]
= Weekly Trains and Releases =
Each week, or for each scheduled release, QA receives a new build for testing in the Beta (BrowserID). The Dev teams write, test, and release the build to the OPs team. The OPs team is responsible for deploying the build to the Beta or Stage environment. Once the new build is deployed, the QA team verifies the deployment, then completes all required testing and signs-off on the results. Once this process has completed, the OPs team is cleared to deploy the build to production.
[https://wiki.mozilla.org/QA/Browser_Technologies/Services/Releases Services QA: All Releases]
[https://wiki.mozilla.org/QA/Browser_Technologies/Services/Releases/BrowserID BrowserID Releases]
=Projects=
<onlyinclude>
This section should contain a list to the active current team project page. The section will be included as part of the top level QA organization page.
{| class="fullwidth-table"
| [https://wiki.mozilla.org/QA/BrowserID/TestPlan BrowserID Test Plan]
| BrowserID allows users with a verified email address against Mozilla platform to request access to websites
| John
|-
| [https://wiki.mozilla.org/Identity/AttachedServices PiCL (Profile in the Cloud)]
| Service that allows users to access synced bookmarks, history, web apps, and passwords from any device.
| James
|-
| [https://wiki.mozilla.org/QA/Firefox_Share_Test_Plan Firefox Share Test Plan]
| A feature for the browser that allows you to share links in a fast and fun way. One is able to share links from within the browser without leaving the page using the same services one already know and uses
| TBD (STATUS UNKNOWN)
|}
</onlyinclude>
=Environments=
Services projects use a handful of environments to get their work done. Generally, it's broken down by:
* Development Sandbox
* Staging
* Beta (Q3 goal)
* Production
A handful of environments are listed [https://intranet.mozilla.org/QA/Mozilla_Services_Environment here]. However, many of them require Mozilla Internal access and VPN, so if you are part of a special project, please see the QA staff for more info.
=Resources=
* QA Sync Server documentation
** [https://wiki.mozilla.org/QA/Sync QA Sync Server site]
* QA Persona/BrowserID documentation
** [https://wiki.mozilla.org/QA/BrowserID QA Persona/BrowserID site]
* QA AITC/TokenServer documentation
** [https://wiki.mozilla.org/QA/AITC_TS QA AITC and TokenServer site]
* Automated Testing
** [https://wiki.mozilla.org/QA/BrowserID_Automation BrowserID Automation]
=Meetings=
=Community Contribution=
We're piloting a program for contributors looking for a deeper connection to cloud services development. We'd as you commit 5 hrs a week for 3 months. In that, you will learn and grow your own skills in writing test cases, testing new features, and helping deploy a web service. Please email edwong at mozilla dot com or jump on IRC #Identity fxa or #Services-dev if you're interested.
'''Anyone can participate.''' There are several ways in which '''YOU''' can participate:
* Plan new features testing
* Help others who want to get involved.
=Archive=
[https://wiki.mozilla.org/QA/Services_Archive Archived Links]
