#[CoversNamespace] and #[UsesNamespace]

[sebastianbergmann]

Suggested by @spriebsch:

• @covers-namespace vendor\foo should cover all units of code where the fully qualified name of the unit begins with vendor\foo
• @uses-namespace vendor\foo should allow all units of code where the fully qualified name of the unit begins with vendor\foo

[sebastianbergmann]

@spriebsch Do you still think that this would be useful?

[spriebsch]

I'd say this conversation is way beyond what should be discussed in ticket comments.

[nikophil]

Hi!

I'd be interested into this feature. Would you accept a PR about it?

[sebastianbergmann]

I do not see how this can be implemented before sebastianbergmann/php-code-coverage#519 has been implemented.

[nikophil]

this issue is pretty old, is there a blocker here? or does it needs a huge effort to be fixed?

[carnage]

@spriebsch Do you still think that this would be useful?

I came here to open this issue as I think it's a useful feature.

My use case revolves around component level testing for parser type classes which, for example, read a data structure from json/yaml and parse it into a set of data objects. The test should produce coverage for all the data objects as well as the parser class itself.

[charjr]

Here's a use-case

We have many, many small classes with specific jobs.
Once we start getting into functional tests, making use of many of those classes. We start having over 60 LoC dedicated to #[UsesClass]

On top of this, half of the classes we've imported are only imported to use inside #[UsesClass] so this effectively doubles it. You have to scroll to L150 before you even see the tests.