We’ve been playing around with Geb for a while now and writing tests using WebDriver and Groovy has been a delight! Geb integrates well with JUnit, TestNG, Spock, and Cucumber. All there is left to do is integrating it with FitNesse … or not :-).
Setup Gradle and Dependencies
First we start with grabbing the gradle fitnesse classpath builder from Arjan Molenaar.
Add the following dependencies to the gradle build file:
[objc]
compile ‘org.codehaus.groovy:groovy-all:2.3.7’
compile ‘org.gebish:geb-core:0.9.3’
compile ‘org.seleniumhq.selenium:selenium-java:2.43.1
[/objc]
Configure different drivers with the ConfigSlurper
Geb provides a configuration mechanism using the Groovy ConfigSlurper. It’s perfect for environment sensitive configuration. Geb uses the geb.env system property to determine the environment to use. So we use the ConfigSlurper to configure different drivers.
[objc]
import org.openqa.selenium.chrome.ChromeDriver
import org.openqa.selenium.firefox.FirefoxDriver
driver = { new FirefoxDriver() }
environments {
chrome {
driver = { new ChromeDriver() }
}
}
[/objc]
FitNesse using the ConfigSlurper
We need to tweak the gradle build script to let FitNesse play nice with the ConfigSlurper. So we pass the geb.env system property as a JVM argument. Look for the gradle task "wiki" in the gradle build script and add the following lines.
[objc]
def gebEnv = (System.getProperty("geb.env")) ? (System.getProperty("geb.env")) : "firefox"
jvmArgs "-Dgeb.env=${gebEnv}"
[/objc]
Since FitNesse spins up a separate ‘service’ process when you execute a test, we need to pass the geb.env system property into the COMMAND_PATTERN of FitNesse. That service needs the geb.env system property to let Geb know which environment to use. Put the following lines in the FitNesse page.
[objc]
!define COMMAND_PATTERN {java -Dgeb.env=${geb.env} -cp %p %m}
[/objc]
Now you can control the Geb environment by specifying it on the following command line.
gradle wiki -Dgeb.env=chrome
The gradle build script will pass the geb.env system property as JVM argument when FitNesse starts up. And the COMMAND_PATTERN will pass it to the test runner service.
Want to see it in action? Sources can be found here.
Qxperts. We empower companies to deliver reliable & high-quality software. Any questions? We are here to help! www.qxperts.io