Web Testing/Automation/automation-27-01-2011: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(9 intermediate revisions by 4 users not shown)
Line 3: Line 3:
* Grid Updating
* Grid Updating
** Current plan: Have multiple environments with the same name running for the popular test environments (i.e. Firefox-default;en-us;MacOSX6) and let Grid distribute the jobs accordingly. There will be ~4 environments of Firefox-default;en-us;MacOSX6, and so 4 concurrent executors active on Hudson. As for the other environments, we can have as many copies of selenium running of them as we see fit.
** Current plan: Have multiple environments with the same name running for the popular test environments (i.e. Firefox-default;en-us;MacOSX6) and let Grid distribute the jobs accordingly. There will be ~4 environments of Firefox-default;en-us;MacOSX6, and so 4 concurrent executors active on Hudson. As for the other environments, we can have as many copies of selenium running of them as we see fit.
* Input Tests require the latest beta, can Raymond/Tanay tell us if we have one setup so we can add a new test to be run?
* Tanay sent email about using [http://www.gnu.org/software/screen/ screen] - any objections?  I confess it'd probably take me a bit to ramp up on, but if the folks who are maintaining Grid think it'd be more useful, then I'm all for it - stephend
* Someone needs to own Grid, which means:
** Keeping browsers up-to-date (within versions)
** Upgrading VMWare Fusion
** etc.
* Input Tests require the latest beta, can Raymond/Tanay tell us if we have one set up so we can add a new test to be run?
* Adding Notes to CI Task so others can see
* Adding Notes to CI Task so others can see


Line 14: Line 19:


===[https://wiki.mozilla.org/Sumo SUMO] [http://qa-selenium.mv.mozilla.com:8080/view/SUMO%20Tests/ CI]===
===[https://wiki.mozilla.org/Sumo SUMO] [http://qa-selenium.mv.mozilla.com:8080/view/SUMO%20Tests/ CI]===
 
* We should flag in-testsuite? for bugs that either aren't covered by unit tests, or could use more coverage
** Absolutely- there are some waiting, and more will be added [RB]


===[https://wiki.mozilla.org/Firefox/Input Input] [http://qa-selenium.mv.mozilla.com:8080/job/input%20stage/ CI]===
===[https://wiki.mozilla.org/Firefox/Input Input] [http://qa-selenium.mv.mozilla.com:8080/job/input%20stage/ CI]===
Line 26: Line 32:


===Mozilla.com [http://qa-selenium.mv.mozilla.com:8080/job/mozilla.com/ CI]===
===Mozilla.com [http://qa-selenium.mv.mozilla.com:8080/job/mozilla.com/ CI]===
*  
* [https://github.com/retornam/mcom-tests Tests] for review from David Burns


==Action Items==
==Action Items==
* Raymond and Tanay to have a look at capacity needs for the Grid and mail the team. Do we need more than 1 Mac Mini?
* Raymond and Tanay to have a look at capacity needs for the Grid and mail the team. Do we need more than 1 Mac Mini?
*
* DavidB is to have a look at Screen
* DavidB to look at screen shots on Hudson

Latest revision as of 18:23, 27 January 2011

<< Last meeting | WebQA Automation Next meeting >>

Discussion topics

  • Grid Updating
    • Current plan: Have multiple environments with the same name running for the popular test environments (i.e. Firefox-default;en-us;MacOSX6) and let Grid distribute the jobs accordingly. There will be ~4 environments of Firefox-default;en-us;MacOSX6, and so 4 concurrent executors active on Hudson. As for the other environments, we can have as many copies of selenium running of them as we see fit.
  • Tanay sent email about using screen - any objections? I confess it'd probably take me a bit to ramp up on, but if the folks who are maintaining Grid think it'd be more useful, then I'm all for it - stephend
  • Someone needs to own Grid, which means:
    • Keeping browsers up-to-date (within versions)
    • Upgrading VMWare Fusion
    • etc.
  • Input Tests require the latest beta, can Raymond/Tanay tell us if we have one set up so we can add a new test to be run?
  • Adding Notes to CI Task so others can see

Status Update

AMO | CI

  • AMO rewrite has started
    • Tests are in my Github at the moment. Unfortunately not had time to expand because of playing "whack the mole" with current AMO tests

SUMO CI

  • We should flag in-testsuite? for bugs that either aren't covered by unit tests, or could use more coverage
    • Absolutely- there are some waiting, and more will be added [RB]

Input CI

  • Have Tobbi, a contributor and soon to be intern, started looking at these
  • We still get lots (too many) service unavailable messages
    • Takes time to be sure it's the cause of failures - screenshots would help here
  • We currently need to update when new Firefox desktop/mobile versions are available, perhaps come up with better solution if this becomes a maintenance issue

Socorro CI

  • Have been running fine since move to PHX

Mozilla.com CI

  • Tests for review from David Burns

Action Items

  • Raymond and Tanay to have a look at capacity needs for the Grid and mail the team. Do we need more than 1 Mac Mini?
  • DavidB is to have a look at Screen
  • DavidB to look at screen shots on Hudson
Retrieved from "https://wiki.mozilla.org/index.php?title=Web_Testing/Automation/automation-27-01-2011&oldid=280551"