QA/Execution/Web Testing/Meetings/2014-09-11: Difference between revisions

From MozillaWiki
< QA‎ | Execution‎ | Web Testing‎ | Meetings
Jump to navigation Jump to search
(Created page with "<small>Web QA Home</small> = Meeting Details = {{:QA/Execution/Web Testing/Meetings}} = Lead / Scribe = * Lead: ** Bob * Scribe: ** Matt ** Sc...")
 
 
(9 intermediate revisions by 3 users not shown)
Line 17: Line 17:
* Takeways:
* Takeways:
** bob and davehunt to add documentation on how to --squash [carryover]
** bob and davehunt to add documentation on how to --squash [carryover]
*** WIP - https://wiki.mozilla.org/Web_Testing/Automation/CodeReviewProcess#Squashing_commits_before_merging_a_feature_branch
** stephend do a blog post about the lab. [carryover]
** stephend do a blog post about the lab. [carryover]
* Action Items:
* Action Items:
Line 24: Line 25:


= Discussion Items / Updates =
= Discussion Items / Updates =
* Selenium updates - if, when and how often [bsilverberg]
* Gift from the team and community [mbrandt]


= [https://wiki.mozilla.org/QA/Goals/2014q3 Goals Check-in] - 1st and 3rd meetings, monthly =
= [https://wiki.mozilla.org/QA/Goals/2014q3 Goals Check-in] - 1st and 3rd meetings, monthly =
Line 32: Line 35:
= Blog Ideas =
= Blog Ideas =
If you have any ideas for blog posts, share them here.
If you have any ideas for blog posts, share them here.
*  
* Draft a call to action + team change post
* Draft roles post
* Explore what does means to be an expert
* Community test plan - how we do CD
* How dev can work with automation
* Blog post about the lab and how we scale


= Lightning talk / Show 'n Tell =
= Lightning talk / Show 'n Tell =
Line 38: Line 46:
= Project Status / goals for next week (keep it brief)  =
= Project Status / goals for next week (keep it brief)  =
*Affiliates
*Affiliates
** investigating spurious automation failures - pull request inbound after our meeting
*Bouncer
*Bouncer
** continuing to capture data so we can investigate why the service sometimes appears to 500
*Engagement
*Engagement
*Firefox Health Report
*Firefox Health Report
** No updates
*Firefox OS
*Firefox OS
*Marketplace / AMO
*Marketplace / AMO
*Mozillians
*Mozillians
*Mozilla.com
*Mozilla.com
** Testing Legal notice updates
*MDN
*MDN
** Tested GitHub sign in ability
** Continuous deployment, no updates
** Continuous deployment, no updates
*Socorro
*Socorro
** Continuous delivery, no updates
*SUMO
*SUMO
** Continuous deployment, no updates
** Continuous deployment, no updates
*MozTrap
*MozTrap
** priority feature requests have been synced from Bugzilla to https://www.pivotaltracker.com/s/projects/280483
** project dev env setup README has been vetted for correctness
** bug verification and automation coverage continue to be the current focus
*Wiki
*Wiki


Line 62: Line 79:


= Takeaways and Action Items =
= Takeaways and Action Items =
* Takeways:
* Action Items
**
** [bsilverberg] carry-over, is drafting the —squash post
* Action Items:
** [AndreiH] ping Matt about writing blog post
**
** [AndreiH] to work with [mbrandt] on updating the moz-grid-config notes for upgrade notes, what are the touch points to update in a pull request?
** [stephend] draft a post/testday
** [bsilverberg] give screencast prezo to rbillings and mbrandt
* Next owner / scribe:
* Next owner / scribe:
** juilan / stephend
* Next week's meeting notes:
* Next week's meeting notes:

Latest revision as of 00:52, 17 September 2014

Web QA Home

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:
    • Matt
    • 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

Action Items / Takeaways from Last Week

Discussion Items / Updates

  • Selenium updates - if, when and how often [bsilverberg]
  • Gift from the team and community [mbrandt]

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

Testday Ideas

Blog Ideas

If you have any ideas for blog posts, share them here.

  • Draft a call to action + team change post
  • Draft roles post
  • Explore what does means to be an expert
  • Community test plan - how we do CD
  • How dev can work with automation
  • Blog post about the lab and how we scale

Lightning talk / Show 'n Tell

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

  • Affiliates
    • investigating spurious automation failures - pull request inbound after our meeting
  • Bouncer
    • continuing to capture data so we can investigate why the service sometimes appears to 500
  • Engagement
  • Firefox Health Report
    • No updates
  • Firefox OS
  • Marketplace / AMO
  • Mozillians
  • Mozilla.com
    • Testing Legal notice updates
  • MDN
    • Tested GitHub sign in ability
    • Continuous deployment, no updates
  • Socorro
    • Continuous delivery, no updates
  • SUMO
    • Continuous deployment, no updates
  • MozTrap
    • priority feature requests have been synced from Bugzilla to https://www.pivotaltracker.com/s/projects/280483
    • project dev env setup README has been vetted for correctness
    • bug verification and automation coverage continue to be the current focus
  • Wiki

CI Updates

If you've worked on Jenkins or Selenium Grid in the last week, add the necessary info in the Wiki

Community Update

Time off / Out-of-office

Takeaways and Action Items

  • Action Items
    • [bsilverberg] carry-over, is drafting the —squash post
    • [AndreiH] ping Matt about writing blog post
    • [AndreiH] to work with [mbrandt] on updating the moz-grid-config notes for upgrade notes, what are the touch points to update in a pull request?
    • [stephend] draft a post/testday
    • [bsilverberg] give screencast prezo to rbillings and mbrandt
  • Next owner / scribe:
    • juilan / stephend
  • Next week's meeting notes: