QA/Execution/Web Testing/Meetings/2014-09-11
From MozillaWiki
< QA | Execution | Web Testing | Meetings
Contents
- 1 Meeting Details
- 2 Lead / Scribe
- 3 Action Items / Takeaways from Last Week
- 4 Discussion Items / Updates
- 5 Goals Check-in - 1st and 3rd meetings, monthly
- 6 Testday Ideas
- 7 Blog Ideas
- 8 Lightning talk / Show 'n Tell
- 9 Project Status / goals for next week (keep it brief)
- 10 CI Updates
- 11 Community Update
- 12 Time off / Out-of-office
- 13 Takeaways and Action Items
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
- Takeways:
- bob and davehunt to add documentation on how to --squash [carryover]
- stephend do a blog post about the lab. [carryover]
- Action Items:
- Matt to blog about how he does his test plans
- Matt to email dev-quality with tea time pairings
- AndreiH: ping Matt about writing blog post
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: