Arguments to a fluent Truth assertion appear to be reversed based on the argument names.
int expected = 1; assertThat(expected).isEqualTo(codeUnderTest());
This is problematic as the quality of Truth’s error message depends on the
argument order. If
2, this code will output:
expected: 2 but was : 1
Which will likely make debugging the problem harder. Truth assertions should follow the opposite order to JUnit assertions. Compare:
assertThat(actual).isEqualTo(expected); assertEquals(expected, actual);
See https://truth.dev/faq#order for more details.
Suppress false positives by adding the suppression annotation
@SuppressWarnings("TruthAssertExpected") to the enclosing element.