This repository was archived by the owner on Jun 27, 2019. It is now read-only.
Repository navigation
This repository was archived by the owner on Jun 27, 2019. It is now read-only.
Extending Xebium with your own fixtures #120
Description
Sometimes it'd be handy to write your own fixtures that can access the WebDriver instance created by our SeleniumDriverFixture, without having to explicitly pass that around in the FitNesse tests.
What would be the way to accomplish this? Does FitNesse already provide any infrastructure for this?
Activity
raboof commentedon May 5, 2014
To whet your appetite: if we can find an elegant way to do this, I'd like to write a query table fixture that gets its data from an HTML table :).
jguglielmi commentedon May 6, 2014
Arnout, I am not sure if this answers your question or not...probably not...but I worked on creating custom fixtures for sikuli that combine selenium and sikulidrivers. A hybrid fixture if you will. Hopefully, this can lead you down the right path. I'd also recommend talking to ejakubowski. He really gave me some good ideas to solve these issues.
1.defaultwebdriversupplier.java as a bypass. I actually incorporated the sikuliwebdrivers into OASIS to call them directly under the org.sikuli directory.
https://github.com/jguglielmi/OASIS-Maven/tree/master/src/main/java/org/sikuli/webdriver
https://github.com/jguglielmi/OASIS-Maven/blob/master/src/main/java/com/xebia/incubator/xebium/DefaultWebDriverSupplier.java
https://github.com/jguglielmi/OASIS-Maven/blob/master/src/main/java/com/xebia/incubator/xebium/SikuliWebDriverFixture.java