Daniel Wilkowski

I was following behat documentation, I followed the suggestion to use phpunit, and I encountered this error, not mentioned anywhere. Can we remove the suggestion from the documentation, and suggest...

@acoulton I used https://github.com/webmozarts/assert, and it's not really good, because it shows `Expected a value equal to array. Got: array`.

I created a simple comparison of multiple assertion libraries, feel free to edit: https://github.com/danon/behat-assertions @acoulton I understand that the exception messages should be one-liners in behat, right? 🤔 Because I...

Using phpunit assertions we can see the difference of elements: I think that looks good.

> [@danon](https://github.com/danon), thanks that's helpful, I've had a quick look and pinged you a PR to add a very quick-and-dirty github action to make it easier to see results. Thanks!...

> > That's right. I actually saw that in my comment before. Also, there remains the issue of IDE support. For example, if I use PhpStorm, then the error will...

> IMO phpunit's assertions are still the best option for usable failure output by quite a long way - I don't think the other assertion libraries available are really designed...

> > But I abstracted my assertions away behind a simple Assert.assertEquals(), that doesn't know whether I'm comparing primitives, arrays or objects. I would have to use two methods, like...

I managed to get it to work both from CLI and PhpStorm using a custom differ: ```php #[Then('the booking status of :workerName is :bookingStatus')] public function theStatusIs(string $workerName, string $bookingStatus):...

> IMO phpunit's assertions are still the best option for usable failure output by quite a long way - I don't think the other assertion libraries available are really designed...