Selenium 3 and Xebium

[rueck...@gmail.com]

Hi all,

do anybody know if there are plans that xebium keeps working with selenium 3?

So far as I have seen, there are problems with e.g. compiling xebium with selenium3 (newest beta verison).

it´s important for our future of our testframework ...

wkr,

Michael

[Cirilo Wortel]

Hi Michael, 

There is no active development/maintenance on Xebium from our site at this moment. But if you see the need for upgrading it, you're absolutely invited to do so and make the required changes. The community is welcome to contribute. So its up to you :)

Regards,

Cirilo

--
You received this message because you are subscribed to the Google Groups "Xebium" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xebium+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[michae...@silverpopdev.com]

Hello everyone,

I am also interested in this topic.  

The main problem here is that the Selenium RC interface was deprecated with the 3.x release.  This includes all packages com.thoughtworks.selenium.* -- which are being implemented with the Selenium Driver Fixture in Xebium.  

My java skills are limited, but the fixture classes appear to be very robust. The goal would be to migrate from using the CommandProcessor classes to using WebDriver classes in the org.openqa.selenium.* packages.  The documentation on the Selenium Java bindings is slightly unclear to me, but I have successfully updated Xebium code so that it compiles and runs some of my test pages without the CommandProcessor and HttpCommandProcessor classes.

My understanding was that the WebDriverCommandProcessor would still be available with this release, but it is not, so attempting to build Xebium with Selenium versions greater than 2.53.1 is still failing with my code changes.

Does anyone with more knowledge of Selenium 3.x know if there is an equivalent to the WebDriverCommandProcessor interface in org.openqa.selenium? After reviewing some of the documentation, it appears that the new interface would be org.openqa.selenium.interactions.ActionChainExecutor.  

Any input would be valuable, as I don't think much more would be required to get Xebium up and running with Selenium 3.x and the latest browsers supported. 

On Friday, October 7, 2016 at 3:03:53 AM UTC-4, Cirilo Wortel wrote:

Hi Michael, 

There is no active development/maintenance on Xebium from our site at this moment. But if you see the need for upgrading it, you're absolutely invited to do so and make the required changes. The community is welcome to contribute. So its up to you :)

Regards,

Cirilo

On Thu, Oct 6, 2016 at 4:54 PM, <rueck...@gmail.com> wrote:

Hi all,

do anybody know if there are plans that xebium keeps working with selenium 3?

So far as I have seen, there are problems with e.g. compiling xebium with selenium3 (newest beta verison).

it´s important for our future of our testframework ...

wkr,

Michael

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

To unsubscribe from this group and stop receiving emails from it, send an email to xebium+un...@googlegroups.com.

[michae...@silverpopdev.com]

So, I wish I had done some more research before I started making the code changes mentioned above.  It turns out that the Selenium developers were very considerate of situation like this, and it may be possible to simply add a new dependency to the pom.xml in the project (this is used by Maven). I can't say definitively that it will run without issues, and many of the test pages in the original Xebium suite will likely fail. This approach has worked for me for the time being, though as I am only relying on the WebDriver framework and none of the Selenium RC interfaces. 

Add the following dependency to the pom.xml, and then comment out or delete SeleneseScriptFixture.java and SeleniumServerFixture.java.

    <dependency>
      <groupId>org.seleniumhq.selenium</groupId>
      <artifactId>selenium-leg-rc</artifactId>
      <version>${selenium.version}</version>
    </dependency>

I also had to make a small change to FastHttpCommandExecutor.java -- add org.openqa.selenium.NotFoundException to the list of imports and then update line 131 to NotFoundException from SessionNotFoundException.

Finally, as I mentioned in my earlier post, I am far from an expert when it comes to the Xebium code base, and I am more interested in getting this to some kind of working state with Selenium 3.x, so I can continue testing against the latest browsers.  Please take ALL of this information for granted and don't assume this to be professional or expert advice.  I'm just trying to help anyone out that is in the same boat as me.

-Michael

[kukrani...@gmail.com]

Thanks Michael,your suggested changes work fine. However leg-rc package won't be officially supported so I think we must move to selenium 3. I would be happy to join hands and see if we can migrate to selenium 3. Although I see that WebDriverCommandProcessor is not deprecated like you mentioned above. 
Any more information would be helpful. 

[kukrani...@gmail.com]

Oh yeah i see it now. Basically the whole package com.thoughtworks.selenium.* is gone. it exists in the 3.0.1 leg-rc but not on 3.0.1.
We will have to rewrite the whole SeleniumDriverfixture mainly and other places as well. Although you can look at : https://github.com/andreptb/fitnesse-selenium-slim . This project is same as Xebium but built on selenium 3. Although fixtures are not same as what you would get from Xebium Formatter on IDE
If the fixtures would have been same as Xebium then we could have simply used xebium formatter

[sebastie...@gmail.com]

has anybody found a solution to run xebium with selenium 3.x ?

regards

Sebastien

[kukrani...@gmail.com]

Hi Sebestien

You can only do this via legacy RC package for now. Untill Selenium retires the legacy RC package too. If you are starting to use fitnesse i would say either build your own fixtures or upgrade xebium to use selenium 3.x which requires codes changes for Xebium. 

If you want to use legacy RC package, Micahel has already written instructions here : https://github.com/xebia/Xebium/issues/165

[gkrr...@gmail.com]

We are extremely satisfied to report the arrival of Selenium 3.0. On the off chance that you've been sitting tight for a steady discharge since 2.53.1, now's your opportunity to refresh. What's more, on the off chance that you do, here is the thing that you'll discover: Selenium Training In Bangalore | Best SeleniumTraining in Bangalore

As we've said previously, for clients of the WebDriver APIs this is a drop-in substitution. You'll see that advanced programs, for example, Chrome and Edge will keep on working similarly as previously, and we've accepted the open door to settle a few bugs and enhance solidness. Selenium Grid clients may expect updates to their setup as the json config record design has been refreshed, as have some of charge line parameter choices, yet the overhaul ought to likewise be smooth. 

The significant change in Selenium 3.0 is we're expelling the first Selenium Core usage and supplanting it with one sponsored by WebDriver. This will influence all clients of the Selenium RC APIs. For more data, please observe the past post. 

A great deal has changed in the 5 years between forms 2 and 3. When we dispatched Selenium 2, the Selenium venture was in charge of giving the driver to every program. Presently, we are glad to state that all the significant program merchants deliver their own usage (Apple, Google, Microsoft, and Mozilla). Since the program merchants know their programs superior to anybody, their WebDriver usage can be firmly coupled to the program, prompting a superior testing background for you. 

The other eminent change has been that there is presently a W3C detail for program mechanization, in view of the Open Source WebDriver. This still can't seem to achieve "suggestion" status, yet the general population chipping away at it (counting individuals from the Selenium venture!) are currently concentrating on completing the content and composing the usage. Selenium Training In Bangalore | Best SeleniumTraining in Bangalore

Mozilla has been a leader in actualizing the W3C WebDriver convention. On the in addition to side, this has uncovered issues with the spec as it has advanced, however it likewise implies that Firefox bolster is difficult to track as their designing endeavors have been forward looking, instead of on supporting the momentum wire convention utilized by Selenium WebDriver. Until further notice, the best exhortation we can offer is for you to attempt the most recent arrival of geckodriver and Selenium together. 

These are energizing circumstances for program mechanization! Selenium 3.0 is a noteworthy discharge and we're anticipating enhancing things further, and also following the continuous work of the W3C spec. We will probably keep the progressions your tests need to manage to an outright least, to keep saving the diligent work that is gone into composing your current tests. 

As an individual note, I'd get a kick out of the chance to state thank you to every one of the numerous individuals that have worked so difficult to make Selenium 3 conceivable. That is not only the designers and supporters of the Open Source venture (over a wide span of time), yet in addition the architects from Google, Microsoft, Mozilla, and Apple, and everybody required with the W3C spec. I'd additionally jump at the chance to state thank you to everybody who's set aside the opportunity to report bugs, our clients and our group. The task is awesome amusing to take a shot at and you're the explanation behind that. A last thank you is because of the Software Freedom Conservancy, who have given important help the coordinations of running a substantial OSS venture. 

Upbeat hacking, everybody! May your tests run quick and genuine!

Selenium Training In Bangalore | Best SeleniumTraining in Bangalore