Add end-to-end tests for timestamp insertion, and patch the conversion issue #1201
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.
Summary
This PR introduces an
e2etests/
directory with "end to end" tests:This can catch issues that a unit test against the engine itself cannot.
There is only a single test thus far, and it is fairly verbose. I know that there is at least one more issue with timestamps, and I will open a follow-up PR to address that issue as soon as I track down its source. For now I'm opting for clarity rather than code reusability.
Lastly, this PR introduces a little patch to the timestamp conversion logic, which was accidentally broken in #1061 because it only handles
string
but the server layer now passes it[]byte
. This patch is very dumb and simple: just convert[]byte
tostring
before parsing.Motivation
#1139