Confirmed users
9,511
edits
QA/Team Meeting/QA Team Meeting-2014-10-22: Difference between revisions
Jump to navigation
Jump to search
QA/Team Meeting/QA Team Meeting-2014-10-22 (view source)
Revision as of 16:43, 24 October 2014
, 24 October 2014→Action Items and notes from the meeting
| Line 53: | Line 53: | ||
== Action Items and notes from the meeting == | == Action Items and notes from the meeting == | ||
* Please '''bold''' action items. | * Please '''bold''' action items. | ||
* good feedback from those attended both the Profiler and Mozmill training: | |||
** wish it were longer (some) | |||
** others wished it were more hands-on | |||
** install your own, write your own test, have a prepared (bad) test to debug | |||
** immediacy (not useful for everyone right now. useful in 3 months) | |||
** call out the pre-reqs a bit better (vpn access for mozmill-ci, etc) | |||
* other feedback about types of requested training: | |||
** (desired) high-level overview of our testing frameworks + their uses (MDN lists some) | |||
** Advanced/useful Bugzilla querying | |||
** perhaps a refresher on Moztrap? | |||
** how to make the best use out of Air Mozilla, across QA | |||
** intro to debugging, using wireshark, etc | |||
Tiles load testing: | |||
* takeaway from anything that depends on Services/Websites: | |||
** ask questions/coordinate/double-check that a feature in Firefox/elsewhere doesn't depend on a service/website, or -- if it does -- that it's covered with backend/integration testing, or called out as a risk | |||
* find out how we can tell if a particular machine/graphics card is in the slow path (<--- liz, help! did I capture this right?) I am not sure what people we're talking about here. - liz | |||
* Firefox releases: | |||
** have a little less than 1 1/2 weeks to get ready for the 33.1 release deadline | |||
** please use the Alder branch as your primary test build for the forseeable future | |||
** please sign up for the Firefox 10-year anniversary mailing list for testing challenges | |||
** should see localized tiles for your particular locale | |||
*Ways we can help catch graphics/other issues in the future: | |||
** see if you can help come up with ideas to try to catch graphics-card issues in the wild | |||
*** feel free/encouraged to email qa@mozilla.org / post to mozilla.dev.quality (goes to the same place, so no need to post twice) | |||
** push the bug filed last year, filed to audit blacklisting (aaron) | |||
** downgrading video drivers. how to. we need documentation.... (kevin) | |||
** support after crash? (or in FHR) | |||
* perhaps we should get graphics-driver information into about:support (kairo) +1!!! | |||
* advocate for ability for end user to turn off risky feature (via pref) in the future? | |||
* not enough data, typically, to back up our risk-assessed push-back decisions, from betas | |||
** then we get burned in release | |||
** what kind of mechanisms can we get in place, to help validate our push-back and quality assessments, going forward? | |||
** lots of data point to a combination of integrated chipset with an additional video card -- most-evidenced in laptops | |||
** we're examining the most-common/most-problematic configurations (at least from SUMO/Socorro) | |||
** we should look into what Telemetry data can provide us, as well | |||
** '''Request from Juan''': | |||
* get your Firefox feature tests, per area (in whatever form they exist), over to Juan, so he can build out the E10S test-suite | |||
* We will take notes on [https://etherpad.mozilla.org/qa-team-meeting-notes this etherpad] | * We will take notes on [https://etherpad.mozilla.org/qa-team-meeting-notes this etherpad] | ||