Web Testing/Automation/automation-22-07-2011
From MozillaWiki
<< Last meeting | WebQA Automation | Next meeting >>
Contents
Discussion topics
- Any progress on using py.test marks unambiguously?
- a/b testing
- CI job name convention; suggestion:
- amo.zamboni.allizom.bft
- Leadership of the meetings/timing of the wiki page being sent out
- Need a meeting to discuss sharing Waverly resources between WebQA projects and how that will be communicated
Status Update
AMO [CI]
- Getting closer to handling impala vs. zamboni
- Still need a better long term solution for a/b testing Marlena will talk to AMO devs about this
- Stand ups are working
- code review queue slowly getting processed
SUMO [CI]
- fixed test_questiosn_sort.py
Input [CI]
- Working with Webdev to diagnose the timeouts on stage (tofumatt ftw)
Socorro [CI]
- Elastic Search should land soon (today or early next week). Once it does going to rev. up a Waverly resource.
MDN [CI]
Mozilla.com [CI]
QMO [CI]
- CAPTCHA removed from staging to allow tests to run.
- Outstanding PHP issue still being investiated. bug 667495
Wiki [CI]
- Tests are occasionally failing due to Selenium bug 1020
- Tests are also sometimes failing due to page title being blank. David Burns is investigating. May be a Selenium issue.
Action Items
- Post Waverly visit conversation with team
- Get an update from David regarding py.test decorators
- 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.
Next Meeting Owner/Chair
- Krupa