Web Testing/Automation/automation-05-08-2011: Difference between revisions
Jump to navigation
Jump to search
| Line 56: | Line 56: | ||
== Action Items == | == Action Items == | ||
* Have a meeting with everyone including Waverly to discuss the notes from Romania visit. | |||
* 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. | |||
* Investigate locking down workspaces / yaml | |||
* Use bugtype for broken tests and for refactoring tests. | |||
* Moving more tests from zamboni to impala | |||
== Next Meeting Owner/Chair == | == Next Meeting Owner/Chair == | ||
http://files.myopera.com/drlaunch/albums/37656/ya-srsly001.jpg | http://files.myopera.com/drlaunch/albums/37656/ya-srsly001.jpg | ||
Revision as of 16:46, 5 August 2011
<< Last meeting | WebQA Automation | Next meeting >>
Action Items from last meeting
- 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.
Discussion topics / General Updates
- Thoughts on https://github.com/weluse/django-nose-selenium? jsocol pointed me to it, but David had a brief discussion with him about why we switched to, and still use, pytest
- Dave, can you give an update on Grid 2? Thanks!
- 4 outstanding issues
- 2 grid issues
- 2 core Selenium issues
- 4 outstanding issues
- How are Firefox 6 + Fennec Selenium/Python bindings?
- Jenkins: we're now launching with java jar -Xms8g -Xmx8g -XX:MaxPermSize=512M jenkins.war, and it's fixed our OOM issues; it just increases the heap allocation
- Can someone own trying to figure out how to surpress username/password logging in Jenkins' workspace? I'd like us to at least open-up our CI outside the VPN, or perhaps merge w/Webdev
- We could prioritize code reviews/merges made on pull requests. Refactoring pulls should have a higher priority because they can block writing tests in the refactored area. Also, further refactoring might be needed if a test is merged before a refactoring pull that covers the same area.
- Update on fixing test execution duration in reports
- Status of Impala/Zamboni for AMO
- Checklist of current status for Impala implementation: https://github.com/jbalogh/zamboni/commit/4e1c931242779184b74726da1303ec1b3ac3f34f (not sure how up-to-date this is/will be)
Status Update
AMO [CI]
- Krupa, Marlena, and I (PHB) agree that we'll:
- Continue to develop new tests from Pivotal Tracker/uncaught regressions, while:
- Trying to maintain the current coverage in our legacy tests (where the benefit > cost-to-fix, and where we have gaps in the new suite
- Currently having an ongoing discussion in email about how to improve our syntax
- Planning the next testday with softvision -short meeting after the meeting to discuss today.
Flightdeck/Addon-Builder [CI]
SUMO [CI]
- No updates
Input [CI]
Socorro [CI]
- No updates; hope to engage Softvision soon!
MDN [CI]
Mozilla.com [CI]
- http://qa-selenium.mv.mozilla.com:8080/view/Mozilla.com/job/mozilla.com.prod/2849/console
- E UnboundLocalError: local variable 'end' referenced before assignment
QMO [CI]
Wiki [CI]
Action Items
- Have a meeting with everyone including Waverly to discuss the notes from Romania visit.
- 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.
- Investigate locking down workspaces / yaml
- Use bugtype for broken tests and for refactoring tests.
- Moving more tests from zamboni to impala
Next Meeting Owner/Chair
