Recently I've been playing around with Spock and a bit with Geb. I'm under big impression so today let's check out what Geb is.

Version for managers -> It's a technology that will make your developers test and allow you to cut costs. Now go send email to dev team that they should check it out, shoo.

Version for devs -> It's a sexy framework with jQuery like DSL over Webdriver/Selenium allowing easy use of Page Objects and wiring it all up with Groovy. Those of you that had chance to work with Selenium and write traditional functional web tests in Java, most likely are now wondering what sexy can be in Webdriver.

Well, most importantly, Geb takes away all the boilerplate code and Java ceremony, leaving for you to fill only the important parts with simple syntax, that all of jQuery users know already (most of the examples are taken from Geb site).

$("div.some-class p:first[title='something']")
$("h1", 2, class: "heading")
$("p", text: contains("Geb"))
//Manipulating forms
$("form").name = "Geb"
assert $("form").name == "Geb"

Well, for me it looks like a jQuery. When you get out of syntax and reach test context, it's even better. Regardless of what testing framework you're currently using, Geb will work out of the box with it. Personally I've been using it with Spock, but it has support for JUnit, TestNG, EasyB and Cucumber. So you don't have to be concerned about learning another tool.

Let's check out example below where it's used with Spock

class LoginSpec extends GebSpec {
    def "login to admin section"() {
        to LoginPage

        loginForm.with {
            username = "admin"
            password = "password"


        at AdminPage

As you can see, it's just a standard Specification. Only difference is that you use one of Geb spec classes.

Big win in Geb are Page Objects. I haven't used them in Selenium, however as I understand they are available there. What is a Page Object? As name suggests, it's an object representation of a page :) To be bit more specific: it's a class inheriting from geb.Page class which role is to encapsulate all the interaction with the HTML page.

class SignupPage extends Page {
    static url = ""
    static at = { title == "Logowanie | iZawody" }
    static content = {
        loginField { $("input#login") }
        passwordField { $("input#password") }
        loginButton(to: DashboardPage) { $("input#loginButton") }

    void login(String login. String password) {
        loginField.value login
		passwordField.value password

class DashboardPage extends Page {
    static at = { waitFor { title.endsWith("| iZawody dashboard") } }

//Test script {
    to SignupPage
    login("admin", "admin")
    at DashboardPage

It helps as you create a lot of reusable code that encapsulate a lot of moving parts, like text on pages, id's, HTML structure. So after updating page template you need to only update page object in order to fix dozens of failing unit tests! That's just a huge win! As a side bonus, all the elements specified in the content section, are reachable in test script, so each element may have an abstraction layer :)

As Geb is just an more readable abstraction layer over Webdriver, as a bonus you get a full support for all the browsers that selenium uses, so you may run your tests in FF, Chrome, Opera, IE and there is experimental support for mobile browsers. If you're running on a server there is a driver for headless browser, so all covered :)

Only place where Geb falls short is if you aim for job security. Even with code obfuscator you're going to fail. Code is just damn too simple :(  Other than that Happy coding!