Testing
Spock integrates with Spring Boot via the spock-spring module, which brings @SpringBootTest, @SpringBean, and @SpringSpy into Spock specs. You get the full Spring context with Spock's readable BDD syntax, mock injection via @SpringBean, and real bean overrides via @SpringSpy. This guide covers setup, common patterns, and how
Testing
Spock's built-in test output is minimal — pass/fail counts with method names. The Spock Reports plugin generates rich HTML reports that show your BDD specification blocks (given/when/then) in readable prose, making test results accessible to non-engineers. This guide covers setup, template customization, and publishing
Testing
Spock's mocking is one of its strongest features. Unlike Mockito, where you set up stubs and verify interactions using separate API calls (when(...).thenReturn(...) and verify(...)), Spock combines stubbing and interaction verification into its block syntax. The result is specifications that read like requirements rather than API calls.
Testing
Spock's interaction-based testing uses three collaborator types: Mock() for verifying interactions, Stub() for providing canned responses without verification, and Spy() for partially mocking real objects. Interactions are declared in the then: block and verified automatically — no verify() call needed. This guide covers all three with cardinality expressions
Spock
Spock is a Groovy-based testing framework that runs on the JVM and tests Java code perfectly well. Its given-when-then blocks enforce BDD structure, where: tables make parameterized tests readable, Mock/Stub/Spy have distinct semantics, @Unroll generates individual test names from data, and interaction-based testing with
Testing
Spock extensions let you hook into the test lifecycle — before specs, before features, around iterations — through a clean annotation-driven SPI. Built-in extensions like @Shared and @Stepwise solve common problems. Custom extensions give you reusable, project-specific behavior: database resets, feature flags, test timing, and more. Built-in Extensions
API Testing
Static SOAP tests — send a request, assert a response — cover the basics. But real-world testing requires dynamic behavior: generating unique values, extracting data from one response to use in the next request, conditional logic based on response content, and loops. SoapUI's Groovy scripting engine handles all of