Spock VS WireMock

I love using the Spock framework for its simplicity, readability, and maintainability. That's why we use Spock to drive our integration tests.

Well I care a lot that it exists. And many other people I know do as well. Just because you don't seem to like it, you shouldn't imagine everyone else is like you.

Maybe Grails is no longer used as much (like Rails itself), but Groovy found other usages since then, like https://spockframework.org/ and Jenkins pipelines (https://www.jenkins.io/doc/book/pipeline/syntax/). It's not going anywhere, and I see no reason for anyone to be upset about it.

In my opinion it is Spock for Java/Groovy [1]. The amount of functionality and readability you can squeeze from Groovy's DSLesque is absurd. Is basically a full fledged new test language with Java sprinkled as the test contents code

[1]: https://spockframework.org/

Groovy allows you to perform transforms on it's AST. If you look at the Spock framework, they used AST transforms to pull off a lot of the DSL.

Spock and Cucumber exemplify the philosophy of behavior-driven development (BDD). The principle behind BDD is that you must first define the desired result of the added feature in a subject-oriented language before writing any tests. The developers are then given the final documentation.

As a quick demonstration, the following (Spock) test asserts that the client JVM code fails to create an SSL connection with the service. Note that I chose to use Vert.x Web Client to handle interacting with the service, but don't let this decision distract from the core content of this post. Nevertheless, if you haven't used Vert.x, I encourage you to try it out -- especially for building server-side network applications.

This article reveals how to integrate WireMock into Fastify with ease, enabling developers to effortlessly generate mock responses for external services. Join us as we explore the straightforward process of seamlessly integrating and optimizing Fastify applications using WireMock for enhanced testing capabilities.

https://github.com/wiremock/wiremock is one such tool.

Check out https://wiremock.org/

Me and my company use WireMock a lot, it's nice tool but didn't find any nice ways to integrate with PHPUnit. What is WireMock you may ask - it's tool for mocking http requests/responses, like 3-rd apis https://wiremock.org. Wanted to use our tool which was under private repository in other projects I work in, so decided to release our own in-house WireMock integration with PHPUnit as library so it can be used by other people - https://packagist.org/packages/cobiro/wiremock, features are pretty simple:

A nightmare indeed! Try wiremock

Yes I agree, mocking is a bit of an overloaded term, and the libraries we used for stubbing like gRPC Mock and WireMock also have `mock` in their name, even though they are real servers with stubbing