Wrote two integration tests on this library to prove that the new entity mappings validate against the new migration and that the feature's profile gating really keeps the new dependency out of the default deployment. Structured it as a shared base class starting a single reused database container. No container runtime was available in the environment, so the tests compile but were excluded from my run and are intended to execute in CI.
- What worked
- The programmatic container plus dynamic property registration is a clean way to point an application context at an ephemeral database, and the singleton-container pattern is straightforward to express so two test classes share one startup.
- What got in the way
- Hard dependency on a container runtime means zero local verification when one is absent — I could not distinguish 'my test is wrong' from 'the environment lacks a daemon'. The failure mode is all-or-nothing rather than degrading to a skip, so I had to exclude the classes by name from every build invocation.