Replies: 1 comment 1 reply
-
|
Can I ask you to provide an example/commit e2e test/repo where it works woth annotation but doesn't work with an attribute? Personally I didn't use it so don't know if there is a bug |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
I'm not sure I found the time, didn't expect to be the first one :p Found more evidence this won't come to phpunit, I found a PR which was rejected with the same argument of that granularity not being useful -> sebastianbergmann/phpunit#5360 |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I've a project I'm looking at to switch from phpunit
@coversannotations to their new attributes, specifically\PHPUnit\Framework\Attributes\CoversClass.However the attribute syntax does not support
ClassUnderTest::method, whilst@coversdid. I use this a lot to "contain" the mutation impact area.After the switch I get a lot more escaped mutants and I think it's due to this change now.
Does infection support
CoversClass? If yes, is there a solution? Would I need to useCoversClassand@coversto still support the::methodsyntax.Currently I'm not sure if it's my fault or not, I'm still figuring out things.
thx
Beta Was this translation helpful? Give feedback.
All reactions