TestEngineering/Services
Overview
Mozilla Services is the branch of mozilla where Client products meet Server interaction. Services can be expanding into any products that can utilize modular and scalable API's, to provide web developers the flexibility on creating products within the server-client interaction. Current products like Sync and Identity, make up the beginnings of existing products that drive this offering.
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
| Name | Contact | Availability | Project Assignments |
| Edwin Wong | edwong@mozilla.com | MoCo Employee (full time) | Services QA Manager |
| John Morrison | jrgm@mozilla.com | MoCo Employee (full time) | Server side QA |
| James Bonacci | jbonacci@mozilla.com | MoCo Employee (full time) | Server side QA |
| Karl Thiessen | kthiessen@mozilla.com | MoCo Employee (full time) | Server side QA |
Current Status
- Updated: March 28, 2013
- BrowserID
- Shipped BigTent
- PiCL: In design
- Push Notification: In design
Working Docs
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.
Projects
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.
}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 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
- Sync Client and Server Test Documents
- Sync Server Installation and Configuration
- QA Sync Server documentation
- QA Persona/BrowserID documentation
- QA AITC/TokenServer documentation
- Automated Testing
Meetings
- Monday 3pm - Vidyo: QA
Team Goals
Goals are attached to core Cloud Services Goals Goals specific to QA are:
- Add automated test cases
- Support Deployments
- Log bugs
- Review test coverage and test cases
- Advocate for users
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 or #Services-dev if you're interested.
Anyone can participate. There are several ways in which YOU can participate:
- File bugs
- Triage bugs (confirm existing bugs and assign them to the right buckets)
- Help test new features
- Write test cases
- Plan new features testing
- Help others who want to get involved.
Archive
| BrowserID Test Plan | BrowserID allows users with a verified email address against Mozilla platform to request access to websites | John |
| PiCL (Profile in the Cloud) | Service that allows users to access synced bookmarks, history, web apps, and passwords from any device. | James |
| 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) |