TestEngineering/Services: Difference between revisions
Line 8: | Line 8: | ||
== Source Repositories == | == Source Repositories == | ||
==== Firefox Accounts ==== | |||
* Authentication | * Authentication | ||
** https://github.com/mozilla/fxa-auth-server | ** https://github.com/mozilla/fxa-auth-server | ||
Line 17: | Line 17: | ||
* Client bugs and tracking issues are filed in bugzilla, here's the tree view: | * Client bugs and tracking issues are filed in bugzilla, here's the tree view: | ||
** https://bugzilla.mozilla.org/showdependencytree.cgi?id=969593&hide_resolved=1 | ** https://bugzilla.mozilla.org/showdependencytree.cgi?id=969593&hide_resolved=1 | ||
* Load Testing | |||
** TokenServer and Sync 1.5 Load Testing: https://wiki.mozilla.org/QA/Services/TokenServerAndSyncLoadTesting | |||
** FxA Load Testing: https://wiki.mozilla.org/QA/Services/FxALoadTesting | |||
** FxA, TS, Sync Test Environments: https://wiki.mozilla.org/QA/Services/FxATestEnvironments | |||
** Fxa/Sync 1.5 Test Plan: https://wiki.mozilla.org/QA/Services/SyncTestPlanV1 | |||
* Push Notification Server | * Push Notification Server | ||
Line 27: | Line 33: | ||
* Find My Device - Web | * Find My Device - Web | ||
** https://github.com/jrconlin/wmf/tree/dev | ** https://github.com/jrconlin/wmf/tree/dev | ||
* Heka | |||
** https://wiki.mozilla.org/QA/Services/HekaInfo | |||
''' SvcOps (moz-staff-only)''' | ''' SvcOps (moz-staff-only)''' |
Revision as of 16:31, 14 February 2014
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.
Mission: Building secure, user controlled cloud services that bring user delight and utility in a multi-screen world.
Current Projects
Update 2/13/2014
Source Repositories
Firefox Accounts
- Authentication
- Client bugs and tracking issues are filed in bugzilla, here's the tree view:
- Load Testing
- TokenServer and Sync 1.5 Load Testing: https://wiki.mozilla.org/QA/Services/TokenServerAndSyncLoadTesting
- FxA Load Testing: https://wiki.mozilla.org/QA/Services/FxALoadTesting
- FxA, TS, Sync Test Environments: https://wiki.mozilla.org/QA/Services/FxATestEnvironments
- Fxa/Sync 1.5 Test Plan: https://wiki.mozilla.org/QA/Services/SyncTestPlanV1
- Push Notification Server
- Find My Device - Web
SvcOps (moz-staff-only)
- https://github.com/mozilla-services/puppet-config
- https://github.com/mozilla-services/svcops-oompaloompas
Tools
- mozilla central incremental builds - https://tbpl.mozilla.org
- jenkins - https://ci.mozilla.org
monitoring (private)
- aws: https://moz-svc-dev.signin.aws.amazon.com/console
- https://app.stackdriver.com
- PROD FXA: http://kibana.shared.us-west-2.prod.mozaws.net/index.html#/dashboard/file/weblogs.json
- DEV FXA: http://logs.dev.lcip.org/kibana/index.html#/dashboard/file/weblogs.json
FxA - Where to log Bugs
- Desktop
- sync UI bugs: Firefox:Sync
- sync non UI bugs: Mozilla Services::Sync Backend
- authentication bugs: Core::FxA
- Fx for Android:
- Android UI bugs: Android Background Services:FxA
- Android non UI bugs: Android Background Services:Android Sync
- Sync servers:
- Mozilla Services::Server:Sync
- Mozilla Services::Server:Token
- ops - issues:
- mozilla services::operations
Resources
- Sync Client and Server Test Documents
- Sync Server Installation and Configuration
- QA Sync Server documentation
- QA AITC/TokenServer documentation
Meetings
- Monday 3:30pm - 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 #fxa 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.