TestEngineering/Services: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
(Pointer to new docs.)
 
(26 intermediate revisions by 4 users not shown)
Line 1: Line 1:
= Overview =
Information about the Test Engineering team has largely moved off the Wiki -- see
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. 
https://firefox-test-engineering.readthedocs.io/
 
for the latest revisions of our team documentation.
= Mission =
Building 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.
 
=Current Status=
Update 2/13/2014
 
== Source Repositories ==
'''Firefox Accounts'''
* Authentication
** https://github.com/mozilla/fxa-auth-server
** https://github.com/mozilla/fxa-content-server
** https://github.com/mozilla/fxa-js-client
** https://github.com/mozilla/fxa-profile-server (in planning)
 
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
 
''' 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
** [https://wiki.mozilla.org/QA/Sync/Test_Plan#Client Client Test Plan]
** [https://wiki.mozilla.org/QA/Sync/Test_Plan#Servers Server Test Plan - out of date]
** [https://wiki.mozilla.org/QA/Sync/Test_Plan/grinder_tests Grinder - deprecated]
** [https://wiki.mozilla.org/QA/Sync/Test_Plan/Test_Level_Summaries#Client Client Summaries]
** [https://wiki.mozilla.org/QA/Sync/Test_Plan/Test_Level_Summaries#Servers Server Summaries - out of date]
 
* [https://wiki.mozilla.org/Services/Process/ServerReleaseProcess Server Release Process - out of date]
 
* Sync Server Installation and Configuration
** [http://docs.services.mozilla.com/howtos/run-sync.html Installation]
** [http://docs.services.mozilla.com/server-devguide/index.html Devguide]
** [http://docs.services.mozilla.com/server-devguide/configuration.html Configuration]
** [https://wiki.mozilla.org/Services/ Services Main Site]
** [http://docs.services.mozilla.com/ Services Documentation]
** [http://docs.services.mozilla.com/#services Services Information]
** [http://docs.services.mozilla.com/#server-side-development-guide Development Guide]
 
* QA Sync Server documentation
** [https://wiki.mozilla.org/QA/Sync QA Sync Server site]
 
* QA AITC/TokenServer documentation
** [https://wiki.mozilla.org/QA/AITC_TS QA AITC and TokenServer site]
 
=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.

Latest revision as of 18:19, 18 December 2017

Information about the Test Engineering team has largely moved off the Wiki -- see https://firefox-test-engineering.readthedocs.io/ for the latest revisions of our team documentation.

Retrieved from "https://wiki.allizom.org/index.php?title=TestEngineering/Services&oldid=1185903"