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

From MozillaWiki
< QA‎ | Execution‎ | Web Testing‎ | Meetings
Jump to navigation Jump to search
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:

Revision as of 15:48, 11 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

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
  • MDN
    • 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

  • Takeways:
  • Action Items:
  • Next owner / scribe:
  • Next week's meeting notes: