QA/Execution/Web Testing/Automation/ToDo: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
'''This page aims to cover the current/running list of to-dos for our Selenium Grid (and Hudson) set up'''  
'''This page aims to cover the current/running list of to-dos for our Selenium Grid (and Hudson) setup:'''  


#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>  

Revision as of 23:24, 16 February 2011

This page aims to cover the current/running list of to-dos for our Selenium Grid (and Hudson) setup:

  1. 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)
  2. 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++
  3. Continue to evaluate "screen"
  4. Make sure our Python packages are up-to-date, and working (Dave Hunt noticed warnings when upgrading)
  5. Make sure our RCs are all up-to-date
  6. Investigate and attempt to safe-guard against the "startupdisc out of space" error we saw last weekend (Feb 12-14)
  7. Investigate running in virtualenvs
  8. At some point, move to Jenkins, rather than Hudson
  9. Try to ensure no profiles have the Add-ons Manager "newly installed add-ons" pop-ups, which can be fixed by |extensions.update.notifyUser| = "false" and |extensions.newAddons| = "false"
  10. Make sure we're on the latest Firefox releases (per version -- don't jump versions accidentally) and betas