QA/Execution/Web Testing/Meetings/2012-03-29: Difference between revisions

From MozillaWiki
< QA‎ | Execution‎ | Web Testing‎ | Meetings
Jump to navigation Jump to search
 
(23 intermediate revisions by 6 users not shown)
Line 8: Line 8:
** Team to stretch to meet Stephen's challenge - let's get our test days scheduled and rock it!
** Team to stretch to meet Stephen's challenge - let's get our test days scheduled and rock it!
** Stephen spoke to Sergey - he hasn't had time to work on it but it is in process
** Stephen spoke to Sergey - he hasn't had time to work on it but it is in process
** Zac has found a plugin for Jenkins that well generate backups - he is going to ensure we are able to easily do a restore from a backup
** Zac has found a plugin for Jenkins that will generate backups - he is going to ensure we are able to easily do a restore from a backup
** Stephen installed FF11 on the Mac nodes
** Stephen installed FF11 on the Mac nodes
* Action Items:
* Action Items:
Line 17: Line 17:
*** DONE: https://wiki.mozilla.org/index.php?title=Web_Testing/Automation/CodeReviewProcess&curid=43522&diff=413549&oldid=413548
*** DONE: https://wiki.mozilla.org/index.php?title=Web_Testing/Automation/CodeReviewProcess&curid=43522&diff=413549&oldid=413548
** 2nd floor computer lab - find home for qa-selenium7 and the Android devices (tegra boards & ics phones) - stephend/raymond
** 2nd floor computer lab - find home for qa-selenium7 and the Android devices (tegra boards & ics phones) - stephend/raymond
*** Not done :-(
** Stephen and Raymond will find a community owner for QMO - probably do a blog post
** Stephen and Raymond will find a community owner for QMO - probably do a blog post
*** Not done :-(
** Zac has found a plugin for Jenkins that well generate backups - he is going to ensure we are able to easily do a restore from a backup
** Zac has found a plugin for Jenkins that well generate backups - he is going to ensure we are able to easily do a restore from a backup


= Discussion Items / Updates =
= Discussion Items / Updates =
* How are we doing with investigating performance testing/tools/metrics we need to measure?
* How are we doing with investigating performance testing/tools/metrics we need to measure?
** https://github.com/mozilla/jmeter-scripts/pull/2 -- we should check out his pull
** https://wiki.mozilla.org/QA/Execution/Web_Testing#Performance_and_Load-Testing_Tools
* Discuss changes to Engagement and how it impacts our team.
* Discuss changes to Engagement and how it impacts our team.
* Q2 goals
* Q2 goals
** Brainstorm them here: https://mozqa.etherpad.mozilla.org/mozwebqa-Q22012-Goals
*** WebDev's Q2 draft goals: https://etherpad.mozilla.org/webdev-q2-2012
*** https://intranet.mozilla.org/Innovation_Q2_2012_goals#Webdev
* Can we do mobile tests for page title/login&logout for Mozillians?  (seems like there's a reason why we held off and I can't remember - Marlena)
* Can we do mobile tests for page title/login&logout for Mozillians?  (seems like there's a reason why we held off and I can't remember - Marlena)
** mozillians-tests is still using Selenium RC
* Any objection to updating QMO to remove the Selenium RC steps? https://quality.mozilla.org/docs/webqa/running-webqa-automated-tests/
* Anyone should feel free to fix any failing test, anytime (likewise for code reviews)


= Engagement Project Status =
= Engagement Project Status =
If you've worked on an engagement project in the last week, enter your name, the project name, and time spent in hours (estimated).
If you've worked on an engagement project in the last week, enter your name, the project name, and time spent in hours (estimated).
* Betafarm - 5hrs rbillings
* Betafarm - 5hrs rbillings
* Browserquest 16hrs marlenac
* Browserquest 16hrs marlenac, 12hrs Zac


= Project Status / goals for next week (keep it brief)  =
= Project Status / goals for next week (keep it brief)  =
Line 36: Line 46:
**[https://quality.mozilla.org/2012/03/web-qa-testday-for-the-affiliates-project-march-29-2012/ Test day today]
**[https://quality.mozilla.org/2012/03/web-qa-testday-for-the-affiliates-project-march-29-2012/ Test day today]
*AMO
*AMO
**[http://cl.ly/1i233r1k0K2G2V250z3L AMO 6.4.8] going live at 2pm
**Testday was Wednesday, a big Thanks to everyone for help with moderating!
**Testday was Wednesday, a big Thanks to everyone for help with moderating!
*Marketplace
*Marketplace
 
**[http://cl.ly/1i233r1k0K2G2V250z3L MP 6.4.8] going live at 2pm
*Input
*Input


Line 44: Line 55:


*Mozilla.com
*Mozilla.com
** shipping one mozilla today 3/29


*Mozillians
*Mozillians
**Still working on the [rel:03/21/2012] [http://bit.ly/GYDgqr release], hope to push it today or tomorrow
**Still working on the [rel:03/21/2012] [http://bit.ly/GYDgqr release], hope to push it today or tomorrow
* Mozilla Reps [https://quality.mozilla.org/2012/03/web-qa-testday-for-mozilla-reps-march-30-2012/ testday] tomorrow
*MDN
*MDN
** shipped 2.6 on 3/28


*Socorro
*Socorro
Line 67: Line 81:
= Takeaways and Action Items =
= Takeaways and Action Items =
* Takeways:
* Takeways:
**
**  
* Action Items:
* Action Items:
**
** Stephen to do or delegate updating Firefox Beta on nodes
** Stephen to delegate removing Beta and Aurora environoments on most nodes; leave them only on one
** Marlena to let us know when Scott Barber has responded about performance testing
** Matt to add other members of the team to the WebQA Pivotal Tracker, as admins
** 2nd floor computer lab - find home for qa-selenium7 and the Android devices (tegra boards & ics phones) - stephend/raymond
** Marlena to work with Raymond on setting up the Google Galaxy Nexus phones to the Grid
** Stephen to talk to Chris More/morgamic about getting more up-front involvement/information about re-orgs that affect QA
** Stephen to talk to Clint/Tony about Q2 goals, and what we're looking for
** Stephen to talk to Raymond to get Pivotal tasks for remaining Mozilla.com automation needs
* Next owner:
* Next owner:
* Next week's meeting notes:
* Next week's meeting notes:

Latest revision as of 16:48, 29 March 2012

previous mtg | Web QA Home | next mtg

Meeting Details

Please see our public calendar for all upcoming events and meetings.

Our regular team meeting occurs every Thursday @ 9am Pacific

Action Items / Takeaways from Last Week

  • Takeaways:
    • Team to stretch to meet Stephen's challenge - let's get our test days scheduled and rock it!
    • Stephen spoke to Sergey - he hasn't had time to work on it but it is in process
    • Zac has found a plugin for Jenkins that will generate backups - he is going to ensure we are able to easily do a restore from a backup
    • Stephen installed FF11 on the Mac nodes
  • Action Items:
    • Matt to fix the dial in number for the WebQA meeting
    • Marlena to email Scott Barber about getting pricing on performance-testing training (done)
    • Team to clean up the WebQA Pivotal Tracker - please ensure the stories are current and mark items as completed if they are
    • Stephen to update the code review checklist as a result of the non-merge fiasco - post-merge the merger should stick around and ensure the build continues to be green
    • 2nd floor computer lab - find home for qa-selenium7 and the Android devices (tegra boards & ics phones) - stephend/raymond
      • Not done :-(
    • Stephen and Raymond will find a community owner for QMO - probably do a blog post
      • Not done :-(
    • Zac has found a plugin for Jenkins that well generate backups - he is going to ensure we are able to easily do a restore from a backup

Discussion Items / Updates

Engagement Project Status

If you've worked on an engagement project in the last week, enter your name, the project name, and time spent in hours (estimated).

  • Betafarm - 5hrs rbillings
  • Browserquest 16hrs marlenac, 12hrs Zac

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

  • Jetpack Builder (aka FlightDeck)
  • Mozilla.com
    • shipping one mozilla today 3/29
  • Mozillians
    • Still working on the [rel:03/21/2012] release, hope to push it today or tomorrow
  • Mozilla Reps testday tomorrow
  • MDN
    • shipped 2.6 on 3/28
  • Socorro
  • SUMO
    • no updates
  • Case Conductor
    • Testing the .9 release, trying to find bugs during the last few days with the Meyers
  • Wiki
    • no updates

Community Update

  • There was no meeting this week, so no update

Time off / Out-of-office

Takeaways and Action Items

  • Takeways:
  • Action Items:
    • Stephen to do or delegate updating Firefox Beta on nodes
    • Stephen to delegate removing Beta and Aurora environoments on most nodes; leave them only on one
    • Marlena to let us know when Scott Barber has responded about performance testing
    • Matt to add other members of the team to the WebQA Pivotal Tracker, as admins
    • 2nd floor computer lab - find home for qa-selenium7 and the Android devices (tegra boards & ics phones) - stephend/raymond
    • Marlena to work with Raymond on setting up the Google Galaxy Nexus phones to the Grid
    • Stephen to talk to Chris More/morgamic about getting more up-front involvement/information about re-orgs that affect QA
    • Stephen to talk to Clint/Tony about Q2 goals, and what we're looking for
    • Stephen to talk to Raymond to get Pivotal tasks for remaining Mozilla.com automation needs
  • Next owner:
  • Next week's meeting notes:
Retrieved from "https://wiki.allizom.org/index.php?title=QA/Execution/Web_Testing/Meetings/2012-03-29&oldid=413856"