assertObjectHasAttribute deprecated #317
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PHPUnit deprecated assertObjectHasAttribute, arguing that any test that relies on it is of dubious value: sebastianbergmann/phpunit#4601
I tend to agree, these tests feel a little pointless to me. They're basically testing that a Response class has certain properties on it, which can never not be true unless we intentionally change the class.
@typhonius are you okay with this general approach? We use this pattern in dozens, possibly hundreds of tests. I want to be sure before I go fixing them all.
Edit: Ugh. It looks like mutation tests may indeed fail if we don't explicitly test the return types.