Thanks for the thoughts everyone. I believe Oscar.Rieken was correct here,
with respect to the lack of memory or cpu causing a timing issue.
My original code was:
def set_date(field_label, content)
date_field = find_coach_frame.label(:text =>
field_label).parent.text_field(:type => 'text')
date_field.send_keys content
end
I changed it to:
def set_date(field_label, content)
date_field = find_coach_frame.label(:text =>
field_label).parent.text_field(:type => 'text')
date_field.send_keys content
Watir::Wait.until { date_field.value =~ /\d{2}-\d{2}-\d{4}/ }
end
Adding the Wait.until call to ensure the script didn't move forward until
the value was confirmed lets me get past the issue. I think what was
happening is that the commands were all issued in the thread, but the
browser itself was bogged down by all the concurrent activity, so the form
submission was being attempted before the date-picker could finish doing
it's client side work to actually set the value properly.
So, it indeed seems there's no inherent problem with running multiple
browsers at once, or any thread-safety problems (at least in my situation),
it was just that I needed to add some wait calls to ensure the browser had
caught up to what my code was assuming the situation was.
Thanks everyone!
--
--
Before posting, please read http://watir.com/support. In short: search before
you ask, be nice.
[email protected]
http://groups.google.com/group/watir-general
[email protected]
---
You received this message because you are subscribed to the Google Groups
"Watir General" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
