QA/Execution/Web Testing/Meetings/2013-05-16

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

Action Items / Takeaways from Last Week

  • Takeaways:
  • Action Items:
    • Stephen to talk to the ATeam about the gaia-ui-tests desktop branch
    • To seperate Marketplace test in a new job in Jenkins or not?
      • zac: will do this after the payment tests are in
    • Stephen to sent devices to SV
      • waiting Legal's clearance to send Inari devices to SV. If not, send unagis.
      • Stephend: sent unagis, SV now has access to the builds

Discussion Items / Updates

  • say hi to Iulian he is joining our team and will work with Krupa
  • Web Ops will be adding another node to the generic/Engagement clusters
    • should help with dev/staging being down and not noticed
    • StephenD: webops mtg, filed bugs, failures were for the same reason, IT does not monitor dev & staging servers, they don't get paged. Got them to agree to add another Zeus node so if Zeus or Apache is down it will pick it up. And they will be notified, although not by paging.
  • Sauce Labs jobs in prod are failing due to DNSSEC issues
    • Stephen will file a Sauce Labs issue
  • Bebe: We need credentials for email test. Retornam: add an email account that is not hotmail or gmail for activesync. Look into Mozilla.com email.
  • Krupa: Need marketplace tests. Bebe: start with same tests on desktop & mobile, but run them on Android. Do not run destructive tests.

Goals Check-in

  • stephend: we've added two more Inaris, need to rename in Jenkins, JSON files in creds repo and on the boxes themselves. Mapping is not currently in sync. Stephend and Retornam: will resolve this
    • Inaris were never given access to mozilla wifi, reason for failures. They have been put back on Mozilla Guest to resolve this issue.
  • v1.1 is marked with a '?', good that we did that as Leo RIL is not good. Been broken for close to 4 weeks now.
  • Bebe: we have green build for Inaris for v1.1

Blog Ideas

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

  • What is community and how we keep it open.
    • Mbrandt: Want to write a low-touch blog post about active participation and also those who lurk. Discussion of value of using a mailing list to communicate. Why do we do it, and how it relates to Mozilla culture. Would like help on this.

Lightning talk / Show 'n Tell

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

  • Affiliates
    • No updates
  • Engagement
  • Firefox Health Report
  • Firefox OS
    • Firefox Flicks rolled out new blog posts, carousel updates and partner info
    • Reps has put out many of the pieces for the new voting system- which is up on dev for testing
  • Marketplace / AMO
  • Mozillians
  • Mozilla.com
  • MDN
  • Socorro
  • SUMO
    • Continuous deployment, no updates
  • 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

Takeaways and Action Items

  • Takeways:
  • Action Items:
    • StephenD to talk to the ATeam about the gaia-ui-tests desktop branch [carryover]
    • zac: separate marketplace tests after the payment tests are in
    • Stephend: Will file a sauce labs ticket
    • Retornam: add an email account that is not hotmail or gmail for activesync. Look into Mozilla.com email.
    • Bebe: start with same tests on desktop & mobile, but run them on Android. Do not run destructive tests.
    • Stephend and Retornam: will resolve Inari mapping issues for Jenkins, JSON files & in the credentials repo
    • Mbrandt: Looking for help writing Community blog post
    • StephenD: do community stuff with unagi, look into if it's possible with 1.0.1 RIL to contributors
    • Bebe: doing a webqa workshop, need people to enter beginning Issues
    • StephenD: moz.com and maybe mdn - work with retornam to get issues

for meetups I'd like to see a way of helping contributors understand that they can assess, understand and contribute to coverage beyond just looking at listed issues

      • bebe: this is too hard for beginning conference, where they are just learning selenium- maybe in the future
  • Next owner / scribe: AlinT / Mbrandt
  • Next week's meeting notes:
Retrieved from "https://wiki.mozilla.org/index.php?title=QA/Execution/Web_Testing/Meetings/2013-05-16&oldid=656730"