Prefer to construct Fact-style methods, typically by using failWithActual(simpleFact(...)). However, if you want to preserve your exact failure message as a
migration aid, you can inline this method (and then inline the resulting method call, as
well).
Prefer to construct Fact-style methods, typically by using Subject.failWithActual(Fact, Fact...). However, if you want to preserve your exact failure
message as a migration aid, you can inline this method.
Prefer to construct Fact-style methods, typically by using Subject.failWithActual(String, Object). However, if you want to preserve your exact failure
message as a migration aid, you can inline this method (and then inline the resulting
method call, as well).
Prefer to construct Fact-style methods, typically by using Subject.failWithActual(Fact, Fact...). However, if you want to preserve your exact failure
message as a migration aid, you can inline this method.
Prefer to construct Fact-style methods, typically by using Subject.failWithoutActual(Fact, Fact...). However, if you want to preserve your exact failure
message as a migration aid, you can inline this method.
Prefer to construct Fact-style methods, typically by using failWithoutActual(simpleFact(...)). However, if you want to preserve your exact failure message as a
migration aid, you can inline this method (and then inline the resulting method call, as
well).
Prefer to construct Fact-style methods, typically by using failWithoutActual(simpleFact(...)). However, if you want to preserve your exact failure message as a
migration aid, you can inline this method.
Use hasMessageThat().isEqualTo(expected) instead. You may also consider
using inexact matching of the message (e.g. hasMessageThat().contains(substring))
for less brittle tests.
AtomicLongMap does not define equality (i.e., it does not implement
equals()), so you probably don't want to call this method. Instead, perform your assertion
on the map view (e.g., assertThat(atomicLongMap.asMap()).isEqualTo(EXPECTED_MAP)).
AtomicLongMap does not define equality (i.e., it does not implement
equals()), so you probably don't want to call this method. Instead, perform your assertion
on the map view (e.g., assertThat(atomicLongMap.asMap()).isNotEqualTo(UNEXPECTED_MAP)).