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