I originally posted this on the user forum but my question might be
more appropriate here:
The XPath evaluation on IE (all versions) is excruciatingly slow (at
least for me) when using RC. I searched the forums & there were
suggestion to switch to "javascript-xpath". I did, but it didn't help
at all, well it did but the improvement in speed was for all practical
purpose useless. So I downloaded the javascript-xpath library from the
authors site http://coderepos.org/share/wiki/JavaScript-XPath and
manually inserted it in to the web page of interest & ran my xpath
queries. Surprise, it was blazingly fast - I mean there was absolutely
no comparison!
So my question is very simple - is RC doing something special with
this javascript-xpath library? I am using the Perl driver if that
matters. Why is it so excruciatingly slow in Selenium & blazingly fast
outside? I even checked the version of the library & Selenium is
indeed using the latest available (well it's been the latest for a
while now). So any suggestions as to what is going on? Thanks.
I believe what you are experiencing is difference in speed when the
xpath is being evaluated from a different windows. Apparently the
cross-window talk slows it down big time :(
On Fri, Dec 11, 2009 at 1:44 PM, Aditya Ivaturi <ivat...@gmail.com> wrote:
> I originally posted this on the user forum but my question might be
> more appropriate here:
> The XPath evaluation on IE (all versions) is excruciatingly slow (at
> least for me) when using RC. I searched the forums & there were
> suggestion to switch to "javascript-xpath". I did, but it didn't help
> at all, well it did but the improvement in speed was for all practical
> purpose useless. So I downloaded the javascript-xpath library from the
> authors site http://coderepos.org/share/wiki/JavaScript-XPath and
> manually inserted it in to the web page of interest & ran my xpath
> queries. Surprise, it was blazingly fast - I mean there was absolutely
> no comparison!
> So my question is very simple - is RC doing something special with
> this javascript-xpath library? I am using the Perl driver if that
> matters. Why is it so excruciatingly slow in Selenium & blazingly fast
> outside? I even checked the version of the library & Selenium is
> indeed using the latest available (well it's been the latest for a
> while now). So any suggestions as to what is going on? Thanks.
> --
> You received this message because you are subscribed to the Google Groups "selenium-developers" group.
> To post to this group, send email to selenium-developers@googlegroups.com.
> To unsubscribe from this group, send email to selenium-developers+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/selenium-developers?hl=en.
If your application is not a 'frame-busting' one that changes window.top or
window.parent, you can run your selenium RC test using single-window mode
(command line flag: -singleWindow, I believe), which eliminates much of the
slowdown. I don't necessarily think that is will be as blazingly fast as
'outside', although if you're willing to provide numbers we'd love to have
them :)
-Jen
On Fri, Dec 11, 2009 at 2:33 PM, Patrick Lightbody <patr...@lightbody.net>wrote:
> I believe what you are experiencing is difference in speed when the
> xpath is being evaluated from a different windows. Apparently the
> cross-window talk slows it down big time :(
> On Fri, Dec 11, 2009 at 1:44 PM, Aditya Ivaturi <ivat...@gmail.com> wrote:
> > I originally posted this on the user forum but my question might be
> > more appropriate here:
> > The XPath evaluation on IE (all versions) is excruciatingly slow (at
> > least for me) when using RC. I searched the forums & there were
> > suggestion to switch to "javascript-xpath". I did, but it didn't help
> > at all, well it did but the improvement in speed was for all practical
> > purpose useless. So I downloaded the javascript-xpath library from the
> > authors site http://coderepos.org/share/wiki/JavaScript-XPath and
> > manually inserted it in to the web page of interest & ran my xpath
> > queries. Surprise, it was blazingly fast - I mean there was absolutely
> > no comparison!
> > So my question is very simple - is RC doing something special with
> > this javascript-xpath library? I am using the Perl driver if that
> > matters. Why is it so excruciatingly slow in Selenium & blazingly fast
> > outside? I even checked the version of the library & Selenium is
> > indeed using the latest available (well it's been the latest for a
> > while now). So any suggestions as to what is going on? Thanks.
> > --
> > You received this message because you are subscribed to the Google Groups
> "selenium-developers" group.
> > To post to this group, send email to
> selenium-developers@googlegroups.com.
> > To unsubscribe from this group, send email to
> selenium-developers+unsubscribe@googlegroups.com<selenium-developers%2Bunsu bscribe@googlegroups.com>
> .
> > For more options, visit this group at
> http://groups.google.com/group/selenium-developers?hl=en.
> --
> You received this message because you are subscribed to the Google Groups
> "selenium-developers" group.
> To post to this group, send email to selenium-developers@googlegroups.com.
> To unsubscribe from this group, send email to
> selenium-developers+unsubscribe@googlegroups.com<selenium-developers%2Bunsu bscribe@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/selenium-developers?hl=en.
We did primary research on Selenium playing tests of Ajax application
in IE and Firefox. The performance stinks. 30 seconds in Firefox, 30
minutes in IE. I presented the findings at The Server Side Symposium
last Spring. The slides and recommended mitigation is at: http://downloads.pushtotest.com/200903/TSS_PushToTest_RIA.pdf
-Frank
On Dec 11, 2009, at 2:33 PM, Patrick Lightbody wrote:
> I believe what you are experiencing is difference in speed when the
> xpath is being evaluated from a different windows. Apparently the
> cross-window talk slows it down big time :(
> On Fri, Dec 11, 2009 at 1:44 PM, Aditya Ivaturi <ivat...@gmail.com>
> wrote:
>> I originally posted this on the user forum but my question might be
>> more appropriate here:
>> The XPath evaluation on IE (all versions) is excruciatingly slow (at
>> least for me) when using RC. I searched the forums & there were
>> suggestion to switch to "javascript-xpath". I did, but it didn't help
>> at all, well it did but the improvement in speed was for all
>> practical
>> purpose useless. So I downloaded the javascript-xpath library from
>> the
>> authors site http://coderepos.org/share/wiki/JavaScript-XPath and
>> manually inserted it in to the web page of interest & ran my xpath
>> queries. Surprise, it was blazingly fast - I mean there was
>> absolutely
>> no comparison!
>> So my question is very simple - is RC doing something special with
>> this javascript-xpath library? I am using the Perl driver if that
>> matters. Why is it so excruciatingly slow in Selenium & blazingly
>> fast
>> outside? I even checked the version of the library & Selenium is
>> indeed using the latest available (well it's been the latest for a
>> while now). So any suggestions as to what is going on? Thanks.
>> --
>> You received this message because you are subscribed to the Google
>> Groups "selenium-developers" group.
>> To post to this group, send email to selenium-developers@googlegroups.com >> .
>> To unsubscribe from this group, send email to selenium-developers+unsubscribe@googlegroups.com >> .
>> For more options, visit this group at http://groups.google.com/group/selenium-developers?hl=en >> .
> --
> You received this message because you are subscribed to the Google
> Groups "selenium-developers" group.
> To post to this group, send email to selenium-developers@googlegroups.com > .
> To unsubscribe from this group, send email to selenium-developers+unsubscribe@googlegroups.com > .
> For more options, visit this group at http://groups.google.com/group/selenium-developers?hl=en > .
--
Frank Cohen, http://www.PushToTest.com, phone 408 871 0122
PushToTest, the open-source test automation company
Twitter: fcohen, LinkedIn: Frank Cohen
> you can run your selenium RC test using single-window mode
> (command line flag: -singleWindow, I believe), which eliminates much of the
> slowdown.
It does, actually I see a significant improvement & I can have tests
finish in this lifetime ;). Anyhoo, I am going to collect some numbers
on different options & may be try to find where the bottleneck is.
Thanks.
Does anyone know if the new WebDriver core will solve this problem for
Selenium?
Also, can you specify single-window mode from the test script? Or must it
be specified when you start Sel-RC Server? About 10% of my tests involve
multiple windows but if I could specify it for my single window tests I'd
still gain a significant performance improvement.
I've had this problem also for sometime and have just "put up with it" due
to lack of time but I'd love to have a solution.
Jennifer Bevan
<jennifer.bevan@g mail.com> To Sent by: selenium-develop...@googlegroups.co selenium-develope m r...@googlegroups.c cc om
Subject Re: [selenium-developers] 12/11/2009 10:44 javascript-xpath & IE PM
Please respond to selenium-develope r...@googlegroups.c om
If your application is not a 'frame-busting' one that changes window.top or
window.parent, you can run your selenium RC test using single-window mode
(command line flag: -singleWindow, I believe), which eliminates much of the
slowdown. I don't necessarily think that is will be as blazingly fast as
'outside', although if you're willing to provide numbers we'd love to have
them :)
-Jen
On Fri, Dec 11, 2009 at 2:33 PM, Patrick Lightbody <patr...@lightbody.net>
wrote:
I believe what you are experiencing is difference in speed when the
xpath is being evaluated from a different windows. Apparently the
cross-window talk slows it down big time :(
On Fri, Dec 11, 2009 at 1:44 PM, Aditya Ivaturi <ivat...@gmail.com>
wrote:
> I originally posted this on the user forum but my question might be
> more appropriate here:
>
> The XPath evaluation on IE (all versions) is excruciatingly slow (at
> least for me) when using RC. I searched the forums & there were
> suggestion to switch to "javascript-xpath". I did, but it didn't help
> at all, well it did but the improvement in speed was for all practical
> purpose useless. So I downloaded the javascript-xpath library from the
> authors site http://coderepos.org/share/wiki/JavaScript-XPath and
> manually inserted it in to the web page of interest & ran my xpath
> queries. Surprise, it was blazingly fast - I mean there was absolutely
> no comparison!
>
> So my question is very simple - is RC doing something special with
> this javascript-xpath library? I am using the Perl driver if that
> matters. Why is it so excruciatingly slow in Selenium & blazingly fast
> outside? I even checked the version of the library & Selenium is
> indeed using the latest available (well it's been the latest for a
> while now). So any suggestions as to what is going on? Thanks.
>
> --
>
> You received this message because you are subscribed to the Google
Groups "selenium-developers" group.
> To post to this group, send email to
selenium-developers@googlegroups.com.
> To unsubscribe from this group, send email to selenium-developers
+unsubscribe@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/selenium-developers?hl=en.
>
>
>
--
You received this message because you are subscribed to the Google Groups
"selenium-developers" group.
To post to this group, send email to selenium-developers@googlegroups.com
.
To unsubscribe from this group, send email to selenium-developers
+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/selenium-developers?hl=en.
--
You received this message because you are subscribed to the Google Groups
"selenium-developers" group.
To post to this group, send email to selenium-developers@googlegroups.com.
To unsubscribe from this group, send email to selenium-developers
+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/selenium-developers?hl=en.
We've put the hooks in for in-test control of multi- vs. single-window mode
into the Java RC client, and possibly (I'd have to check) the Python RC
client, but you said "test script" -- are you using the HTML tests? If so,
I believe you'd have to use the command-line flag "-singleWindow", at least
for the time being.
As far as the Webdriver core's impact goes, the hypothesis is that it will
help, although we do not yet know how much. The discussion so far has
basically been to continue with the webdriver integration into Selenium 2.0
and then see what remains to be done to make the multi- vs. single- window
performance more comparable.
On Mon, Dec 14, 2009 at 2:36 AM, <PGrandj...@idc.com> wrote:
> Does anyone know if the new WebDriver core will solve this problem for
> Selenium?
> Also, can you specify single-window mode from the test script? Or must it
> be specified when you start Sel-RC Server? About 10% of my tests involve
> multiple windows but if I could specify it for my single window tests I'd
> still gain a significant performance improvement.
> I've had this problem also for sometime and have just "put up with it" due
> to lack of time but I'd love to have a solution.
> [image: Inactive hide details for Jennifer Bevan
> <jennifer.be...@gmail.com>]Jennifer Bevan <jennifer.be...@gmail.com>
> *Jennifer Bevan <jennifer.be...@gmail.com>*
> Sent by: selenium-developers@googlegroups.com
> 12/11/2009 10:44 PM
> Please respond to
> selenium-developers@googlegroups.com
> To
> selenium-developers@googlegroups.com
> cc
> Subject
> Re: [selenium-developers] javascript-xpath & IE
> If your application is not a 'frame-busting' one that changes window.top or
> window.parent, you can run your selenium RC test using single-window mode
> (command line flag: -singleWindow, I believe), which eliminates much of the
> slowdown. I don't necessarily think that is will be as blazingly fast as
> 'outside', although if you're willing to provide numbers we'd love to have
> them :)
> -Jen
> On Fri, Dec 11, 2009 at 2:33 PM, Patrick Lightbody <*patr...@lightbody.net
> * <patr...@lightbody.net>> wrote:
> I believe what you are experiencing is difference in speed when the
> xpath is being evaluated from a different windows. Apparently the
> cross-window talk slows it down big time :(
> On Fri, Dec 11, 2009 at 1:44 PM, Aditya Ivaturi <*ivat...@gmail.com*<ivat...@gmail.com>>
> wrote:
> > I originally posted this on the user forum but my question might be
> > more appropriate here:
> > The XPath evaluation on IE (all versions) is excruciatingly slow (at
> > least for me) when using RC. I searched the forums & there were
> > suggestion to switch to "javascript-xpath". I did, but it didn't help
> > at all, well it did but the improvement in speed was for all
> practical
> > purpose useless. So I downloaded the javascript-xpath library from
> the
> > authors site *http://coderepos.org/share/wiki/JavaScript-XPath*<http://coderepos.org/share/wiki/JavaScript-XPath>and
> > manually inserted it in to the web page of interest & ran my xpath
> > queries. Surprise, it was blazingly fast - I mean there was
> absolutely
> > no comparison!
> > So my question is very simple - is RC doing something special with
> > this javascript-xpath library? I am using the Perl driver if that
> > matters. Why is it so excruciatingly slow in Selenium & blazingly
> fast
> > outside? I even checked the version of the library & Selenium is
> > indeed using the latest available (well it's been the latest for a
> > while now). So any suggestions as to what is going on? Thanks.
> > --
> > You received this message because you are subscribed to the Google
> Groups "selenium-developers" group.
> > To post to this group, send email to *
> selenium-developers@googlegroups.com*<selenium-developers@googlegroups.com>
> .
> > To unsubscribe from this group, send email to *
> selenium-developers+unsubscribe@googlegroups.com*<selenium-developers%2Buns ubscribe@googlegroups.com>
> .
> > For more options, visit this group at *
> http://groups.google.com/group/selenium-developers?hl=en*<http://groups.google.com/group/selenium-developers?hl=en>
> .
> --
> You received this message because you are subscribed to the Google
> Groups "selenium-developers" group.
> To post to this group, send email to *
> selenium-developers@googlegroups.com*<selenium-developers@googlegroups.com>
> .
> To unsubscribe from this group, send email to *
> selenium-developers+unsubscribe@googlegroups.com*<selenium-developers%2Buns ubscribe@googlegroups.com>
> .
> For more options, visit this group at *
> http://groups.google.com/group/selenium-developers?hl=en*<http://groups.google.com/group/selenium-developers?hl=en>
> .
> --
> You received this message because you are subscribed to the Google Groups
> "selenium-developers" group.
> To post to this group, send email to selenium-developers@googlegroups.com.
> To unsubscribe from this group, send email to
> selenium-developers+unsubscribe@googlegroups.com<selenium-developers%2Bunsu bscribe@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/selenium-developers?hl=en.
> --
> You received this message because you are subscribed to the Google Groups
> "Selenium Developers" group.
> To post to this group, send email to selenium-developers@googlegroups.com.
> To unsubscribe from this group, send email to
> selenium-developers+unsubscribe@googlegroups.com<selenium-developers%2Bunsu bscribe@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/selenium-developers?hl=en.
1) Is there any option within the Selenium server (or in the RC
client) that spits out the time it takes for a command to execute? I
turned on the debug option and there was a lot of info, but nothing
related to execution time of a command. So if there is none, I am
thinking of probably putting in some hooks in the core to capture that
info for me. From a simple perusal, it seems selenium-executionloop.js
might be a good place. Am I looking at the right place?
2) I originally posted this question in response to Patrick's comment
but for some reason the post didn't show up. May be I never hit the
submit button. According to Patrick - "Apparently the cross-window
talk slows it down big time". What I wanted to ask was - why is it not
a problem in FF? Is it because FF has inbuilt XPath evaluator & you
don't have to send data back & forth? If that is correct, then that
means the driver window (in case of IE) requests the HTML from the
target window & processes the XPath (since it has the external XPath
library) & this "chatter" causes the delay? Is that correct?
For #1 I recommend you try running your Selenium tests in TestMaker.
The SeleniumRC Script Runner in TestMaker tracks test and command- level execution time. It also data enables the scripts to get
operational test data from a CSV file and relational database.
TestMaker provides dozens of reports to correlate the Selenium command
performance to overall scalability in your application. Details at http://www.pushtotest.com/products
-Frank
On Dec 14, 2009, at 11:52 AM, Aditya Ivaturi wrote:
> 1) Is there any option within the Selenium server (or in the RC
> client) that spits out the time it takes for a command to execute? I
> turned on the debug option and there was a lot of info, but nothing
> related to execution time of a command. So if there is none, I am
> thinking of probably putting in some hooks in the core to capture that
> info for me. From a simple perusal, it seems selenium-executionloop.js
> might be a good place. Am I looking at the right place?
> 2) I originally posted this question in response to Patrick's comment
> but for some reason the post didn't show up. May be I never hit the
> submit button. According to Patrick - "Apparently the cross-window
> talk slows it down big time". What I wanted to ask was - why is it not
> a problem in FF? Is it because FF has inbuilt XPath evaluator & you
> don't have to send data back & forth? If that is correct, then that
> means the driver window (in case of IE) requests the HTML from the
> target window & processes the XPath (since it has the external XPath
> library) & this "chatter" causes the delay? Is that correct?
> --aditya
> --
> You received this message because you are subscribed to the Google
> Groups "Selenium Developers" group.
> To post to this group, send email to selenium-developers@googlegroups.com > .
> To unsubscribe from this group, send email to selenium-developers+unsubscribe@googlegroups.com > .
> For more options, visit this group at http://groups.google.com/group/selenium-developers?hl=en > .
--
Frank Cohen, http://www.PushToTest.com, phone 408 871 0122
PushToTest, the open-source test automation company
Twitter: fcohen, LinkedIn: Frank Cohen
> For #1 I recommend you try running your Selenium tests in TestMaker.
Frank - Thanks for the link, but looks like this is a test harness for
your selenium scripts. We have built a whole framework on top of
Selenium for our testing & I was feeling lazy to go through the whole
setup.
Regardless, I was looking in the right place to get the command
execution time. All I did was put in an extra statement in the
_executeCurrentCommand function prototype to add "info" for each
command execution & enable -browserSideLog while starting selenium-
server. This gave me numbers for each command that was executing.
The example command I looked at was - getXpathCount (which we use
heavily in our testing). And since I was running this on my local
laptop with all the crap (read antivirus et.al), for fairness sake
(not statistically valid though) I did three runs for -singleWindow &
the regular dual window option for IE.
XPath query I used - //table[@class='tblList'] - and getXpathCount
will return the count as 17. And in IE with respective options, here
are the execution times in Selenium:
And using the javascript-xpath library directly on the HTML page in IE
the time it took to parse the same query - 15ms, 21ms, 13ms.
As you can see (from my rather crude experiment), the singleWindow
option in IE actually gives a significant improvement in performance
of XPath processing in IE & the direct use of javascript-xpath is
indeed balzingly fast.
So can any one shed any more light on what is that "chatter" in
Selenium that is slowing things down so much for IE?
yes, I meant Sel-RC-Java 'test scripts' as actual test programs written in
Java. I couldn't remember if those 'hooks' could be put in on a per-test
bases.
tnx.
Jennifer Bevan
<jennifer.bevan@g mail.com> To Sent by: selenium-develop...@googlegroups.co selenium-develope m r...@googlegroups.c cc om
Subject Re: [selenium-developers] 12/14/2009 05:00 javascript-xpath & IE PM
Please respond to selenium-develope r...@googlegroups.c om
We've put the hooks in for in-test control of multi- vs. single-window mode
into the Java RC client, and possibly (I'd have to check) the Python RC
client, but you said "test script" -- are you using the HTML tests? If so,
I believe you'd have to use the command-line flag "-singleWindow", at
least for the time being.
As far as the Webdriver core's impact goes, the hypothesis is that it will
help, although we do not yet know how much. The discussion so far has
basically been to continue with the webdriver integration into Selenium 2.0
and then see what remains to be done to make the multi- vs. single- window
performance more comparable.
-Jen
On Mon, Dec 14, 2009 at 2:36 AM, <PGrandj...@idc.com> wrote:
Does anyone know if the new WebDriver core will solve this problem for
Selenium?
Also, can you specify single-window mode from the test script? Or must it
be specified when you start Sel-RC Server? About 10% of my tests involve
multiple windows but if I could specify it for my single window tests I'd
still gain a significant performance improvement.
I've had this problem also for sometime and have just "put up with it"
due to lack of time but I'd love to have a solution.
Inactive hide details for Jennifer Bevan <jennifer.be...@gmail.com>
Jennifer Bevan <jennifer.be...@gmail.com>
Jennifer Bevan
< jennifer.bevan@ gmail.com> To Sent by:
selenium-develo selenium-developers@ pers@googlegrou googlegroups.com ps.com
cc
12/11/2009
10:44 PM Subject
Re:
[selenium-developers ] javascript-xpath & IE Please respond to
selenium-developers@googlegroups.com
If your application is not a 'frame-busting' one that changes window.top
or window.parent, you can run your selenium RC test using single-window
mode (command line flag: -singleWindow, I believe), which eliminates much
of the slowdown. I don't necessarily think that is will be as blazingly
fast as 'outside', although if you're willing to provide numbers we'd
love to have them :)
-Jen
On Fri, Dec 11, 2009 at 2:33 PM, Patrick Lightbody <patr...@lightbody.net
> wrote:
I believe what you are experiencing is difference in speed when the
xpath is being evaluated from a different windows. Apparently the
cross-window talk slows it down big time :(
On Fri, Dec 11, 2009 at 1:44 PM, Aditya Ivaturi <ivat...@gmail.com>
wrote:
> I originally posted this on the user forum but my question might
be
> more appropriate here:
>
> The XPath evaluation on IE (all versions) is excruciatingly slow
(at
> least for me) when using RC. I searched the forums & there were
> suggestion to switch to "javascript-xpath". I did, but it didn't
help
> at all, well it did but the improvement in speed was for all
practical
> purpose useless. So I downloaded the javascript-xpath library
from the
> authors site http://coderepos.org/share/wiki/JavaScript-XPath and
> manually inserted it in to the web page of interest & ran my
xpath
> queries. Surprise, it was blazingly fast - I mean there was
absolutely
> no comparison!
>
> So my question is very simple - is RC doing something special
with
> this javascript-xpath library? I am using the Perl driver if that
> matters. Why is it so excruciatingly slow in Selenium & blazingly
fast
> outside? I even checked the version of the library & Selenium is
> indeed using the latest available (well it's been the latest for
a
> while now). So any suggestions as to what is going on? Thanks.
>
> --
>
> You received this message because you are subscribed to the
Google Groups "selenium-developers" group.
> To post to this group, send email to
selenium-developers@googlegroups.com.
> To unsubscribe from this group, send email to selenium-developers
+unsubscribe@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/selenium-developers?hl=en.
>
>
>
--
You received this message because you are subscribed to the Google
Groups "selenium-developers" group.
To post to this group, send email to
selenium-developers@googlegroups.com.
To unsubscribe from this group, send email to selenium-developers
+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/selenium-developers?hl=en.
--
You received this message because you are subscribed to the Google Groups
"selenium-developers" group.
To post to this group, send email to selenium-developers@googlegroups.com
.
To unsubscribe from this group, send email to selenium-developers
+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/selenium-developers?hl=en.
--
You received this message because you are subscribed to the Google Groups
"Selenium Developers" group.
To post to this group, send email to selenium-developers@googlegroups.com
.
To unsubscribe from this group, send email to selenium-developers
+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/selenium-developers?hl=en.
--
You received this message because you are subscribed to the Google Groups
"Selenium Developers" group.
To post to this group, send email to selenium-developers@googlegroups.com.
To unsubscribe from this group, send email to selenium-developers
+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/selenium-developers?hl=en.
> yes, I meant Sel-RC-Java 'test scripts' as actual test programs written in > Java. I couldn't remember if those 'hooks' could be put in on a per-test > bases.
AFAIK they can't. Would need a modified version of the Sever and and libs if I'm correct (which I have no doubt that the googlers can do pretty easily). Jen, do you know in detail how is that done? In case you have a patched version of the server, is there a chance your team could spend the time needed to contribute that back to Selenium 1.0? The functionality is valuable, and I have no doubt Selenium 1.0 will coexist with 2.0 much longer than what we'd like.
Will Selenium 2 fix this problem? It may if you're using the webdriver-backed selenium, it won't if you continue to use the pure JS multi-window Selenium implementation.
Although it may not be very useful to you, I do advise teams to avoid using xpath unless absolutely necessary, partly because the performance on IE will always be sub-optimal because it doesn't have an xpath engine that runs over HTML, and so it must always be simulated using IE's (relatively slow) javascript engine.
On Mon, Dec 14, 2009 at 10:36 AM, <PGrandj...@idc.com> wrote: > Does anyone know if the new WebDriver core will solve this problem for > Selenium?
> Also, can you specify single-window mode from the test script? Or must it > be specified when you start Sel-RC Server? About 10% of my tests involve > multiple windows but if I could specify it for my single window tests I'd > still gain a significant performance improvement.
> I've had this problem also for sometime and have just "put up with it" due > to lack of time but I'd love to have a solution.
> [image: Inactive hide details for Jennifer Bevan > <jennifer.be...@gmail.com>]Jennifer Bevan <jennifer.be...@gmail.com>
> *Jennifer Bevan <jennifer.be...@gmail.com>* > Sent by: selenium-developers@googlegroups.com
> 12/11/2009 10:44 PM > Please respond to > selenium-developers@googlegroups.com
> To
> selenium-developers@googlegroups.com > cc
> Subject
> Re: [selenium-developers] javascript-xpath & IE
> If your application is not a 'frame-busting' one that changes window.top or > window.parent, you can run your selenium RC test using single-window mode > (command line flag: -singleWindow, I believe), which eliminates much of the > slowdown. I don't necessarily think that is will be as blazingly fast as > 'outside', although if you're willing to provide numbers we'd love to have > them :)
> -Jen
> On Fri, Dec 11, 2009 at 2:33 PM, Patrick Lightbody <*patr...@lightbody.net > * <patr...@lightbody.net>> wrote:
> I believe what you are experiencing is difference in speed when the > xpath is being evaluated from a different windows. Apparently the > cross-window talk slows it down big time :(
> On Fri, Dec 11, 2009 at 1:44 PM, Aditya Ivaturi <*ivat...@gmail.com*<ivat...@gmail.com>> > wrote: > > I originally posted this on the user forum but my question might be > > more appropriate here:
> > The XPath evaluation on IE (all versions) is excruciatingly slow (at > > least for me) when using RC. I searched the forums & there were > > suggestion to switch to "javascript-xpath". I did, but it didn't help > > at all, well it did but the improvement in speed was for all > practical > > purpose useless. So I downloaded the javascript-xpath library from > the > > authors site *http://coderepos.org/share/wiki/JavaScript-XPath*<http://coderepos.org/share/wiki/JavaScript-XPath>and > > manually inserted it in to the web page of interest & ran my xpath > > queries. Surprise, it was blazingly fast - I mean there was > absolutely > > no comparison!
> > So my question is very simple - is RC doing something special with > > this javascript-xpath library? I am using the Perl driver if that > > matters. Why is it so excruciatingly slow in Selenium & blazingly > fast > > outside? I even checked the version of the library & Selenium is > > indeed using the latest available (well it's been the latest for a > > while now). So any suggestions as to what is going on? Thanks.
> > --
> > You received this message because you are subscribed to the Google > Groups "selenium-developers" group. > > To post to this group, send email to * > selenium-developers@googlegroups.com*<selenium-developers@googlegroups.com> > . > > To unsubscribe from this group, send email to * > selenium-developers+unsubscribe@googlegroups.com*<selenium-developers%2Buns ubscribe@googlegroups.com> > . > > For more options, visit this group at * > http://groups.google.com/group/selenium-developers?hl=en*<http://groups.google.com/group/selenium-developers?hl=en> > .
> --
> You received this message because you are subscribed to the Google > Groups "selenium-developers" group. > To post to this group, send email to * > selenium-developers@googlegroups.com*<selenium-developers@googlegroups.com> > . > To unsubscribe from this group, send email to * > selenium-developers+unsubscribe@googlegroups.com*<selenium-developers%2Buns ubscribe@googlegroups.com> > . > For more options, visit this group at * > http://groups.google.com/group/selenium-developers?hl=en*<http://groups.google.com/group/selenium-developers?hl=en> > .
> --
> You received this message because you are subscribed to the Google Groups > "selenium-developers" group. > To post to this group, send email to selenium-developers@googlegroups.com. > To unsubscribe from this group, send email to > selenium-developers+unsubscribe@googlegroups.com<selenium-developers%2Bunsu bscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/selenium-developers?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "Selenium Developers" group.
> To post to this group, send email to selenium-developers@googlegroups.com. > To unsubscribe from this group, send email to > selenium-developers+unsubscribe@googlegroups.com<selenium-developers%2Bunsu bscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/selenium-developers?hl=en.
> yes, I meant Sel-RC-Java 'test scripts' as actual test programs written in >> Java. I couldn't remember if those 'hooks' could be put in on a per-test >> bases.
> AFAIK they can't. Would need a modified version of the Sever and and libs > if I'm correct (which I have no doubt that the googlers can do pretty > easily). > Jen, do you know in detail how is that done? In case you have a patched > version of the server, is there a chance your team could spend the time > needed to contribute that back to Selenium 1.0? The functionality is > valuable, and I have no doubt Selenium 1.0 will coexist with 2.0 much longer > than what we'd like.
> Santi
> -- > You received this message because you are subscribed to the Google Groups > "Selenium Developers" group. > To post to this group, send email to selenium-developers@googlegroups.com. > To unsubscribe from this group, send email to > selenium-developers+unsubscribe@googlegroups.com<selenium-developers%2Bunsu bscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/selenium-developers?hl=en.
> xpath unless absolutely necessary, partly because the performance on IE will > always be sub-optimal because it doesn't have an xpath engine that runs over > HTML, and so it must always be simulated using IE's (relatively slow) > javascript engine.
Well, this is something that I am unable to wrap my head around & one of the reasons to start this thread. If you see my comment with the numbers I posted, simulated XPath using IE's javascript engine wasn' t "that" slow when used directly. i.e. if I run javascript-xpath on an HTML page directly (outside of Selenium) the numbers were rather surprisingly fast. But inside Selenium it becomes exponentially slow.
And I asked this question before & hopefully some one can answer it - why is it so slow inside Selenium - be it singleWindow or dual window?
On Mon, Dec 28, 2009 at 11:58 AM, Aditya Ivaturi <ivat...@gmail.com> wrote: >> xpath unless absolutely necessary, partly because the performance on IE will >> always be sub-optimal because it doesn't have an xpath engine that runs over >> HTML, and so it must always be simulated using IE's (relatively slow) >> javascript engine.
> Well, this is something that I am unable to wrap my head around & one > of the reasons to start this thread. If you see my comment with the > numbers I posted, simulated XPath using IE's javascript engine wasn' t > "that" slow when used directly. i.e. if I run javascript-xpath on an > HTML page directly (outside of Selenium) the numbers were rather > surprisingly fast. But inside Selenium it becomes exponentially slow.
> And I asked this question before & hopefully some one can answer it - > why is it so slow inside Selenium - be it singleWindow or dual window?
> --
> You received this message because you are subscribed to the Google Groups "Selenium Developers" group. > To post to this group, send email to selenium-developers@googlegroups.com. > To unsubscribe from this group, send email to selenium-developers+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/selenium-developers?hl=en.
Have you tried the various XPath libraries? I forget the exact details, but I know there at least 2 (and maybe 3) different libraries. I'd make sure that the one you're including is the same one that Selenium is indeed using.
On Mon, Dec 28, 2009 at 1:43 PM, Aditya Ivaturi <ivat...@gmail.com> wrote:
>> How are you running the xpath expressions "directly (outside of >> Selenium)"? We may be comparing apples and oranges here...
> In the HTML page I include the javascript-xpath library & then I > evaluate XPath on page load using a function call.
> --
> You received this message because you are subscribed to the Google Groups "Selenium Developers" group. > To post to this group, send email to selenium-developers@googlegroups.com. > To unsubscribe from this group, send email to selenium-developers+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/selenium-developers?hl=en.
> Have you tried the various XPath libraries? I forget the exact > details, but I know there at least 2 (and maybe 3) different > libraries. I'd make sure that the one you're including is the same one > that Selenium is indeed using.
As far as I know (at least based on the Perl driver's POD) there are 3 options that can be used - default, ajaxslt & javascript-xpath. "default" option loads the Google's ajaxslt & javascript-xpath uses Cybozu Labs' library. Google's ajaxslt is definitely slower than javascript-xpath and so I did my testing with javascript-xpath. I used the copy that is distributed with the RC & is located in core/xpath of the slenium-server.jar file. BTW, it is the same version that can also be found at the original author's site http://svn.coderepos.org/share/lang/javascript/javascript-xpath/trunk... (v0.1.11).
OK, cool - then it sounds like you've explored all the different avenues. I guess the only next step is for you to get us a simple test case that demonstrates the slow times in Selenium and fast times when invoked by clicking on a button. Is that something you might be able to put together?
On Mon, Dec 28, 2009 at 2:32 PM, Aditya Ivaturi <ivat...@gmail.com> wrote:
>> Have you tried the various XPath libraries? I forget the exact >> details, but I know there at least 2 (and maybe 3) different >> libraries. I'd make sure that the one you're including is the same one >> that Selenium is indeed using.
> As far as I know (at least based on the Perl driver's POD) there are 3 > options that can be used - default, ajaxslt & javascript-xpath. > "default" option loads the Google's ajaxslt & javascript-xpath uses > Cybozu Labs' library. Google's ajaxslt is definitely slower than > javascript-xpath and so I did my testing with javascript-xpath. I used > the copy that is distributed with the RC & is located in core/xpath of > the slenium-server.jar file. BTW, it is the same version that can also > be found at the original author's site > http://svn.coderepos.org/share/lang/javascript/javascript-xpath/trunk... > (v0.1.11).
> --
> You received this message because you are subscribed to the Google Groups "Selenium Developers" group. > To post to this group, send email to selenium-developers@googlegroups.com. > To unsubscribe from this group, send email to selenium-developers+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/selenium-developers?hl=en.
> OK, cool - then it sounds like you've explored all the different > avenues. I guess the only next step is for you to get us a simple test > case that demonstrates the slow times in Selenium and fast times when > invoked by clicking on a button. Is that something you might be able > to put together?
I think I can do that, but I'll have to get to it next week - I am on vacation from today afternoon.
> OK, cool - then it sounds like you've explored all the different > avenues. I guess the only next step is for you to get us a simple test > case that demonstrates the slow times in Selenium and fast times when > invoked by clicking on a button. Is that something you might be able > to put together?
I have a test page ready to demonstrate it. Where can I upload it?
On Tue, Jan 5, 2010 at 3:02 PM, Aditya Ivaturi <ivat...@gmail.com> wrote: >> OK, cool - then it sounds like you've explored all the different >> avenues. I guess the only next step is for you to get us a simple test >> case that demonstrates the slow times in Selenium and fast times when >> invoked by clicking on a button. Is that something you might be able >> to put together?
> I have a test page ready to demonstrate it. Where can I upload it?
> -- > You received this message because you are subscribed to the Google Groups "Selenium Developers" group. > To post to this group, send email to selenium-developers@googlegroups.com. > To unsubscribe from this group, send email to selenium-developers+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/selenium-developers?hl=en.