[SMALL] Split TemporalTranslations into per-type suites #35371
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
roji
changed the title
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 is a simple refactor-only change that splits TemporalTranslations into different test suites.
There seem to be enough tests for each type (DateTime, DateTimeOffset...) to justify different suites... But more importantly, for some providers there are multiple mapping options: DateTime can be mapped to
timestamp with time zoneortimestamp without time zoneon PostgreSQL,datetimeordatetime2on SQL Server, etc. This allows easily extending DateTimeTranslationsTestBase twice, once with each mapping strategy.Continues #34872