Skip to content

The Enterprise-ready testing and specification framework.

License

Notifications You must be signed in to change notification settings

AndreasTu/spock

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

License Maven Central GitHub Workflow Status (branch) Jitpack Codecov Gitter Revved up by Develocity

spock main logo

Spock Framework

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 use the Groovy Web Console.

Latest Versions

  • The latest 2.x release version is 2.4-M4 (2.4-M4-groovy-2.5, 2.4-M4-groovy-3.0, 2.4-M4-groovy-4.0), released on 2024-03-21.

  • The current development version is 2.4-SNAPSHOT (2.4-groovy-2.5-SNAPSHOT, 2.4-groovy-3.0-SNAPSHOT, , 2.4-groovy-4.0-SNAPSHOT).

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

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 repository

  2. Use org.spockframework.spock as groupId and the normal artifact-id

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

dependencies {
    testImplementation 'org.spockframework.spock:spock-core:spock-2.4-M4'
    testImplementation 'org.spockframework.spock:spock-spring:spock-2.4-M4'
}
  1. 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.

Building

Prerequisites

Spock needs both a JDK 8 and JDK 17+ installed.

  • JDK 8 is required to compile Spock via toolchains (automatic download is disabled).

  • The gradle build itself requires at least JDK 17 to run.

JDK locations must be made known to toolchains via JDK<version>=<PATH> environment variable, e.g., JDK8=/path/to/jdk8.

Supported versions

Spock is supported for Java version 8+.

Spock is supported for Groovy versions 2.5, 3.0, and 4.0.

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

The Groovy 3.0 and 4.0 variant should pass on all supported JDK versions, Groovy 2.5 does not work with Java 17+:

./gradlew build

To build a specific variant of Spock, use the variant name as a parameter

./gradlew build -Dvariant=4.0

To test against a specific Java version, use the java version name as a parameter, the path to the Java version must be set via an environment variable JDK<version>=<PATH>. Of course, this can combined with the variant selection from above.

./gradlew build -DjavaVersion=17

(Windows: gradlew 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;
}

The Spock Logo, created by Ayşe Altınsoy (@AltinsoyAyse), is managed in the spock-logo repository.

🖖 Live Long And Prosper!

The Spock Framework Team

About

The Enterprise-ready testing and specification framework.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Java 55.9%
  • Groovy 44.1%