borinquenkid opened a new pull request, #15781: URL: https://github.com/apache/grails-core/pull/15781
## Summary Full test suite for the GormRegistry implementation in #15780. Separated into its own PR so reviewers can evaluate design and coverage independently. **Unit tests — `grails-datamapping-core`:** - `GormRegistrySpec` — lifecycle, registration, removal, factory fallback - `GormRegistryConcurrencySpec` — concurrent registration and lookup under load - `GormRegistryEntityRegistrationSpec` — entity → datastore → API wiring - `GormApiResolverSpec` — qualifier routing, fallback, multi-tenant mode dispatch - `GormApiFactorySpec` / `DefaultGormApiFactorySpec` — factory delegation - `GormStaticApiSpec` / `GormInstanceApiSpec` — API execution and qualifier propagation - `GormEnhancerAllQualifiersSpec` — all qualifier expansion scenarios - `CurrentTenantHolderSpec` / `TenantsSpec` — thread-safe tenant binding - `TenantContextProfilingSpec` — DISCRIMINATOR vs DATABASE/SCHEMA mode routing - `MultiTenantEventListenerSpec` — tenant lifecycle events - `TransactionalTransformSpec` / `ServiceTransformSpec` — AST transform correctness - `DefaultTransactionTemplateFactorySpec` — transaction template pluggability - Registry subtype specs: `GormStaticApiRegistrySpec`, `GormInstanceApiRegistrySpec`, `GormValidationApiRegistrySpec` **TCK expansion — `grails-datamapping-tck`:** - Multi-datasource connection routing - Multi-tenant discriminator, schema-per-tenant, and DATABASE-per-tenant scenarios - `ALL` qualifier expansion - `DataTestSetupInterceptor` registry lifecycle in Spock tests ## Test plan - [ ] `./gradlew :grails-datamapping-core:test` passes - [ ] `./gradlew :grails-datamapping-tck:test` passes ## Stack - Prereq: #15779 (`feat/gorm-datastore-infra`) - Prereq: #15780 (`feat/gorm-registry-core-impl`) - **This PR** — tests for #15780 - Next: per-adapter wiring PRs (H5, MongoDB, Neo4j, Simple, misc, H7) 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
