Let's take a look at one last feature to help document the requirements via tests.

We've seen that Spock has a focus on readability and tests as documentation. The @Subject annotation, the labelled blocks, Strings as test method names plus all you can do to customise these String values all contribute to being able to use the automated tests as a documentation for what the system should do.

We can also add more information, again for readability or documentation purposes, to the blocks in our tests.

def "should be able to create a stub"() {
    given: "a palette with red as the primary colour"
    Palette palette = Stub()
    palette.getPrimaryColour() >> Colour.Red

    and: "a renderer initialised with the red palette"
    def renderer = new Renderer(palette)

    expect: "the renderer to use the palette's primary colour as foreground"
    renderer.getForegroundColour() == Colour.Red
}

We can add a String next to the label to give a more detailed description of the block. If we want to split a block into further blocks, for readability or to add documentation, we can use the and: label, this is just to let us break things up further.

The text is available to the Spock runtime, so these messages can be used in messages and reports.

Spock tests, with the help of the Groovy language, can be very descriptive. These automated tests also tell us, the developer, what we should expect to see from our application.

Finally, let's summarise what we've seen, and the shortcuts we've used.