Can JHipster integration tests run without production database credentials?

A generated JHipster application should be able to exercise its Spring integration tests without relying on production datasource credentials. The unresolved point is which test-database behavior a particular generator release selects: an embedded database, a Testcontainers-managed service, or an explicitly configured external database.

Because the JHipster release, database choice, build tool, and blueprint are unspecified, no single default can be assumed. The test profile is typically located under src/main/resources/config, with additional test configuration under src/test/resources. Its presence alone does not establish that production secrets are inaccessible or that the datasource has been replaced.

For a specific generated project, can the effective test profile and build configuration establish which datasource integration tests use? Which generator options or test annotations control that selection, and what evidence would confirm that the tests start without production credentials?