QA/Execution/Meetings/2009-11-04

« previous mtg | index | next mtg »

Discussion Items

  • Current Priorities check
    • Crash Investigation. The no.1 priority is Firefox crash investigation. See Craskill wiki.
      • Additional notes (Tomcat)
        • Working on a list for the QA CrashKill Wiki with the Bugs from the Overall Crashkill List with Bugs that need steps to reproduce/testcases etc - also with a owner field for QA that is also open for interested community members) - should be done end of the week
    • Fx3.6 beta work. quicker beta cycles starting this week. Testing still needed around major components and fix verifications
      • Plan for quick beta cycles: Spot checks (smoketest?), spot checks on l10n, and updates, at most.
      • Next Two Weeks: Identify areas where things are unclear: Windows 7 in general, session store, tabbed browsing, lightweight themes, plugins, odds and ends. Then spend quality time, a day of full-force FFT level testing on these areas.
    • Fennec b5 work. A beta 5 is coming today or tomorrow. includes ~10 locales. Extra sets of eyes will help
      • Additional notes below
    • Fx 3.5.5 testing. Al and team are working on release testing this week
      • Additional notes below
    • Your other work you have. Put them on a temporary backseat if you can.
  • QMO Forum topic fields (aakashd)
    • currently, non-admin users cannot create forum topics. they can only comment in them. reasons is to block spam, but is this the best use of forum topics?
      • Forum will be fully back in function when bug 519428 is fixed (Tomcat)
  • Shorter 3.next beta cycles (juanb)
    • Starting next week, we are looking at shorter beta cycles. How does this impact qa?
      • juanb: We need three people the day of shipping for spot-checks, l10n, and updates. Ongoing bug verifications as part of our day-to-day operations.
  • Remote access to Lab Machines (marcia, raymond)
    • any new updates on this?
      • Raymond can do this next week, work with marcia to set priorities
      • Request which ones to prioritize first? (See Inventory)
      • Machines will be opened on the team via VPN
  • VM updates (abillings)
    • Any discussion on cleaning up old vms?
    • Fusion 3 licenses issued, new virtual machines are on FS, everything is a go.
  • Team hiring (timr, tchung)
    • project approaches and prioritization going into 2010
    • looking into contract services to assist with the daily grind work

Project Updates

  • Firefox 3.0x, 3.5x (abillings)
    • update?
  • Firefox 3.6 (juanb)
    • update?
  • Tegra (marcia)
    • Running the new OS and reporting and verifying bugs
    • Conference call with Nvidia scheduled for tomorrow AM
  • Fennec (aakashd)
    • update?
  • WebQA (stephend)
    • shipped SUMO 1.4.2 last night
      • working on Selenium coverage (search/forums, particularly)
    • Five Years of Firefox testing underway (looking great)
  • Weave Sync (tchung)
    • Weave sync 0.8 is out
    • beta is landing next week. Sync 1.0 is targeted before all hands in dec
    • feature is an extension that is targeting fennec and firefox integration by Q1/Q2 2010
    • Tracy will be driving the testing of smoketests, testplans, and filing bugs in the interim
  • Mozmill Testcase automation (henrik)
    • Aakash is working on Add-ons manager tests
    • Software update tests have been revised by a community member (Maverick). Some issues have to be addressed.
    • A lot of back-end work has been done the last week
    • Started to clean-up broken tests
  • QMO & Community (marcia, aakashd)
    • Trying to plan a mobile meetup for November. Awaiting word from dougt re: availability
    • Still have not had time to edit videos from MozCamp. Working with Lukas to carve out time.
  • Accessibility (marcoz)
    • Hunting new top crasher that first showed up in 3.6b1. No STR so far, and I can't reproduce, but hard on this one. bug 525579
    • Tables-related patches landed on Firefox 3.6b2pre last Thursday, testing and watching crash-stats to make sure we didn't regress. So far looks good.
    • Pursuing another ARIA-related report which hasn't been formulated into a bug yet, but which might be a potential 3.6 regression. More on this over the next couple of days.


  • QA Metrics ( Murali )
    • Windows code coverage data is generated. Coverage at 58 percent without jstest runs.
    • Exported code coverage data from native windows file format to XML.
      • Need to write scripts to transform XML to HTML report.
    • Working on POLISH bugs dashboard.
    • Minor improvements and consolidations done to dashboard

Round Table