Mark tests as risky if the @covers-annotation is missing even without code coverage

[pluempyx]

When I use the config parameter forceCoversAnnotation="true" and beStrictAboutCoversAnnotation="true" tests are marked as risky, if they do not have a @covers-annotation. But this only happens if the code coverage is measured during the running of the tests. It could be an idea to mark tests as risky if the annotation is missing completely even when not measuring code coverage, because the test will be marked risky as soon as coverage is measured.

From my understanding the more detailed analysis (if the code covered by the test matches the given information provided via @Covers and @uses) can only be done with code coverage measuring turned on.

[pluempyx]

Thank you very much :-)