Hi,
I think there is a problem with the latest build when using selenium
waitForCondition.
e.g. from Selenium log window
nfo(1265883357685): Executing: |getBundleResponse | [{"uid":"","args":
["selenium.browserbot.getCurrentWindow().betfair.User.getLoginState()===
'loggedOut'","60000"],"name":"waitForCondition","sequ":64}] | |
Does not actually wiat for the statement to eval to true, instead it
appears to call once and proceed irrespective of the result, so when I
change the script so that it will allways return false, it still runs
once and proceeds.
info(1265884649685): Executing: |getBundleResponse | [{"uid":"","args":
["selenium.browserbot.getCurrentWindow().betfair.User.getLoginState()===
'loggedOut1'","10000"],"name":"waitForCondition","sequ":25}] | |
A more generic Javascript that you could use to test would be
waitForCondition("try {var doc =
selenium.browserbot.getCurrentWindow(true).document;doc.readyState ==
'complete'}catch(err){false}")
If you change 'complete' to anything else it will not error or timeout
as it should. I suspect this is happening with more or less anything
that uses selenium's timeout functionality.
Also there is a problem with user extensions. e.g. my custom jQuery
click method (not needed any more I know, but does illustrate the
point).
# info(1265885104194): Executing: |getBundleResponse |
[{"uid":"account.loginMessages.membershipNumberLink","args":
["jquery=#customerNumberLinkText"],"name":"waitForElementVisibleJQ","sequ":
43}] | |
# error(1265885104194): Unexpected Exception: selenium[apiName] is
undefined
# error(1265885104195): Exception details: message ->
selenium[apiName] is undefined, fileName ->
http://localhost:4444/selenium-server/core/scripts/tellurium.js,
lineNumber -> 957, stack -> ([object Object],[object Object])@http://
localhost:4444/selenium-server/core/scripts/tellurium.js:957 ()@http://
localhost:4444/selenium-server/core/scripts/tellurium.js:911 ("[{\"uid
\":\"account.loginMessages.membershipNumberLink\",\"args\":
[\"jquery=#customerNumberLinkText\"],\"name\":\"waitForElementVisibleJQ
\",\"sequ\":43}]","")@http://localhost:4444/selenium-server/core/
scripts/tellurium-extensions.js:337 ("[{\"uid\":
\"account.loginMessages.membershipNumberLink\",\"args\":
[\"jquery=#customerNumberLinkText\"],\"name\":\"waitForElementVisibleJQ
\",\"sequ\":43}]","")@http://localhost:4444/selenium-server/core/
scripts/htmlutils.js:60 ([object Object],[object Object])@http://
localhost:4444/selenium-server/core/scripts/selenium-
commandhandlers.js:330 ()@http://localhost:4444/selenium-server/core/
scripts/selenium-executionloop.js:112 (-10)@http://localhost:4444/
selenium-server/core/scripts/selenium-executionloop.js:78 (-10)@http://
localhost:4444/selenium-server/core/scripts/htmlutils.js:60 , name ->
TypeError
I suspect that the two problems are related.
--
You received this message because you are subscribed to the Google Groups
"tellurium-users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/tellurium-users?hl=en.
