What is the best testing framework for Java code nowadays? Spock or JUnit 5? Check it out in this ultimate feature comparison.
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.
Check out how to simplify your Gradle configuration for artifact signing (and releasing) on a CI server (and along the way avoid CVE-2020-13165 in Gradle <6.5).
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.
How to not get into trouble writing custom reduction operation on (parallel) streams with Java 8+ (including Java 14).
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 :).
Have you even committed to Git using wrong email address working on/for different projects/companies? Luckily with a little configuration Git can auto-switch the identities for you.
Learn how leverage Spock 1.2 to slice a Spring context of a legacy application writing integration tests.