Stefano Cordio
Stefano Cordio
If I understand correctly, AssertJ breaks Spock interoperability as soon as the `then` block has string assertions like in the second example but it works correctly in the first example,...
I also have the feeling preventing specific method names in AssertJ shouldn't be the way to go but I'm happy to elaborate on it better. @nweiser94 would you mind raising...
> I actually think that this is not just a Spock specific issue, but a more general conflict with the Groovy language as assertj now hides Groovy built-ins. I'm reading...
According to https://github.com/spockframework/spock/issues/1897#issuecomment-1971450856, this isn't something to be solved in AssertJ, so I'm closing the issue but happy to reconsider in case of new arguments.
> AssertJ does not play well here with the Groovy semantic @AndreasTu is the Groovy semantic and the `asBoolean` as a reserved name documented somewhere? The [power assertions](https://groovy-lang.org/testing.html#_power_assertions) section doesn't...
@AndreasTu looking at the plain Groovy example, what is the purpose of prefixing the `assertThat` call with `assert`? We have [some basic Groovy integration tests](https://github.com/assertj/assertj/tree/main/assertj-tests/assertj-integration-tests/assertj-core-groovy/src/test/groovy/org/assertj/core/tests/groovy) and none of them uses...
> The only additional thing I could see, is to open a ticket at Groovy and ask them I was halfway through it when I realized that it's the usage...
No, that's ok @quaff, and thanks a lot for the proposal! Your intention is clear. I would like to double-check the user experience in case of errors, i.e., when the...
I believe the reported binary incompatibility issue is a false positive – raised siom79/japicmp#384.
@snicoll aside from enhancing test coverage, I don't expect major changes to the productive code. Could you check if this is what you expect? About: > - Evaluate the addition...