QA/Browser Technologies/Services: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 96: Line 96:


=Resources=
=Resources=
* <add your links here> 
* Sync Client and Server Test Plans
** [https://wiki.mozilla.org/QA/Sync/Test_Plan#Client Client Test Plan]
** [https://wiki.mozilla.org/QA/Sync/Test_Plan#Servers Server Test Plan]
** [https://wiki.mozilla.org/QA/Sync/Test_Plan/grinder_tests Grinder]
*** This will be replaced by FunkLoad for Sync Server API automation
** [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 Sumamries]


* [https://wiki.mozilla.org/Services/Process/ServerReleaseProcess Server Release Process] - Breakdown of the deployment for weekly server work
* [https://wiki.mozilla.org/Services/Process/ServerReleaseProcess Server Release Process] - Breakdown of the deployment for weekly server work
* 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://bugzilla.mozilla.org/enter_bug.cgi?product=mozilla.org&format=itrequest Bugzilla IT Request]
* [https://bugzilla.mozilla.org/enter_bug.cgi?alias=&assigned_to=nobody@mozilla.org&blocked=&bug_file_loc=http://&bug_severity=normal&bug_status=NEW&cf_blocking_191=---&cf_blocking_192=---&cf_blocking_20=---&cf_blocking_fennec=---&cf_crash_signature=&cf_status_191=---&cf_status_192=---&cf_status_20=---&cf_status_firefox5=---&cf_status_firefox6=---&cf_status_firefox7=---&cf_tracking_firefox5=---&cf_tracking_firefox6=---&cf_tracking_firefox7=---&comment=&component=Operations&contenttypeentry=&contenttypemethod=autodetect&contenttypeselection=text/plain&data=&dependson=&description=&flag_type-325=X&flag_type-354=X&flag_type-37=X&flag_type-4=X&flag_type-607=X&flag_type-647=X&flag_type-708=X&flag_type-720=X&flag_type-721=X&form_name=enter_bug&groups=services-infra&keywords=&maketemplate=Remember%20values%20as%20bookmarkable%20template&op_sys=Linux&priority=--&product=Mozilla%20Services&qa_contact=operations@services.bugs&rep_platform=All&requestee_type-325=&requestee_type-4=&requestee_type-607=&short_desc=&status_whiteboard=&target_milestone=---&version=unspecified Bugzilla OPs Request]
* Services
** [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]
* BrowserID Information
** TBD
* Tools
** TPS
*** [https://wiki.mozilla.org/Auto-tools/Projects/CrossWeave CrossWeave site 1]
*** [https://wiki.mozilla.org/Services/Sync/FxSync/Crossweave2 CrossWeave site 2]
*** [https://hg.mozilla.org/automation/crossweave CrossWeave in Mercurial]
*** [https://wiki.mozilla.org/Services/Sync/TPS TPS]
*** [https://developer.mozilla.org/en/TPS TPS developer site]
*** [https://hg.mozilla.org/services/tps TPS in Mercurial]
** FunkLoad
*** [http://funkload.nuxeo.org/ FunkLoad Main Site]
*** [http://funkload.nuxeo.org/installation.html FunkLoad Documentation]
*** [http://blog.redturtle.it/redturtle-blog/how-to-write-funkload-test-in-few-minutes FunkLoad Tutorial]
*** [http://pypi.python.org/pypi/funkload/ FunkLoad Downloads]
*** [https://github.com/highriseo/funk-smoke FunkLoad In-House Site]


=Meetings=
=Meetings=

Revision as of 03:21, 25 July 2011

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
Tony Chung tchung@mozilla.com MoCo Employee (full time) QA Team Manager
James Bonacci jbonacci@mozilla.com MoCo Employee (full time) Team Lead, Sync server, load, Identity
Tracy Walker twalker@mozilla.com MoCo Employee (full time) Client side QA, Sync specialist
Owen Coutts ocoutts@mozilla.com MoCo Intern Load testing guru

Current Status

  • Updated: July 8, 2011
  • Sync - Client
    • InstantSync: landed on Fx6 beta
    • Sync Setup Improvements: wip
  • Sync - Server
    • Python Sync server deployed
    • Load: FunkLoad project underway (server ops). QA investigation and planning full steam ahead
  • Identity
    • Server: wip, prototype
    • Client: ?? (ask ddahl)
  • Notifications: In design
  • F1 Share: On Hold. moved to labs for design

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.

Project Description QA Owner
Firefox Sync Test Plan Firefox Sync site (both extension and Integrated feature) summarizing Test strategy, testcases, Milestone testplans, and schedules Tracy
Sync Server Documentation Sync Server main site summarizing Dev, OPs, and QA tasks and responsibilities James
Identity Documentation Identity allows users with a verified email address against Mozilla platform to request access to websites James
Notifications Spec Push notifications from the cloud to the browser and other 3rd party clients TBD
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
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

  • BrowserID Information
    • TBD

Meetings

Services Team status meetings 

 Dial In: 800-707-2533 conf 8616
  at 9am PDT (4th floor)
 irc.mozilla.org #services for backchannel

Team Goals

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.
Retrieved from "https://wiki.mozilla.org/index.php?title=QA/Browser_Technologies/Services&oldid=332814"