Spock is a testing framework for Java and Groovy applications that is inspired by JUnit, RSpec, jMock, Mockito, Groovy and Scala. It uses a specification-based approach to testing that allows tests to be written in a more expressive manner than traditional unit tests. Spock tests can range from unit to end-to-end testing and leverage Groovy language features.

2. Spock:
Boldly go where no test has
gone before
Andres Almiray
Canoo Fellow
Canoo Engineering AG
@aalmiray

3. Andres Almiray
Speaker Bio
■ Java developer since the beginning
■ True believer in open source
■ Groovy committer since 2007
■ Project lead of the Griffon framework
■ Currently working for
3

4. What is Spock?
Where, Who, How?
Why?
■ http://spockframework.org
■ Expressive testing language
■ Peter Niederwiser @pniederw
■ Easy to learn
■ Usable from unit to end-to-end
■ Groovy based Testing Language
level
■ Byte code manipulation at compile ■ Leverages Groovy language
time
features
■ Inspired by JUnit, Rspec, jMock, ■ Runs with JUnit: compatible with
Mockito, Groovy, Scala and IDEs, build tools CI
Vulcans
■ Extensible for specialized testing
scenarios
4

5. First Cut
class HelloSpock extends spock.lang.Specification {
def length of Spock's and his friends' names() {
expect:
name.size() == length
where:
name | length
Spock | 5
Kirk | 4
Scotty | 6
}
}
5

6. Introducing a bug
class HelloSpock extends spock.lang.Specification {
def length of Spock's and his friends' names() {
expect:
name.size() == length
where:
name | length
Spock | 5
Kirk | 4
Scotty | 7
}
}
6

7. A wild error appears!
Condition not satisfied:
name.size() == length
| | | |
| 6 | 7
Scotty false
at com.acme.HelloSpock.length of Spock's and his
friends' names(HelloSpock.groovy:6)
7

8. Feature List (1)
Blocks
■ given:
preconditions, data fixtures, etc.
■ when:
actions that trigger some outcome
■ then:
makes assertions about outcome
■ expect:
short alternative to when then
■ where:
applies varied inputs
■ and:
sub-divides other blocks
■ setup:
alias for given
■ cleanup:
post-conditions, housekeeping, etc.
8

9. Feature List (2)
Lifecycle
Data Driven
■ setup
■ List based variables
■ cleanup
■ Table based variables
■ setupSpec
■ @Unroll
■ cleanupSpec
■ @Shared
9

10. Unrolling
class HelloSpock extends spock.lang.Specification {
@Unroll
def Length of #name should be #name.size(), actual value is
#length() {
expect:
name.size() == length
where:
name | length
Spock | 5
Kirk | 4
Scotty | 6
}
}
10

11. Unrolling as seen by an IDE
11

12. Interactions (Mocks)
class BindableSpec extends Specification {
def Model properties are observable() {
given:
def model = new Model()
def listener = Mock(PropertyChangeListener)
when:
model.addPropertyChangeListener(listener)
model.name = 'Groovy'
model.name = 'Java'
then:
1 * listener.propertyChange({it.newValue == 'Groovy'})
1 * listener.propertyChange({it.newValue == 'Java'})
}
}
12

13. But wait, there’s more!
■ http://docs.spockframework.org/en/latest/
■ Spock is extensible via plugins
■ Functional web testing with GEB
■ Plugins exist for Grails and Griffon
■ Next release will be 1.0
13

14. QA
Andres Almiray
@aalmiray