Skip to content
The Enterprise-ready testing and specification framework.
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
.idea changes to idea files Dec 25, 2013
buildSrc add buildSrc to allow use of spock-gradle from spock build Feb 5, 2013
config Sign and publish artifacts from Shippable Feb 28, 2015
docs Release Spock 1.3 Mar 4, 2019
gradle Release Spock 1.3 Mar 4, 2019
internal-backport Add NamedParam support for gradle-2.5 with backport to 2.4 (#921) Oct 7, 2018
spock-bom Don't publish jar signature artifacts for spock-bom (#953) Nov 29, 2018
spock-core Add implicit assertions for CodeArgument constraints (#956) Jan 22, 2019
spock-gradle Start iteration for 1.1-SNAPSHOT Mar 2, 2015
spock-guice Use maven-publish plugin for publishing (#950) Nov 18, 2018
spock-report Add :spock-specs:mock-integration subproject (#902) Sep 11, 2018
spock-specs Add implicit assertions for CodeArgument constraints (#956) Jan 22, 2019
spock-spring Add support for JDK 11 (#900) Nov 18, 2018
spock-tapestry Fix #974 Feb 26, 2019
spock-unitils Use maven-publish plugin for publishing (#950) Nov 18, 2018
.gitignore Improve build configuration for shippable CI Sep 14, 2014
.travis.yml Add support for JDK 11 (#900) Nov 18, 2018 Add CodeTriage badge to spockframework/spock (#826) Jun 30, 2018
NOTICE Update, Disable publish until 2.0 is on master Mar 4, 2019
build.gradle Update, Disable publish until 2.0 is on master Mar 4, 2019 Enable parallel by default for local env but keep disabled on ci Jun 28, 2018
gradlew Update to gradle 4.0.2 (use -bin distro again) Aug 4, 2017
gradlew.bat Update to Gradle 3.5 May 18, 2017
settings.gradle Use maven-publish plugin for publishing (#950) Nov 18, 2018

License Maven Central Linux Build Status Windows Build Status CircleCI branch Jitpack Codecov Gitter

Spock Framework

Spock is a developer testing and specification framework for Java and Groovy applications. To learn more about Spock, visit To run a sample spec in your browser, go to

Latest Versions

The latest release version is 1.3 (1.3-RC1-groovy-2.4, 1.3-RC1-groovy-2.5), released on 2019-01-22. The current development version is 2.0-SNAPSHOT (2.0-groovy-2.5-SNAPSHOT).

NOTE: Spock 1.3 is the last planned release for 1.x based on JUnit 4. Spock 2.0 will be based on the JUnit 5 Platform and require Java 8/groovy-2.5

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

Ad-Hoc Intermediate Releases

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

  1. Add as a respository
  2. Use org.spockframework.spock as groupId and the normal artifact-id
repositories {
    // ...
    maven { url '' }

dependencies {
        compile 'org.spockframework.spock:spock-core:spock-1.3'
        compile 'org.spockframework.spock:spock-spring:spock-1.3'
  1. 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-report -- Interactive, business-friendly HTML reports.


Supported versions

Spock is supported for Java version 7, and 8 (with Groovy 2.5 Java 9+ are supported as well).

Spock is supported for Groovy version 2.4+

The tests are testing spock with a specific versions (variants) of groovy. Default is groovy version 2.4

The groovy 2.4 and 2.5 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!

Java 9 Module Names

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 {
  requires org.spockframework.core;
  requires org.spockframework.spring;


Live Long And Prosper!

The Spock Framework Team

You can’t perform that action at this time.