fix: correct unit tests in hyper-optimised-telemetry exercise #1796
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 PR fixes two unit tests on the hyper-optimised-telemetry exercise that wrongly assume
0
andInt16.MaxValue
(32767) should be encoded into signed shorts, rather than unsigned shorts as specified in the exercise instructions.Directly targets issue #1795 and #1621 (The latter having been closed, though it reports the same problem)
This PR is incompatible with PR #1756, as the author of that PR aims to change the instructions to be in line with how the unit tests have been set up, while this PR aims to do the exact inverse by changing the unit tests to match the instructions instead.