Confirmed users
6,361
edits
QA/Browser Technologies/2012-02-23: Difference between revisions
QA/Browser Technologies/2012-02-23 (view source)
Revision as of 20:04, 23 February 2012
, 23 February 2012→Action Items
| (2 intermediate revisions by the same user not shown) | |||
| Line 14: | Line 14: | ||
* How to handle maple fixed bugs? (fennec team discussion) | * How to handle maple fixed bugs? (fennec team discussion) | ||
** <strike>Tony's suggestion is comment in bugs on latest maple builds, and use whiteboard "verified-maple". Then reverify after it lands on M-C later. </strike> | ** <strike>Tony's suggestion is comment in bugs on latest maple builds, and use whiteboard "verified-maple". Then reverify after it lands on M-C later. </strike> | ||
** '''discussion''' wait until maple merges on m-c, then verify fixes, regressions and qawanted bugs | ** '''discussion''' wait until maple merges on m-c, then verify fixes, regressions and qawanted bugs afterwards. | ||
* Next Testdays Plans? | * Next Testdays Plans? | ||
| Line 30: | Line 30: | ||
** [https://mozqa.etherpad.mozilla.org/mozbtech-communityPlan Etherpad] of ideas | ** [https://mozqa.etherpad.mozilla.org/mozbtech-communityPlan Etherpad] of ideas | ||
** wiki cleanup, new projects for QMO, etc.. | ** wiki cleanup, new projects for QMO, etc.. | ||
** '''update''' list of actionable tasks broken down for this quarter. See Notes below. | |||
* Case conductor status (cam) | * Case conductor status (cam) | ||
| Line 84: | Line 85: | ||
= Round Table = | = Round Table = | ||
= | = Action Items = | ||
Community Plans | |||
Tracy: | |||
* blog 3 times this quarter on your project (either on QMO or personal) | |||
* create 1 actionable project on QMO (getting involved with Sync) | |||
Aaron: | |||
* blog 3 times this quarter on your project (either on QMO or personal) | |||
* create 1 actionable project on QMO (Web compatibility testing across devices?) | |||
Martijn: | |||
* write QMO blog post and point to the robocop wikis. or taking a litmus test and how they can create an automated test | |||
James: | |||
* mentoring a college student to learn how to test BrowserID (Zak from fort lewis college) | |||
* goal is to write testcases, and move them to case conductor | |||
JRGM: | |||
* blogpost on selenium tests for BrowserID. provide examples, screenshots, and what areas we still need for tests. | |||
Kevin: | |||
Naoki: | |||
* write blogpost on detecting and killing crashes | |||
* talk about socorro stuff [done/ongoing] | |||
* introduce pancake development and status of beta | |||
* write a blogpost on general exploratory testing | |||
* talk to jaclyn and video tape them on their demos, broadcast their videos on QMO. | |||
Tony | |||
* write a blogpost on reading and posting bugzilla metrics for web compatibility | |||
* cleaning up old services and fennec wikis | |||