Do you have any other programs or services running in the background? (In particular any monitoring programs in the System Tray?) Have you tried collecting system performance metrics while you run your test?
So just for fun I did this:
#################################3
require 'watir'
include Watir
@ie = IE.new
@ie.set_fast_speed
1.upto 3000 do |num|
@ie.goto("C:\\Documents and Settings\\cmcmahon\\Desktop\\3000\\buttons1.html")
puts num
@ie.button(:name, "b1").click
end
##########################################
where buttons1.html just goes to itself:
<input type = button class="italic_button" name = b1 id = b2 value = "Click Me" document.location='buttons1.html';" title = "this is button1">
and found some interesting things. First of all, there's a memory leak. Watch your ruby process in taskmanager and it's clear to see. It's not too egregious, but on a system with other demands on memory, could be a problem.
The other thing is a little weirder. On my box at least, if I kill this process and re-start, the next ruby/watir process grabs as much memory as it had when I killed the previous process. I've never seen this behavior before and I can't explain it.
At about 2700 clicks, the rate of clicking dropped dramatically, to maybe 2 or 3 clicks every 10 seconds, or even longer. It picked back up again, but at one point it was slow enough that a timeout could definitely have come into play.
So I vote for a memory-leak problem or a timeout problem.
_______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
