You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: stop tagging "test exception" testcases as synthetic skip
"test exception" is not a synthetic placeholder emitted by any test
framework — JUnit 4, JUnit Platform, Gradle's adapters, Spock and Kotest
all reserve "initializationError"/"executionError" for that purpose, not
generic English names. In dd-trace-java the entries observed in CI came
from a real Spock feature method (`def "test exception"()` in
HttpServerTest.groovy), not a framework synthetic. Tagging that name
unconditionally silently masks real pass/fail outcomes for any
Spock/JUnit 5 @DisplayName/Kotest test that happens to use it.
Drop "test exception" from JUnitReport.tagSyntheticFailures and document
the criteria for future synthetic entries (must be framework-emitted,
must link to the source pinned to a release tag). Annotate the two
remaining entries — initializationError (JUnit 4 + Gradle) and
executionError (Gradle) — with the canonical source locations.
0 commit comments