JSONAssert
Spock
Our great sponsors
JSONAssert | Spock | |
---|---|---|
2 | 11 | |
963 | 3,489 | |
0.1% | 0.3% | |
0.0 | 9.4 | |
8 months ago | 3 days ago | |
Java | Java | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
JSONAssert
-
Unit Testing Backward Compatibility of Message Format
And finally, we check that the supplied json equals to the one we got on step 3 (I use JSONAssert library here). The false boolean parameter tells to check only overlapping fields. For example, if the actual result contains the addressV2 field and the expected object doesn’t, it won’t trigger the failure. That’s a normal situation because backward compatibility data is static while the OrderCreated might grow with new parameters.
-
Stop requiring only one assertion per unit test: Multiple assertions are fine
This can be improved, it'd be worth Googling for a better solution than what you have.
https://github.com/skyscreamer/JSONassert seems decent.
but it can be done from scratch in a few hours (I'd recommend this if you have 'standardized' fields which you may want to ignore):
1) Move to a matcher library for assertions (Hamcrest is decent), and abstract `toJSON` into the a matcher, rather on the input.
This would change the assertion from:
`assertEquals(toJson(someObject), giantJsonBlobFromADifferentFile)`
to:
`assertThat(someObject, jsonEqual(giantJsonBlobFromADifferentFile))`
The difference here is subtle: it allows `jsonEqual` to control the formatting of the test failure output, so on a failure you can:
* convert both of the strings back to JSON
* perform a diff, and provide the diff in the test output.
Decent blog post on the topic: https://veskoiliev.com/use-custom-hamcrest-matchers-to-level...
Spock
-
Mastering Spring Cloud Gateway Testing: Predicates (part 1)
I love using the Spock framework for its simplicity, readability, and maintainability. That's why we use Spock to drive our integration tests.
-
Helidon Níma is the first Java microservices framework based on virtual threads
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.
-
Ask HN: What's your favorite software testing framework and why?
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/
- 7 Awesome Libraries for Java Unit & Integration Testing
- There is framework for everything.
-
Are there languages that allow to extend its syntax ?
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.
-
Using Cucumber and Spock for API test Automation — What Benefits Can You Expect?
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.
- A linguagem de programação Groovy - Radar da itexto
- Gradle 7.0 Released
-
HTTPS Client Certificate Authentication With Java
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.
What are some alternatives?
AssertJ - AssertJ is a library providing easy to use rich typed assertions
Cucumber - Cucumber for the JVM
Hamcrest - Java (and original) version of Hamcrest
REST Assured - Java DSL for easy testing of REST services
TestNG - TestNG testing framework
Awaitility - Awaitility is a small Java DSL for synchronizing asynchronous operations
Mockito - Most popular Mocking framework for unit tests written in Java
JUnit - A programmer-oriented testing framework for Java.
ArchUnit - A Java architecture test library, to specify and assert architecture rules in plain Java