Setting a Tomcat version with Spring Boot and Gradle

Spring Boot allows you to easily specify a tomcat version when using Maven (Docs). But there doesn’t seem to be an equivalent mechanism for Gradle.

To lock down a specific tomcat version for war deployment, I found that I had to exclude the starter-tomcat module and add the dependencies specified in the tomcat starter POM in my Spring Boot project’s build.gradle file.

   exclude module: spring-boot-starter-tomcat
providedRuntime 'org.apache.tomcat.embed:tomcat-embed-core:7.0.52'
providedRuntime 'org.apache.tomcat.embed:tomcat-embed-el:7.0.52'
providedRuntime 'org.apache.tomcat.embed:tomcat-embed-logging-juli:7.0.52'
providedRuntime 'org.apache.tomcat:tomcat7-websocket:7.0.52'

Note: embed-el doesn’t seem to be included in versions below 7.0.52.

I imagine a similar approach would be needed to use Jetty 9.

Deploying Spring Boot Groovy scripts as a Jar file in Cloud Foundry

This post is a step by step guide on deploying a Spring Boot application on Cloud Foundry using the spring jar feature introduced in 1.0.0.RC2.

If you read the Cloud Foundry documentation, they would claim that the proper way to deploy Spring Boot Groovy scripts is via:

spring grab *.groovy
cf push

Unfortunately, this approach is almost as effective as Sex Panther Cologne.

It fails badly when you try to include other starter packs, such as the websocket starter pack.

Using the jar approach outlined here allows us to overcome the errors that you might encounter in Cloud Foundry otherwise. Continue reading

Extending Geb Navigators to work with Third Party Javascript Libraries

In Asgard, we use the select2 jQuery library to make combo boxes on our pages more user friendly.

This causes a problem when writing functional tests, however, since you cannot use the default drop down selection mechanisms provided by Geb.

A pretty powerful technique mentioned in Marcin Edrmann’s Advanced Geb talk is to extend the default navigators to provide your own methods to acommodate third party libraries.

In this post, I will show you how we use this to provide our own dropdown selection method.

Continue reading

Mocking out Amazon AWS SDK with the Betamax Recording Proxy for testing

One of the ways you can make your testing more efficient is to mock out external services.

If you are using Amazon Web Services in your application, you can use the Betamax proxy to record and playback responses so they are consistent across your tests.

Here is an example Spock specification on how to mock out the SDK’s http service so it plays nice with Betamax:

    @Betamax(tape = "mytape")
    void 'can use betamax to stub out amazon service'() {

        // set up an AWS client configuration that uses a proxy
        ClientConfiguration clientConfig = new ClientConfiguration()
        clientConfig.proxyHost = ''
        clientConfig.proxyPort = 5555

        // configure your AWS client, here we use the SimpleDBClient as an example
        AmazonSimpleDBClient simpleDbClient = new AmazonSimpleDBClient(
            new BasicAWSCredentials('accessKey', 'secretKey'),
        // setup the betamax proxy on the AWS SDK's httpClient

        // now, when a request is made, the test will first check on the betamax tape to see if it has been previously recorded.
        SelectResult result = SelectRequest("select * from MYRESOURCELIST limit 20", true))
        result.size() == 20