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

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.

Services QA: All Releases

BrowserID Releases

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.

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)
Load Test Refactoring	Refactoring current Grinder tests to support functional tests with FunkLoad environment	Owen

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
  • Client Test Plan
  • Server Test Plan - out of date
  • Grinder - deprecated
  • Client Summaries
  • Server Summaries - out of date

• Server Release Process - out of date

• Sync Server Installation and Configuration
  • Installation
  • Devguide
  • Configuration
  • Services Main Site
  • Services Documentation
  • Services Information
  • Development Guide

• QA Sync Server documentation
  • QA Sync Server site

• QA Persona/BrowserID documentation
  • QA Persona/BrowserID site

• QA AITC/TokenServer documentation
  • QA AITC and TokenServer site

• Automated Testing
  • BrowserID Automation

Meetings

• TBD

Team Goals

Identity Deliverables:

• [NEW] Add AWS webhead to data center
• [NEW] Deploy bigtent - gmail
• [NEW] Deploy bigtent - hotmail

The 2013 goal of services QA is to reduce testing time while increasing quality of deployments. We can accomplish this by increasing automation breadth and depth and utilizing monitoring/sampling user experience.

We need infrastructure to enable such an approach:

• Scaling testing.
  • [NEW] Automation breadth: Add bigtent selenium tests, unit tests
  • [NEW] Automation depth: Write wiki on how we can get code coverage numbers for unit, selenium tests for API, GUI, and/or Server.
  • [NEW] Portable manual testing: write test plan to enable community or others to execute
  • [NEW] Inform QA and community about how Sign In and PiCL work: Give demo
• Continuous Deployment
  • [NEW] Research: Write wiki on how we can releases to sample and measure. Release to IP range, percentage of users, monitoring metrics requirements.
• Reduce end game risk, no suprises:
  • [NEW] Write wiki to set deployment criteria at start of a project
  • [NEW] Write deployment checklist
  • [NEW] Write wiki: How do we find bugs earlier in cycle

Drive b2g success:

• [NEW] Execute test pass on B2G and log all bugs early in cycle.

Community Contribution

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

Archived Links