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

From MozillaWiki
< QA‎ | Execution‎ | Web Testing‎ | Meetings
Jump to navigation Jump to search
 
(12 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]!
Line 32: Line 32:
* [davehunt] I'm experimenting with GitHub webhooks to trigger Jenkins jobs.
* [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.
* [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 49: 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 63: 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 77: 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]

Latest revision as of 13:53, 3 November 2015

Meeting details

Please see our public calendar for all upcoming events and meetings.

Our regular team meeting occurs every Thursday @ 9am Pacific

Lead / Scribe

  • Lead: Bob
  • Scribe: Dave
    • Scribe is responsible for:
      • adding the action items and takeaways to the current meeting's minutes
      • creating the agenda for the next meeting and carrying the action items and takeaways over to it
      • sending out a notice of the availability of that agenda along with the meeting invite
      • completing all of the above by the end of the week during which the meeting occurred

Last week's action items

  • [davehunt] Look into latest Selenium (2.48) upgrade
  • [DONE] [davehunt] Remove HOSTS entry for www-dev.allizom.org on Selenium-staging nodes
  • [all] Reminder to remove your dev/staging HOSTS entries for testing PHX1-exit migration

Read-only

Discussion items

  • [davehunt] Welcome back Snippets to our Jenkins!
    • Three builds running every 10 minutes - I've set the build retention to 4 weeks.
  • [davehunt] Also welcome back Bouncer!
    • Retention also set to 4 weeks due to builds running every 5 minutes.
  • [davehunt] Can we try to 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?
  • [davehunt] Our new Bedrock functional tests picked up on a Firefox crasher!
  • [davehunt] We also had a test fix due to a locator change, 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 wiki page to track how we're progressing towards certain automation goals.
  • [mbrandt] proposal to bring back tea time

Goals Check-in - 1st and 3rd meetings, monthly

Upcoming Events

The Web QA Events page shows any upcoming meetups, test days, and other events for the team.

Blog Ideas

Have ideas you want to blog about, or you think would make interesting topics? Note them here! this is a template, so update here please

Lightning talks

Project status / goals for next week (keep it brief)

    • SUMO
  • Available for ownership:
    • Webmaker
    • REMO/Mozilla Reps
    • Wiki

CI updates

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.
  • [stephend] selenium4 (Windows VM in SCL3) was restarted last night by :gcox - it was causing bedrock + bidpom build failures

Community update

Time off / Out-of-office

PTO and other time out of office for Firefox Test Engineering

  • [davehunt] - October 26 - PTO
  • [davehunt] - December 12-14 - Honolulu marathon

Buildmaster (2-week duration)

  • Hands off to the next person at the end of the current Buildmaster's 2-week role, in the Web QA Thursday meeting

Rotation

The Web QA Buildmaster Rotation page contains the past and upcoming schedule.

These entries are in reverse chronological order.

  • 2016-05-05 - 2016-05-19 - stephend
  • 2016-04-21 - 2016-05-05 - mbrandt
  • 2016-04-07 - 2016-04-21 - davehunt
  • 2016-03-24 - 2016-04-07 - rbillings
  • 2016-03-10 - 2016-03-24 - krupa

Action items

  • [CARRY OVER] [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 owner / scribe: [mbrandt]
  • Next week's meeting notes: [rbillings]
Retrieved from "https://wiki.allizom.org/index.php?title=QA/Execution/Web_Testing/Meetings/2015-10-29&oldid=1103924"