GridDialectOperationInvocationsTest does only check the GridDialect invocations for non associations.
We need to expand it with association tests:
one to one
many to one
one to many
many to many
Here the idea to detect whether the driving engine is doing the expected number of calls and not too many conceptually. And track evolution over time.
This is orthogonal to potential tests that check how many explicit calls to the datastore the dialect is doing,
needs to test persist, merge, remote
needs to test manual ids and generated ids
Check also RedisPerformanceTest ~ line 84 when the gd daughter is removed and how many getTuple calls are made.