Web Testing/Automation/automation-19-08-2011: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 23: Line 23:


=== Flightdeck/Addon-Builder [[http://qa-selenium.mv.mozilla.com:8080/job/Fd.functional.tests/ CI]] ===
=== Flightdeck/Addon-Builder [[http://qa-selenium.mv.mozilla.com:8080/job/Fd.functional.tests/ CI]] ===
= Almost finished Page Object refactor which brings the framework up to the Automation team's standard and hence forms a good base for writing tests. This has taken longer than expected but has been more thorough.
= Will start writing new tests to the spec next week.
= Can't run on Jenkins due to no Sel2 on grid unfortunately.


=== [https://wiki.mozilla.org/Sumo SUMO] [[http://qa-selenium.mv.mozilla.com:8080/view/SUMO%20Tests/ CI]] ===
=== [https://wiki.mozilla.org/Sumo SUMO] [[http://qa-selenium.mv.mozilla.com:8080/view/SUMO%20Tests/ CI]] ===

Revision as of 16:16, 19 August 2011

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

Action Items from last meeting

  • Have a meeting with everyone including Waverly to discuss the notes from Romania visit.
  • Get an update from David regarding py.test decorators
    • (DB) Due to other tasks this has taken a hit. Sorry this has taken a back burner but Automation Services items have come up. This is in the Automation Services Pivotal Tracker
  • Meeting owners should send out the an email 24-hours prior to the meeting with an url to the wiki to give people time to insert updates and discussion items.
  • Investigate locking down workspaces / yaml
  • Use bugtype for broken tests and chores for refactoring tests.
  • Moving more tests from zamboni to impala

Discussion topics / General Updates

  • Removing amo/addons from variable names and test names in the amo tests. Is this something we want to do?
  • webapps - There is now a weekly meeting for this. Double check of who should be involved with webapps, where we are, etc.
  • Simon to stop by next week and work with us on trying to troubleshoot our Grid issue

Status Update

AMO [CI]

  • Down from 66 failing tests to 23 failing tests
  • Testday is underway
  • Some tests appear missing in jenkins -- we think it has to do with the pyyaml install

Flightdeck/Addon-Builder [CI]

= Almost finished Page Object refactor which brings the framework up to the Automation team's standard and hence forms a good base for writing tests. This has taken longer than expected but has been more thorough. = Will start writing new tests to the spec next week. = Can't run on Jenkins due to no Sel2 on grid unfortunately.

SUMO [CI]

I've just been removing tests that aren't hooked up or haven't been passing in eons

Input [CI]

  • Staging env issues -- the hope is new staging env hardware will obviate the currently filed bug

Socorro [CI]

MDN [CI]

Mozilla.com [CI]

  • No update

QMO [CI]

Wiki [CI]

Action Items