What are the use cases for methods with BooleanSupplier parameter?

[Marcono1234]

There are a few methods in Assertions and Assumptions which have a java.util.function.BooleanSupplier as parameter, e.g. Assertions.assertTrue(BooleanSupplier). They were introduced by ad2b5fe and b8d9229.

What is the use case for these methods?
Given that JUnit has to always get the boolean value from the supplier and that JUnit is apparently not enhancing any exceptions thrown by the supplier (or when the supplier is null), the only reasonable use case I can think of are classes which actually implement BooleanSupplier, though I guess that is rather rare. In all other use cases it would be easier to directly provide the boolean value.

[sbrannen]

the only reasonable use case I can think of are classes which actually implement BooleanSupplier

That is one category of use cases: types that implement BooleanSupplier.

Another category of use cases includes methods that return a BooleanSupplier.

In all other use cases it would be easier to directly provide the boolean value.

Yes, if you already have the boolean or Boolean, there is no need to wrap it in a BooleanSupplier.

[Marcono1234]

Thank you for the answer. Using a type implementing BooleanSupplier directly as argument of an assertion method might reduce readability in some cases (especially when the name of the type does not indicate that it can supply boolean values), but I guess there are also cases then where it might be useful to have such assertion methods.