QA/Browser Technologies/Meetings/2012-03-20

Fennec Updates

(eg. Status, top issues)

• Mozilla (test lead)
  • Fuzzy target date for Beta: Apr 14
  • focus this week: pin down crashiness regression on nightly so we can merge to aurora (about 5x larger now)
  • Plan for Testday is March 30th
    • focus on areas uplifted for aurora, fixes. website compatibility
  • notice about Fx12 Beta 2 XUL build today. Only one known change addressing the update channel fix (firefox fix)

• Waverley (Ioana, Andreea, Catalin, Camelia, Nicolae, Paul)
  • run BFTs and daily smoke tests on following devices ( Galaxy Tab, LG Optimus 2X P990, HTC Desire Z, Google Nexus S, Motorola Droid 2, Motorola Droid Pro, Samsung Galaxy SII) daily results ; archive .
  • bug validation Commented bugs;
  • Logged issues
  • watch assigned features - spreadsheet
  • GL layers testing. Results here
  • BFTs and exploratory - Nightly 14.0a1
  • in-litmus TCs and update TCs for Test Run 13
  • BFT ran over the Aurora 13.0a2 (Tablet - XUL; Phone - Native)
    • Failed TCs: http://bit.ly/FailedTablet
    • Broken TCs: http://bit.ly/BrokenTablet
    • Failed TCs: http://bit.ly/FailedPhone
    • Broken TCs: http://bit.ly/BrokenPhone
  • Beta 12.0b1
  • bug verification on Firefox 13.0a1&Firefox 14.0a1

• Important bugs:
  • bug 736099 - Crash [@ java.lang.NullPointerException: at org.mozilla.gecko.gfx.GLController.disposeGLContext(GLController.java) ]
  • bug 736481 - Fennec process is stopped when loading a WebGL page due to "Low Memory"
  • bug 735600 - MAPLE: Crash Report [@ mozilla::layers::CompositorParent::GetPrimaryScrollableLayer ]
  • bug 737088 - crash [@ memcpy | sqlite3_test_control ]
  • bug 735609 - Font inflation on webpages footer
  • bug 735279 - MAPLE: Black layer & flickering screen when closing AwesomeBar while VKB is up

• Issues/Questions/ Proposals

BrowserID Updates

• (SoftVision - Ioana Budnar)
• Tasks done
  • Verify fixed bugs (in progress).
  • Full regression testing on Android (in progress).
• To Do:
  • Full regression testing on iOS (might not be possible due to lack of devices).
  • Exploratory testing on new features.
  • Start creating test cases.