Stefano Cordio
Stefano Cordio
@itkhanz I'm not entirely sure the feature you're proposing has a strong connection with soft assertions. What if we provided a new entry point in `Assertions`, like `assertAny(Runnable...)` or `assertAnyOf(Runnable...)`,...
@alihmzyv sure, this is up for grabs. @joel-costigliola any preference between `assertAny(Runnable...)` and `assertAnyOf(Runnable...)`? In case we go with `assertAny`, I'd keep `satisfiesAnyOf` aligned, i.e., dropping the `Of` suffix
> Also it would be good if we decide on whether we should define something like JUnit [Executable](https://junit.org/junit5/docs/5.12.0/api/org.junit.jupiter.api/org/junit/jupiter/api/function/Executable.html) and use that instead of Runnable Thanks for the reminder, yes, I...
You can ignore that because it's checking breaking changes against the last release, which is the previous major version and we already introduced breaking changes on `main`.
Feel free to ping me next time a mac issue arises 🙂
We started getting flaky tests on 303704ef. The most recent change that could be related is at bcb4e142, but I don't see any reason why things got worse with it.
Sure and thanks, @danaebu!
Impressive analysis, well done @danaebu and @martinfrancois!
As briefly discussed, it might be interesting to see how other projects like [EqualsVerifier](https://github.com/jqno/equalsverifier/) handle the data baseline.
> Clone https://github.com/assertj/assertj locally As I reverted the upgrade to JUnit 6, please use assertj/assertj@f90a09a25ba23ee077dbd1719acd643c7fea4da0 to verify the issue.