Describe the enhancement requested
AssertJ gives us readable, fluent assertions that make tests easier to write and failures easier to analyze. With JUnit's assertEquals(expected, actual) it's easy to mix up argument order, and you end up with confusing failure messages. AssertJ's assertThat(actual).isEqualTo(expected) reads naturally and always gets the order right. Additionally, it provides a lot of flexibility when asserting things.
Compound checks that need multiple JUnit assertions collapse into a single chain:
// JUnit
assertNotNull(list);
assertEquals(3, list.size());
assertTrue(list.contains("foo"));
// AssertJ
assertThat(list).hasSize(3).contains("foo");
When something fails, AssertJ tells you exactly what went wrong and makes debugging much easier, because the failure message usually contains enough details to understand the issue. For example, an assertion on a list would fail with expected list to contain 'foo' but was ['bar', 'baz']. JUnit assertions on the other hand would only contain expected true but was false.
It also covers cases where JUnit assertions are just clunky: exception messages, collection contents, map entries, string patterns, comparisons with custom comparators. All without needing Hamcrest matchers or custom helper methods.
I'm planning to add it as a project-wide test dependency so new tests can use it immediately. Existing tests don't need to be migrated, and we can move them over incrementally where it makes sense.
Component(s)
No response
Describe the enhancement requested
AssertJ gives us readable, fluent assertions that make tests easier to write and failures easier to analyze. With JUnit's
assertEquals(expected, actual)it's easy to mix up argument order, and you end up with confusing failure messages. AssertJ'sassertThat(actual).isEqualTo(expected)reads naturally and always gets the order right. Additionally, it provides a lot of flexibility when asserting things.Compound checks that need multiple JUnit assertions collapse into a single chain:
When something fails, AssertJ tells you exactly what went wrong and makes debugging much easier, because the failure message usually contains enough details to understand the issue. For example, an assertion on a list would fail with
expected list to contain 'foo' but was ['bar', 'baz']. JUnit assertions on the other hand would only containexpected true but was false.It also covers cases where JUnit assertions are just clunky: exception messages, collection contents, map entries, string patterns, comparisons with custom comparators. All without needing Hamcrest matchers or custom helper methods.
I'm planning to add it as a project-wide test dependency so new tests can use it immediately. Existing tests don't need to be migrated, and we can move them over incrementally where it makes sense.
Component(s)
No response