jack-kerouac / spock

The Enterprise-ready testing and specification framework.

Spock Framework

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

Latest Versions

The latest release version is 1.1 (1.1-groovy-2.0, 1.1-groovy-2.3, 1.1-groovy-2.4), released on 2017-05-05. The current development version is 1.2-SNAPSHOT (1.2-groovy-2.4-SNAPSHOT).

NOTE: Spock 1.2 drops support for Java 6, Groovy 2.0 and Groovy 2.3.

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 https://jitpack.io as a respository
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-1.1'
        compile 'org.spockframework.spock:spock-spring:spock-1.1'
}

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

Modules

• 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.

Building

Supported versions

Spock is supported for Java version 7, and 8.

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 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).

Contributing

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

Support

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

Links

• Spock Homepage -- http://spockframework.org
• Spock Web Console -- http://webconsole.spockframework.org
• GitHub Organization -- http://github.spockframework.org
• Reference Documentation -- http://docs.spockframework.org
• Old Wiki -- http://wiki.spockframework.org
• Javadoc -- http://javadoc.spockframework.org
• User Forum -- http://forum.spockframework.org
• Developer Forum -- http://dev-forum.spockframework.org
• Issue Tracker -- http://issues.spockframework.org
• Build Server -- http://builds.spockframework.org
• Spock Example Project -- http://github.spockframework.org/spock-example
• Twitter -- http://twitter.spockframework.org

Live Long And Prosper!

The Spock Framework Team