The current tests are using @covers effectively to filter the code coverage report to include only executed code from the referenced code parts. This is to ensure that code is only marked as covered if there are dedicated tests for it, but not if it is used indirectly by the tests for a different class, thus avoiding false positives for code coverage. ref
However, some of the tests which include an Amadeus object, need to cover all the namespaces inside the Amadeus, otherwise, there will be some risks in the coverage report.
Thus, the current tests need to be improved and decoupled for reducing the redundant @covers annotations.
The current tests are using
@coverseffectively to filter the code coverage report to include only executed code from the referenced code parts. This is to ensure that code is only marked as covered if there are dedicated tests for it, but not if it is used indirectly by the tests for a different class, thus avoiding false positives for code coverage. refHowever, some of the tests which include an Amadeus object, need to cover all the namespaces inside the Amadeus, otherwise, there will be some risks in the coverage report.
Thus, the current tests need to be improved and decoupled for reducing the redundant
@coversannotations.