QA/Execution/Web Testing/Automation/ToDo: Difference between revisions
< QA | Execution | Web Testing | Automation
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
#Figure out why the SUMOFFProfile on qa-selenium4.mv.mozilla.com doesn't launch (we need it for SUMO tests that use a logged-in state, since it has the accepted certificate)<br> | #Figure out why the SUMOFFProfile on qa-selenium4.mv.mozilla.com doesn't launch (we need it for SUMO tests that use a logged-in state, since it has the accepted certificate)<br> | ||
#Figure out what our new Grid setup should look like, and introduce the two new Mac Minis we got a couple weeks back, and get them going -- MOAR executors++ | #Figure out what our new Grid setup should look like, and introduce the two new Mac Minis we got a couple weeks back, and get them going -- MOAR executors++ | ||
#Continue to evaluate "screen" | #Continue to evaluate "screen" | ||
#Make sure our Python packages are up-to-date, and working (Dave Hunt noticed warnings when upgrading) | #Make sure our Python packages are up-to-date, and working (Dave Hunt noticed warnings when upgrading) | ||
#Make sure our RCs are all up-to-date | #Make sure our RCs are all up-to-date | ||
#Investigate and attempt to safe-guard against the "startupdisc out of space" error we saw last weekend (Feb 12-14) | |||
Revision as of 23:14, 16 February 2011
This page aims to cover the current/running list of to-dos for our Selenium Grid (and Hudson) set up
- Figure out why the SUMOFFProfile on qa-selenium4.mv.mozilla.com doesn't launch (we need it for SUMO tests that use a logged-in state, since it has the accepted certificate)
- Figure out what our new Grid setup should look like, and introduce the two new Mac Minis we got a couple weeks back, and get them going -- MOAR executors++
- Continue to evaluate "screen"
- Make sure our Python packages are up-to-date, and working (Dave Hunt noticed warnings when upgrading)
- Make sure our RCs are all up-to-date
- Investigate and attempt to safe-guard against the "startupdisc out of space" error we saw last weekend (Feb 12-14)