Get even more compact reporting for parameterized tests with Spock 2.1.

Stuck with the 'The Spock compiler plugin cannot execute because Spock 1.3-groovy-2.5 (3.0) is not compatible with Groovy 3.0 (4.0)' error message? Find out what can be done about that (using Gradle and Maven).

Spock 2.0(-M3) reduced number of provided Groovy dependencies. If you started to get various Groovy-related 'ClassNotFoundException's after migration and wonder why and what to do, read on.

What is the best testing framework for Java code nowadays? Spock or JUnit 5? Check it out in this ultimate feature comparison.

Make sure you know all the places where putting the 'assert' keyword in Spock is necessary to avoid false sense of security and tests which - effectively - do nothing.

Discover dead simple, improved PIT and JUnit 5 configuration in Gradle (with gradle-pitest-plugin 1.4.7+).

Get know what you can expect from Spock 2.0 M2 (based on JUnit 5), how to migrate to it in Gradle and Maven, and why it is important to report spotted problems :).

Learn how leverage Spock 1.2 to slice a Spring context of a legacy application writing integration tests.

Discover how to automatically inject Spock's mocks and spies into the Spring context using Spock 1.2.

Learn about new, built-in, official support in Mockito for managing a mocking life cycle if JUnit 5 is used.