Selenium 2.25.0 Is Out

[Mark Collin]

Doesn’t look like this has hit SeleniumHQ or the Selenium blog yet but the new version 2.25.0 of Selenium is available for download now:

 

http://code.google.com/p/selenium/downloads/list

 

[Mark Collin]

This may be useful for people as well:

 

v2.25.0

=======

WebDriver:

  * Added API for dealing with BASIC and DIGEST authentication

    dialogs. Currently not implemented in any drivers.

  * Warn users that the IE driver will no longer use the DLL in the

    next release.

  * Deprecated browser specific WebElement subclasses.

  * Added support for "requiredCapabilities" to the remote webdrivers

    and implemented basic support for these in the firefox

    driver. Failure to fulfull a required capability will cause a

    SessionNotCreatedException to be thrown.

  * Added the ability to determine how unhandled alerts should be

    handled. This is handled by the "unexpectedAlertBehaviour"

    capability, which can be one of "accept", "dismiss" or

    "ignore". Java code should use the UnexpectedAlertBehaviour

    enum. This is only implemented in Firefox for now.

  * Allow native events to be configured in Firefox and

    (experimentally) in IE using the "nativeEvents" capability.

  * Updated supported versions of Firefox to 17.

  * Firefox driver will enumerate through client rects until finding

    one with non-zero dimensions when clicking.

  * Better support for hovering on linux.

  * Safari driver will dismiss open alerts to prevent tests from

    hanging.

  * Better handling of overflow edge cases when determining element

    visibility.

  * Point users in the right direction when Safari fails to load a

    file:// URL.

  * Allowed to use IEDriverServer logging abilities in Java binding.

  * Avoid an issue where a call to submit could hang the firefox

    driver.

  * FluentWait will now handle any Throwable, not just

    RuntimeExceptions.

  * FIXED: 3897: Allow windows to be resized from a frame.

 

WebDriverJS:

  * Better stack traces from test code.

  * Update webdriver.atoms.element.type to recognize

    webdriver.Key.SEPARATOR

 

RC:

  * Better emulation provided by the WebDriver-backed Selenium when

    using IE, particularly when emulating firing of events.

 

Grid:

  * FIXED: 3230: Implementing /lifecycle-manager?action=shutdown

    command for the Grid Hub to ensure backward compatibility with

    Grid1 behaviour.

 

Selenium Server:

  * Reworked SSL certificate generation code when proxying HTTPS

    connections to use non-deprecated APIs in BouncyCastle.

--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To post to this group, send email to seleniu...@googlegroups.com.
To unsubscribe from this group, send email to selenium-user...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[alladi sai]

Thanks mark, It's really helpful,

I thought that in this release we will get a support to handle the alert box by setting the capability , unfortunately we got this facility for Firefox only , may be in next release we will get it for all browsers .

I am talking about this point.

"Added the ability to determine how unhandled alerts should be

    handled. This is handled by the "unexpectedAlertBehaviour"

    capability, which can be one of "accept", "dismiss" or

    "ignore". Java code should use the UnexpectedAlertBehaviour

    enum. This is only implemented in Firefox for now."

Regard's

Sai baba

--
You received this message because you are subscribed to the Google Groups "webdriver" group.
To post to this group, send email to webd...@googlegroups.com.
To unsubscribe from this group, send email to webdriver+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/webdriver?hl=en.

--
Regard's

Sai..

[Mike Riley]

Actually, Safari seems to have it as well:

  * Safari driver will dismiss open alerts to prevent tests from
    hanging.

My question is about the IEDriverServer, which was also upgraded.  Can I put that driver so it is run by both 2.25.0 and 2.24.1 as I evaluate the new version, or is there a compatibility issue?  One thing I have noticed with the ChromeDriver is that you can have the newer version and it works just fine with the older Selenium versions.  I am hoping the IEDriverServer.exe is designed to work in the same manner?

Mike

To post to this group, send email to selenium-users@googlegroups.com.
To unsubscribe from this group, send email to selenium-users+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "webdriver" group.
To post to this group, send email to webd...@googlegroups.com.

To unsubscribe from this group, send email to webdriver+unsubscribe@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/webdriver?hl=en.

--
Regard's

Sai..

[Jim Evans]

Newer versions of the IEDriverServer.exe should fit seamlessly into older versions of WebDriver, as long as the WebDriver library knows how to launch and talk to IEDriverServer.exe. Any later version of IEDriverServer.exe should work with 2.24.1 of the Java language bindings, at least for now[1].

[1] I don't foresee that changing, but I wanted to give myself the wiggle room in case the protocol changes significantly at some point in the future. What You Say On The Internet Is Forever (TM) after all.

[Jim Evans]

That's very odd. The build process between 2.24 and 2.25 for the .NET bindings has not changed one iota to my knowledge. The NuGet package is built from the same output as the .zip file creation, so I'm concerned about how this happened. I've just downloaded the .zip file from the googlecode site, created a new .NET Framework 4.0 console application project, referencing the assemblies from the net40 folder, and I got no assembly errors. Could there be something else at play here?

--Jim

On Thursday, July 19, 2012 8:02:15 AM UTC-7, Nathan Dace wrote:

Just a heads up.. 

The C# WebDriver download .NET 4.0 folder contains WebDriver assemblies that are targetting .NET 2.0.  I ran into a bunch of assembly errors when updating my dlls this way.

However, C# NuGet correctly has the .NET 4.0 assemblies packaged.

[Mike Riley]

Yes, if the protocol changes or something critical in the API to get the driver to work properly (like we had a while back with Opera due to a change in browser features) then it obviously will have a disconnect.  That can be announced in the release notes though, so people will be aware of it.

I like the idea of a separate driver module, because it lets the driver track the browser releases and the Selenium doesn't have to stay in sync with it, only the driver needs to.  That would seem to work well for the W3C standard as well, because the browser developers can maintain that code themselves and release it at the same time as the browser is released.

Mike

[ankit]

Could someone explain a little bit about this point to me:

  * Added support for "requiredCapabilities" to the remote webdrivers

   and implemented basic support for these in the firefox

   driver. Failure to fulfull a required capability will cause a

   SessionNotCreatedException to be thrown.

Doesn't the grid server setup already handle requiredCapabilities? I've been using it to dispatch tests to different browser versions without any problems. Or is this functionality now being implemented in standalone servers too? 

[Graham]

It's not available via Maven - how does it get pushed there?

[Mark Collin]

Yes it is, it was when I originally posted this as well (I updated my maven projects before posting):

 

http://central.maven.org/maven2/org/seleniumhq/selenium/selenium-server/2.25.0/

 

http://central.maven.org/maven2/org/seleniumhq/selenium/selenium-java/2.25.0/

 

Example POM available here:

 

https://github.com/Ardesco/Selenium-Maven-Template/blob/master/pom.xml

--

You received this message because you are subscribed to the Google Groups "webdriver" group.

To view this discussion on the web visit https://groups.google.com/d/msg/webdriver/-/WDBe6gHgVV0J.

To post to this group, send email to webd...@googlegroups.com.

To unsubscribe from this group, send email to webdriver+...@googlegroups.com.

[Vidit]

This is awesome news!! 

[Test SCF]

Yes Maven is also working perfect - I was able to download all jars :)

This is awesome news!! 

--

You received this message because you are subscribed to the Google Groups "webdriver" group.

To view this discussion on the web visit https://groups.google.com/d/msg/webdriver/-/8G2fcTwn8cwJ.

[Krishnan Mahadevan]

Can you please try and clear out your firefox profiles once and retry again ?

Thanks & Regards
Krishnan Mahadevan

"All the desirable things in life are either illegal, expensive, fattening or in love with someone else!"

On Wed, Aug 1, 2012 at 9:13 AM, Oliver <oliver29...@gmail.com> wrote:

Kindly help me out.

This code worked in 2.24.1 but in 2.25.0 throwing errors

I can find the element and get its text but cannot click on it. 

So you were literally working with the same Firefox Version when you toggled between 2.24.1 (where it works for you) and 2.25.0 (where it doesnot work for you) ?

 

Exception in thread "main" org.openqa.selenium.NoSuchElementException: Unable to locate element: {"method":"xpath","selector":"//td[text()=\"Search\"]"}

Command duration or timeout: 10 milliseconds

For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html

Build info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:09:54'

System info: os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1', java.version: '1.6.0_25'

Driver info: driver.version: RemoteWebDriver

Session ID: 4212428c-d1e7-4daa-9d3a-23a540182aaf

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)

at java.lang.reflect.Constructor.newInstance(Constructor.java:513)

at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:188)

at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:145)

at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:498)

at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:268)

at org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:353)

at org.openqa.selenium.By$ByXPath.findElement(By.java:343)

at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:260)

at CreateUserGroups.createUserGroups(CreateUserGroups.java:69)

at CreateUserGroups.main(CreateUserGroups.java:91)

Caused by: org.openqa.selenium.remote.ErrorHandler$UnknownServerException: Unable to locate element: {"method":"xpath","selector":"//td[text()=\"Search\"]"}

Build info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:09:54'

System info: os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1', java.version: '1.6.0_25'

Driver info: driver.version: unknown

at <anonymous class>.<anonymous method>(file:///C:/Users/OLIVER~1.VIN/AppData/Local/Temp/anonymous8046751778136140934webdriver-profile/extensions/fxdr...@googlecode.com/components/driver_component.js:6607)

at <anonymous class>.<anonymous method>(file:///C:/Users/OLIVER~1.VIN/AppData/Local/Temp/anonymous8046751778136140934webdriver-profile/extensions/fxdr...@googlecode.com/components/driver_component.js:6615)

at <anonymous class>.<anonymous method>(file:///C:/Users/OLIVER~1.VIN/AppData/Local/Temp/anonymous8046751778136140934webdriver-profile/extensions/fxdr...@googlecode.com/components/command_processor.js:10131)

at <anonymous class>.<anonymous method>(file:///C:/Users/OLIVER~1.VIN/AppData/Local/Temp/anonymous8046751778136140934webdriver-profile/extensions/fxdr...@googlecode.com/components/command_processor.js:10136)

at <anonymous class>.<anonymous method>(file:///C:/Users/OLIVER~1.VIN/AppData/Local/Temp/anonymous8046751778136140934webdriver-profile/extensions/fxdr...@googlecode.com/components/command_processor.js:10074)

On Thursday, 19 July 2012 16:07:34 UTC+8, Mark Collin wrote:

Doesn’t look like this has hit SeleniumHQ or the Selenium blog yet but the new version 2.25.0 of Selenium is available for download now:

 

http://code.google.com/p/selenium/downloads/list

 

--

You received this message because you are subscribed to the Google Groups "webdriver" group.

To view this discussion on the web visit https://groups.google.com/d/msg/webdriver/-/6zv0wkpFwJMJ.

[Oliver Vincent]

Hi Krishna

It is exactly throwing errors that it cannot locate the element. I used the same browser running both the tests. I did not set any profiles by the way. 

--
Regards

Oliver Vincent

[Krishnan Mahadevan]

Oliver, 

You may need to first check if your xpath is correct (I know this kind of sounds absurd, since the same xpath works fine in 2.24 but not in 2.25 is what you claim). See if you can narrow it down to an xpath which works for both versions.

That being said, I am running out of options to be frank :) Perhaps someone else can continue helping you.

Note: I think you are better off starting a new thread, since your problem doesnt have anything to do with this thread (which was basically an announcement sent to the users that Selenium 2.25 is out)

Thanks & Regards
Krishnan Mahadevan

"All the desirable things in life are either illegal, expensive, fattening or in love with someone else!"

[darrell]

Is changing from 2.24.1 to 2.25.0 the only change? Are you using the
exact same web browser (it didn't auto-upgrade)? Is this a new build
of the website? Can you go back to 2.24.1 and confirm it works? Did
you upgrade the Selenium Server and ALL the libraries for the client?
Did you update your build path so it is finding all the new libraries?

If everything above is fine, try changing the xpath to "//
td[contains(text(), 'Search')]" and see if that works for you.

Darrell

On Jul 31, 11:43 pm, Oliver <oliver29.vinc...@gmail.com> wrote:
> Kindly help me out.
>
> This code worked in 2.24.1 but in 2.25.0 throwing errors
> I can find the element and get its text but cannot click on it.
>

> Exception in thread "main" org.openqa.selenium.NoSuchElementException:
> Unable to locate element:
> {"method":"xpath","selector":"//td[text()=\"Search\"]"}
> Command duration or timeout: 10 milliseconds
> For documentation on this error, please visit:http://seleniumhq.org/exceptions/no_such_element.html
> Build info: version: '2.25.0', revision: '17482', time: '2012-07-18
> 21:09:54'
> System info: os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1',
> java.version: '1.6.0_25'
> Driver info: driver.version: RemoteWebDriver
> Session ID: 4212428c-d1e7-4daa-9d3a-23a540182aaf
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAcce ssorImpl.java:39)
> at

> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstru ctorAccessorImpl.java:27)

> at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
> at
> org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:1 88)
> at
> org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler. java:145)
> at
> org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:498 )
> at
> org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java :268)
> at

> org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriv er.java:353)

> at org.openqa.selenium.By$ByXPath.findElement(By.java:343)
> at
> org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java :260)
> at CreateUserGroups.createUserGroups(CreateUserGroups.java:69)
> at CreateUserGroups.main(CreateUserGroups.java:91)
> Caused by: org.openqa.selenium.remote.ErrorHandler$UnknownServerException:
> Unable to locate element:
> {"method":"xpath","selector":"//td[text()=\"Search\"]"}
> Build info: version: '2.25.0', revision: '17482', time: '2012-07-18
> 21:09:54'
> System info: os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1',
> java.version: '1.6.0_25'
> Driver info: driver.version: unknown
> at <anonymous class>.<anonymous

> method>(file:///C:/Users/OLIVER~1.VIN/AppData/Local/Temp/anonymous804675177 8136140934webdriver-profile/extensions/fxdri...@googlecode.com/components/driver_component.js:6607)

> at <anonymous class>.<anonymous

> method>(file:///C:/Users/OLIVER~1.VIN/AppData/Local/Temp/anonymous804675177 8136140934webdriver-profile/extensions/fxdri...@googlecode.com/components/driver_component.js:6615)

> at <anonymous class>.<anonymous

> method>(file:///C:/Users/OLIVER~1.VIN/AppData/Local/Temp/anonymous804675177 8136140934webdriver-profile/extensions/fxdri...@googlecode.com/components/command_processor.js:10131)

> at <anonymous class>.<anonymous

> method>(file:///C:/Users/OLIVER~1.VIN/AppData/Local/Temp/anonymous804675177 8136140934webdriver-profile/extensions/fxdri...@googlecode.com/components/command_processor.js:10136)

> at <anonymous class>.<anonymous

> method>(file:///C:/Users/OLIVER~1.VIN/AppData/Local/Temp/anonymous804675177 8136140934webdriver-profile/extensions/fxdri...@googlecode.com/components/command_processor.js:10074)

>
>
>
>
>
>
>
> On Thursday, 19 July 2012 16:07:34 UTC+8, Mark Collin wrote:
>

> > Doesn’t look like this has hit SeleniumHQ or the Selenium blog yet but the
> > new version 2.25.0 of Selenium is available for download now:
>

> > * *
>
> >http://code.google.com/p/selenium/downloads/list