Interface and Description |
---|
org.assertj.core.api.iterable.Extractor
use
Function instead |
Class and Description |
---|
org.assertj.core.api.Java6Assertions
For Android compatible assertions use the latest assertj 2.x version which is based on Java 7 only.
Assertions compatible with Android. Duplicated from |
org.assertj.core.api.Java6BDDAssertions
For Android compatible assertions use the latest assertj 2.x version which is based on Java 7 only.
Android-compatible BDD-style assertions duplicated from |
org.assertj.core.api.Java6BDDSoftAssertions
For Android compatible assertions use the latest assertj 2.x version which is based on Java 7 only.
BDD-style Android-compatible soft assertions. Duplicated from |
org.assertj.core.api.Java6JUnitBDDSoftAssertions
For Android compatible assertions use the latest assertj 2.x version which is based on Java 7 only.
Duplicate of |
org.assertj.core.api.Java6JUnitSoftAssertions
For Android compatible assertions use the latest assertj 2.x version which is based on Java 7 only.
JUnitSoftAssertions rule compatible with Android. Duplicated from |
org.assertj.core.api.Java6SoftAssertions
For Android compatible assertions use the latest assertj 2.x version which is based on Java 7 only.
Soft assertions compatible with Android. Duplicated from |
org.assertj.core.api.JUnitJupiterBDDSoftAssertions
use
SoftAssertionsExtension instead.
Same as SoftAssertions , but with the following differences: First, it's a JUnit Jupiter extension, which can be used without having to call assertAll() , example:
Second, the failures are recognized by IDE's (like IntelliJ IDEA) which open a comparison window. |
org.assertj.core.api.JUnitJupiterSoftAssertions
use
SoftAssertionsExtension instead.
Same as SoftAssertions , but with the following differences: First, it's a JUnit Jupiter extension, which can be used without having to call assertAll() , example:
Second, the failures are recognized by IDE's (like IntelliJ IDEA) which open a comparison window. |
Method and Description |
---|
org.assertj.core.api.Assert.equals(Object)
Throws
if called. It is easy to accidentally call
equals(Object) instead of . |
org.assertj.core.api.AbstractAssert.equals(Object)
use
AbstractAssert.isEqualTo(java.lang.Object) instead |
org.assertj.core.util.Maps.format(Map<?, ?>)
use
StandardRepresentation.toStringOf(Map) instead. |
org.assertj.core.util.Maps.format(Representation, Map<?, ?>)
use
StandardRepresentation.toStringOf(Map) instead. |
org.assertj.core.api.AbstractFileAssert.hasContentEqualTo(File)
use
AbstractFileAssert.hasSameContentAs(File) instead |
org.assertj.core.api.AbstractInputStreamAssert.hasContentEqualTo(InputStream) |
org.assertj.core.api.AbstractClassAssert.hasFields(String...)
use
AbstractClassAssert.hasPublicFields(String...) instead. |
org.assertj.core.api.AbstractDateAssert.isAfterOrEqualsTo(Date)
prefer calling
AbstractDateAssert.isAfterOrEqualTo(Date) |
org.assertj.core.api.AbstractDateAssert.isAfterOrEqualsTo(String)
prefer calling
AbstractDateAssert.isAfterOrEqualTo(String) |
org.assertj.core.api.AbstractDateAssert.isBeforeOrEqualsTo(Date)
prefer calling
AbstractDateAssert.isBeforeOrEqualTo(Date) |
org.assertj.core.api.AbstractDateAssert.isBeforeOrEqualsTo(String)
prefer calling
AbstractDateAssert.isBeforeOrEqualTo(String) |
org.assertj.core.api.AbstractObjectAssert.isEqualToComparingFieldByFieldRecursively(Object)
Prefer calling
AbstractObjectAssert.usingRecursiveComparison() for comparing objects field by field as it offers more flexibility, better reporting and an easier to use API.
Asserts that the object under test (actual) is equal to the given object based on a recursive property/field by property/field comparison (including
inherited ones). This can be useful if actual's equals implementation does not suit you.
The recursive property/field comparison is not applied on fields having a custom equals implementation, i.e.
the overridden equals method will be used instead of a field by field comparison.
The recursive comparison handles cycles. By default
You can specify a custom comparator per (nested) fields or type with respectively The objects to compare can be of different types but must have the same properties/fields. For example if actual object has a name String field, it is expected the other object to also have one. If an object has a field and a property with the same name, the property value will be used over the field. Example:
|
org.assertj.core.api.AbstractCharSequenceAssert.isJavaBlank()
Use
AbstractCharSequenceAssert.isBlank() instead. |
org.assertj.core.api.AbstractCharSequenceAssert.isNotJavaBlank()
Use
AbstractCharSequenceAssert.isNotBlank() instead. |
org.assertj.core.api.AbstractDateAssert.isWithinDayOfMonth(int)
use
AbstractDateAssert.hasDayOfMonth(int) instead. |
org.assertj.core.api.AbstractDateAssert.isWithinDayOfWeek(int)
use
AbstractDateAssert.hasDayOfWeek(int) instead. |
org.assertj.core.api.AbstractDateAssert.isWithinHourOfDay(int)
use
AbstractDateAssert.hasHourOfDay(int) instead. |
org.assertj.core.api.AbstractDateAssert.isWithinMillisecond(int)
use
AbstractDateAssert.hasMillisecond(int) instead. |
org.assertj.core.api.AbstractDateAssert.isWithinMinute(int)
use
AbstractDateAssert.hasMinute(int) instead. |
org.assertj.core.api.AbstractDateAssert.isWithinMonth(int)
use
AbstractDateAssert.hasMonth(int) instead. |
org.assertj.core.api.AbstractDateAssert.isWithinSecond(int)
use
AbstractDateAssert.hasSecond(int) instead. |
org.assertj.core.api.AbstractDateAssert.isWithinYear(int)
use
AbstractDateAssert.hasYear(int) instead. |
org.assertj.core.api.AtomicBooleanAssert.usingComparator(Comparator<? super AtomicBoolean>)
Custom Comparator is not supported for Boolean comparison.
|
org.assertj.core.api.AtomicBooleanAssert.usingComparator(Comparator<? super AtomicBoolean>, String)
Custom Comparator is not supported for Boolean comparison.
|
org.assertj.core.api.AbstractBooleanAssert.usingComparator(Comparator<? super Boolean>)
Custom Comparator is not supported for Boolean comparison.
|
org.assertj.core.api.AbstractBooleanAssert.usingComparator(Comparator<? super Boolean>, String)
Custom Comparator is not supported for Boolean comparison.
|
org.assertj.core.api.AbstractMapAssert.usingDefaultElementComparator()
Custom element Comparator is not supported for MapEntry comparison.
|
org.assertj.core.api.AbstractCharSequenceAssert.usingDefaultElementComparator()
Custom element Comparator is not supported for CharSequence comparison.
|
org.assertj.core.api.AbstractBooleanArrayAssert.usingDefaultElementComparator()
Custom element Comparator is not supported for Boolean array comparison.
|
org.assertj.core.api.AbstractBooleanArrayAssert.usingElementComparator(Comparator<? super Boolean>)
Custom element Comparator is not supported for Boolean array comparison.
|
org.assertj.core.api.AbstractCharSequenceAssert.usingElementComparator(Comparator<? super Character>)
Custom element Comparator is not supported for CharSequence comparison.
|
org.assertj.core.api.AbstractMapAssert.usingElementComparator(Comparator<? super Map.Entry<? extends K, ? extends V>>)
Custom element Comparator is not supported for MapEntry comparison.
|