Confirmed users
6,361
edits
QA/Browser Technologies/Meetings/2013-01-29: Difference between revisions
QA/Browser Technologies/Meetings/2013-01-29 (view source)
Revision as of 15:35, 29 January 2013
, 29 January 2013→BrowserID Updates
| Line 67: | Line 67: | ||
* Mozilla (Tony) | * Mozilla (Tony) | ||
=== Goals Draft === | |||
* Deliverables | |||
** Goal: Qualify the deployment of Fennec Native for Android to Google Play | |||
*** {{new|}} Qualify Firefox Native 19, 20 for Android | |||
**** {{new|}} support deployment of Armv6 Device 600Mhz | |||
- evaluating lower device chip and memory requirements, and screen size. conducting a testplan that will qualify the lower requirement support | |||
**** {{new|}} support deployment of x86 devices (pending Google Play compatibility) | |||
*** {{new|}} supporting WebRTC for Android Fennec (understand their roadmap and what needs testing | |||
*** {{new|}} supporting Marketplace for Android Fennec (Aaron confirm if this is a Q1 goal) | |||
*** {{new|}} support Sync 2.0 Android Fennec (Tracy to confirm if this is a Q1 goal) | |||
*** {{new|}} support WebGL for Android Fennec (Kevin to confirm if this is a Q1 goal) | |||
*** {{new|}} Support testing of MWC test scripts | |||
** Goal: Implement Automation Coverage against Fennec | |||
*** {{carry|}} Identifying 2-3 smoketests on new features for Robocop automation | |||
*** {{carry|}} Work through the BFTs, building out more tests for Robocop automation | |||
*** {{new|}} run this against our own test environment (aka get a pandaboard) | |||
*** {{new|}} automate stress tests? (eg. open 100 tabs, creating 1000 bookmarks, syncing large accounts, etc.. SV owning) | |||
*** {{carry|}} Develop Automated and reporting coverage for website compatibility detection (what happened to Spade?) | |||
** Goal: Increase interaction within the Mobile Community | |||
** {{new|}} Posting monthly updates and involvment projects to blogs, social media, and newsgroups | |||
--- Weekly blogposts (or communication method) on QMO on something exciting this week, crashers we're finding, useful URLs. Something that can be tweeted or blogged. We dont want static content. Focus more on forward facing versus status'y stuff. | |||
**** Reworking the QA/Fennec hierarchal wiki pages. They should be clear and organized as a Test Strategy should be. (summary, channel pages, localization, testplans and results for each build, a template for future releases, howTo steps for community, tutorials on flags and such) | |||
** {{new|}} provide documentation and how to write testcases for robocop | |||
** {{new|}} Add a One-and-Done project per month | |||
** {{new|}}} Identify and outreach to more new community members | |||
==Community == | ==Community == | ||