Claude 91b9e29588 build: make ./gradlew test cover the KMP modules, and close two coverage gaps ...

The Kotlin Multiplatform plugin registers no plain `test` task - it creates one
per target (jvmTest, androidUnitTest, linuxX64Test, ...) plus `allTests`. A root
`./gradlew test` runs `test` only in projects that own one and silently skips the
rest; Gradle errors only when no project at all has the task, and the Java/Android
modules do, so it exited 0 looking healthy while never running quartz, commons,
commonsUI, quic, nestsClient or marmotQuic - about 8k of the ~11.7k tests here.

- Root build registers a `test` alias onto `jvmTest` for every KMP subproject.
  `./gradlew test` now runs 11,690 tests across 11 modules instead of 3,567
  across 5. It maps to jvmTest rather than allTests deliberately: allTests also
  pulls androidUnitTest and native targets that cannot run on a given host.
- CI (build.yml) gains :quic:jvmTest and :marmotQuic:jvmTest. Neither appeared in
  any workflow - `grep -rn quic .github/workflows/` returned nothing - so quic's
  495 RFC-vector and adversarial tests for the hand-rolled QUIC/TLS stack were
  running in no CI job at all.
- The pre-push hook gains :commonsUI:jvmTest and :marmotQuic:jvmTest, which it
  had never listed. It stays an explicit list rather than calling `./gradlew
  test`: a bare `test` would pull in :desktopApp:test, which needs a display
  server and is skipped on CLAUDE_CODE_REMOTE.
- CLAUDE.md documented `./gradlew test` as the way to run tests; it now says what
  that covers and how to name a single KMP module's suite.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Nxd2uiYajDGuymQK93txzG

2026-09-18 21:09:02 +00:00

..

pre-commit

- Fixes copyright using KDoc patterns instead of simpler comments

2026-02-09 13:06:41 -05:00

pre-push

build: make ./gradlew test cover the KMP modules, and close two coverage gaps

2026-09-18 21:09:02 +00:00