jqwik
aws-junit5
Our great sponsors
jqwik | aws-junit5 | |
---|---|---|
7 | 1 | |
524 | 20 | |
2.9% | - | |
9.2 | 1.8 | |
1 day ago | over 1 year ago | |
Java | Java | |
Eclipse Public License 2.0 | MIT License |
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.
jqwik
- Jqwik – Property-Based Testing on the JUnit Platform
- Any library you would like to recommend to others as it helps you a lot? For me, mapstruct is one of them. Hopefully I would hear some other nice libraries I never try.
-
Built a library to help generate test pojos with relevant but random data. I’d love some feedback.
See https://jqwik.net
- I just implemented a method that checks if a binary tree is symmetric, and now I want to test it with Junit. Do I need to manually create a bunch of trees, or is there an easier way?
-
Simple example of property-based testing
Once we knew which property to use it was very straightforward to add a property-based test for it. We used the jqwik library. We like it because it has very good documentation and it is integrated with Junit.
-
must known frameworks/libs/tech, every senior java developer must know(?)
Jqwik - I love property based testing and the way it can make you think differently about some of your code.
-
Mutation testing java projects
Different to mutation testing, but on a semi-relatednpath, I've found property-based testing (e.g. https://jqwik.net/) to be valuable - thinking about the “shape“ of the expected output and getting a bunch of pseudorandom tests is pretty handy, especially for utility functions.
aws-junit5
-
No-bullshit guide on publishing your Gradle projects to Maven Central
If you got stuck here, check out this repository, a project that I’ve moved to the Maven Central Repository recently, that inspired me summarizing my experience here.
What are some alternatives?
junit-quickcheck - Property-based testing, JUnit-style
publish-plugin - Gradle plugin for publishing to Nexus repositories
Deep Dive - Fluent assertions library for Java
elementary - A suite of libraries that simplify creating and unit testing annotation processors.
JQF - JQF + Zest: Coverage-guided semantic fuzzing for Java.
zerocode - A community-developed, free, opensource, automated testing framework for microservices APIs, Kafka(Data Streams) and Load testing. Zerocode Open Source enables you to create, change and maintain your automated test scenarios via simple JSON or YAML files. Visit documentation below:
Testcontainers - Testcontainers is a Java library that supports JUnit tests, providing lightweight, throwaway instances of common databases, Selenium web browsers, or anything else that can run in a Docker container.
yamaledt - JUnit 5 Parameterized Test Yaml Test Data Source
webtau - WebTau (web test automation) is a testing API, command line tool and a framework to write unit, integration and end-to-end tests. Test across REST-API, WebSocket, GraphQL, Browser, Database, CLI and Business Logic with a consistent set of matchers and concepts. REPL mode speeds-up tests development. Rich reporting cuts down investigation time.
maven-it-extension - Experimental JUnit Jupiter Extension for writing integration tests for Maven plugins/Maven extensions/Maven Core
console-captor - 🎯 ConsoleCaptor captures console output for unit and integration testing purposes
Springy-Store-Microservices - Springy Store is a conceptual simple μServices-based project using the latest cutting-edge technologies, to demonstrate how the Store services are created to be a cloud-native and 12-factor app agnostic. Those μServices are developed based on Spring Boot & Cloud framework that implements cloud-native intuitive, design patterns, and best practices.