QA/Execution/Web Testing/Meetings/2011-05-20: Difference between revisions

From MozillaWiki
< QA‎ | Execution‎ | Web Testing‎ | Meetings
Jump to navigation Jump to search
No edit summary
 
(6 intermediate revisions by 2 users not shown)
Line 9: Line 9:
** What should we do next?
** What should we do next?
* Engagement-project on-ramping
* Engagement-project on-ramping
* AMO automation [http://quality.mozilla.org/events/2011/05/11/webqa-automation-test-day-24051/ testday on the 24th]


= Project Status / goals for next week (keep it brief)  =
= Project Status / goals for next week (keep it brief)  =


*AMO  
*AMO  
** [http://tinyurl.com/3ekb64c AMO 5.0.10 went live]
**[http://tinyurl.com/3ekb64c AMO 5.0.10 went live]  
*Input  
*Input  
**2 week iterations are in effect.  
**2 week iterations are in effect.  
**successful 3.5 release on 5.18.11  
**successful [http://goo.gl/SOWBP 3.5 release] on 5.18.11  
*Mark Up  
*Mark Up  
**pulled from prod on 5.17.11. Prepping for 5.31.11 release<br>
**pulled from prod on 5.17.11. Prepping for 5.31.11 release<br>  
**[http://goo.gl/7Tkdu 1.0 milestone] bugs  
**[http://goo.gl/7Tkdu 1.0 milestone] bugs  
*Mozilla.com  
*Mozilla.com  
**[Mozilla.com2.5 http://bit.ly/m9ai59] parts going live 5/20
**[Mozilla.com2.5 http://bit.ly/m9ai59] parts going live 5/20  
*MDN  
*MDN  
** No update
**No update  
*GetPersonas.com
*GetPersonas.com  
** None
**None  
*Socorro  
*Socorro
** [https://bugzilla.mozilla.org/buglist.cgi?list_id=306699&classification=Server%20Software&query_based_on=Socorro1.7.8-FIXED&query_format=advanced&component=Socorro&target_milestone=1.7.8&product=Webtools&known_name=Socorro1.7.8-FIXED 1.7.8] will go out next Thursday
*Spark  
*Spark  
** No update
**No update  
*SUMO  
*SUMO  
**Weekly releases are in effect- 2.8.3 this week, prepping for 2.8.4 next week  
**Weekly releases are in effect- 2.8.3 this week, prepping for 2.8.4 next week  
**Preparing for a community testday in the next two weeks for Users&amp;Groups&amp;Private Messaging, am in discussion with ktopal  
**Preparing for a community testday in the next two weeks for Users&amp;Groups&amp;Private Messaging, am in discussion with ktopal  
*Webify Me
*Webify Me  
**The new QA cycle is scheduled to start 30th of May.
**The new QA cycle is scheduled to start 30th of May.


Line 40: Line 42:


= Takeaways and Action Items =
= Takeaways and Action Items =
* Matt Evans to bring up a goal-writing workshop w/Debbie
* Stephen to follow-up with Dave and David on load-testing w/user-interactions in Selenium 2 + the Selenium-running vendors
* Stephen to follow-up with Matt Brandt and see what we can do with multi-node jmeter
* Matt Brandt to work with the team and come up with a list of tests for Engagement projects we can automate

Latest revision as of 18:50, 20 May 2011

previous mtg | QA/Execution/Web Testing/ Web QA Home | next mtg

Discussion Items / Updates

Project Status / goals for next week (keep it brief)

  • AMO
  • Input
    • 2 week iterations are in effect.
    • successful 3.5 release on 5.18.11
  • Mark Up
    • pulled from prod on 5.17.11. Prepping for 5.31.11 release
    • 1.0 milestone bugs
  • Mozilla.com
  • MDN
    • No update
  • GetPersonas.com
    • None
  • Socorro
    • 1.7.8 will go out next Thursday
  • Spark
    • No update
  • SUMO
    • Weekly releases are in effect- 2.8.3 this week, prepping for 2.8.4 next week
    • Preparing for a community testday in the next two weeks for Users&Groups&Private Messaging, am in discussion with ktopal
  • Webify Me
    • The new QA cycle is scheduled to start 30th of May.

Time off / Out-of-office

  • Rbillings: school Friday 5/20
  • mbrandt: visiting with a friend Monday 5/23

Takeaways and Action Items

  • Matt Evans to bring up a goal-writing workshop w/Debbie
  • Stephen to follow-up with Dave and David on load-testing w/user-interactions in Selenium 2 + the Selenium-running vendors
  • Stephen to follow-up with Matt Brandt and see what we can do with multi-node jmeter
  • Matt Brandt to work with the team and come up with a list of tests for Engagement projects we can automate