ddd4j-javalin Testing

Overview

Covers Javalin 6/7 HTTP, Keycloak, PostgreSQL, MQ, Testcontainers, Docker, port 0, and lifecycle uniformly. Confirm the maintenance line with ddd4j-javalin-version-selection first, then read the current branch source.

When to Use

• Building the test suite for a ddd4j-javalin service on 6.7.x, 7.1.x, or 7.2.x: HTTP contract tests via web-testkit paths, plus Keycloak, PostgreSQL, and MQ broker round-trips via Testcontainers.
• Writing lifecycle tests: startup success, partial failure with rollback, restart, and repeated starts without shutdown-hook accumulation.
• Deciding evidence honestly: Docker-unavailable, skipped containers, and zero-test runs must be reported BLOCKED/SKIPPED, never PASS.
• Verifying the same behavior across Javalin 6 and 7 maintenance lines, each on its own toolchain.
• Keeping configuration, behavior, container, CI, and publish evidence in separate tiers when reporting suite results.

When NOT to Use

Do not use this skill when: