Russ Thomas wrote:
Any reason why goBack doesn't use "andWait" by default - same as Open
and Click?
Actually, "click" no longer waits implicitly, though "open" still does.
Yes, I guess "goBack" could/should probably wait implicitly too -
there's not much point to it without the "AndWait".
- Original Message -
From: "Mike Williams" <[EMAIL PROTECTED]>
To:
Sent: Thursday, November 24, 2005 10:49 AM
Subject: Re: goBack bug? (was Re: [Selenium-users] spurious failures)
There is a race-condition bug in page-reload detection on Firefox, which
I haven't ye
There is a race-condition bug in page-reload detection on Firefox, which
I haven't yet been able to get to the bottom of. See
http://jira.public.thoughtworks.org/browse/SEL-77
However, I suspect your problem might be use of "goBack". Try
"goBackAndWait" instead. The "AndWait" suffix tell
Sandy Demi wrote:
I'm not sure if this is related, but I found that goBack causes the Safari
browser to crash. I'll try adding a pause to see if that makes any
difference.
"goBack" isn't supported in Safari (or Konqueror), as they appear to
disallow access to window.history.back()
--
chee
ovember 23, 2005 1:45 PM
To: selenium-users@lists.public.thoughtworks.org
Subject: goBack bug? (was Re: [Selenium-users] spurious failures)
Ok, I think I may have found the problem.
It appears that goBack does not always allow time for the DOM to be fully
constructed[1].
If I place a pause of 250
fully "ready"... and why it's not working in goBack.
[2] where "never" = thousands of sample runs in my dataset.
- Original Message -
From: "Russ Thomas" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, November 23, 2005 5:45 PM
Subject: [Selenium-users]
Hi all,
I'm starting to ramp up my tests/testsuite and have noticed some strange
behaviours in Selenium. Basically, "Access Denied" is returned from some
tests, while others return "Element x not found". Both of these appear
"randomly" - for example, if I repeatedly run and rerun the same tes
