Add `assertObjectHasProperty()` and `assertObjectHasNotProperty()`

[jasverix]

The assertObjectHasAttribute() is deprecated because the word "attribute" means something different in the PHP world now. But it was deprecated without any replacement, stating that it is bad code causing this assertion, one should use classes etc instead.

The problem is that I am using PhpUnit to unit-test my JSON API, and I cannot see a replacement for just checking the JSON structure. Of course, assertTrue(property_exists()) works, but the error message yielded is not nearly as good as assertObjectHasAttribute was.

Can we consider making assertObjectHasProperty()? That name will never be wrong, because it is the exact same word as in property_exists().

[sebastianbergmann]

I think this can be done, but it should target main (which will become PHPUnit 10.1).

[westerp]

So the solution is to downgrade to 9.6.0 as all minor updates after that breaks since AFAIK there is no way to suppress this and it fails the tests. My library still supports 7.4 so I cannot go up and the fix isn't backported :-(

[stronk7]

Yeah, if the warnings were backported to 9.6.x (by #5160).... then the new methods should be also available there, so cases can be fixed in 9. Without the methods... the warnings are just useless noise and only solutions are:

• Or you stay with 9.6.0 (before the warnings were added).
• Or you convert to interim assertTrue(property_exists(....)) or implement them as custom method ... or some other hack.

Both far from ideal, I'd say, sigh. Ciao :-)

[raziel057]

In my mind the methods should be added from same release the deprecation have been added to provide an upgrade path. It's not always possible to update to phpunit 10 (if you are using the symfony/phpunit-bridge for example) you are stuck on phpunit 9.6.x.

@sebastianbergmann I can create a PR that targets the 9.6 branch if you are agree with that.