QA/Browser Technologies/2010-06-17: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
mNo edit summary
 
(14 intermediate revisions by 5 users not shown)
Line 6: Line 6:
** [https://intranet.mozilla.org/QA/Q22010_QAgoals#Labs_QA_Goals Labs]
** [https://intranet.mozilla.org/QA/Q22010_QAgoals#Labs_QA_Goals Labs]
*Q310 Upcoming goals
*Q310 Upcoming goals
** Fennec stuff!
** Fennec
*** Fennec 2.0alpha, Android alphas, GTK maemo 5, QT?
*** Fennec 2.0alpha, Android alphas, GTK maemo 5
*** Client automation (carry over)
*** Client automation (carry over).  getting browser-chrome tests to supplement nightly smoketests across devices
** Jetpack
** Jetpack
*** bundle wizard includes test examples
*** bundle wizard includes test examples
*** flightdeck testing
*** testing flightdeck
** Weave / Test Pilot
** Weave / Test Pilot
*** most work will be FF4 feature related
*** most work will be FF4 feature related
*** maintenance releases
*** maintenance releases
** Community
*** Community engagement strategy for fennec (beta feedback tools to start)
*** similar strategy for Lab projects (jetpack and weave)


*Community  
*Community  
**Summit presentations  
**Summit presentations  
***No plans for a specific BT breakout session
***No plans for a specific BT breakout session
***There are places to talk about testing within mobile sessions, Sync Session, and the Engineering QA keynote
***There are places to talk about testing within mobile sessions, Sync Session, and the Engineering QA keynote (highlight the breakout sessions for each group)
**[http://quality.mozilla.org/teams/browser-technologies/ BT QMO] Content
**[http://quality.mozilla.org/teams/browser-technologies/ BT QMO] Content
*** Mobile looks full, jetpack too
*** Mobile looks full, jetpack too
Line 30: Line 33:
** This was an idea for july qa meetup, to have a testnight session onsite
** This was an idea for july qa meetup, to have a testnight session onsite
** or the other plan is to do a FF4beta testnight session
** or the other plan is to do a FF4beta testnight session
** '''update''' july meetup will be with FF4b1.  Select a few front facing features, and have a testday onsite.  
** '''update''' july meetup will be with FF4b1.  Select a few front facing features, and have a testday onsite.
** '''discussion''' can we use BYOB in the future for nightly testing?


= Project Status  =
= Project Status  =
Line 36: Line 40:
*Fennec  
*Fennec  
**Client update (aakashd)  
**Client update (aakashd)  
*** We'll need to have the Reporter for Fennec removed from AMO soon once reporter.mozilla.org is archived
*** Release tested [https://wiki.mozilla.org/QA/Fennec1.1/ReleaseTest/RC1_b3 1.1 RC B3]
*** [http://www.flickr.com/photos/aakashhdesai/sets/72157624165014245/ Completed Beta Tester Tools mock-ups], talk to Stuart on scheduling
**Automation update (martijn)  
**Automation update (martijn)  
*** Fennectrolysis is currently tested running full functional tests.
*** Joel is working on getting mochitests on fennectrolyis working
*** A list of litmus tests is compiled that could be converted into browser-chrome tests
*** Discussion on litmus test triage for browser-chrome candidate test. {{bug|553474}}


*Weave  
*Weave  
** Client (tracy)  
** Client (tracy)
*** 1.3.1 released last week
*** Migration to PHX of pre-1.3 accounts at SJ pending 1.3.1 uptake
*** 1.4 trunk landing targeted for EOD 6/18
** Crossweave (ayan)
** Crossweave (ayan)
*** Will follow up with jgriffin about crossweave in the coming week.
*** What is [https://wiki.mozilla.org/Auto-tools/Projects/CrossWeave crossweave]?
*** jgriffin to help setup crossweave and write test cases.


*FF Home (tchung)  
*FF Home (tchung)  
Line 49: Line 64:
**targeting Appstore submission on 6/29
**targeting Appstore submission on 6/29


*Test pilot (tracy)  
*Test pilot (tracy)
** 1.0b7 broke trunk in many ways.  Jono solved the issue in the extension CSS overlay
** will be bundled with Fx 4 betas


*Jetpack (ayan)
*Jetpack (ayan)
** what is jetpack?
** What is jetpack?
** where do I stand in the project?
** Where do I stand in the project?
** Demo (hopefully!!)


= Round Table  =
= Round Table  =


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

Latest revision as of 21:20, 17 June 2010

« previous mtg | Browser Technologies Home | next mtg »

Discussion Items

  • Q210 Goals recap
  • Q310 Upcoming goals
    • Fennec
      • Fennec 2.0alpha, Android alphas, GTK maemo 5
      • Client automation (carry over). getting browser-chrome tests to supplement nightly smoketests across devices
    • Jetpack
      • bundle wizard includes test examples
      • testing flightdeck
    • Weave / Test Pilot
      • most work will be FF4 feature related
      • maintenance releases
    • Community
      • Community engagement strategy for fennec (beta feedback tools to start)
      • similar strategy for Lab projects (jetpack and weave)
  • Community
    • Summit presentations
      • No plans for a specific BT breakout session
      • There are places to talk about testing within mobile sessions, Sync Session, and the Engineering QA keynote (highlight the breakout sessions for each group)
    • BT QMO Content
      • Mobile looks full, jetpack too
      • Content is still thin for weave and test pilot
  • BYOB
    • Built a byob with a labs qa collection. Currently contains Sync, Test Pilot, Account Manager
    • will include contacts
    • in review progress by tomcat
    • This was an idea for july qa meetup, to have a testnight session onsite
    • or the other plan is to do a FF4beta testnight session
    • update july meetup will be with FF4b1. Select a few front facing features, and have a testday onsite.
    • discussion can we use BYOB in the future for nightly testing?

Project Status

  • Fennec
    • Client update (aakashd)
    • Automation update (martijn)
      • Fennectrolysis is currently tested running full functional tests.
      • Joel is working on getting mochitests on fennectrolyis working
      • A list of litmus tests is compiled that could be converted into browser-chrome tests
      • Discussion on litmus test triage for browser-chrome candidate test. bug 553474
  • Weave
    • Client (tracy)
      • 1.3.1 released last week
      • Migration to PHX of pre-1.3 accounts at SJ pending 1.3.1 uptake
      • 1.4 trunk landing targeted for EOD 6/18
    • Crossweave (ayan)
      • What is crossweave?
      • jgriffin to help setup crossweave and write test cases.
  • FF Home (tchung)
    • beta 12 has been deployed
    • rc1 eta friday
    • QA signoff ETA 6/28. Testplan.
    • targeting Appstore submission on 6/29
  • Test pilot (tracy)
    • 1.0b7 broke trunk in many ways. Jono solved the issue in the extension CSS overlay
    • will be bundled with Fx 4 betas
  • Jetpack (ayan)
    • What is jetpack?
    • Where do I stand in the project?
    • Demo (hopefully!!)

Round Table

Takeaways and Action Items

Retrieved from "https://wiki.allizom.org/index.php?title=QA/Browser_Technologies/2010-06-17&oldid=231568"