Hi, all
Yes Iam also facing the same kind of problem,when Iam using the testrunner with (.html)extension,then while running the script Iam getting Access denied messages in value column(i,e Expected Result Column) what could be the problem here any suggestions on this will be very helpful
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
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
- 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 yet been able to get to
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".
Sandy Demi a écrit :
A test I recorded with
the Selenium Recorder on Firefox uses
the following xpath _expression_ to locate an element:
//tbody/tr[2]/td/[EMAIL PROTECTED]"LearningCurveServlet?skill_id=229"]
When I run the test
script on Firefox (WinXP), the element
Mike Williams a écrit :
Quoting Alexandre Garel
<[EMAIL PROTECTED]>:
xpath=(//[EMAIL PROTECTED]"name1"])[3] should
work.but because selenium wants a xpath to start with // (known bug)
you can use
xpath=//XX|(//[EMAIL PROTECTED]"name1"])[3] instead
That bug was fixed for
