ArchUnit VS Spock

More examples you can find at official user guide https://www.archunit.org/userguide/html/000_Index.html or at github repository https://github.com/TNG/ArchUnit

I feel like the types of people that use ArchUnit are the types of people that misuse it anyway. Even the elevator pitch example in the project repository is of the backwards horizontal layering that leads any change to carpet bomb a project.

I looked around but couldn't find anything that was very popular. Are there any packages similar to ArchUnit (See: https://github.com/TNG/ArchUnit)?

JUnit 4

ArchUnit 0.15.0 released (2 min read) 🎉 https://github.com/TNG/ArchUnit/releases/tag/v0.15.0

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.