Over a million developers have joined DZone.

Taking a Screenshot When UI tests Written in Geb Fail

· Java Zone

Navigate the Maze of the End-User Experience and pick up this APM Essential guide, brought to you in partnership with CA Technologies

This is a second post about Geb in a short time. This time we will learn how to configure Geb to take a screenshot every time our UI test fails. Image of page at the moment when test failed is often very helpful in debugging mysteriously failing UI test on CI server and can save a lot of time when trying to solve such problems.

The Problem

We need a simple way to configure Geb UI tests to take a screenshot on each test fail. This should be “add and forget” config that does not need any changes when we add more tests to our application.


We have to find some type of listener that waits for different test results and fires proper method when test fails. In TestNG we have a TestListenerAdapter so probably Geb or Spock should have something similar.

After some digging I was able to locate IRunListener with method I need:

public interface IRunListener {
    void beforeSpec(org.spockframework.runtime.model.SpecInfo specInfo);
    void beforeFeature(org.spockframework.runtime.model.FeatureInfo featureInfo);
    void beforeIteration(org.spockframework.runtime.model.IterationInfo iterationInfo);
    void afterIteration(org.spockframework.runtime.model.IterationInfo iterationInfo);
    void afterFeature(org.spockframework.runtime.model.FeatureInfo featureInfo);
    void afterSpec(org.spockframework.runtime.model.SpecInfo specInfo);
    void error(org.spockframework.runtime.model.ErrorInfo errorInfo); // < -- this is it
    void specSkipped(org.spockframework.runtime.model.SpecInfo specInfo);
    void featureSkipped(org.spockframework.runtime.model.FeatureInfo featureInfo);

Simple version of test failure listener
Luckily this interface comes with abstract class named AbstractRunListener that allows us to implement only methods we want instead of fulfilling the whole contract specified by IRunListener.

So our first step will be to print something to the console every time our test fails:

class TakeScreenshotOnTestFailureListener extends AbstractRunListener {
   def void error(ErrorInfo error) {
       System.out.println("Error in method " + error.method.name);

Adding custom listener to all tests with Spock extension
But except implementation of a listener, we have to add this listener to our tests. Currently in Spock this is possible only with extensions. Again, I had to find proper extension to use and ended with interface IGlobalExtension which has only one method visiting each spec (test method) in our codebase:

public interface IGlobalExtension {
  void visitSpec(SpecInfo spec);

So extension implementation looks as follows, to each visited spec we add our TakeScreenshotOnTestFailureListener listener:

class GlobalSpecExtension implements IGlobalExtension {
    void visitSpec(SpecInfo specInfo) {
        specInfo.addListener(new TakeScreenshotOnTestFailureListener())

Registering Spock global extension
Each global extension have to be registered to Spock. This can be achieved by placing text file with easy to remember name in META-INF/services directory. File must be named org.spockframework.runtime.extension.IGlobalExtension and should contain full name of our implementation of IGlobalExtension interface:


Taking a screenshot on each UI test fail
Now on each test fail we will see that our text message is printed to the console. This proves that our solution is going in the right direction and last thing still not implemented is taking a screenshot.

Taking a screenshot using Selenium driver is quite easy, it is one method call, but before that we have to acquire driver instance in our listener class. Directly it is impossible to access driver directly from the listener so we need to store it in globally accessible object. Simplest solution is to save reference to the driver when we create it in our GebConfig file. So let’s create a singleton that will hold our browser:

class BrowserInstance {
    def FirefoxDriver browser;

and initialise it in GebConfig.groovy script located in root package of our project:

driver =
        newDriver = new FirefoxDriver()
        BrowserInstance.instance.browser = newDriver
        return newDriver

Now we can access driver from our listener object, so final taking screenshot logic is pretty straightforward:

class TakeScreenshotOnTestFailureListener extends AbstractRunListener {
   def void error(ErrorInfo error) {
       File screenFile = BrowserInstance.instance.browser.getScreenshotAs(OutputType.FILE); // take a screenshot
       String fileName = createFileName(error) // generate file name based on test class and method names
       File destinationFile = new File(System.getProperty("java.io.tmpdir") + System.getProperty("file.separator") + fileName)
       Files.copy(screenFile, destinationFile)
       System.out.println("##teamcity[publishArtifacts '" + destinationFile.getAbsolutePath() + "']"); // publish as artifact in TeamCity
    def private String createFileName(ErrorInfo error) {
        String specName = error.method.parent.name
        String testName = error.method.name
        String milliseconds = new Date().getTime()
        String fileName = specName + ": '" + testName + "' " + milliseconds + ".png"

And that’s all. Each test fail will now appear with corresponding screenshot from browser.

Thrive in the application economy with an APM model that is strategic. Be E.P.I.C. with CA APM.  Brought to you in partnership with CA Technologies.


Published at DZone with permission of Tomasz Dziurko, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}