Spock is a BDD-style developer testing and specification framework for Java and Groovy applications. To learn more about Spock, visit https://spockframework.org. To run a sample spec in your browser, go to https://meetspock.appspot.com/.

• The latest 2.0 release version is 2.0 (2.0-groovy-2.5, 2.0-groovy-3.0), released on 2021-05-17.
• The current development version is 2.1-SNAPSHOT (2.1-groovy-2.5-SNAPSHOT, 2.1-groovy-3.0-SNAPSHOT).

NOTE: Spock 2.0 is based on the JUnit 5 Platform and require Java 8+/groovy-2.5+ (Groovy 3.0 is recommended, especially in projects using Java 12+).

Releases are available from Maven Central. Development snapshots are available from Sonatype OSS.

For intermediate stable builds we recommend to use Jitpack (go here for instructions):

1. Add https://jitpack.io as a repository
2. Use org.spockframework.spock as groupId and the normal artifact-id

repositories {
    // ...
    maven { url 'https://jitpack.io' }
}

dependencies {
        compile 'org.spockframework.spock:spock-core:spock-2.0'
        compile 'org.spockframework.spock:spock-spring:spock-2.0'
}

3. For intermediate releases you can also use the commit-hash as version, e.g. compile com.github.spockframework.spock:spock-core:d91bf785a1

• spock-core -- Core framework. This is the only mandatory module.
• spock-specs -- Specifications for spock-core, implemented using Spock. Not required for using Spock.
• spock-spring -- Integration with the Spring TestContext Framework.
• spock-tapestry -- Integration with the Tapestry 5 IoC container.
• spock-guice -- Integration with Guice 2/3.
• spock-unitils -- Integration with Unitils.

Spock is supported for Java version 8+.

Spock is supported for Groovy versions 2.5 and 3.0.

The tests are testing Spock with the specific versions (variants) of Groovy and Java. Default Groovy version is 2.5.

The Groovy 2.5 and 3.0 variant should pass on all supported JDK versions:

./gradlew clean build

(Windows: gradlew clean build). All build dependencies, including the build tool itself, will be downloaded automatically (unless already present).

Contributions are welcome! Please see the contributing page for detailed instructions.

If you have any comments or questions, please direct them to the user forum. All feedback is appreciated!

All published jars (beginning with Spock 1.2) will contain Automatic-Module-Name manifest attribute. This allows for Spock to be used in a Java 9 Module Path.

• spock-core -- org.spockframework.core
• spock-spring -- org.spockframework.spring
• spock-tapestry -- org.spockframework.tapestry
• spock-guice -- org.spockframework.guice
• spock-unitils -- org.spockframework.unitils

So module authors can use well known module names for the spock modules, e.g. something like this:

open module foo.bar {
  requires org.spockframework.core;
  requires org.spockframework.spring;
}

• Spock Homepage -- https://spockframework.org
• Spock Web Console -- https://meetspock.appspot.com/
• GitHub Organization -- https://github.com/spockframework
• Reference Documentation -- https://docs.spockframework.org
• User Forum -- https://github.com/spockframework/spock/discussions
• Issue Tracker -- https://github.com/spockframework/spock/issues
• Spock Example Project -- https://github.com/spockframework/spock-example
• Twitter -- https://twitter.com/SpockFramework

Live Long And Prosper!

The Spock Framework Team