QA/Execution/Web Testing/Meetings/2011-12-08: Difference between revisions

From MozillaWiki
< QA‎ | Execution‎ | Web Testing‎ | Meetings
Jump to navigation Jump to search
 
(15 intermediate revisions by 3 users not shown)
Line 13: Line 13:
**python package dependencies
**python package dependencies
*Automation Leads should play with py.test2.2 with negation
*Automation Leads should play with py.test2.2 with negation
*Raymond will move the android vm to qa-selenium and will post an email to selenium *developers group and cross-post to mozwebqa
**Dave posted https://gist.github.com/1442986 as a proposal
*Raymond will move the android vm to qa-selenium and will post an email to selenium developers group and cross-post to mozwebqa
**Android VM moved to qa-selenium and filed bug http://code.google.com/p/selenium/issues/detail?id=3022
*Project leads will update the Jenkins jobs with the new settings to clear the workspace
*Project leads will update the Jenkins jobs with the new settings to clear the workspace
*Continue discussion about versions in Python package dependencies on mailing list until next week  
*Continue discussion about versions in Python package dependencies on mailing list until next week  
Line 32: Line 34:
* Selenium 2.15.0 is almost ready; (when) do we want it, given we just upgraded to 2.14.0?
* Selenium 2.15.0 is almost ready; (when) do we want it, given we just upgraded to 2.14.0?
* QA-Selenium2 - Do we still want this machine as part of our grid?
* QA-Selenium2 - Do we still want this machine as part of our grid?
* Sergey has been doing a great job of helping our Q4 goal of getting marketing/Engagement: https://github.com/stupchiy/marketing-project-template


= Project Status / goals for next week (keep it brief)  =
= Project Status / goals for next week (keep it brief)  =
Line 51: Line 54:


*Mozilla.com
*Mozilla.com
** shipped 4.9 this week
** rbillings pick up DTPT project
** rbillings pick up DTPT project


Line 57: Line 61:


*MDN
*MDN
** no release this week


*SUMO  
*SUMO  
Line 71: Line 76:


= Takeaways and Action Items  =
= Takeaways and Action Items  =
* Stephen to set up a meeting about infrastructure planning
* Stephen to work with Marlena to see about getting the WebQA email alias used for outbound build-status notifications
* Team to look at adding Sergey's https://github.com/stupchiy/marketing-project-template templates into our Jenkins
* Stephen to investigate Vidyo for the next meeting
* Team to retire qa-sel2?


*Next meeting: https://wiki.mozilla.org/QA/Execution/Web_Testing/Meetings/2011-12-15
= Next meeting:=
*Chair:  
*https://wiki.mozilla.org/QA/Execution/Web_Testing/Meetings/2011-12-15
*Chair: Rebecca
*Carryover:
*Carryover:

Latest revision as of 20:49, 8 December 2011

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

Every Thursday @ 9am PDT/PST

Dial-in Information:

650-903-0800 or 650-215-1282 x92 Conf# 303 (US/INTL)
1-800-707-2533 (pin 369) Conf# 303 (US)

Action Items / Takeaways from Last Week

  • Carryover: Update jenkins with pycache settings (??)
  • Everyone involved in automation re-read the thread and comments for:
    • Production tags
    • python package dependencies
  • Automation Leads should play with py.test2.2 with negation
  • Raymond will move the android vm to qa-selenium and will post an email to selenium developers group and cross-post to mozwebqa
  • Project leads will update the Jenkins jobs with the new settings to clear the workspace
  • Continue discussion about versions in Python package dependencies on mailing list until next week
  • Continue the discussion about markers on the mailing list until the group takes a decision
    • Should we use @destructive / @nondestructive marks?
    • For AMO we will use temporary marks until the final decision
  • Update from Raymond on mobile-testing setup/infra
  • BHAGS -- what do we want WebQA to be/look like/do, in 2012?:
  • Socorro test day tomorrow. Please sign up and help.

Discussion Items / Updates

  • We should add Firefox 8 support to our Grid
  • We need to look into a replacement for Gmail, for outbound failure emails (due to rate-limiting)
  • Selenium 2.15.0 is almost ready; (when) do we want it, given we just upgraded to 2.14.0?
  • QA-Selenium2 - Do we still want this machine as part of our grid?
  • Sergey has been doing a great job of helping our Q4 goal of getting marketing/Engagement: https://github.com/stupchiy/marketing-project-template

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

  • Affiliates
    • Test plan is moving towards a rapid release goal
    • BrowserID will be introduced to staging early next week
  • AMO
    • webdriver is merged in (working on fixes for remaining failing tests)
    • modifying our BrowserID page object for general consumption
    • production job for jenkins
  • Input
    • moved to Webdriver (yay! thx davehunt & community!)
    • introducing a production run using nondestructive as the py.test marker
  • Jetpack Builder (aka FlightDeck)
  • Mozilla.com
    • shipped 4.9 this week
    • rbillings pick up DTPT project
  • Mozillians
    • BrowserID will be introduced to staging env by early next week
  • MDN
    • no release this week
  • SUMO
    • 12/6 release goes out tomorrow, delay from issues
    • 12/13 release in process
    • #3 SUMO Questions day on 12/1 - went well
    • Editing Volunteer Guidelines with mluna
  • Case Conductor
    • no news is good news

Time off / Out-of-office

  • rbillings out 12/9
  • stephend out 12/14 - 12/28

Takeaways and Action Items

  • Stephen to set up a meeting about infrastructure planning
  • Stephen to work with Marlena to see about getting the WebQA email alias used for outbound build-status notifications
  • Team to look at adding Sergey's https://github.com/stupchiy/marketing-project-template templates into our Jenkins
  • Stephen to investigate Vidyo for the next meeting
  • Team to retire qa-sel2?

Next meeting:

Retrieved from "https://wiki.mozilla.org/index.php?title=QA/Execution/Web_Testing/Meetings/2011-12-08&oldid=377162"