TestEngineering/Web/Automation: Difference between revisions
(→AMO) |
|||
| Line 29: | Line 29: | ||
=== AMO === | === AMO === | ||
*[https://wiki.mozilla.org/QA/Execution/Web_Testing/Docs/Automation/Testcases/ | *[https://wiki.mozilla.org/QA/Execution/Web_Testing/Docs/Automation/Testcases/AMO_POM_Libraries Libraries for Page Object Model] | ||
*[https://wiki.mozilla.org/QA/Execution/Web_Testing/Docs/Automation/Testcases/ConfigFiles Config Files] | *[https://wiki.mozilla.org/QA/Execution/Web_Testing/Docs/Automation/Testcases/ConfigFiles Config Files] | ||
*[https://wiki.mozilla.org/QA/Execution/Web_Testing/Docs/Automation/Testcases/SharedLibraries Shared Libraries (pre-POM)] | |||
=== SUMO === | === SUMO === | ||
Revision as of 22:03, 30 September 2010
Automation Homepage
<enter fluff here>
Selenium
Architecture
We have 4 Mac Minis running various Selenium RC environments, integrated via Hudson Continuous Build Integration and Selenium Grid. All machines can be VNCed into from within the MV-Office intranet (VPN if offsite). In order to start the entire system (Hudson Master, Hudson Slave, Selenium Grid, and All VMs with Selenium RCs), ensure that all the Mac Minis are powered on and logged in. Run startAll.sh on the desktop of qa-selenium.mv.mozilla.com (VPN required), and everything should start up. Everything can be shut down by running killAll.sh on the desktop of qa-selenium.mv.mozilla.com. This safely tears down Hudson and Selenium grid, terminates all Terminal sessions on OSX based computers, and sends the shut down command to all VMs.
Hudson Build Schedule
Product
AMO
SUMO
Mozilla.com
Meeting Notes
- September,2010
- August,2010