QA/Fennec/Waverley/2011-08-02

From MozillaWiki
< QA‎ | Fennec‎ | Waverley
Jump to: navigation, search

Meeting Notes for 2011-08-02

Welcome

(eg. headcount, updates with staffing, vacation/away time)

  • juanb: Away Aug 5 - 23; Anthony Hughes is your go-to person.
  • ashughes:
    • August 4 -- traveling home from Romania
    • August 5 -- day off to recharge, back on Monday
    • August 14 to 19 -- in Mountain View working from the Mozilla HQ
  • teodosia: Away Aug 8 - 12
  • AaronMT:
    • August 22nd-26th, vacation

Take Ways From Last Week

(eg. Action items from last weeks's Take Aways)

  • Forgot to write them down last week. Anyone remember?

Round Table

(eg. Other items to discuss)

  • Softvision Work Week Day 1 Take Aways (wiki)
    • tasks are well defined but the end goal is not communicated
    • communication is excellent and effective but there's room for improvement; especially external to the team
    • wiki.mo needs improvement in the areas of discoverability, organization, and level of doc maintenance
    • questions about task priority need to be answered via team leads
    • some debate about test automation priority (features vs backlog)
      • some feel automation development should focus on offloading high-cost low-value manual tasks; manual testing should focus on aggressive features testing; features should not be automated until stable
      • others feel automation must give some coverage to new features
      • trying to develop a compromised solution
    • trying to find ways to enable and support the Romanian community
  • Day 2 Agenda
    • 3 breakout sessions in the morning (opportunity to sit down and work hands-on to find solutions with teams)
    • 2 un-con talks in the afternoon (opportunity to discuss and debate things in an open platform)
    • Topics to include Code Process & Reviews, Improving Communication, Infrastructure, Strategy & Interviews, and Community
  • Daily standup with Softvision as an alternative to this meeting? If so, how would we communicate team/project status and discussion "externally" on a weekly basis?
    • should be specific to each team (webqa, desktop, automation) -- too many people would make it noisy
    • broad team status meeting will probably still be necessary to communicate across teams
    • investigate other technological ways that can be used to facilitate these meetings (vidyo?)

Firefox Updates

(eg. Status, top issues)

  • Mozilla (test lead)
    • Fx6 Beta 4: Shipped
    • Beta 5: Go to build this Wed. If all goes well, RC will be cut from it.
    • 3.6.20: Go to build next week. BlackHat conference is this week -- elevated potential for chemspill
  • Waverley (Alin, Andrei, George, Simona, Vlad G)
    • DevTools Meeting
    • Test plan
      • Firefox 6.0 Beta 4
        • Smoketests - Wiki-page
        • Spotchecking around changes on WebGL, Flash and Silverlight
        • Fixed Bug verification from pushlog - Spreadsheet
        • Spotchecking on l10n - German, Spanish, Italian, Russian, French
      • Fixed bug verification across platforms - Spreadsheet
      • Logged issues - Bugzilla query
      • Bug triage - Spreadsheet
      • Updated testcases in Litmus - Spreadsheet
    • Project tracking
      • Watch QA assigned Features - Spreadsheet
        • Landing of the "Tab animation" feature in Central caused some regressions in behavior:
        • Found issues on "Tab animation":
      • Identified new features
      • Contacted feature owners
      • Reviewed commented bugs
    • Meetings with Matt Brandt and Anthony Hughes

Automation Updates

(eg. Status, top issues)

WebQA (Selenium)
  • Waverly (Teodosia, Florin)
    • Stopped implementing tests for AMO because the pull request queue is too big
    • Research on Selenium 2
    • Update wiki pages related to WebQA testing Style Guide, Code Review Guide
    • Code reviewing
    • Merging pull requests
    • Meetings with Matt Brandt and Anthony Hughes
  • Mozilla (Marlena)
    • (see above list)
Desktop (Mozmill)
  • Waverley (Alex, Vlad)
  • Mozilla (Anthony)

Fennec Updates

(eg. Status, top issues)

  • Mozilla (test lead)
    • Firefox 6 beta 5 being built on Wednesday
    • DeviceAnywhere test runs have been bumpy
      • AaronMT will send out an email for improvements in this component of testing, stay tuned
  • Waverley (Andreea, Anna, Nicolae)
    • Weekly Status:
      • run BFTs, OS integration tests and daily smoke tests on all new devices (Tablet Acer 500 Iconia, LG Optimus 2X P990, HTC Desire Z, Google Nexus S, Motorola Droid 2) daily results ; archive . Builds tested as follows: Smoketests on Aurora (weekly) on Nightly (daily), BFTs and OS Integration Tests on Nightly and BFTs on Aurora.
      • bug validation daily results ; Commented bugs;
      • bug triage state of triaged bugs
      • run performance tests (all) against daily builds with the add-on (daily on aurora and nightly)(result are on server)
      • Beta 6.0b4 Results: here
      • Logged issues
    • Important bugs:
      • bug 672787 - Aurora build crashes [@ _moz_pixman_image_composite32] at start-up (07/20)
      • bug 672779 - Fennec not re-sized correctly after switching between portrait/landscape mode on mobile webpages
      • bug 673910 - Suggestion popup is overlapped by a thumbnail/small graphic area when left sidebar is dismissed
      • bug 674516 - Multi lang Nightly generates default bookmarks in Russian
      • bug 675588 - Google layout for classic version is not rendered correctly
      • bug 674498 - Search field missing on mobile version of www.google.com
    • Questions / Issues:
      • Three from four devices that we tried for testing beta 4 on DevicesAnywhere have connection problems and the other one has no option in Application settings for allowing installation of non-Market applications therefore we could not install Fx6b4 and run test against it.

Take Aways This Week

(eg. Action items)

Take Aways This Week

(eg. Action items)

  • Is Vidyo an alternative for Waverley calls? - Juanb
  • There have been issues with DeviceAnywhere connectivity. Aaron to send out email explaining how we could improve testing in this area. - Aaron, Tony