QA/Execution/Web Testing/Meetings/2012-10-04

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

Action Items / Takeaways from Last Week

  • Action Items:
      • (Bebe) Global vars will continue work on this week [carryover- not done yet]
      • (Matt/Bebe) Mozillians test day stop, collaborate and listen. Automation is our main target. Rbillings doing some manual testing. [done - testday is not ready yet, will come back later]
      • (All) Addons - do some work on it [ carryover - This is problematic, we should work on it, but don't stop working on marketplace in order to do this.]
      • (All) focus on test stability [carryover - This is ongoing, especially amo.dev. Would like to remove some tests to get this leaner and meaner.]


Discussion Items / Updates

  • Let's take a look at the <a href="https://wiki.mozilla.org/QA/Execution/Web_Testing/Contributor_Corner">Contributors Corner page</a> and come up with a few brainstorm ideas on how to make it look less like a rough draft!
  • Need someone(s) to step up and test/help test Bouncer - <a href="https://bugzilla.mozilla.org/buglist.cgi?list_id=4562337;classification=Server%20Software;query_format=advanced;component=Bouncer;target_milestone=2.0;product=Webtools">buglist</a>
    • there are test cases in the indiv. bugs, we can also ask for them. need a mtg for high level test cases.
    • I have a little more information from Laura, who's leading the project, to pass down offline
    • What are people's thoughts on Bob's soft-assert approach? https://github.com/mozilla/mcom-tests/pull/120
      • How much more time/discussion do we need as a team to come to a decision; I'd like to not rush, but get a clear sense of when we can move forward with a decision
      • Where are we at, as a team with this approach. This is a prototype for other projects, need a discussion. Zac: I chatted with Bob about this, agreed in short term to go for simpler approach. Complex approach woudl req. changes to py.test, would take a month +. We only need Raymond's final approval as it's his project and he understands the priorities best. !! Raymond to contact bob directly regarding approval/questions.
  • Syracuse Project Update: Now moving towards Web QA Automation
  • Q4 Goals:
    • I need to work on these today and tomorrow; they will likely be:
      • Carrying over the automation work with Marionette for this quarter
      • Likewise, carrying over the "everybody helps with Firefox OS" goal
      • + 1 or maybe 2, at most, more -- strategic ones
      • [Adi_J] There are 5-6 students to work on QA automation, need some tasks or an outline of a goal, or a mentor from London or Mtn. View. I can start them with the basics, but need communication with a mentor on the Mozilla side. Course is 2 semesters long, almost a year.
      • Perhaps send the students to look at available tasks and ping the lead with questions.
  • One and Done (aka QA Taskboard) update

Engagement Project Status

If you've worked on an engagement project in the last week, enter your name, the project name, and time spent in hours (estimated).

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

  • Affiliates
    • Coming soon - bug 760631 - Allow affiliates to link back to a personal website - display website on leaderboard
  • AMO
  • Marketplace
  • Mozillians (automation)
    • The team is doing an outstanding job of fixing and refactoring our automation suite. A huge shout our and thank you!
    • In discussions to move the project to continuous deployment.
  • Mozilla.com
  • MDN
  • Socorro
  • SUMO
  • MozTrap
  • Wiki
  • B2G
    • We need help doing manual testing- B2G: browser & email client

Buildmaster

Community Update

Time off / Out-of-office

  • rbillings 1/2 day Friday 10/5

Takeaways and Action Items

  • Takeways:
  • Action Items:
    • rbillings: schedule a brainstorm meeting for contributors corner page
    • mbrandt: volunteers to work on Bouncer - need more volunteers
    • mbrandt: will schedule a meeting next Tues/Wed to discuss One and Done further
    • someone discuss setting up using marketplace api in mktplace tests
  • Next owner / scribe:
    • Matt - lead, Alin - scribe
  • Next week's meeting notes: