ddd4j-boot Testing

Overview

Covers ApplicationContextRunner, slice, matrix, HTTP, database, Redis, Broker, and Testcontainers uniformly, not split per artifact. Before use, confirm the maintenance line through ddd4j-boot-version-selection.

When to Use

• Testing a ddd4j-boot auto-configuration's conditional wiring and user-override paths with ApplicationContextRunner or slice tests.
• Building the test matrix across the 13 maintenance lines (Boot 2.3–4.1) so a fix on one line is verified on the others.
• Designing HTTP contract, database, Redis, and broker round-trip tests against real backends with Testcontainers.
• Deciding what evidence a verification claim needs: context, bean creation, real behavior, CI, and publishing kept separate.
• Recording an honest run inventory — which suites passed, which are BLOCKED because Docker is unavailable, which were SKIPPED.
• Reviewing an existing test suite for gaps: untested override paths, missing disabled-state coverage, or skipped container suites counted as passes.

When NOT to Use

Do not use this skill when: