QA/Browser Technologies/2011-05-19: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "<small>« previous mtg | Browser Technologies Home | next mtg » </smal...")
 
 
(14 intermediate revisions by 6 users not shown)
Line 4: Line 4:
* Fennec Stuff  
* Fennec Stuff  
** branch testing / deployment.  Thoughts so far?
** branch testing / deployment.  Thoughts so far?
*** '''discussion''' big thing is getting to beta, to get the audience feedback
*** nothing has been blockable yet
*** concerning that locale switcher into 5 beta. (we didnt have heads up on this)  '''wasnt this a fennec 6 issue'''
*** also about bugs that are fixed that need approval for landing (eg. password one)
*** QA would want to advocate for pushing out beta deployments if major bugs are landing (eg. password one).  we'll need to discuss this with dev
*** documentation and testplans seem to be fine
*** '''Q:''' Clone the test suites for branch?
*** '''Q:''' Clone the test suites for branch?
**** '''discussion''' keep the existing suite at 1, and add tests to keep it simple. also, TCM will handle tagging and grouping test suites; reduce dupes
** Updates on Device services
** Updates on Device services
*** '''discussion''' Kevin & Waverley ran the trial period, no big red flags.  Except long tap isnt available.  Naoki will try out the service and test around VKB
** community device support update (aaronmt)
** community device support update (aaronmt)


Line 18: Line 26:


* Hiring update (tchung)
* Hiring update (tchung)


= Project Status  =
= Project Status  =
*Fennec  
*Fennec  
** Execution (aakash)
** Execution (aakash)
*** [[QA/Fennec/Milestones/5.0|Fx5]] and [[QA/Fennec/Milestones/6.0|Fx6]] test plans created
** Automation (martijn)  
** Automation (martijn)  
*** First version of Test harness extension with reftests working
*** The reftests need to be run from outside the extension directory, working on that
*** https://wiki.mozilla.org/QA/Browser_Technologies/Mobile_Unit_Testing_Addon
** Website Compatibility / Device Compatibility (aaront)
** Website Compatibility / Device Compatibility (aaront)
*** [http://www.surveygizmo.com/s3/545781/Firefox-for-mobile-Website-Compatibility-Testing Website compatibility form rewritten]
*** [http://bit.ly/fx-mobile-untested-survey untested device backlog survey] published ~ 70 responses thus far


*Sync (Tracy)
*Sync (Tracy)
** Weekly train model is working well.  We're no longer getting slammed with big change sets.
** I expect Python reg/sreg server should pass QA this cycle. If so, it will be pushed to production on Monday.


*Test pilot (tracy)
*Test pilot (tracy)
** 1.2pre 4/5 builds in testing this week
** Awesomebar HD study pushed to limited audience


*Identity (tracy)
*Identity (tracy)
** Project responding to security issues. (Thunder out this week)


*Share (Aaron)
*Share (Aaron)
 
**Will not land in Firefox 6, their target land date was missed, awaiting response about their definitive answer to the internal prd
*FF Home (Naoki)
*FF Home (Naoki)
** Still waiting for more stuff from Dev; Fennec put as priority until then
** Visual Designs : https://wiki.mozilla.org/Home/Features/ux


*Open Web Apps (tchung)
*Open Web Apps (tchung)

Latest revision as of 18:40, 19 May 2011

« previous mtg | Browser Technologies Home | next mtg »

Discussion Items

  • Fennec Stuff
    • branch testing / deployment. Thoughts so far?
      • discussion big thing is getting to beta, to get the audience feedback
      • nothing has been blockable yet
      • concerning that locale switcher into 5 beta. (we didnt have heads up on this) wasnt this a fennec 6 issue
      • also about bugs that are fixed that need approval for landing (eg. password one)
      • QA would want to advocate for pushing out beta deployments if major bugs are landing (eg. password one). we'll need to discuss this with dev
      • documentation and testplans seem to be fine
      • Q: Clone the test suites for branch?
        • discussion keep the existing suite at 1, and add tests to keep it simple. also, TCM will handle tagging and grouping test suites; reduce dupes
    • Updates on Device services
      • discussion Kevin & Waverley ran the trial period, no big red flags. Except long tap isnt available. Naoki will try out the service and test around VKB
    • community device support update (aaronmt)
  • Services QA
    • Weekly s-c deployment update (tracy)
    • some projects are revisiting strategy
    • Functional Load test automation project (owen)
  • Jetpack / Flightdeck update (tchung)
    • FD work: transferred to webdevqa
    • Jetpack work: no resources
  • Hiring update (tchung)

Project Status

  • Sync (Tracy)
    • Weekly train model is working well. We're no longer getting slammed with big change sets.
    • I expect Python reg/sreg server should pass QA this cycle. If so, it will be pushed to production on Monday.
  • Test pilot (tracy)
    • 1.2pre 4/5 builds in testing this week
    • Awesomebar HD study pushed to limited audience
  • Identity (tracy)
    • Project responding to security issues. (Thunder out this week)
  • Share (Aaron)
    • Will not land in Firefox 6, their target land date was missed, awaiting response about their definitive answer to the internal prd
  • Open Web Apps (tchung)
    • no updates

Round Table

Notes

Retrieved from "https://wiki.mozilla.org/index.php?title=QA/Browser_Technologies/2011-05-19&oldid=310614"