QA/Execution/Web Testing/Meetings/2014-02-13

From MozillaWiki
< QA‎ | Execution‎ | Web Testing‎ | Meetings
Jump to: navigation, search

Meeting Details

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

Our regular team meeting occurs every Thursday @ 9am Pacific

User / Scribe

  • stephend / AndreiH

Action Items / Takeaways from Last Week

  • Takeways:
    • Think about ways to start measuring and reporting on the goals for the team
  • Action Items:
    • Bob to consider giving an overview/demo of the new mozwebqa dashboard
      • [bsilverberg] My apologies but I'm not sure what the action here is. I believe I demoed the Marketplace Tests dashboard at a previous meeting, but would be happy to show the issues dashboard. Is the intended audience of this a group other than Web QA?

Discussion Items / Updates

  • Let's discuss and then make team decisions to end the confusion around:
    • Whose job it is to send next week's meeting invite, and by when
    • Who populates/carries over the previous week's action items and takeaways
      • [bsilverberg] A suggestion: The 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
  • I'd like -- where possible -- Travis jobs for our automation
  • We started tracking our work on WebQA in:
  • Are we using http://mozilla.github.io/mozwebqa-dashboard/#/xfails? Are we also pointing community at it? If not to either, why not? :-)
  • Tutorial for getting started with Firefox OS is almost complete:
    • https://docs.google.com/document/d/1FFgITAa6trKkCypkvu81Dg-E0EEp8OdzmgFRk0yFdAk/edit
    • Please read and feedback (annotate in the doc)
    • Even if you want to *do* the tutorial that would be even better; it should take 1-2 hours.
    • It is aimed at being a hands off way to give newb contributors skills in test automation and Firefox OS
    • Plan to move to MDN where we can translate it and also track page metrics through each section of the test (ie how far the person gets)
    • Want to have it uploaded next week

Goals Check-in

Testday Ideas

Blog Ideas

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

Lightning talk / Show 'n Tell

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

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