QA/Execution/Web Testing/Meetings/2015-10-29: Difference between revisions

 
(15 intermediate revisions by 3 users not shown)
Line 1: Line 1:
= Meeting details =
= Meeting details =
{{:QA/Execution/Web Testing/Meetings}}
{{:QA/Execution/Web Testing/Meetings}}
* [https://air.mozilla.org/web-qa-weekly-meeting-20150723/ Recording]
* [https://air.mozilla.org/web-qa-weekly-meeting-20151029/ Recording]


=  Lead / Scribe =
=  Lead / Scribe =
Line 25: Line 25:
* [davehunt] Also welcome back [https://webqa-ci.mozilla.com/view/Bouncer/ Bouncer]!
* [davehunt] Also welcome back [https://webqa-ci.mozilla.com/view/Bouncer/ Bouncer]!
** Retention also set to 4 weeks due to builds running every 5 minutes.
** Retention also set to 4 weeks due to builds running every 5 minutes.
* [davehunt] GitHub isn't smart enough to auto close issues resolved by pull requests unless we follow [https://help.github.com/articles/closing-issues-via-commit-messages/ their documentation]. Can we try to adopt this, or to at least manually close issues after they've been resolved.
* [davehunt] Can we try to [https://help.github.com/articles/closing-issues-via-commit-messages/ close issues via commit message], or ensure we manually close issues when they're resolved?
* [bsilverberg] Can we turn on author attribution on the Web QA blog?
* [bsilverberg] Can we turn on author attribution on the Web QA blog?
* [davehunt] Our new Bedrock functional tests picked up on a [https://bugzilla.mozilla.org/show_bug.cgi?id=1219251 Firefox crasher]!
* [davehunt] Our new Bedrock functional tests picked up on a [https://bugzilla.mozilla.org/show_bug.cgi?id=1219251 Firefox crasher]!
* [davehunt] We also had a test fix due to a locator change, [https://github.com/mozilla/bedrock/commit/385a6c752efffa1c67418f7033eff41aaea0c42f in the same commit]!
* [davehunt] pytest-selenium 1.0 has been released! I'll be working on migrating projects.
* [davehunt] I'm experimenting with GitHub webhooks to trigger Jenkins jobs.
* [davehunt] I've created a [[QA/Execution/Web_Testing/Automation/Baseline|wiki page]] to track how we're progressing towards certain automation goals.
* [mbrandt] proposal to bring back tea time


= [https://wiki.mozilla.org/QA/Execution/Web_Testing/Goals/2015/Q4 Goals Check-in] - 1st and 3rd meetings, monthly =
= [https://wiki.mozilla.org/QA/Execution/Web_Testing/Goals/2015/Q4 Goals Check-in] - 1st and 3rd meetings, monthly =
Line 45: Line 50:
** Marketplace / AMO
** Marketplace / AMO
** MDN
** MDN
*** BrowserCompat Skateboard - preparing for a large splash of work eoq if this lands in Q4.
**** https://docs.google.com/document/d/1J8Ip8NjXTcnMcsOg4OWtvWvT1vCgQnMU3_Ug7HB9m64/edit#heading=h.1v3746wcnaxa
** Mozilla.org
** Mozilla.org
*** [davehunt] Bedrock functional tests now running in their [https://ci.us-west.moz.works/view/Bedrock%20Pipeline/?fullscreen=true build pipeline]!
*** [davehunt] Bedrock functional tests now running in their [https://ci.us-west.moz.works/view/Bedrock%20Pipeline/?fullscreen=true build pipeline]!
** MozTrap
** MozTrap
** Mozillians
*** Stephend and Pierros are working on a plan to define potential support levels
*** The dev team has planned a 1 month sprint for Nov 15 - Dec 15, 2015
**** Web QA has committed to helping co-host a test day
**** Dev team will ideate one&done tasks and git issues
** One and Done
** One and Done
** Socorro
** Socorro
*** Arian sent out a missive - instead of report numbers being generated during daily crons, the project is beginning the move to real time number crunching
**** New reports - will become final in ~2 weeks, after feedback from users, crash-stat links will be updated to point to these reports then
**** TCBS -  https://crash-stats.mozilla.com/topcrashers/?product=Firefox&version=42.0b&date_range_type=report&process_type=browser&platform=&_facets_size=50&days=7
***Daily Crashes - https://crash-stats.mozilla.com/crashes-per-user/?p=Firefox
** SUMO
** SUMO
* Available for ownership:
* Available for ownership:
Line 59: Line 76:
If you've worked on Jenkins or Selenium Grid in the last week, add the necessary info in the Wiki
If you've worked on Jenkins or Selenium Grid in the last week, add the necessary info in the Wiki
* [davehunt] I've upgraded staging Jenkins to 1.625.1 with the latest plugins. If it's all still looking good I'll apply the updates to production.
* [davehunt] I've upgraded staging Jenkins to 1.625.1 with the latest plugins. If it's all still looking good I'll apply the updates to production.
* [stephend] [https://wiki.mozilla.org/QA/Execution/Web_Testing/Automation/Selenium_Grid#Windows_Nodes selenium4] (Windows VM in SCL3) was restarted last night by :gcox - it was causing bedrock + bidpom build failures
** we should all familiarize ourselves with [https://bugzilla.mozilla.org/attachment.cgi?id=8659209 vSphere-control instructions]


= Community update =
= Community update =
Line 73: Line 92:


= Action items =
= Action items =
*
* {{prev|}}[davehunt] Look into latest Selenium (2.48) upgrade
* {{new|}}[stephend] Provide [davehunt] with suitable dev owners for Bouncer and Snippets
* {{done|}}[davehunt] Add Matt as a co-owner for Bouncer jobs
* {{new|}}[bsilverberg] Follow up with Craig Cook about adding an author credit to our blog
* {{new|}}[mbrandt] E-mail mailing list about setting up more 'tea time' meetings


= Next Meeting =
= Next Meeting =
* Next owner / scribe:
* Next owner / scribe: [mbrandt]
* Next week's meeting notes:
* Next week's meeting notes: [rbillings]
Confirmed users
2,177

edits