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

Revision as of 09:35, 5 August 2011

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.

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!
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
- I've documented this: https://wiki.mozilla.org/QA/Execution/Web_Testing/Automation/Selenium_Grid#Starting_Jenkins

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

@@ Line 9: / Line 9: @@
 * Dave, can you give an update on Grid 2?  Thanks!
 * 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
+* 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
 ** I've documented this: https://wiki.mozilla.org/QA/Execution/Web_Testing/Automation/Selenium_Grid#Starting_Jenkins