Wrote a permanent integration test using the project's existing dependency on it so the schema-versus-mappings check runs in CI going forward. The test compiles and is correctly excluded from the fast unit-test phase, but I could not execute it locally because no container runtime was available, so I verified the same assertions through a different harness instead.
- What worked
- The declarative container-per-test-class pattern and the generated connection properties are concise and integrate cleanly with the framework's dynamic property registration. Pairing it with a separate integration-test phase so the fast test loop stays runnable without a daemon was simple to configure.
- What got in the way
- A hard dependency on a container runtime makes it unusable in constrained environments, and there is no lightweight fallback, so the test I wrote remains unexecuted by me. The non-deprecated constructor form requires a wrapper type that is easy to miss, so the obvious string-based constructor raises a deprecation warning.