Over a million developers have joined DZone.

Spocklight: Ignoring Other Feature Methods Using @IgnoreRest [Snippet]

DZone's Guide to

Spocklight: Ignoring Other Feature Methods Using @IgnoreRest [Snippet]

Unit tests are like your love life. Sometimes you want to ignore the chosen one, sometimes you want to ignore everything else. @IgnoreRest does the latter.

· DevOps Zone ·
Free Resource

Open source vulnerabilities are on the rise. Read here how to tackle them effectively.

 To ignore feature methods in our Spock specification, we can use the annotation @Ignore. Any feature method or specification with this annotation is not invoked when we run a specification. With the annotation @IgnoreRest we indicate that feature methods that do not have this annotation must be ignored. So, any method with the annotation is invoked, but the ones without aren't. This annotation can only be applied to methods and not to a specification class.

In the next example, we have a specification with two feature methods that will be executed, and one that is ignored:

import spock.lang.Specification
import spock.lang.IgnoreRest
import spock.lang.Subject

class SampleSpec extends Specification {

    private final underTest = new Sample()

    void 'run this spec'() {
        underTest.message('Asciidoctor') == 'Asciidoctor is awesome.'

    void 'run this spec also'() {
        underTest.message('Groovy') == 'Groovy is awesome.'

    void 'ignore this spec'() {
        underTest.message('Word') == 'Word is awesome'


class Sample {
    String message(String tool) {
        println "Getting message for $tool"
        "$tool is awesome."

We can run this specification directly from the command line:

$ groovy SampleSpec.groovy
Getting message for Asciidoctor
Getting message for Groovy
JUnit 4 Runner, Tests: 2, Failures: 0, Time: 54

Written with Spock 1.0 and Groovy 2.4.10.

Learn about the ins and outs of open source security and management.

spock ,groovy ,tutorial ,testing ,unit tests

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

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

{{ parent.tldr }}

{{ parent.urlSource.name }}