- 🇺🇸United States mile23 Seattle, WA
Given #23 let's call this issue postponed on ✨ Allow run-tests.sh to generate coverage reports Needs work . We currently don't do a coverage report for core for the project CI, AFAICT.
Follow up to #2105583: Add some sane strictness to phpunit tests to catch risky tests →
Checking for unintentionally covered code is useful for identifying weakness in coverage reports and making them more useful. However, checkForUnintentionallyCoveredCode's current behavior causes some problems because it doesn't recursively check parent classes for @uses information. This means any code run in our UnitTestCase::setUp() method will always be "unintentionally covered."
Obviously we don't want to work around this by adding the @uses to _every_ unit test we implement so we either need to
1) Remove that code from the setUp
2) Allow usage of phpunit's testcase and convert most tests to use it. add @uses to tests that do user Drupal's UnitTestCase.
3) Work upstream to support recursive @uses resolution.
I don't think 1 or 2 are likely so we'll probably need to work with phpunit to get this feature added.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Given #23 let's call this issue postponed on ✨ Allow run-tests.sh to generate coverage reports Needs work . We currently don't do a coverage report for core for the project CI, AFAICT.