Confirmed users
964
edits
TestEngineering/Services: Difference between revisions
→Team Goals
| Line 117: | Line 117: | ||
=Team Goals= | =Team Goals= | ||
* | === Services QA 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= | =Community Contribution= | ||