Webdriver with Firefox 6

[Aravind Kannan]

Hi,

Has anyone tried webdriver with Firefox 6?
I tried to run my webdriver tests on Firefox 6 and the browser opens
and stays like that.The url is not typed on the address bar.


Thanks,
Aravind

[Simon Stewart]

Firefox 6 support arrived in Selenium 2.4. It works for me, though
I've fixed a couple of minor niggles today.

Simon

> --
> 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.
>
>

[aravind....@gmail.com]

Thanks for the update, Simon!
I will try it and email you.

Also thanks for all the great work on Webdriver!

Aravind

Sent from my phone. Please excuse the shortness and typos.

[Gulshan Saini]

Simon - I think this is same issue that I reported yesterday on selenium group https://groups.google.com/forum/#!topic/selenium-users/qJhOQ8pN3oU

However i don't see any updates on the download page http://code.google.com/p/selenium/downloads/list

Please advise.

Thanks
Gulshan

[Simon Stewart]

2.5 will be out soon, but 2.4 is on the download page already.

Simon

> --
> 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/-/Q_2JCvGWEyQJ.

[Gulshan Saini]

Thanks, Simon

[krainevsky]

Great news! Thanks, Simon

On Aug 17, 7:46 pm, Simon Stewart <simon.m.stew...@gmail.com> wrote:
> 2.5 will be out soon, but 2.4 is on the download page already.
>
> Simon
>
>
>
>
>
>
>
> On Wed, Aug 17, 2011 at 1:34 AM, Gulshan Saini <gulshan.sa...@gmail.com> wrote:
> > Simon - I think this is same issue that I reported yesterday on selenium

> > grouphttps://groups.google.com/forum/#!topic/selenium-users/qJhOQ8pN3oU

[Allen Liu]

Hi Simon,

I tried 2.4 on FF 6 but I have the same issue as described in the
first post by Aravind Kannan.

org.openqa.selenium.firefox.NotConnectedException: Unable to connect
to host localhost on port 7055 after 45000 ms
at
org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.start(NewProfileExtensionConnection.java:
96)
at
org.openqa.selenium.firefox.FirefoxDriver.startClient(FirefoxDriver.java:
142)
at
org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:
85)
at
org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:
121)
at
org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:
77)

On Aug 17, 11:46 pm, Simon Stewart <simon.m.stew...@gmail.com> wrote:
> 2.5 will be out soon, but 2.4 is on the download page already.
>
> Simon
>
>
>
>
>
>
>
> On Wed, Aug 17, 2011 at 1:34 AM, Gulshan Saini <gulshan.sa...@gmail.com> wrote:
> > Simon - I think this is same issue that I reported yesterday on selenium

> > grouphttps://groups.google.com/forum/#!topic/selenium-users/qJhOQ8pN3oU

[Aravind Kannan]

Hi Allen,

I tried with 2.4 and it works for me. I have made my BaseTest retry for the webdriver instance for 10 times before failing.
I saw Unable to connect to host localhost on port 7055 after 45000 ms once for the 2nd rertry, just once, Never saw this problem again. Works good so far.

Thanks,

Aravind

[Gulshan Saini]

Hi Simon - I am getting same error today. browser opens up with Webdriver written at bottom and nothing happens.
Do you have idea what is causing this issue.

[rmahnovetsky]

I had this problem when I upgraded firefox to version 5. Now I'm going
to have the same problem when I upgrade to 6... Is this going to be a
repeating exercise every 6 weeks? I also use web driver on my
continuous integration server. So another upgrade on that box.

Is it possible to design web driver so we don't have to upgrade our
projects with a new version of web driver when firefox upgrades itself
every 6 weeks?

I like to ensure my software is up to date with the latest libraries
but I do prefer to choose when I upgrade.

[Simon Stewart]

It turns out that webdriver is sufficiently complex that we're
uncovering bugs in Firefox. These are being closed, and as they are
we're bumping up the minimum supported supported version of Firefox.

Of course, we can only test our code in browsers that actually exist,
and the fact is that there's a new browser every 6 weeks. Changes go
in until the last minute, and some of those will effect our driver,
necessitating changes. This is one of the strong reasons why we're
working on creating an official standard for browser automation: so
that the tools are updated in step with the browser.

Simon