Use tracing for testing ConnectorMetadata invocations #18587
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This refactors
TestInformationSchemaConnector.testMetadataCalls
toleverage
TracingConnectorMetadata
instead of manually performed countswithin
CountingMockConnector. Among other things this exposes
listViews` calls which were previously not counted.The differences in expected counts in the test come from the fact how
the counting was done previously. For example
MockConnectorMetadata.listTables
callslistSchemaNames
beforelistTables
, so this single metadata call was being recorded as bothlistSchemaNames
andlistTables
(zero or more times).Extracted from #18586