QA/Browser Technologies/2010-05-20: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 60: Line 60:
** We need YOU (interns and GSOC folks) to help create Browser-Chrome Automation: https://wiki.mozilla.org/Mobile/Fennec_Unittests/NewTests
** We need YOU (interns and GSOC folks) to help create Browser-Chrome Automation: https://wiki.mozilla.org/Mobile/Fennec_Unittests/NewTests
** When identifying new tests needed we need you to completely specify what the test steps should be like so: https://bugzilla.mozilla.org/show_bug.cgi?id=489158#c1
** When identifying new tests needed we need you to completely specify what the test steps should be like so: https://bugzilla.mozilla.org/show_bug.cgi?id=489158#c1
** As a rule, keep away from verifying device-specific items - files on devices in particular locations, soft keyboards, specific phone buttons etc (we want the browser-chrome tests to test the flow inside of Fennec, not the Fennec interaction with the outside phone which would be device specific).
** As a rule, keep away from verifying device-specific items - files on devices in particular locations, soft keyboards, specific phone buttons etc (we want the browser-chrome tests to test the flow inside of Fennec, not the Fennec interaction with the outside phone which would be device specific).  This way, these tests are portable from device to device.


= Takeaways and Action Items =
= Takeaways and Action Items =

Revision as of 18:09, 20 May 2010

« previous mtg | Browser Technologies Home | next mtg »

Discussion Items

  • QMO2 content
    • Latest update in these notes
    • List docs to be added for now
      • needing docs on how we test, and what we do with that testing.
      • How-to on various tools
      • land in page hierarchy > Labs. There are examples of the tree
      • Groups on QMO need to be updated
  • uTest and Waverly (matt)
    • Things working out?
    • Future projects
  • Community
    • Summit presentations
    • June Meetup. Ideas? Thinking about doing a weave
    • Recruiting Community? blogging, brownbags, demos, videos
  • Video
    • Ideas for project videos? fennec, weave, jetpack

Project Status

  • Weave (tracy)
    • 5/17 release slipped due to server issues. Now shooting for 5/25.
    • There have been some bad reports against 1.2.3
      • I think most of these issues are known and fixed in 1.3. That or other extension caused.
  • Weave for Iphone (tchung)
    • beta 10 has been deployed
    • If you have a iphone or itouch, submit your udid immediately to caitlin
  • Test pilot (tracy)
    • 1.0a5 released 5/17
    • to add Litmus test suite for Fx 4.0beta inclusion
  • Jetpack (ayan)
    • On track to learn more about Jetpack SDK by going through the online documents.
    • Meeting(5/21) with Myk and Tony to formulate test plans for end to end testing of SDK 0.5 release planned in mid-june.

Round Table

  • Tchung vacation 5/24-6/8. Someone want to run June 3rd meeting?
  • Automation for Mobile:
    • We need YOU (interns and GSOC folks) to help create Browser-Chrome Automation: https://wiki.mozilla.org/Mobile/Fennec_Unittests/NewTests
    • When identifying new tests needed we need you to completely specify what the test steps should be like so: https://bugzilla.mozilla.org/show_bug.cgi?id=489158#c1
    • As a rule, keep away from verifying device-specific items - files on devices in particular locations, soft keyboards, specific phone buttons etc (we want the browser-chrome tests to test the flow inside of Fennec, not the Fennec interaction with the outside phone which would be device specific). This way, these tests are portable from device to device.

Takeaways and Action Items

  • item 1
  • item 2
Retrieved from "https://wiki.allizom.org/index.php?title=QA/Browser_Technologies/2010-05-20&oldid=224589"