QA/Execution/Web Testing/Meetings/2012-04-12

From MozillaWiki
< QA‎ | Execution‎ | Web Testing‎ | Meetings
Jump to: navigation, search

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

    • Stephen to delegate removing Beta and Aurora environoments on most nodes; leave them only on one
      • Not done -- someone please take this!
    • marlenac will send info to stephend from Scott Barber, but doesn't have exact prices, know it'll take more than a day
    • 2nd floor computer lab - find home for qa-selenium7 and the Android devices (tegra boards & ics phones) - stephend/raymond
      • Not done -- on the back-burner
    • Stephen to talk to Raymond to get Pivotal tasks for remaining Mozilla.com automation needs
      • Totally done
    • retornam needs to list what needs to be done for [mozilla.com] and put items into Pivotal Tracker or send an email to get what is needed.
    • Add goals for any upcoming projects if you know about ones not on the list. Can update goals list directly & then tell stephend.
    • Help needed: team could help complete the last 1% of automation for Mozillians.
    • If team sees Tobbi online, give him support for working on Mozillians

Discussion Items / Updates

  • Selenium 2.21.0 is ALIVE!
    • http://code.google.com/p/selenium/downloads/list
    • Zac has a pull; needs thorough testing
      • Sorry, I closed the pull because it does not include the required timeout configuration changes. I am currently testing 2.21 locally and will submit a new pull once I'm confident that it is at least as stable as 2.19. (davehunt)
  • Selenium infra update:
    • Folks from https://bugzilla.mozilla.org/show_bug.cgi?id=741956#c4 should be able to SSH in (see details in the bug; you must be connected to Mozilla-MPT -- this is a new requirement from IT; it will not affect our hosts' abilities to connect to ci.mozilla.org)
      • For the Windows VMs, I recommend using CORD: http://cord.sourceforge.net/. Also note that the username/password should be guessable -- find me if it's not!
    • Who is going to set up the hub and nodes for this? Considering this is for AMO can we just set up WD nodes? Should we just stick to installing Firefox 7 for now as that's what AMO is using at the moment? Should we wait for the outcome of 2.21 testing rather than introduce known stability issues? Does Web QA need assistance from Automation Development? (davehunt)
  • Great job on Socorro, team Ro + Zac; let's get mcom-tests back up + Marketplace coverage in (along with, of course, existing-test fixes for flightdeck, AMO, etc.)
  • Leah created a pull for a 'PageProvider' as a way of delivering the first page object in tests. Leah has had this pull open for a while but we haven't got team/community's thoughts on it yet so I urge you to comment.
  • Review build triggers (davehunt)
    • Arbitrary schedules aren't much value. Where possible tests should only be run when there is value in the results. For example, when a new version of the AUT is deployed, or when the test repository is updated.
      • We have used URL triggers for noticing the the AUT has been updated and this is working well - do more apps need a suitable revision URL? Could someone perform an audit?
      • Due to Jenkins not being public we need to perform SCM polling for checking if the test repositories have been updated. What is a reasonable schedule for this?
    • Is there value in also triggering on an infrequent basis (perhaps once a day) to detect environmental issues?
  • We really need to take a look at Sergey's pull for the jmeter-script for AMO: https://github.com/mozilla/jmeter-scripts/pull/2

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).

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

  • Affiliates
    • Release being delayed until tomorrow to complete dev work
    • Moving to continuous deployment (we have statsd)
  • AMO
    • Marlena writing some "fully dressed" use cases for apps
    • Focus is on keeping the build green
  • Marketplace
    • Automation tasks are being added to the WebQA tracker
  • Input
  • Jetpack Builder (aka FlightDeck)
  • Mozilla.com
    • working on 2.0 release
  • Mozillians
    • Latest release is tagged and ready to be deployed
    • New responsive UI hotness
  • Moztrap: 1.0 release, testing internally
  • Socorro
  • SUMO
    • no news
  • Wiki
    • Prod cutover to the new host should happen soon; thanks for the help testing

Community Update

  • No meeting, no update

Time off / Out-of-office

  • Stephen and Raymond to be in London from 14th, returning the 22nd
    • Stephen's not planning on taking much time off (maybe a day or two at most); will be working from the London office
  • Bebe: 12 - 17 April PTO
  • Alin: 17 - 18 April PTO
  • April 16 is a National Holiday in Romania
  • May 1st(ish) - mbrandt to Crested Butte, Colorado

Takeaways and Action Items

  • Action Items:
    • (needs owner) Beta and Aurora build nodes - for now we're going to support Beta (on all nodes), aurora and nightly only on one node. If need be we will increase the number of instances.
      • Install/update Beta to all nodes
      • reduce Nighty and Aurora
    • (Stephend) 1) install/update beta on all nodes 2) reduce Nightly/Aurora to just one node, and install/update them
    • (Stephend) Scott Barber - check with Bob if there is a budget for bringing Scott Barber on - action Stephen to talk to Bob - if he says yes then we'll follow up with Scott to make sure the presentation is tailored to our env and needs
    • tegra boards & ics phones - don't have a home yet - need to work with IT (Raymond)
      • we need to work to create an SLA with IT to get our needs/concerns covered
      • qa-selenium7 replacement is currently in a drawer - we need to coordinate with IT on getting this hooked up
    • (Stephen) to talk to Bob about our goals - the wording may change but we suspect the intent of the goals won't change
    • (Matt) to talk to Tobbi to understand where the Mozillian tests are and how we can unblock him
  • Takeways:
    • Setup nodes and hub forCan use Cord for osx to get around the rdp connection problems - Need an owner for (dave, raymond, and stephen to talk in London)
      • Folks from https://bugzilla.mozilla.org/show_bug.cgi?id=741956#c4 should be able to SSH in (see details in the bug; you must be connected to Mozilla-MPT -- this is a new requirement from IT; it will not affect our hosts' abilities to connect to ci.mozilla.org)
      • For the Windows VMs, I recommend using CORD: http://cord.sourceforge.net/. Also note that the username/password should be guessable -- find me if it's not!
      • Uho is going to set up the hub and nodes for this? Considering this is for AMO can we just set up WD nodes? Should we just stick to installing Firefox 7 for now as that's what AMO is using at the moment? Should we wait for the outcome of 2.21 testing rather than introduce known stability issues? Does Web QA need assistance from Automation Development? (davehunt)
    • (team) please review Leah's https://github.com/mozilla/sumo-tests/pull/92
    • (team) please review Sergey's https://github.com/mozilla/jmeter-scripts/pull/2
  • Next owner:
  • Next week's meeting notes:
Retrieved from "https://wiki.mozilla.org/index.php?title=QA/Execution/Web_Testing/Meetings/2012-04-12&oldid=421794"