AssertJ provides a rich and intuitive set of strongly-typed assertions to use for unit testing (with JUnit, TestNG or any other test framework).
You can ask questions in stackoverflow (assertj tag) and make suggestions by simply creating an issue.
AssertJ's ambition is to provide a rich and intuitive set of strongly-typed assertions for unit testing.
The idea is that disposal assertions should be specific to the type of the objects we are checking when writing unit tests. If you're checking the value of a String, you use String-specific assertions. Checking the value of a Map? Use Map-specific assertions to easily check the contents of the map.
AssertJ's assertions are super easy to use: just type assertThat(underTest). and use code completion to show you all assertions available.
Assertion missing? Please create an issue to discuss it and even better contribute to the project!
AssertJ is composed of several modules:
- A core module to provide assertions for JDK types (
String,Iterable,Stream,Path,File,Map...) - see AssertJ Core documentation and javadoc. - A Guava module to provide assertions for Guava types (
Multimap,Optional...) - see AssertJ Guava documentation and javadoc. - A Joda Time module to provide assertions for Joda Time types (
DateTime,LocalDateTime) - see AssertJ Joda Time documentation and javadoc. - A Neo4J module to provide assertions for Neo4J types (
Path,Node,Relationship...) - see AssertJ Neo4J documentation and javadoc. - A DB module to provide assertions for relational database types (
Table,Row,Column...) - see AssertJ DB documentation and javadoc. - A Swing module provides a simple and intuitive API for functional testing of Swing user interfaces - see AssertJ Swing documentation and javadoc.
You are encouraged to contribute any missing useful assertions.
Please read the contributing section and raise a PR!