W-23708419: Actually exclude TCK conformance on PR builds via scalatest tag

[mlischetti]

Problem

The project convention is that the DataWeave TCK conformance suite runs only on master, not on PRs (see CLAUDE.md → CI). CI enforces this two ways:

• The dedicated Run CLI TCK Conformance step is gated on github.ref == 'refs/heads/master' ✅ (correctly skipped on PRs).
• The earlier build-foundation step runs on every branch and passes -PskipTCKTests=true, which was supposed to exclude the TCK suite from the aggregate build.

But -PskipTCKTests=true used Gradle's Test.exclude('**/TCKCliTest.class'), and that filter is a no-op under the com.github.maiflai.scalatest runner — the plugin replaces Gradle's test runner and ignores its include/exclude class-pattern filters. So all 708 TCK scenarios still ran on every PR inside build-foundation (~3–4 min per OS × 3 OSes), silently defeating the master-only intent.

Fix

Use ScalaTest tag exclusion, which the maiflai runner does honor:

• Tag the TCK scenarios with a ScalaTest Tag (TckConformance).
• When -PskipTCKTests=true, exclude that tag via the plugin's tags { exclude } DSL (maps to scalatest's -l <tag> runner arg — verified against the plugin source in gradle-scalatest 0.33).

On PR builds the tagged scenarios are now filtered out while the module's other IT specs still run. The master-only Run CLI TCK Conformance step is unaffected.

Verification

./gradlew native-cli-integration-tests:test -PskipTCKTests=true locally:

• Before: 708 TCK scenarios executed.
• After: Total number of tests run: 5 (the non-TCK IT specs), TCK scenarios excluded, BUILD SUCCESSFUL.

Note

The ****** Running with weaveSuiteVersion ****** log line and TCK zip extraction still appear, because they run in the TCKCliTest class constructor when the class is instantiated. Tag exclusion filters the test bodies (the expensive native dw run invocations), not class construction — so the conformance work no longer runs, but the constructor-level logging remains. Eliminating that entirely would require gating the whole test task (a larger behavioral change that also drops the other IT specs from PR builds).

🤖 Generated with Claude Code