This repository has been archived by the owner on Jan 24, 2021. It is now read-only.
Altered datetime serialisation tests to cope with offsets better #2385
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.
With the Easter 2016 clocks going forward the serialisation tests for
DateTime
failed.The serialiser converts
Unspecified
dates to Local and then formats using theToString("o")
formatter.This will append the timezone differences if a date is Local.
This PR uses the recommended
TimeZoneInfo.Local.GetUtcOffset(myDate);
to find the timezone offset. We then use this in the tests to assert the value the serialiser'sToString("o")
formatter returns with the datetime passed into the SUT.