TestEngineering/Services: Difference between revisions

Jump to navigation Jump to search

TestEngineering/Services (view source)

Revision as of 23:28, 7 October 2013

859 bytes removed ,  7 October 2013
no edit summary
No edit summary
Line 70: Line 70:
  | 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
  | 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)
  | 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>
</onlyinclude>


Line 118: Line 114:


=Meetings=
=Meetings=
* TBD
* Monday 3pm - Vidyo: QA


=Team Goals=
=Team Goals=
Identity
Goals are attached to core Cloud Services Goals
Deliverables:
Goals specific to QA are:
* {{new|}}Add AWS webhead to data center
* Add automated test cases
* {{new|}}Deploy bigtent - gmail
* Support Deployments
* {{new|}}Deploy bigtent - hotmail
* Log bugs
* Review test coverage and test cases
* Advocate for users


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.   
=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 #Identity or #Services-dev if you're interested.
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:
'''Anyone can participate.''' There are several ways in which '''YOU''' can participate:
* File bugs
* File bugs
Edwong
Confirmed users
964

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/724321"

Navigation menu