TestEngineering/Services: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Pointer to new docs.)
 
(43 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.
=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  ==
 
{| class="fullwidth-table"
|-
| style="background:#EFEFEF; width:30%" | '''Name'''
| style="background:#EFEFEF; width:30%" | '''Contact'''
| style="background:#EFEFEF; width:10%" | '''Availability'''
| style="background:#EFEFEF; width:30%" | '''Project Assignments'''
|-
| Edwin Wong
| [mailto:edwong@mozilla.com edwong@mozilla.com]
| MoCo Employee (full time)
| Services QA Manager
|-
| John Morrison
| [mailto:jrgm@mozilla.com jrgm@mozilla.com]
| MoCo Employee (full time)
| Server side QA
|-
| James Bonacci
| [mailto:jbonacci@mozilla.com jbonacci@mozilla.com]
| MoCo Employee (full time)
| Server side QA
|-
| Karl Thiessen
| [mailto:kthiessen@mozilla.com 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.
 
[https://wiki.mozilla.org/QA/Browser_Technologies/Services/Releases Services QA: All Releases]
 
[https://wiki.mozilla.org/QA/Browser_Technologies/Services/Releases/BrowserID BrowserID Releases]
 
=Projects=
<onlyinclude>
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.
 
{| class="fullwidth-table"
| [https://wiki.mozilla.org/QA/BrowserID/TestPlan BrowserID Test Plan]
| BrowserID allows users with a verified email address against Mozilla platform to request access to websites
| John
|-
| [https://wiki.mozilla.org/Identity/AttachedServices PiCL (Profile in the Cloud)]
| Service that allows users to access synced bookmarks, history, web apps, and passwords from any device.
| James
|-
| [https://wiki.mozilla.org/QA/Firefox_Share_Test_Plan Firefox Share Test Plan]
| A feature for the browser&nbsp;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)
|-
| [https://wiki.mozilla.org/QA/Sync/Test_Plan/grinder_tests Load Test Refactoring]
| Refactoring current Grinder tests to support functional tests with FunkLoad environment
| Owen
|}
</onlyinclude>
 
=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 [https://intranet.mozilla.org/QA/Mozilla_Services_Environment 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
** [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 Persona/BrowserID documentation
** [https://wiki.mozilla.org/QA/BrowserID QA Persona/BrowserID site]
 
* QA AITC/TokenServer documentation
** [https://wiki.mozilla.org/QA/AITC_TS QA AITC and TokenServer site]
 
* Automated Testing
** [https://wiki.mozilla.org/QA/BrowserID_Automation 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=
[https://wiki.mozilla.org/QA/Services_Archive Archived Links]

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"