QA/Execution/Web Testing/Meetings/2014-05-08

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

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:
    • Stephen
  • 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:
  • Action Items:
    • [DONE] Dave - organise meeting between mbrandt, dave, psiinon about ZAP job on Jenkins
    • Stephen - Follow up with Krupa about keeping Mac job for AMO
    • Dave - Lightning talk about iPython and iPython Notebook

Discussion Items / Updates

Setup goals for finalizing testing tools/API's for OneAndDone and get started [:bitgeeky]

Testday Ideas

Blog Ideas

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

Lightning talk / Show 'n Tell

  • [davehunt] iPython and iPython Notebook

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

  • Affiliates
  • Bouncer
  • Engagement
  • Firefox Health Report
  • Firefox OS
  • Marketplace / AMO
  • Mozillians
  • MDN
  • Plugin Check:
  • Socorro
  • SUMO
  • MozTrap
  • 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

  • Julian - PTO: May 13 - 19
  • bsilverberg - Working from Mineappolis - May 13 - 16

Takeaways and Action Items

  • Takeways:
    • Future work - Build out a new Jenkins instance just for b2g testing (stephend, retornam)
  • Action Items:
    • Raymond and Stephen to work with jabba to get ldap auth back on Jenkins
    • Dave - Lightning talk about iPython and iPython Notebook
    • Raymond - add a Flame to the current Jenkins
      • Switch out one Hamachi for the Flame
      • Zac to set up the job(s) for the Flame
    • bitgeeky to move forward with oneanddone-tests using the "old way"
      • tests in their own repo and using the API for data population