Web Testing/Automation/automation-02-09-2011

<< Last meeting | WebQA Automation | Next meeting >>

Action Items from last meeting

• Marlena to look at how long it is going to take to make remove references to amo and addons in amo tests
• QA WebApps Meeting is on Mondays at 10.30 am. Interested parties should contact David Clarke to be added to calendar
• Look into moving SUMO pyyaml files

Discussion topics / General Updates

• pytest-mozwebqa with custom report is ready for review!
  • I'd like as many eyes as possible on this so please look over the pull request. I'm planning a 0.2 (beta) release, and a 1.0 final once we're happy with it. Enhancement requests should come int he form of issues in Github or even better pull requests! :)
    • pull request: https://github.com/davehunt/pytest-mozwebqa/pull/8
    • raise issues/enhancement requests here: https://github.com/davehunt/pytest-mozwebqa/issues
• Pull request for removing lxml dependency from mcom-tests. Is this the right action?
  • https://github.com/mozilla/mcom-tests/pull/4
• Trigger Jenkins jobs when test repositories are updated?
  • I would love this, and think it makes total sense in a CI/CD world - stephend

Status Update

AMO [CI]

• Has been updated to use mozwebqa py.test plugin
  • https://github.com/mozilla/Addon-Tests/pull/115
• All the failing impala tests have been solved. We have now a green build!!!
• Our staging server has moved to Phoenix. We are now using https://addons-dev.allizom.org/

Flightdeck/Addon-Builder [CI]

• Has been updated to use mozwebqa py.test plugin
  • https://github.com/mozilla/FlightDeck-selenium/pull/5
• Large scale refactor to give -n durability. Search tests added. Needs reviewing
  • Race bug will cause occasional failures with -n>1
  • https://github.com/mozilla/FlightDeck-selenium/pull/6

SUMO [CI]

• Has been updated to use mozwebqa py.test plugin
  • https://github.com/mozilla/sumo-tests/pull/28

Input [CI]

• In maintenance mode for the remainder of the quarter
• Looking at failing tests with dev, and we'll get a new staging server during the all-hands week (IT promised!)

Socorro [CI]

• Has been updated to use mozwebqa py.test plugin
  • https://github.com/mozilla/Socorro-Tests/pull/14
• Wish to take garmr for a spin
• Current CI failures are associated with stale data on stage. Until we get new hardware QA will have to file a bug on a weekly basis to get the data refreshed.
• Successful 2.2.2 milestone released on 8/31
  

MDN [CI]

• Test Refactor still waiting on review

Mozilla.com [CI]

• Merged changes that remove lxml dependency

QMO [CI]

• Now using pytest-mozwebqa plugin
  • https://github.com/mozilla/qmo-tests/pull/3

Wiki [CI]

• Pull request submitted for switching to use pytest-mozwebqa.
  • https://github.com/mozilla/wiki-tests/pull/3

Action Items

• Project owners: Add a build trigger for whenever our test automation repository is updated, make sure we don"t change cronjobs