Document another advantage of `ExpectFailure`.
Specifically, it ensures that you use the failure strategy that the user configured by calling `fail*()` or `check(...`), rather than delegating internally to `assertThat(...)`.
RELNOTES=n/a
@@ -60,8 +60,8 @@ import org.junit.runners.model.Statement;
* <p>{@code ExpectFailure} is similar to JUnit 5's <a
* href="http://junit.org/junit5/docs/current/api/org/junit/jupiter/api/Assertions.html#assertThrows-java.lang.Class-org.junit.jupiter.api.function.Executable-">{@code
* assertThrows}</a>. We recommend it over {@code assertThrows} when you're testing a Truth subject
- * because it also checks that the assertion you're testing correctly calls {@link
- * FailureStrategy#fail} only once.
+ * because it also checks that the assertion you're testing uses the supplied {@link
+ * FailureStrategy} and calls {@link FailureStrategy#fail} only once.
*/
public final class ExpectFailure implements Platform.JUnitTestRule {
private final FailureStrategy strategy =
